From: Yalagada Pavan Kumar <pavankumaryalagada@gmail.com>
To: Keith Busch <kbusch@kernel.org>
Cc: hch@lst.de, sagi@grimberg.me, kch@nvidia.com,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
skhan@linuxfoundation.org,
syzbot+6c46a179b56c651c4c96@syzkaller.appspotmail.com
Subject: Re: [PATCH] nvmet: validate device_path before enabling namespace
Date: Wed, 9 Sep 2026 13:41:57 +0530 [thread overview]
Message-ID: <aqEUzUyPPkwFcT73@user> (raw)
In-Reply-To: <aqBonYN7WeEn26JZ@kbusch-mbp>
On Tue, Sep 08, 2026 at 01:57:17PM -0600, Keith Busch wrote:
> On Wed, Sep 09, 2026 at 01:04:52AM +0530, pavankumaryalagada@gmail.com wrote:
> > From: Yalagada Pavan Kumar <pavankumaryalagada@gmail.com>
> >
> > When buffered_io is enabled, nvmet_bdev_ns_enable() returns -ENOTBLK
> > without checking whether device_path is configured. nvmet_ns_enable()
> > then falls back to nvmet_file_ns_enable(), which passes the NULL
> > device_path to filp_open() and causes a NULL pointer dereference.
> >
> > Validate device_path before attempting to enable to namespace and
> > return -EINVAL when it has not been configured.
>
> This was alraedy closed:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=09d0c07bd9ce3b2f2d993f672698d32a17543c32
Good to hear this has already been fixed. I'll drop the patch.
Thanks
Pavan
prev parent reply other threads:[~2026-09-09 8:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 19:34 [PATCH] nvmet: validate device_path before enabling namespace pavankumaryalagada
2026-09-08 19:57 ` Keith Busch
2026-09-09 8:11 ` Yalagada Pavan Kumar [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=aqEUzUyPPkwFcT73@user \
--to=pavankumaryalagada@gmail.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=skhan@linuxfoundation.org \
--cc=syzbot+6c46a179b56c651c4c96@syzkaller.appspotmail.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 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.