From: Sasha Levin <sashal@kernel.org>
To: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Cc: Joakim Sindholt <opensource@zhasha.com>,
Eric Van Hensbergen <ericvh@kernel.org>,
Sasha Levin <sashal@kernel.org>,
lucho@ionkov.net, asmadeus@codewreck.org, v9fs@lists.linux.dev
Subject: [PATCH AUTOSEL 4.19 2/7] fs/9p: translate O_TRUNC into OTRUNC
Date: Tue, 23 Apr 2024 07:03:12 -0400 [thread overview]
Message-ID: <20240423110318.1659628-2-sashal@kernel.org> (raw)
In-Reply-To: <20240423110318.1659628-1-sashal@kernel.org>
From: Joakim Sindholt <opensource@zhasha.com>
[ Upstream commit 87de39e70503e04ddb58965520b15eb9efa7eef3 ]
This one hits both 9P2000 and .u as it appears v9fs has never translated
the O_TRUNC flag.
Signed-off-by: Joakim Sindholt <opensource@zhasha.com>
Signed-off-by: Eric Van Hensbergen <ericvh@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
---
fs/9p/vfs_inode.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/fs/9p/vfs_inode.c b/fs/9p/vfs_inode.c
index d1a0f36dcdd43..ea32af83729d9 100644
--- a/fs/9p/vfs_inode.c
+++ b/fs/9p/vfs_inode.c
@@ -192,6 +192,9 @@ int v9fs_uflags2omode(int uflags, int extended)
break;
}
+ if (uflags & O_TRUNC)
+ ret |= P9_OTRUNC;
+
if (extended) {
if (uflags & O_EXCL)
ret |= P9_OEXCL;
--
2.43.0
next prev parent reply other threads:[~2024-04-23 11:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 11:03 [PATCH AUTOSEL 4.19 1/7] fs/9p: only translate RWX permissions for plain 9P2000 Sasha Levin
2024-04-23 11:03 ` Sasha Levin [this message]
2024-04-23 11:03 ` [PATCH AUTOSEL 4.19 3/7] 9p: explicitly deny setlease attempts Sasha Levin
2024-04-23 11:03 ` [PATCH AUTOSEL 4.19 4/7] gpio: wcove: Use -ENOTSUPP consistently Sasha Levin
2024-04-23 11:03 ` [PATCH AUTOSEL 4.19 5/7] gpio: crystalcove: " Sasha Levin
2024-04-23 11:03 ` [PATCH AUTOSEL 4.19 6/7] fs/9p: drop inodes immediately on non-.L too Sasha Levin
2024-04-23 11:03 ` [PATCH AUTOSEL 4.19 7/7] net:usb:qmi_wwan: support Rolling modules Sasha Levin
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=20240423110318.1659628-2-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=asmadeus@codewreck.org \
--cc=ericvh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=opensource@zhasha.com \
--cc=stable@vger.kernel.org \
--cc=v9fs@lists.linux.dev \
/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