From: Al Viro <viro@zeniv.linux.org.uk>
To: Hawkins Jiawei <yin31149@gmail.com>
Cc: 18801353760@163.com, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH -next 0/5] fs: fix possible null-ptr-deref when parsing param
Date: Sun, 23 Oct 2022 17:48:53 +0100 [thread overview]
Message-ID: <Y1VwdUYGvDE4yUoI@ZenIV> (raw)
In-Reply-To: <20221023163945.39920-1-yin31149@gmail.com>
On Mon, Oct 24, 2022 at 12:39:41AM +0800, Hawkins Jiawei wrote:
> According to commit "vfs: parse: deal with zero length string value",
> kernel will set the param->string to null pointer in vfs_parse_fs_string()
> if fs string has zero length.
>
> Yet the problem is that, when fs parses its mount parameters, it will
> dereferences the param->string, without checking whether it is a
> null pointer, which may trigger a null-ptr-deref bug.
>
> So this patchset reviews all functions for fs to parse parameters,
> by using `git grep -n "\.parse_param" fs/*`, and adds sanity check
> on param->string if its function will dereference param->string
> without check.
How about reverting the commit in question instead? Or dropping it
from patch series, depending upon the way akpm handles the pile
these days...
next prev parent reply other threads:[~2022-10-23 16:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-23 16:39 Hawkins Jiawei
2022-10-23 16:39 ` [PATCH -next 1/5] smb3: " Hawkins Jiawei
2022-10-23 16:39 ` [PATCH -next 2/5] nfs: " Hawkins Jiawei
2022-10-24 10:53 ` Jeff Layton
2022-10-23 16:39 ` [PATCH -next 3/5] ceph: " Hawkins Jiawei
2022-10-24 0:38 ` Xiubo Li
2022-10-24 0:55 ` Xiubo Li
2022-10-24 2:04 ` Hawkins Jiawei
2022-10-24 2:17 ` Xiubo Li
2022-10-23 16:39 ` [PATCH -next 4/5] gfs2: " Hawkins Jiawei
2022-10-24 9:42 ` Andreas Grünbacher
2022-10-23 16:39 ` [PATCH -next 5/5] proc: " Hawkins Jiawei
2022-10-23 16:48 ` Al Viro [this message]
2022-10-24 0:42 ` [PATCH -next 0/5] fs: " Hawkins Jiawei
2022-10-24 3:34 ` Ian Kent
2022-10-31 11:28 ` Tetsuo Handa
2022-11-01 0:32 ` Ian Kent
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=Y1VwdUYGvDE4yUoI@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=18801353760@163.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yin31149@gmail.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
Powered by JetHome