linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: syzbot <syzbot+32c9f7d8a32ea5127669@syzkaller.appspotmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: WARNING in do_dentry_open (2)
Date: Sat, 1 Feb 2020 13:37:01 +0000	[thread overview]
Message-ID: <20200201133701.GI23230@ZenIV.linux.org.uk> (raw)
In-Reply-To: <00000000000091cacb059d809681@google.com>

On Sat, Feb 01, 2020 at 01:48:11AM -0800, syzbot wrote:
> Hello,
> 
> syzbot found the following crash on:
> 
> HEAD commit:    c677124e Merge branch 'sched-core-for-linus' of git://git...
> git tree:       upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=157511bee00000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=a4c9892b0ce783fa
> dashboard link: https://syzkaller.appspot.com/bug?extid=32c9f7d8a32ea5127669
> compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1476cf66e00000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1640085ee00000
> 
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+32c9f7d8a32ea5127669@syzkaller.appspotmail.com

security_file_open() or ->open() of some file returning a positive number.  No way
to tell which one (or which file had that been) without a reproducer...

      reply	other threads:[~2020-02-01 13:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-01  9:48 WARNING in do_dentry_open (2) syzbot
2020-02-01 13:37 ` Al Viro [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=20200201133701.GI23230@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+32c9f7d8a32ea5127669@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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;
as well as URLs for NNTP newsgroup(s).