netdev - Re: [PATCH net] sunrpc: fix UDP memory accounting for v4.4 kernel

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: <e9d73f769e19418143f381ac724d93c275aa3ecc.camel@thalesgroup.com>
Date:   Thu, 17 Oct 2019 04:30:28 +0000
From:   JABLONSKY Jan <Jan.JABLONSKY@...lesgroup.com>
To:     Paolo Abeni <pabeni@...hat.com>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>
CC:     Trond Myklebust <trond.myklebust@...marydata.com>,
        Anna Schumaker <anna.schumaker@...app.com>,
        "J. Bruce Fields" <bfields@...ldses.org>,
        "Jeff Layton" <jlayton@...chiereds.net>,
        "David S. Miller" <davem@...emloft.net>,
        "linux-nfs@...r.kernel.org" <linux-nfs@...r.kernel.org>,
        Jan Stancek <jstancek@...hat.com>
Subject: Re: [PATCH net] sunrpc: fix UDP memory accounting for v4.4 kernel

On Tue, 2019-10-15 at 11:19 +0200, Paolo Abeni wrote:
> Hi,
> 
> On Tue, 2019-10-15 at 07:21 +0000, JABLONSKY Jan wrote:
> > The same warnings reported by Jan Stancek may appear also on 4.4
> > Based on Paolo Abeni's work.
> > 
> > WARNING: at net/ipv4/af_inet.c:155
> > CPU: 1 PID: 214 Comm: kworker/1:1H Not tainted 4.4.166 #1
> > Workqueue: rpciod .xprt_autoclose
> > task: c0000000366f57c0 ti: c000000034134000 task.ti:
> > c000000034134000
> > NIP [c000000000662268] .inet_sock_destruct+0x158/0x200
> > 
> > Based on: "[net] sunrpc: fix UDP memory accounting"
> 
> Since your goal here is the inclusion into the 4.4.y stable tree, you
> should follow the instructions listed here:
> 
> https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.ht
> ml
> 

Sure,
but unfortunetaly I noticed a41bd25ae67d (with comment Cc: stable@...r.kernel.org # 4.4+)
and since then I haven't seen any additional effort to bring (backport) this patch also for 4.4.
So I want to make it clear, before sending the patch to the 4.4.y stable tree

Thanks for feedback