From: Christian Brauner <brauner@kernel.org>
To: Zhihao Cheng <chengzhihao1@huawei.com>,
viro@zeniv.linux.org.uk, jlayton@kernel.org,
josef@toxicpanda.com
Cc: Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
yangerkun@huawei.com, yi.zhang@huawei.com,
changdiankang@huawei.com
Subject: Re: [PATCH v2] nsfs: fix wrong error code returned for pidns ioctls
Date: Mon, 11 May 2026 16:00:45 +0200 [thread overview]
Message-ID: <20260511-krass-takten-d4ff45841341@brauner> (raw)
In-Reply-To: <20260507112301.1042757-1-chengzhihao1@huawei.com>
On Thu, 07 May 2026 19:23:01 +0800, Zhihao Cheng wrote:
> When executing NS_GET_PID_FROM_PIDNS (or similar pidns ioctls), if the
> target task cannot be found in the corresponding pid_ns, the error code
> should be ESRCH instead of ENOTTY.
>
> This bug was introduced when the extensible ioctl handling was added.
> Without proper return, ret would be overwritten by the default case in
> the extensible ioctl switch statement.
>
> [...]
Applied to the vfs.fixes branch of the vfs/vfs.git tree.
Patches in the vfs.fixes branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.fixes
[1/1] nsfs: fix wrong error code returned for pidns ioctls
https://git.kernel.org/vfs/vfs/c/725ecd80688b
prev parent reply other threads:[~2026-05-11 14:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 11:23 [PATCH v2] nsfs: fix wrong error code returned for pidns ioctls Zhihao Cheng
2026-05-07 11:29 ` yangerkun
2026-05-11 14:00 ` Christian Brauner [this message]
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=20260511-krass-takten-d4ff45841341@brauner \
--to=brauner@kernel.org \
--cc=changdiankang@huawei.com \
--cc=chengzhihao1@huawei.com \
--cc=jlayton@kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
/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