From: syzbot <syzbot+e682cca30bc101a4d9d9@syzkaller.appspotmail.com>
To: axboe@fb.com, axboe@kernel.dk, catalin.marinas@arm.com,
davem@davemloft.net, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
michaelcallahan@fb.com, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: memory leak in new_inode_pseudo (2)
Date: Sat, 27 Jul 2019 03:16:00 -0700 [thread overview]
Message-ID: <0000000000000dc874058ea6f261@google.com> (raw)
In-Reply-To: <000000000000111cbe058dc7754d@google.com>
syzbot has bisected this bug to:
commit a21f2a3ec62abe2e06500d6550659a0ff5624fbb
Author: Michael Callahan <michaelcallahan@fb.com>
Date: Tue May 3 15:12:49 2016 +0000
block: Minor blk_account_io_start usage cleanup
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13565e92600000
start commit: be8454af Merge tag 'drm-next-2019-07-16' of git://anongit...
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=10d65e92600000
console output: https://syzkaller.appspot.com/x/log.txt?x=17565e92600000
kernel config: https://syzkaller.appspot.com/x/.config?x=d23a1a7bf85c5250
dashboard link: https://syzkaller.appspot.com/bug?extid=e682cca30bc101a4d9d9
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=155c5800600000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1738f800600000
Reported-by: syzbot+e682cca30bc101a4d9d9@syzkaller.appspotmail.com
Fixes: a21f2a3ec62a ("block: Minor blk_account_io_start usage cleanup")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-07-27 10:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 7:38 memory leak in new_inode_pseudo (2) syzbot
2019-07-16 8:28 ` syzbot
2019-11-19 5:13 ` Eric Biggers
2019-11-27 12:05 ` Ursula Braun
2019-07-27 10:16 ` syzbot [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=0000000000000dc874058ea6f261@google.com \
--to=syzbot+e682cca30bc101a4d9d9@syzkaller.appspotmail.com \
--cc=axboe@fb.com \
--cc=axboe@kernel.dk \
--cc=catalin.marinas@arm.com \
--cc=davem@davemloft.net \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=michaelcallahan@fb.com \
--cc=netdev@vger.kernel.org \
--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 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.