4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Israel Rukshin
[ Upstream commit 43b92fd27aaef0f529c9321cfebbaec1d7b8f503 ]
A NULL deref happens when nvmet_rdma_remove_one() is called more than once
(e.g. while connected via 2 ports).
The
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Steve Grubb
[ Upstream commit 33e8a907804428109ce1d12301c3365d619cc4df ]
The API to end auditing has historically been for auditd to set the
pid to 0. This patch restores that functionality.
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Keefe Liu
[ Upstream commit ca29fd7cce5a6444d57fb86517589a1a31c759e1 ]
When process the outbound packet of ipv6, we should assign the master
device to output device other than input device.
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Bart Van Assche
[ Upstream commit aba7afc5671c23beade64d10caf86e24a9105dab ]
Avoid that removal of a request queue sporadically triggers the
following warning:
list_del corruption. next->pre
On Fri 15-12-17 12:51:25, Kirill A. Shutemov wrote:
> On Fri, Dec 15, 2017 at 10:28:59AM +0100, Michal Hocko wrote:
> > On Thu 14-12-17 18:35:58, Kirill A. Shutemov wrote:
> > > On Wed, Dec 13, 2017 at 03:39:48PM +0100, Michal Hocko wrote:
> > [...]
> > > > + err = 0;
> > > > + if (page
On Wed, Dec 13, 2017 at 4:56 AM, Stephen Rothwell wrote:
> Hi Tejun,
>
> After merging the cgroup tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> kernel/cgroup/cgroup.c: In function 'init_cgroup_root':
> kernel/cgroup/cgroup.c:1867:3: warning: ignoring return v
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Masahiro Yamada
[ Upstream commit 433dc2ebe7d17dd21cba7ad5c362d37323592236 ]
Some $(call cc-option,...) are invoked very early, even before
KBUILD_CFLAGS, etc. are initialized.
The returned
2017-12-15 17:51 GMT+08:00 David Hildenbrand :
>
>> int main()
>> {
>> int fd = open("/dev/kvm", 0x80102ul);
>> int vm = ioctl(fd, KVM_CREATE_VM, 0);
>> int cpu = ioctl(vm, KVM_CREATE_VCPU, 4);
>
> Not even a memory region :) So maybe the first memory access directly
> triggers a fault?
>
>>
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Daniel Scheller
commit 62229de19ff2b7f3e0ebf4d48ad99061127d0281 upstream.
Follow-up to: ead666000a5f ("media: dvb_frontend: only use kref after
initialized")
The aforementioned commit fixed
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Mauro Carvalho Chehab
commit b1cb7372fa822af6c06c8045963571d13ad6348b upstream.
dvb_frontend_invoke_release() may free the frontend struct.
So, the free logic can't update it anymore after cal
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Reinette Chatre
[ Upstream commit 36b6f9fcb8928c06b6638a4cf91bc9d69bb49aa2 ]
Lockdep warns about a potential deadlock:
[ 66.782842] ==
[
On Thu, Dec 14, 2017 at 05:28:52PM -0800, Nitin Gupta wrote:
> Currently, if the THP enabled policy is "always", or the mode
> is "madvise" and a region is marked as MADV_HUGEPAGE, a hugepage
> is allocated on a page fault if the pud or pmd is empty. This
> yields the best VA translation performan
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Heinz Mauelshagen
[ Upstream commit 233978449074ca7e45d9c959f9ec612d1b852893 ]
Requesting a sync on an active raid device via a table reload
(see 'sync' parameter in Documentation/device-mapp
On Fri, Dec 15, 2017 at 10:43:58AM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.106 release.
> There are 105 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 kno
On Thu, Dec 14, 2017 at 05:28:52PM -0800, Nitin Gupta wrote:
> diff --git a/mm/madvise.c b/mm/madvise.c
> index 751e97a..b2ec07b 100644
> --- a/mm/madvise.c
> +++ b/mm/madvise.c
> @@ -508,6 +508,7 @@ static long madvise_dontneed_single_vma(struct
> vm_area_struct *vma,
>
This is the start of the stable review cycle for the 4.14.7 release.
There are 52 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 Sun Dec 17 09:22:47 UTC 2017.
Anything receive
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Al Viro
commit a5739435b5a3b8c449f8844ecd71a3b1e89f0a33 upstream.
1) it's fput() or sock_release(), not both
2) don't do fd_install() until the last failure exit.
3) not a bug per se, but... d
On Fri, Dec 15, 2017 at 10:58 AM, Wanpeng Li wrote:
> 2017-12-15 17:51 GMT+08:00 David Hildenbrand :
>>
>>> int main()
>>> {
>>> int fd = open("/dev/kvm", 0x80102ul);
>>> int vm = ioctl(fd, KVM_CREATE_VM, 0);
>>> int cpu = ioctl(vm, KVM_CREATE_VCPU, 4);
>>
>> Not even a memory region :) So
On 2017/12/15 14:25, Yunlong Song wrote:
Signed-off-by: Yunlong Song
---
fsck/fsck.c | 19 ---
1 file changed, 16 insertions(+), 3 deletions(-)
diff --git a/fsck/fsck.c b/fsck/fsck.c
index 2212aa3..8ff4e4b 100644
--- a/fsck/fsck.c
+++ b/fsck/fsck.c
@@ -643,7 +643,7 @@ void
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Wei Xu
[ Upstream commit 6e474083f3daf3a3546737f5d7d502ad12eb257c ]
Matthew found a roughly 40% tcp throughput regression with commit
c67df11f(vhost_net: try batch dequing from skb array) as
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Jakub Kicinski
[ Upstream commit 25415cec502a1232b19fffc85465882b19a90415 ]
When cls_bpf offload was added it seemed like a good idea to
call cls_bpf_delete_prog() instead of extending the er
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Willem de Bruijn
[ Upstream commit 0c19f846d582af919db66a5914a0189f9f92c936 ]
Tuntap and similar devices can inject GSO packets. Accept type
VIRTIO_NET_HDR_GSO_UDP, even though not generating
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Jon Maloy
[ Upstream commit a7d5f107b4978e08eeab599ee7449af34d034053 ]
When the function tipc_accept_from_sock() fails to create an instance of
struct tipc_subscriber it omits to free the alr
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Julian Wiedmann
[ Upstream commit 83cf79a2fec3cf499eb6cb9eb608656fc2a82776 ]
When the allocation of the addr buffer fails, we need to free
our refcount on the inetdevice before returning.
Si
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Masamitsu Yamazaki
commit 4f7f5551a760eb0124267be65763008169db7087 upstream.
System may crash after unloading ipmi_si.ko module
because a timer may remain and fire after the module cleaned up
On Fri, Dec 15, 2017 at 10:27:02AM +0800, Jia He wrote:
[...]
> >diff --git a/virt/kvm/arm/arch_timer.c b/virt/kvm/arm/arch_timer.c
> >index 73d262c4712b..544ed15fbbb3 100644
> >--- a/virt/kvm/arm/arch_timer.c
> >+++ b/virt/kvm/arm/arch_timer.c
> >@@ -46,7 +46,7 @@ static const struct kvm_irq_lev
On Thu 14-12-17 12:42:46, Andrew Morton wrote:
> On Thu, 14 Dec 2017 16:17:18 +0100 Michal Hocko wrote:
>
> > > as fast as possible, SRCU instead of reference count is used to
> > > implement get/put_swap_device(). From get_swap_device() to
> > > put_swap_device(), the reader side of SRCU is loc
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Xin Long
[ Upstream commit a8dd397903a6e57157f6265911f7d35681364427 ]
Commit d04adf1b3551 ("sctp: reset owner sk for data chunks on out queues
when migrating a sock") made a mistake that usin
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Wei Xu
[ Upstream commit c33ee15b3820a03cf8229ba9415084197b827f8c ]
tun_recvmsg() supports accepting skb by msg_control after
commit ac77cfd4258f ("tun: support receiving skb through msg_cont
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Neal Cardwell
[ Upstream commit ed66dfaf236c04d414de1d218441296e57fb2bd2 ]
Fix the TLP scheduling logic so that when scheduling a TLP probe, we
ensure that the estimated time at which an RTO
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 8632385022f2b05a6ca0b9e0f95575865de0e2ce ]
When I switched rcv_rtt_est to high resolution timestamps, I forgot
that tp->tcp_mstamp needed to be refreshed in tcp
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: David Ahern
[ Upstream commit 98d11291d189cb5adf49694d0ad1b971c0212697 ]
Florian reported a breakage with anycast routes due to commit
4832c30d5458 ("net: ipv6: put host and anycast routes on
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Wei Xu
[ Upstream commit 61d78537843e676e7f56ac6db333db0c0529b892 ]
tap_recvmsg() supports accepting skb by msg_control after
commit 3b4ba04acca8 ("tap: support receiving skb from msg_control
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Tommi Rantala
[ Upstream commit c7799c067c2ae33e348508c8afec354f3257ff25 ]
Remove the second tipc_rcv() call in tipc_udp_recv(). We have just
checked that the bearer is not up, and calling ti
On 2017/12/15 14:26, Yunlong Song wrote:
Signed-off-by: Yunlong Song
---
fsck/fsck.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/fsck/fsck.c b/fsck/fsck.c
index 11b8b0b..2212aa3 100644
--- a/fsck/fsck.c
+++ b/fsck/fsck.c
@@ -14,6 +14,15 @@
char *tree_ma
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: David Ahern
[ Usptream commit b4d1605a8ea608fd7dc45b926a05d75d340bde4b ]
After this fix : ("tcp: add tcp_v4_fill_cb()/tcp_v4_restore_cb()"),
socket lookups happen while skb->cb[] has not been
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Sunil Goutham
[ Upstream commit fa6d7cb5d76cf0467c61420fc9238045aedfd379 ]
Don't offload IP header checksum to NIC.
This fixes a previous patch which enabled checksum offloading
for both IPv
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Julian Wiedmann
[ Upstream commit 6d69b1f1eb7a2edf8a3547f361c61f2538e054bb ]
Using GSO with small MTUs currently results in a substantial throughput
regression - which is caused by how qeth n
2017-12-15 18:18 GMT+09:00 Ulf Hansson :
> On 24 November 2017 at 17:24, Masahiro Yamada
> wrote:
>>
>> I am working on this IP for Socionext SoCs.
>>
>> I was hit by several issues, and noticed various
>> clean-up candidates.
>>
>> - Fix and clean-up Kconfig
>> - Fix various card detection prob
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Lars Persson
[ Upstream commit 45ab4b13e46325d00f4acdb365d406e941a15f81 ]
The mss variable tracks the last max segment size sent to the TSO
engine. We do not update the hardware as long as we
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 15fe076edea787807a7cdc168df832544b58eba6 ]
syzbot reported crashes [1] and provided a C repro easing bug hunting.
When/if packet_do_bind() calls __unregister_p
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit eeea10b83a139451130df1594f26710c8fa390c8 ]
James Morris reported kernel stack corruption bug [1] while
running the SELinux testsuite, and bisected to a recent
c
On Fri, Dec 15, 2017 at 02:55:03PM +0800, Sean Wang wrote:
> Hi Sergei,
>
> Recently I found the patch commit bafbdd527d56 (phylib: Add device reset
> GPIO support) would have the impact on MT7530 driver. Which causes the
> DSA MT7530 device (it's the child node under mdio bus) gets the
> reset-gp
On Fri, Dec 15, 2017 at 09:09:05AM +, Marc Zyngier wrote:
> On 15/12/17 02:27, Jia He wrote:
> >
> >
>
> [...]
>
> >> @@ -367,6 +368,7 @@ static void vtimer_save_state(struct kvm_vcpu *vcpu)
> >>
> >>/* Disable the virtual timer */
> >>write_sysreg_el0(0, cntv_ctl);
> >> + isb()
On Fri, 2017-12-15 at 01:58 +0100, Rafael J. Wysocki wrote:
> On Thu, Dec 14, 2017 at 3:16 PM, Andy Shevchenko
> wrote:
> > On Thu, 2017-12-07 at 11:03 +0200, Adrian Hunter wrote:
> > >
> > >
> > > +static const struct x86_cpu_id cht_cpu[] = {
> > > + ICPU(INTEL_FAM6_ATOM_AIRMONT), /* Bras
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Mike Maloney
syzkaller found a race condition fanout_demux_rollover() while removing
a packet socket from a fanout group.
po->rollover is read and operated on during packet_rcv_fanout(), via
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mike Maloney
syzkaller found a race condition fanout_demux_rollover() while removing
a packet socket from a fanout group.
po->rollover is read and operated on during packet_rcv_fanout(), via
f
On Fri, Dec 15, 2017 at 08:53:30AM +, Teng Qin wrote:
> To have access to related task_struct is one of the main purposes of these
> patches. Take sched_switch as an example. We depend on the implementation
> of the Tracepoint is called from prev or next (which could, although
> unlikedly,
> c
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Jon Maloy
[ Upstream commit a7d5f107b4978e08eeab599ee7449af34d034053 ]
When the function tipc_accept_from_sock() fails to create an instance of
struct tipc_subscriber it omits to free the alre
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Leon Romanovsky
[ Upstream commit 7d7d065a5eec7e218174d5c64a9f53f99ffdb119 ]
Chelsio cxgb4 HW is big-endian, hence there is need to properly
annotate r2 and stag fields as __be32 and not __u32
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Masahiro Yamada
[ Upstream commit 433dc2ebe7d17dd21cba7ad5c362d37323592236 ]
Some $(call cc-option,...) are invoked very early, even before
KBUILD_CFLAGS, etc. are initialized.
The returned s
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Paul Mackerras
commit b492f7e4e07a28e706db26cf4943bb0911435426 upstream.
These functions compute an IP checksum by computing a 64-bit sum and
folding it to 32 bits (the "nofold" in their names
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Paul Moore
[ Upstream commit 173743dd99a49c956b124a74c8aacb0384739a4c ]
Prior to this patch we enabled audit in audit_init(), which is too
late for PID 1 as the standard initcalls are run afte
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Keefe Liu
[ Upstream commit ca29fd7cce5a6444d57fb86517589a1a31c759e1 ]
When process the outbound packet of ipv6, we should assign the master
device to output device other than input device.
S
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Marc Zyngier
commit 64afe6e9eb4841f35317da4393de21a047a883b3 upstream.
The current pending table parsing code assumes that we keep the
previous read of the pending bits, but keep that variable
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Al Viro
commit a5739435b5a3b8c449f8844ecd71a3b1e89f0a33 upstream.
1) it's fput() or sock_release(), not both
2) don't do fd_install() until the last failure exit.
3) not a bug per se, but... do
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Vincent Pelletier
commit 30bf90ccdec1da9c8198b161ecbff39ce4e5a9ba upstream.
Found using DEBUG_ATOMIC_SLEEP while submitting an AIO read operation:
[ 100.853642] BUG: sleeping function called
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Tommi Rantala
[ Upstream commit c7799c067c2ae33e348508c8afec354f3257ff25 ]
Remove the second tipc_rcv() call in tipc_udp_recv(). We have just
checked that the bearer is not up, and calling tip
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Heiko Carstens
commit fbbd7f1a51965b50dd12924841da0d478f3da71b upstream.
The switch_to() macro has an optimization to avoid saving and
restoring register contents that aren't needed for kernel
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Debabrata Banerjee
[This fix is only needed for v4.9 stable since v4.10+ does not have the issue]
A verdict of NF_STOLEN after NF_QUEUE will cause an incorrect return value
and a potential kern
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Masamitsu Yamazaki
commit 4f7f5551a760eb0124267be65763008169db7087 upstream.
System may crash after unloading ipmi_si.ko module
because a timer may remain and fire after the module cleaned up r
Code-wise, that looks good to me now. I also don't have ARM handy to
validate though - but it looks correct.
Reviewed-by: Darren Kenny
Thanks,
Darren.
On Thu, Dec 14, 2017 at 05:40:50PM -0800, Wanpeng Li wrote:
From: Wanpeng Li
Reported by syzkaller:
BUG: KASAN: stack-out-of-bounds in wr
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Julian Wiedmann
[ Upstream commit 6d69b1f1eb7a2edf8a3547f361c61f2538e054bb ]
Using GSO with small MTUs currently results in a substantial throughput
regression - which is caused by how qeth ne
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Lars Persson
[ Upstream commit 45ab4b13e46325d00f4acdb365d406e941a15f81 ]
The mss variable tracks the last max segment size sent to the TSO
engine. We do not update the hardware as long as we
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Ming Lei
[ Upstream commit 34d9715ac1edd50285168dd8d80c972739a4f6a4 ]
Once blk_set_queue_dying() is done in blk_cleanup_queue(), we call
blk_freeze_queue() and wait for q->q_usage_counter beco
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
[ Upstream commit d803224c84be067754db7fa58a93f36f61566493 ]
On successful rename, the "old_dentry" is retained and is attached to
the "new_dir", so we need to call nfs_set_ver
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Randy Dunlap
[ Upstream commit 1f3c790bd5989fcfec9e53ad8fa09f5b740c958f ]
line-range is supposed to treat "1-" as "1-endoffile", so
handle the special case by setting last_lineno to UINT_MAX.
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Greg Kroah-Hartman
This reverts commit 36e0f05afd4e1d09fd47936761a502aedbc50649 which is
commit 67a9108ed4313b85a9c53406d80dc1ae3f8c3e36 upstream.
Turns there was too many other issues with thi
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Greg Kroah-Hartman
This reverts commit b73adb60852034d84092d123b323196ca42529cd which is
commit c9f2a9a65e4855b74d92cdad688f6ee4a1a323ff upstream.
Turns there was too many other issues with thi
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Greg Kroah-Hartman
This reverts commit 87e2bd898d3a79a8c609f183180adac47879a2a4 which is
commit edc3b9129cecd0f0857112136f5b8b1bc1d45918 upstream.
Turns there was too many other issues with thi
Following error showed up:
drivers/phy/renesas/phy-rcar-gen3-usb2.o: In function
`rcar_gen3_phy_usb2_probe':
/work/tools/linux/drivers/phy/renesas/phy-rcar-gen3-usb2.c:444: undefined
reference to `of_usb_get_dr_mode_by_phy'
Makefile:993: recipe for target 'vmlinux' failed
make: *** [vmlinux] Err
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Stephen Bates
[ Upstream commit 36a3d1dd4e16bcd0d2ddfb4a2ec7092f0ae0d931 ]
If the amount of resources allocated to a gen_pool exceeds 2^32 then the
avail atomic overflows and this causes probl
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Marc Zyngier
commit 5553b142be11e794ebc0805950b2e8313f93d718 upstream.
VTTBR_BADDR_MASK is used to sanity check the size and alignment of the
VTTBR address. It seems to currently be off by one,
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Mike Maloney
syzkaller found a race condition fanout_demux_rollover() while removing
a packet socket from a fanout group.
po->rollover is read and operated on during packet_rcv_fanout(), via
f
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Hangbin Liu
[ Upstream commit f859b4af1c52493ec21173ccc73d0b60029b5b88 ]
After parsing the sit netlink change info, we forget to update frag_off in
ipip6_tunnel_update(). Fix it by assigning f
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Xin Long
[ Upstream commit e39d5246111399dbc6e11cd39fd8580191b86c47 ]
Now when creating fnhe for redirect, it sets fnhe_expires for this
new route cache. But when updating the exist one, it do
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jon Maloy
[ Upstream commit a7d5f107b4978e08eeab599ee7449af34d034053 ]
When the function tipc_accept_from_sock() fails to create an instance of
struct tipc_subscriber it omits to free the alre
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Heiko Carstens
commit fbbd7f1a51965b50dd12924841da0d478f3da71b upstream.
The switch_to() macro has an optimization to avoid saving and
restoring register contents that aren't needed for kernel
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Paul Moore
[ Upstream commit 173743dd99a49c956b124a74c8aacb0384739a4c ]
Prior to this patch we enabled audit in audit_init(), which is too
late for PID 1 as the standard initcalls are run afte
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Keefe Liu
[ Upstream commit ca29fd7cce5a6444d57fb86517589a1a31c759e1 ]
When process the outbound packet of ipv6, we should assign the master
device to output device other than input device.
S
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Mark Bloch
[ Upstream commit 5f22a1d87c5315a98981ecf93cd8de226cffe6ca ]
Maximal message should be used as a limit to the max message payload allowed,
without the headers. The ConnectX-3 check
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jason Baron
[ Upstream commit 92ee46efeb505ead3ab06d3c5ce695637ed5f152 ]
Fengguang Wu reported that running the rcuperf test during boot can cause
the jump_label_test() to hit a WARN_ON(). The
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Herbert Xu
[ Upstream commit 0e74aa1d79a5bbc663e03a2804399cae418a0321 ]
The syzbot found an ancient bug in the IPsec code. When we cloned
a socket policy (for example, for a child TCP socket
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Xin Long
[ Upstream commit cebe84c6190d741045a322f5343f717139993c08 ]
Now when ip route flush cache and it turn out all fnhe_genid != genid.
If a redirect/pmtu icmp packet comes and the old fn
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Kirill A. Shutemov
commit ced108037c2aa542b3ed8b7afd1576064ad1362a upstream.
In case prot_numa, we are under down_read(mmap_sem). It's critical to
not clear pmd intermittently to avoid race wi
On Fri, Dec 15, 2017 at 09:00:41AM +0100, Peter Zijlstra wrote:
> On Thu, Dec 14, 2017 at 09:04:56PM -0800, Dave Hansen wrote:
> >
> > I've got some additions to the selftests and a fix where we pass FOLL_*
> > flags around a bit more instead of just 'write'. I'll get those out as
> > soon as I d
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: David Daney
[ Upstream commit ab42632156becd35d3884ee5c14da2bedbf3149a ]
For powerpc the __jump_table section in modules is not aligned, this
causes a WARN_ON() splat when loading a module con
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Ladislav Michl
[ Upstream commit 7807e086a2d1f69cc1a57958cac04fea79fc2112 ]
gpmc_probe_onenand_child returns success even on gpmc_onenand_init
failure. Fix that.
Signed-off-by: Ladislav Michl
Hi Greg,
On Fri, Dec 15, 2017 at 10:51:37AM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.7 release.
> There are 52 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> le
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Sachin Sant
[ Upstream commit a6d8a21596df041f36f4c2ccc260c459e3e851f1 ]
Tests under alignment subdirectory are skipped when executed on previous
generation hardware, but harness still marks t
Hi,
> -Original Message-
> From: Vladimir Murzin, Sent: Friday, December 15, 2017 7:20 PM
>
> Following error showed up:
>
> drivers/phy/renesas/phy-rcar-gen3-usb2.o: In function
> `rcar_gen3_phy_usb2_probe':
> /work/tools/linux/drivers/phy/renesas/phy-rcar-gen3-usb2.c:444: undefined
>
From: Markus Elfring
Date: Fri, 15 Dec 2017 11:20:33 +0100
Some update suggestions were taken into account
from static source code analysis.
Markus Elfring (7):
Delete an error message for a failed memory allocation in rio_init_mports()
Adjust 12 checks for null pointers
Adjust five functi
On Fri 15-12-17 03:53:23, Yang Shi wrote:
> In the current design, khugepaged need acquire mmap_sem before scanning
> mm, but in some corner case, khugepaged may scan the current running
> process which might be modifying memory mapping, so khugepaged might
> block in uninterruptible state. But, th
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Steffen Klassert
[ Upstream commit e3dc847a5f85b43ee2bfc8eae407a7e383483228 ]
In vti6_xmit(), the check for IPV6_MIN_MTU before we
send a ICMPV6_PKT_TOOBIG message is missing. So we might
repo
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Masahiro Yamada
[ Upstream commit 2dbc644ac62bbcb9ee78e84719953f611be0413d ]
For rpm-pkg and deb-pkg, a source tar file is created. All paths in
the archive must be prefixed with the base nam
From: Markus Elfring
Date: Thu, 14 Dec 2017 15:11:12 +0100
Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/rapidio/rio.c | 1 -
1 file changed, 1 deletion(-)
diff --git
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Alexey Kardashevskiy
[ Upstream commit 7aafac11e308d37ed3c509829bb43d80c1811ac3 ]
The IODA2 specification says that a 64 DMA address cannot use top 4 bits
(3 are reserved and one is a "TVE sel
Hi,
On 15/12/17 10:27, Yoshihiro Shimoda wrote:
> Hi,
>
>> -Original Message-
>> From: Vladimir Murzin, Sent: Friday, December 15, 2017 7:20 PM
>>
>> Following error showed up:
>>
>> drivers/phy/renesas/phy-rcar-gen3-usb2.o: In function
>> `rcar_gen3_phy_usb2_probe':
>> /work/tools/linux
Salil,
On Thu, Dec 14, 2017 at 7:03 PM, Salil Mehta wrote:
> This patch-set contains the support of the HNS3 (Hisilicon Network Subsystem
> 3)
> Virtual Function Ethernet driver for hip08 family of SoCs. The Physical
> Function
> driver is already part of the Linux mainline.
>
> This VF driver
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jim Qu
[ Upstream commit c085bd5119d5d0bdf3ef591a5563566be7dedced ]
Signed-off-by: Jim Qu
Reviewed-by: Alex Deucher
Signed-off-by: Alex Deucher
Signed-off-by: Sasha Levin
Signed-off-by: Gr
201 - 300 of 1178 matches
Mail list logo