linux-kernel - Re: linux-next: runtime warning in next-20220125

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] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 25 Jan 2022 10:46:48 -0500
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Chuck Lever III <chuck.lever@...cle.com>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Anna Schumaker <Anna.Schumaker@...app.com>,
        Trond Myklebust <trondmy@...il.com>,
        Linux NFS Mailing List <linux-nfs@...r.kernel.org>
Subject: Re: linux-next: runtime warning in next-20220125

On Tue, 25 Jan 2022 15:38:22 +0000
Chuck Lever III <chuck.lever@...cle.com> wrote:

> > This should fix it:
> > 
> > I'll make it a real patch and start running it through my tests.  
> 
> Should this be squashed into the patch that adds __get_sockaddr() ?
> 
> I have an updated version of that patch that applies on kernels
> that have __rel_dynamic_array.

Heh, I thought the patch was already in mainline. I just posted the fix.

Just add it to your queue. No need to squash it.

You can remove the Fixes: tag, as it may not reference the right commit.

-- Steve