public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: syzbot <syzbot+b904ba7c947a37b4b291@syzkaller•appspotmail.com>
To: a@unstable•cc, b.a.t.m.a.n@lists•open-mesh.org,
	dan.carpenter@oracle•com, davem@davemloft•net,
	dhowells@redhat•com, info@drgreenstore•com,
	linux-afs@lists•infradead.org, linux-kernel@vger•kernel.org,
	mareklindner@neomailbox•ch, netdev@vger•kernel.org,
	sw@simonwunderlich•de, syzkaller-bugs@googlegroups•com
Subject: Re: WARNING in __proc_create (2)
Date: Thu, 23 Jan 2020 14:22:02 -0800	[thread overview]
Message-ID: <00000000000001df94059cd612b2@google.com> (raw)
In-Reply-To: <000000000000da7a79059caf2656@google.com>

syzbot has bisected this bug to:

commit f4b3526d83c40dd8bf5948b9d7a1b2c340f0dcc8
Author: David Howells <dhowells@redhat•com>
Date:   Thu Nov 2 15:27:48 2017 +0000

    afs: Connect up the CB.ProbeUuid

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1627a721e00000
start commit:   d96d875e Merge tag 'fixes_for_v5.5-rc8' of git://git.kerne..
git tree:       upstream
final crash:    https://syzkaller.appspot.com/x/report.txt?x=1527a721e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=1127a721e00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=83c00afca9cf5153
dashboard link: https://syzkaller.appspot.com/bug?extid=b904ba7c947a37b4b291
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=12c96185e00000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=14f859c9e00000

Reported-by: syzbot+b904ba7c947a37b4b291@syzkaller•appspotmail.com
Fixes: f4b3526d83c4 ("afs: Connect up the CB.ProbeUuid")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

           reply	other threads:[~2020-01-23 22:22 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <000000000000da7a79059caf2656@google.com>]

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=00000000000001df94059cd612b2@google.com \
    --to=syzbot+b904ba7c947a37b4b291@syzkaller$(echo .)appspotmail.com \
    --cc=a@unstable$(echo .)cc \
    --cc=b.a.t.m.a.n@lists$(echo .)open-mesh.org \
    --cc=dan.carpenter@oracle$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=dhowells@redhat$(echo .)com \
    --cc=info@drgreenstore$(echo .)com \
    --cc=linux-afs@lists$(echo .)infradead.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=mareklindner@neomailbox$(echo .)ch \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=sw@simonwunderlich$(echo .)de \
    --cc=syzkaller-bugs@googlegroups$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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