linux-kernel - Re: [PATCH AUTOSEL for 4.15 168/189] nfsd: return RESOURCE not GARBAGE

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]

Message-ID: <20180415143737.GN2341@sasha-vm>
Date:   Sun, 15 Apr 2018 14:37:39 +0000
From:   Sasha Levin <Alexander.Levin@...rosoft.com>
To:     "J. Bruce Fields" <bfields@...hat.com>
CC:     "stable@...r.kernel.org" <stable@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH AUTOSEL for 4.15 168/189] nfsd: return RESOURCE not
 GARBAGE_ARGS on too many ops

On Mon, Apr 09, 2018 at 11:27:47AM -0400, J. Bruce Fields wrote:
>What's your default on these patches on these AUTOSEL patches if you
>don't get an ACK or NACK?  Do you apply them anyway?

Right now it's opt-out, so it'll get merged unless you NACK it.

In general, these patches get higher visibility as a notice will be sent
a few times for each of these, when:

1. I added it to my queue
2. When Greg sends his review cycle
3. Once a stable kernel is released

>(I'd skip this one as it doesn't meet the "It must fix a real bug that
>bothers people" criterion.  But I don't recall it *causing* any bugs
>either, so the stakes are low, I'm mainly just curious.)

I'll drop it, thanks!