linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+0d1fcd7268b21baced4a@syzkaller.appspotmail.com>
To: adobriyan@gmail.com, akpm@linux-foundation.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	sfr@canb.auug.org.au, syzkaller-bugs@googlegroups.com,
	viro@zeniv.linux.org.uk
Subject: Re: general protection fault in load_elf_binary
Date: Fri, 29 Mar 2019 14:48:01 -0700	[thread overview]
Message-ID: <000000000000f3bf550585429fe9@google.com> (raw)
In-Reply-To: <000000000000ddc91405853d6de3@google.com>

syzbot has bisected this bug to:

commit 44e63c4a026325d2e085e46502121ea533a6e315
Author: Alexey Dobriyan <adobriyan@gmail.com>
Date:   Thu Mar 28 23:02:05 2019 +0000

     fs/binfmt_elf.c: free PT_INTERP filename ASAP

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=11d5c23f200000
start commit:   1baf02ec Add linux-next specific files for 20190329
git tree:       linux-next
final crash:    https://syzkaller.appspot.com/x/report.txt?x=13d5c23f200000
console output: https://syzkaller.appspot.com/x/log.txt?x=15d5c23f200000
kernel config:  https://syzkaller.appspot.com/x/.config?x=9d8e70f94f3533a7
dashboard link: https://syzkaller.appspot.com/bug?extid=0d1fcd7268b21baced4a
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=125ca12f200000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=11e1123f200000

Reported-by: syzbot+0d1fcd7268b21baced4a@syzkaller.appspotmail.com
Fixes: 44e63c4a0263 ("fs/binfmt_elf.c: free PT_INTERP filename ASAP")

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

      reply	other threads:[~2019-03-29 21:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-29 15:36 general protection fault in load_elf_binary syzbot
2019-03-29 21:48 ` 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=000000000000f3bf550585429fe9@google.com \
    --to=syzbot+0d1fcd7268b21baced4a@syzkaller.appspotmail.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --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).