From: Qing Wang <wangqing7171@gmail.com>
To: b.sachdev1904@gmail.com
Cc: avagin@gmail.com, brauner@kernel.org, jack@suse.cz,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
ptikhomirov@virtuozzo.com,
syzbot+9e03a9535ea65f687a44@syzkaller.appspotmail.com,
viro@zeniv.linux.org.uk, wangqing7171@gmail.com
Subject: Re: Re: [PATCH] statmount: Fix the null-ptr-deref in do_statmount()
Date: Fri, 13 Feb 2026 18:34:48 +0800 [thread overview]
Message-ID: <20260213103448.2474564-1-wangqing7171@gmail.com> (raw)
In-Reply-To: <DGDQFGJLPLU0.19QNB0MQLITQO@gmail.com>
On Fri, 13 Feb 2026 at 17:38, "Bhavik Sachdev" <b.sachdev1904@gmail.com> wrote:
> Hey!
> I think the fix should be the following instead, AFAIU we don't want a
> call to an internal mount to succeed.
>
> diff --git a/fs/namespace.c b/fs/namespace.c
> index a67cbe42746d..55152bf64785 100644
> --- a/fs/namespace.c
> +++ b/fs/namespace.c
> @@ -5678,6 +5678,8 @@ static int do_statmount(struct kstatmount *s, u64 mnt=
> _id, u64 mnt_ns_id,
>
> s->mnt =3D mnt_file->f_path.mnt;
> ns =3D real_mount(s->mnt)->mnt_ns;
> + if (IS_ERR(ns))
> + return -EINVAL;
> if (!ns)
> /*
> * We can't set mount point and mnt_ns_id since we =
> don't have a
>
> Thanks,
> Bhavik
I had considered returning an error code before but finally decided to
not. Thank you for your suggestion, I agree with it and resend the patch
v3 [0].
[0] https://lore.kernel.org/all/20260213103006.2472569-1-wangqing7171@gmail.com/T/
Look forward to your review.
---
Thanks,
Qing
prev parent reply other threads:[~2026-02-13 10:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 8:42 Qing Wang
2026-02-13 9:38 ` Bhavik Sachdev
2026-02-13 10:34 ` Qing Wang [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=20260213103448.2474564-1-wangqing7171@gmail.com \
--to=wangqing7171@gmail.com \
--cc=avagin@gmail.com \
--cc=b.sachdev1904@gmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ptikhomirov@virtuozzo.com \
--cc=syzbot+9e03a9535ea65f687a44@syzkaller.appspotmail.com \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®