linux-kernel - Re: [PATCH] mm/secretmem: fix panic when growing a memfd

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: <YjzjiDFBgigPqEO9@casper.infradead.org>
Date:   Thu, 24 Mar 2022 21:32:56 +0000
From:   Matthew Wilcox <willy@...radead.org>
To:     Axel Rasmussen <axelrasmussen@...gle.com>
Cc:     Andrew Morton <akpm@...ux-foundation.org>,
        Mike Rapoport <rppt@...nel.org>, linux-mm@...ck.org,
        linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH] mm/secretmem: fix panic when growing a memfd_secret

On Thu, Mar 24, 2022 at 02:09:09PM -0700, Axel Rasmussen wrote:
> This patch avoids the panic by implementing a custom setattr for
> memfd_secret, which detects resizes specifically (setting the size for
> the first time works just fine, since there are no existing pages to try
> to zero), and rejects them as not supported (ENOTSUP).

Isn't ENOTTY the normal return value for this?  Or even ENOSYS?