From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, willy@infradead.org, rppt@kernel.org,
axelrasmussen@google.com, akpm@linux-foundation.org
Subject: [folded-merged] mm-secretmem-fix-panic-when-growing-a-memfd_secret-v2.patch removed from -mm tree
Date: Thu, 14 Apr 2022 18:57:35 -0700 [thread overview]
Message-ID: <20220415015736.9B6ABC385A7@smtp.kernel.org> (raw)
The patch titled
Subject: mm-secretmem-fix-panic-when-growing-a-memfd_secret-v2
has been removed from the -mm tree. Its filename was
mm-secretmem-fix-panic-when-growing-a-memfd_secret-v2.patch
This patch was dropped because it was folded into mm-secretmem-fix-panic-when-growing-a-memfd_secret.patch
------------------------------------------------------
From: Axel Rasmussen <axelrasmussen@google.com>
Subject: mm-secretmem-fix-panic-when-growing-a-memfd_secret-v2
return EINVAL
Link: https://lkml.kernel.org/r/20220412193023.279320-1-axelrasmussen@google.com
Signed-off-by: Axel Rasmussen <axelrasmussen@google.com>
Cc: Matthew Wilcox <willy@infradead.org>
Cc: Mike Rapoport <rppt@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/secretmem.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/mm/secretmem.c~mm-secretmem-fix-panic-when-growing-a-memfd_secret-v2
+++ a/mm/secretmem.c
@@ -165,7 +165,7 @@ static int secretmem_setattr(struct user
unsigned int ia_valid = iattr->ia_valid;
if ((ia_valid & ATTR_SIZE) && inode->i_size)
- return -EOPNOTSUPP;
+ return -EINVAL;
return simple_setattr(mnt_userns, dentry, iattr);
}
_
Patches currently in -mm which might be from axelrasmussen@google.com are
mm-secretmem-fix-panic-when-growing-a-memfd_secret.patch
reply other threads:[~2022-04-15 1:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220415015736.9B6ABC385A7@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=rppt@kernel.org \
--cc=willy@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.