lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <X7O9jdlTgs7IbSGT@kroah.com>
Date:   Tue, 17 Nov 2020 13:09:49 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Yunsheng Lin <linyunsheng@...wei.com>
Cc:     stable@...r.kernel.org, vpai@...mai.com,
        Joakim.Tjernlund@...inera.com, xiyou.wangcong@...il.com,
        johunt@...mai.com, jhs@...atatu.com, jiri@...nulli.us,
        davem@...emloft.net, kuba@...nel.org, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org, linuxarm@...wei.com,
        john.fastabend@...il.com, eric.dumazet@...il.com, dsahern@...il.com
Subject: Re: [PATCH stable] net: sch_generic: fix the missing new qdisc
 assignment bug

On Tue, Nov 10, 2020 at 08:58:17AM +0800, Yunsheng Lin wrote:
> On 2020/11/9 20:46, Greg KH wrote:
> > On Tue, Nov 03, 2020 at 11:25:38AM +0800, Yunsheng Lin wrote:
> >> commit 2fb541c862c9 ("net: sch_generic: aviod concurrent reset and enqueue op for lockless qdisc")
> >>
> >> When the above upstream commit is backported to stable kernel,
> >> one assignment is missing, which causes two problems reported
> >> by Joakim and Vishwanath, see [1] and [2].
> >>
> >> So add the assignment back to fix it.
> >>
> >> 1. https://www.spinics.net/lists/netdev/msg693916.html
> >> 2. https://www.spinics.net/lists/netdev/msg695131.html
> >>
> >> Fixes: 749cc0b0c7f3 ("net: sch_generic: aviod concurrent reset and enqueue op for lockless qdisc")
> >> Signed-off-by: Yunsheng Lin <linyunsheng@...wei.com>
> >> ---
> >>  net/sched/sch_generic.c | 3 +++
> >>  1 file changed, 3 insertions(+)
> > 
> > What kernel tree(s) does this need to be backported to?
> 
> 4.19.x and 5.4.x

Now queued up, thanks.

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ