On 12/18/2017 02:36 AM, Jan Beulich wrote:
On 15.12.17 at 20:52, wrote:
> +static int pcistub_device_reset(struct pci_dev *dev)
> +{
> + struct xen_pcibk_dev_data *dev_data;
> + bool slot = false, bus = false;
> + struct pcistub_args arg = {};
> +
> + if (!dev)
>>>
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
[ Upstream commit fa23b9d1b89fdc34f296f02e496a20aeff5736be ]
This driver uses the MSI domain but has no strict dependency on PCI_MSI, so we
may run into a build failure when CONF
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Tahsin Erdogan
[ Upstream commit 4a3a485b1ed0e109718cc8c9d094fa0f552de9b2 ]
When WB_registered flag is not set, wb_queue_work() skips queuing the
work, but does not perform the necessary clean
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Tomi Valkeinen
[ Upstream commit 9fa1d7537242bd580ffa99c4725a0407096aad26 ]
omap_gem_dmabuf_mmap() returns an error (with a WARN) when called for a
buffer which is allocated with dma_alloc_*()
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
[ Upstream commit 6e526fdff7be4f13b24f929a04c0e9ae6761291e ]
Make sure to check the number of endpoints to avoid dereferencing a
NULL-pointer or accessing memory beyond the endpoi
On Mon, Dec 18, 2017 at 12:59 PM, Viresh Kumar wrote:
> On 18-12-17, 12:35, Rafael J. Wysocki wrote:
>> Well, if SCHED_CPUFRREQ_CLEAR means "this CPU is going to enter the
>> idle loop" really, then it is better to call it
>> SCHED_CPUFRREQ_ENTER_IDLE, for example.
>>
>> SCHED_CPUFRREQ_CLEAR meani
On Fri, 15 Dec 2017 15:49:09 -0800
Randy Dunlap wrote:
> On 12/15/2017 01:41 PM, Michal Suchanek wrote:
> > Actually args are supposed to be renamed to next so both and args
> > hold the previous argument so both can be passed to the callback.
> > This additionla patch
>
>
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Doug Berger
[ Upstream commit 07c52d6a0b955a8a28834f9354793cfc4b81d0e9 ]
Add a spinlock to ensure that irq0_stat is not unintentionally altered
as the result of preemption. Also removed unser
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Dmitry Torokhov
[ Upstream commit a4c2a13129f7c5bcf81704c06851601593303fd5 ]
TUXEDO BU1406 does not implement active multiplexing mode properly,
and takes around 550 ms in i8042_set_mux_mode()
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Hiroyuki Yokoyama
[ Upstream commit a1c2ff53726907aff5feb37e4cfd45c1ff626431 ]
This patch fixes the problem that the missing value of the route path
setting table and incorrect values are set
Op 18-12-17 om 08:08 schreef Daniel Vetter:
> Hm, the bisect looks funny. Only way I can explain that is that my
> patch fixed a pre-existing lockdep splat, and uncovered the issue in
> the ww-mutex self tests. That one is uncovered by the new
> cross-release lockdep checks in 4.15.
>
> Anyway I th
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Florian Westphal
[ Upstream commit 4ca60d08cbe65f501baad64af50fceba79c19fbb ]
consider a bridge with mtu 9000, but end host sending smaller
packets to another host with mtu < 9000.
In this ca
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: David Kozub
commit 62354454625741f0569c2cbe45b2d192f8fd258e upstream.
There is another JMS567-based USB3 UAS enclosure (152d:0578) that fails
with the following error:
[sda] tag#0 FAILED Resul
This is the start of the stable review cycle for the 4.9.71 release.
There are 177 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Wed Dec 20 15:28:22 UTC 2017.
Anything receiv
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Changbin Du
commit 90e406f96f630c07d631a021fd4af10aac913e77 upstream.
The default NR_CPUS can be very large, but actual possible nr_cpu_ids
usually is very small. For my x86 distribution, the N
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Alan Stern
commit 48a4ff1c7bb5a32d2e396b03132d20d552c0eca7 upstream.
A malicious USB device with crafted descriptors can cause the kernel
to access unallocated memory by setting the bNumInterfa
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: NeilBrown
commit 302ec300ef8a545a7fc7f667e5fd743b091c2eeb upstream.
Commit ecc0c469f277 ("autofs: don't fail mount for transient error") was
meant to replace an 'if' with a 'switch', but instea
On Mon, Dec 18, 2017 at 12:22:20PM -0500, Jeff Layton wrote:
> On Mon, 2017-12-18 at 17:34 +0100, Jan Kara wrote:
> > On Mon 18-12-17 10:11:56, Jeff Layton wrote:
> > > static inline bool
> > > inode_maybe_inc_iversion(struct inode *inode, bool force)
> > > {
> > > - atomic64_t *ivp = (atomic64_
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit ecaaab5649781c5a0effdaf298a925063020500e upstream.
When asked to encrypt or decrypt 0 bytes, both the generic and x86
implementations of Salsa20 crash in blkcipher_walk_done
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Doug Berger
[ Upstream commit 71328a3c321f7c14cc1edd33577717037744 ]
The location of the RBUF overflow and error counters has moved between
different version of the GENET MAC. This commit
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Doug Berger
[ Upstream commit eca4bad73409aedc6ff22f823c18b67a4f08c851 ]
The reserved gphy_rev value of 0x01ff must be tested before the old
or new scheme for GPHY major versioning are tested,
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Michael Chan
[ Upstream commit 520ad89a54edea84496695d528f73ddcf4a52ea4 ]
In some situations, the firmware will return 0 for autoneg supported
speed. This may happen if the firmware detects n
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit af3ff8045bbf3e32f1a448542e73abb4c8ceb6f1 upstream.
Because the HMAC template didn't check that its underlying hash
algorithm is unkeyed, trying to use "hmac(hmac(sha3-512-ge
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Andrea Arcangeli
[ Upstream commit 46aa6a302b53f543f8e8b8e1714dc5e449ad36a6 ]
linux/tools/testing/selftests/vm $ make
gcc -Wall -I ../../../../usr/include compaction_test.c -lrt -o
/co
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Guoqing Jiang
[ Upstream commit 9c8043f337f14d1743006dfc59c03e80a42e3884 ]
To avoid memory leak, we need to free the cinfo which
is allocated when node join cluster.
Reviewed-by: NeilBrown
S
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Chandan Rajendra
commit 9d5afec6b8bd46d6ed821aa1579634437f58ef1f upstream.
On a ppc64 machine, when mounting a fuzzed ext2 image (generated by
fsfuzzer) the following call trace is seen,
VFS:
2017-12-18 16:07 GMT+01:00 Christophe LEROY :
>
>
> Le 18/12/2017 à 11:18, Bartosz Golaszewski a écrit :
>>
>> 2017-12-18 11:08 GMT+01:00 Christophe Leroy :
>>>
>>> The GPIO 'value' attribute is time critical. A small bench with
>>> 'perf record' on the app below shows that 80% of the time spent in
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Adam Wallis
commit 6f6a23a213be51728502b88741ba6a10cda2441d upstream.
Commit adfa543e7314 ("dmatest: don't use set_freezable_with_signal()")
introduced a bug (that is in fact documented by the
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit d2890c3778b164fde587bc16583f3a1c87233ec5 upstream.
In rsa_get_n(), if the buffer contained all 0's and "FIPS mode" is
enabled, we would read one byte past the end of the buf
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Scott Mayhew
commit dc4fd9ab01ab379ae5af522b3efd4187a7c30a31 upstream.
If there were no commit requests, then nfs_commit_inode() should not
wait on the commit or mark the inode dirty, otherwise
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Steven Rostedt
commit f73c52a5bcd1710994e53fbccc378c42b97a06b6 upstream.
Daniel Wagner reported a crash on the BeagleBone Black SoC.
This is a single CPU architecture, and does not have a func
On Sun, Dec 17, 2017 at 11:11 PM, Daniel Vetter wrote:
>
> This didn't seem to have made it into -rc4. Anything needed to get it
> going?
Do you actually see the problem in -rc4?
Because we ended up removing the cross-release checking due to other
developers complaining. It seemed to need a lot
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mathias Nyman
commit 5d9b70f7d52eb14bb37861c663bae44de9521c35 upstream.
Avoid null pointer dereference if some function is walking through the
devs array accessing members of a new virt_dev tha
Hi!
(By the way, your mail is HTML and likely will get rejected by many
mailing lists and/or people reading these mailing lists.)
On Mon, Dec 18, 2017 at 12:23:18PM +0800, Cheng-yi Chiang wrote:
>Hi Brian,
> Oder has posted the same fix : [1]https://patchwork.kernel.org/
>patch/10066
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Chunfeng Yun
commit 72b663a99c074a8d073e7ecdae446cfb024ef551 upstream.
For MTK's xHCI 1.0 or latter, TD size is the number of max
packet sized packets remaining in the TD, not including
this TR
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Shuah Khan
commit be6123df1ea8f01ee2f896a16c2b7be3e4557a5a upstream.
stub_send_ret_submit() handles urb with a potential null transfer_buffer,
when it replays a packet with potential malicious
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Felipe Balbi
commit 541b6fe63023f3059cf85d47ff2767a3e42a8e44 upstream.
According to USB Specification 2.0 table 9-4,
wMaxPacketSize is a bitfield. Endpoint's maxpacket
is laid out in bits 10:0.
2017-12-13 12:30 GMT+01:00 Bartosz Golaszewski :
> Add the link to my git tree to the at24 section.
>
> Signed-off-by: Bartosz Golaszewski
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 55af54fa0837..edaf9802a11f 100644
> --- a/MAINT
On Sat, Dec 16, 2017 at 08:36:23AM +0100, Enric Balletbo Serra wrote:
>Guess you missed the discussion in the cover letter of this patchset ;)
>These patches has been accepted and merged soon for 4.16. Alexandre
>will do it.
I wasn't copied on either the patches or the cover letter; I
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jiri Slaby
[ Upstream commit 4dc12ffeaeac939097a3f55c881d3dc3523dff0c ]
l2tp_tunnel_delete does not return anything since commit 62b982eeb458
("l2tp: fix race condition in l2tp_tunnel_delete")
2017-12-13 11:56 GMT+01:00 Bartosz Golaszewski :
> Fix issues reported by checkpatch for at24.c.
>
> Signed-off-by: Bartosz Golaszewski
> ---
> drivers/misc/eeprom/at24.c | 18 +-
> 1 file changed, 9 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/misc/eeprom/at24.c b/drive
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Williamson
[ Upstream commit 16b6c8bb687cc3bec914de09061fcb8411951fda ]
When removing a device, for example a VF being removed due to SR-IOV
teardown, a "soft" hot-unplug via 'echo 1 > re
2017-12-13 11:56 GMT+01:00 Bartosz Golaszewski :
> There are a couple symbols defined in the driver source file which are
> missing the at24_ prefix. This patch fixes that.
>
> For module params: use module_param_named() in order to not break
> userspace.
>
> Signed-off-by: Bartosz Golaszewski
> -
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: "tang.junhui"
[ Upstream commit c157313791a999646901b3e3c6888514ebc36d62 ]
Currently, Cache missed IOs are identified by s->cache_miss, but actually,
there are many situations that missed IOs
2017-12-10 20:29 GMT+01:00 Bartosz Golaszewski :
> A regmap_config struct is pretty big and declaring two of them
> statically just to tweak the reg_bits value adds unnecessary bloat.
>
> Declare the regmap config locally in at24_probe() instead.
>
> Bloat-o-meter output:
>
> add/remove: 0/2 grow/s
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Christoph Hellwig
[ Upstream commit 5e422f5e4fd71d18bc6b851eeb3864477b3d842e ]
There was one spot in xfs_bmap_add_extent_unwritten_real that didn't use the
passed in new extent state but alway
On Mon, 18 Dec 2017 15:13:53 +0100
Petr Mladek wrote:
> One question is if we really want to rely on offloading in
> this case. What if this is printed to debug some stalled
> system.
Correct, and this is what I call when debugging hard lockups, and I do
it from NMI. Which the new NMI code preve
On Sun, Dec 17, 2017 at 10:00:17PM -0800, Joe Perches wrote:
> > Today when we run checkers we get so many warnings it is too hard to
> > make any sense of it.
>
> Here is a list of the checkpatch messages for drivers/infiniband
> sorted by type.
>
> Many of these might be corrected by using
>
On Mon, 2017-12-18 at 10:11 -0500, Jeff Layton wrote:
> From: Jeff Layton
>
> Add a documentation blob that explains what the i_version field is, how
> it is expected to work, and how it is currently implemented by various
> filesystems.
>
> We already have inode_inc_iversion. Add several other
From: Colin Ian King
Function skip_callee is local to the source and does not need to
be in global scope, so make it static. Also return NULL rather than 0.
Cleans up two sparse warnings:
symbol 'skip_callee' was not declared. Should it be static?
Using plain integer as NULL pointer
Signed-off-
On Mon, 2017-12-18 at 12:27 -0500, J. Bruce Fields wrote:
> On Mon, Dec 18, 2017 at 06:17:36PM +0100, Mike Galbraith wrote:
> > On Mon, 2017-12-18 at 18:00 +0100, Mike Galbraith wrote:
> > > On Mon, 2017-12-18 at 11:35 -0500, J. Bruce Fields wrote:
> > > >
> > > > Like I say, I don't really unders
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Liang Chen
[ Upstream commit 330a4db89d39a6b43f36da16824eaa7a7509d34d ]
mutex_destroy does nothing most of time, but it's better to call
it to make the code future proof and it also has some m
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Kara
[ Upstream commit abdc0eb06964fe1d2fea6dd1391b734d0590365d ]
When session starts beyond offset 2^31 the arithmetics in
udf_check_vsd() would overflow. Make sure the computation is don
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Bob Peterson
[ Upstream commit cc555b09d8c3817aeebda43a14ab67049a5653f7 ]
This patch fixes a deadlock caused when the jdata flag is set for
inodes that are already on the ordered write list. S
Ah, finally we¹ve got that NOLOAD flag! This will clear up several nasty
bugs around ptrace and sigkill that come when waiting with signals blocked
in TASK_INTERRUPTIBLE. I see it was added in 2015Š The joys of working
with vendor kernels.
Thanks for these, Neil. I¹ll try to take a careful loo
On Mon, Dec 18, 2017 at 02:05:15PM +0100, Knut Omang wrote:
> https://github.com/torvalds/linux/compare/master...knuto:runchecks
Several of these to rdma/core do not look so big, you should think
about sending them..
Jason
On Mon, 2017-12-18 at 14:19 +, Colin King wrote:
> From: Colin Ian King
Hey Colin.
> Here are some of the more spelling mistakes and typos that I've found
> while fixing up spelling mistakes in kernel error message text since
> October 2017
[]
> diff --git a/scripts/spelling.txt b/scripts/sp
Boris,
Am Montag, 18. Dezember 2017, 16:49:34 CET schrieb Boris Brezillon:
> Historically branches targeting the next release (and pulled in
> linux-next) have been pushed on the l2-mtd repo and fixes branches on
> the linux-mtd one. Now that all MTD maintainers have RW permissions on
> linux-mtd
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
[ Upstream commit 3e351275655d3c84dc28abf170def9786db5176d ]
We could allocate less memory than intended because we do:
bfad->regdata = kzalloc(len << 2, GFP_KERNEL);
T
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: weiping zhang
[ Upstream commit 658e9a6dc1126f21fa417cd213e1cdbff8be0ba2 ]
/sys/class/scsi_disk/0:2:0:0/allow_restart can be changed to 0
unexpectedly by writing an invalid string such as the
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Alexander Duyck
[ Upstream commit dd6b9c2c332b40f142740d1b11fb77c653ff98ea ]
This patch intoduces a slight adjustment for macvlan to address the fact
that in source mode I was seeing two copie
2017-12-16 0:05 GMT+01:00 Heiner Kallweit :
> i2c_new_dummy is typically called from the probe function of the
> driver for the primary i2c client. It requires calls to
> i2c_unregister_device in the error path of the probe function and
> in the remove function.
> This can be simplified by introduc
Change log:
v3->v4:
Addressed comments from Randy. Modified documentation to be clearer,
and fixed small off by one in bounds checking in constructor.
v2->v3:
1) Renamed variables in-code to reflect correct terminology with respect
to the dm-stripe target.
2) Fixed a __must_check missing
This device mapper module remaps and unstripes IO so it lands
solely on a single drive in a RAID 0/dm-stripe target.
In a 4 drive RAID 0 the mapper exposes 1/4th of the LBA range
as a virtual drive. Each IO to that virtual drive will land on
only one of the 4 drives, selected by the user.
Signed-o
Signed-off-by: Scott Bauer
---
Documentation/device-mapper/dm-unstripe.txt | 130
1 file changed, 130 insertions(+)
create mode 100644 Documentation/device-mapper/dm-unstripe.txt
diff --git a/Documentation/device-mapper/dm-unstripe.txt
b/Documentation/device-mapper
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: NeilBrown
[ Upstream commit 235b6003fb28f0dd8e7ed8fbdb088bb548291766 ]
When reshaping a fully degraded raid5/raid6 to a larger
nubmer of devices, the new device(s) are not in-sync
and so that
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: weiping zhang
[ Upstream commit 623401ee33e42cee64d333877892be8db02951eb ]
/sys/class/scsi_disk/0:2:0:0/manage_start_stop can be changed to 0
unexpectly by writing an invalid string.
Signed-o
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jia-Ju Bai
[ Upstream commit 42c8eb3f6e15367981b274cb79ee4657e2c6949d ]
The driver may sleep under a spinlock, and the function call path is:
vt6655_suspend (acquire the spinlock)
pci_set_po
On Mon, 18 Dec 2017 17:23:24 +0100
David Hildenbrand wrote:
> What I need: Start tracing and flush all buffers when exiting. (e.g.
Why don't you use "trace-cmd start" and "trace-cmd extract"?
"trace-cmd record" is all about not losing events. If you are creating
a big buffer, then I think you w
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Bin Liu
commit bd3486ded7a0c313a6575343e6c2b21d14476645 upstream.
When babble condition happens, the musb controller might automatically
turns off VBUS. On DA8xx platform, the controller genera
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Kurt Garloff
[ Upstream commit 909cf3e16a5274fe2127cf3cea5c8dba77b2c412 ]
All EMC SYMMETRIX support REPORT_LUNS, even if configured to report
SCSI-2 for whatever reason.
Signed-off-by: Kurt G
On 18/12/17 17:49, Joe Perches wrote:
> On Mon, 2017-12-18 at 14:19 +, Colin King wrote:
>> From: Colin Ian King
>
> Hey Colin.
>
>> Here are some of the more spelling mistakes and typos that I've found
>> while fixing up spelling mistakes in kernel error message text since
>> October 2017
>
On Mon, 2017-12-18 at 10:46 -0700, Jason Gunthorpe wrote:
> On Sun, Dec 17, 2017 at 10:00:17PM -0800, Joe Perches wrote:
>
> > > Today when we run checkers we get so many warnings it is too hard to
> > > make any sense of it.
> >
> > Here is a list of the checkpatch messages for drivers/infiniban
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Michael Ellerman
[ Upstream commit 05c14c03138532a3cb2aa29c2960445c8753343b ]
In the hv-24x7 code there is a function memord() which tries to
implement a sort function return -1, 0, 1. However
Hi Gustavo,
On Thu, Dec 14, 2017 at 12:38:04PM +, Gustavo Pimentel wrote:
> Ok. I will compile and test it now.
Have you managed to retrieve the patches and test them ?
Thank you,
Lorenzo
> Thanks.
>
>
> On 14/12/2017 12:22, Lorenzo Pieralisi wrote:
> > On Thu, Dec 14, 2017 at 12:16:38PM
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Gao Feng
[ Upstream commit f02b2320b27c16b644691267ee3b5c110846f49e ]
The mutex_destroy only makes sense when enable DEBUG_MUTEX. For the
good readbility, it's better to invoke it in exit func
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Martin Wilck
[ Upstream commit dfb2e6f46b3074eb85203d8f0888b71ec1c2e37a ]
This patch cleans up a lot of warnings when unloading the driver.
A current example of the stack trace starts with:
On Mon, Dec 18, 2017 at 01:29:01PM +0100, Javier Martinez Canillas wrote:
> On 12/18/2017 01:22 PM, Javier Martinez Canillas wrote:
>
> [snip]
>
> >
> > James,
> >
> > Can you please test the following (untested) patch on top of the other two
> > mentioned patches to see if it makes a differenc
On 12/18/2017 06:53 AM, Michal Hocko wrote:
> On Fri 01-12-17 08:23:27, Seth Forshee wrote:
>> On Mon, Sep 25, 2017 at 02:58:25PM +0200, Michal Hocko wrote:
>>> On Thu 21-09-17 00:40:34, Seth Forshee wrote:
> [...]
It seems I don't have that kernel anymore, but I've got a 4.14-rc1 build
a
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Marc Dionne
[ Upstream commit ab94f5d0dd6fd82e7eeca5e7c8096eaea0a0261f ]
The inode timestamps should be set from the client time
in the status received from the server, rather than the
server
On Mon, Dec 18, 2017 at 04:32:25PM +0100, Thomas Richter wrote:
> Commit ad67b74d2469 ("printk: hash addresses printed with %p")
> changed %p to hash pointers in order to avoid leaking
> kernel addresses.
>
> This breaks the tool perf probe.
I also said this likely ends up in a world readable fil
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Martin Wilck
[ Upstream commit 55ca38b4255bb336c2d35990bdb2b368e19b435a ]
I am resubmitting this patch on behalf of Martin Wilck with his
permission.
The original patch can be found here:
htt
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: David Howells
[ Upstream commit 6d06b0d25209c80e99c1e89700f1e09694a3766b ]
afs_write_begin() leaks a ref and a lock on a page if afs_fill_page()
fails. Fix the leak by unlocking and releasing
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Tina Ruchandani
[ Upstream commit 56e714312e7dbd6bb83b2f78d3ec19a404c7649f ]
get_seconds() returns real wall-clock seconds. On 32-bit systems
this value will overflow in year 2038 and beyond.
On 12/18/2017 09:34 AM, Michal Suchánek wrote:
> On Fri, 15 Dec 2017 15:49:09 -0800
> Randy Dunlap wrote:
>
>> On 12/15/2017 01:41 PM, Michal Suchanek wrote:
>>> Actually args are supposed to be renamed to next so both and args
>>> hold the previous argument so both can be passed to the callback.
On Mon, 2017-12-18 at 10:46 -0700, Jason Gunthorpe wrote:
> On Sun, Dec 17, 2017 at 10:00:17PM -0800, Joe Perches wrote:
>
> > > Today when we run checkers we get so many warnings it is too hard to
> > > make any sense of it.
> >
> > Here is a list of the checkpatch messages for drivers/infiniban
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Chen Zhong
[ Upstream commit c955bf3998efa3355790a4d8c82874582f1bc727 ]
Since the previous setup always sets the PLL using crystal 26MHz, this
doesn't always happen in every MediaTek platform.
On Mon, 2017-12-18 at 16:49 +0100, Boris Brezillon wrote:
>
> In the meantime, we should try to keep both l2-mtd and linux-mtd synced
> (that means pushing the xxx/next branches on both l2-mtd and mtd-next).
You could make a symlink which would mean you don't have to (and
mustn't) do that...
smi
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Robert Baronescu
[ Upstream commit 7aacbfcb331ceff3ac43096d563a1f93ed46e35e ]
Fix the way the length of the buffers used for
encryption / decryption are computed.
For e.g. in case of encryptio
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Suzuki K Poulose
[ Upstream commit c7f5828bf77dcbd61d51f4736c1d5aa35663fbb4 ]
When the PMU driver is built as a module, the perf expects the
pmu->module to be valid, so that the driver is prev
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: tangwenji
[ Upstream commit 12d5a43b2dffb6cd28062b4e19024f7982393288 ]
tpg must free when call core_tpg_register() return fail
Signed-off-by: tangwenji
Signed-off-by: Nicholas Bellinger
Sig
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: tangwenji
[ Upstream commit 24528f089d0a444070aa4f715ace537e8d6bf168 ]
When is pr_reg->isid_present_at_reg is false,this function should return.
This fixes a regression originally introduced
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Markus Elfring
[ Upstream commit f6c8a317ab208aee223776327c06f23342492d54 ]
Source code review for a specific software refactoring showed the need
for another correction because the error code
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Bart Van Assche
[ Upstream commit cfe2b621bb18d86e93271febf8c6e37622da2d14 ]
Avoid that cmd->se_cmd.se_tfo is read after a command has already been
freed.
Signed-off-by: Bart Van Assche
Cc:
On Mon, 18 Dec 2017 16:32:25 +0100
Thomas Richter wrote:
> Commit ad67b74d2469 ("printk: hash addresses printed with %p")
> changed %p to hash pointers in order to avoid leaking
> kernel addresses.
>
> This breaks the tool perf probe.
>
> To set a uprobe on a function named inet_pton in libc li
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Christophe Leroy
[ Upstream commit 6b148a7ce72a7f87c81cbcde48af014abc0516a9 ]
IPIC Status is provided by register IPIC_SERSR and not by IPIC_SERMR
which is the mask register.
Signed-off-by: C
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Marc Dionne
[ Upstream commit 627f46943ff90bcc32ddeb675d881c043c6fa2ae ]
Mode bits for an afs file should not be enforced in the usual
way.
For files, the absence of user bits can restrict fi
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: KUWAZAWA Takuya
[ Upstream commit c5504f724c86ee925e7ffb80aa342cfd57959b13 ]
Information about ipvs in different network namespace can be seen via procfs.
How to reproduce:
# ip netns add
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Philipp Zabel
[ Upstream commit a3350f9c57ffad569c40f7320b89da1f3061c5bb ]
The pcf8563_clkout_recalc_rate function erroneously ignores the
frequency index read from the CLKO register and alway
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Qiang
[ Upstream commit 3ad3f8ce50914288731a3018b27ee44ab803e170 ]
PCIe PME and native hotplug share the same interrupt number, so hotplug
interrupts are also processed by PME. In some cases,
701 - 800 of 1686 matches
Mail list logo
