From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: Omar Sandoval <osandov@fb.com>,
syzbot <syzbot+b382ba6a802a3d242790@syzkaller.appspotmail.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk,
Jens Axboe <axboe@fb.com>
Subject: Re: BUG: unable to handle kernel paging request in dput (2)
Date: Wed, 30 Jan 2019 12:23:06 +0100 [thread overview]
Message-ID: <20190130112306.GA28528@kroah.com> (raw)
In-Reply-To: <80e90ecd-77f5-00a3-4e91-5e9eea2aa117@I-love.SAKURA.ne.jp>
On Wed, Jan 30, 2019 at 08:11:17PM +0900, Tetsuo Handa wrote:
> Hello, Omar.
>
> syzbot is reporting a crash due to dput(-EINVAL) [1]. I think the location is
>
> dir = debugfs_lookup(buts->name, blk_debugfs_root);
> if (!dir)
> bt->dir = dir = debugfs_create_dir(buts->name, blk_debugfs_root);
>
> added by commit 6ac93117ab009d39 ("blktrace: use existing disk debugfs directory").
>
> Currently, Greg Kroah-Hartman is posting patches:
>
> When calling debugfs functions, there is no need to ever check the
> return value. The function can work or not, but the code logic should
> never do something different based on this.
>
> Omar, what do you want to do for this case?
>
> [1] https://syzkaller.appspot.com/bug?extid=b382ba6a802a3d242790
>
Obviously debugfs_lookup() should have its return value checked, so
that's fine :)
But how are we getting an error with dput()? Are you sure this is a
debugfs issue and not a relayfs problem?
I'll send patches to clean up the tracing code's use of debugfs later,
as it is, I don't see anything obviously wrong with it.
thanks,
greg k-h
next prev parent reply other threads:[~2019-01-30 11:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 10:35 BUG: unable to handle kernel paging request in dput (2) syzbot
2019-01-30 11:11 ` Tetsuo Handa
2019-01-30 11:23 ` Greg Kroah-Hartman [this message]
2019-01-30 11:26 ` Tetsuo Handa
2019-01-30 11:34 ` Greg Kroah-Hartman
2019-01-30 11:40 ` Greg Kroah-Hartman
2019-01-31 10:09 ` Kees Cook
2019-01-31 10:18 ` Tetsuo Handa
2019-01-31 10:53 ` Greg Kroah-Hartman
2019-01-30 11:20 ` syzbot
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=20190130112306.GA28528@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=axboe@fb.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=osandov@fb.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=syzbot+b382ba6a802a3d242790@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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;
as well as URLs for NNTP newsgroup(s).