From: Matthew Wilcox <willy@infradead.org>
To: Axel Rasmussen <axelrasmussen@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Mike Rapoport <rppt@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] mm/secretmem: fix panic when growing a memfd_secret
Date: Thu, 24 Mar 2022 21:32:56 +0000 [thread overview]
Message-ID: <YjzjiDFBgigPqEO9@casper.infradead.org> (raw)
In-Reply-To: <20220324210909.1843814-1-axelrasmussen@google.com>
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?
next prev parent reply other threads:[~2022-03-24 21:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 21:09 Axel Rasmussen
2022-03-24 21:32 ` Matthew Wilcox [this message]
2022-03-24 21:44 ` Axel Rasmussen
2022-03-31 17:42 ` Axel Rasmussen
2022-04-07 20:50 ` Andrew Morton
2022-04-11 17:29 ` Axel Rasmussen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YjzjiDFBgigPqEO9@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox