linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+a57b2aff60832666fc28@syzkaller.appspotmail.com>
To: adobriyan@gmail.com, akpm@linux-foundation.org,
	dave.hansen@intel.com, eparis@parisplace.org,
	kent.overstreet@gmail.com, linux-kernel@vger.kernel.org,
	marcelo.leitner@gmail.com, nhorman@tuxdriver.com,
	paul@paul-moore.com, peter.enderborg@sony.com, pshelar@ovn.org,
	sds@tycho.nsa.gov, selinux@vger.kernel.org, shli@kernel.org,
	syzkaller-bugs@googlegroups.com, torvalds@linux-foundation.org,
	viro@zeniv.linux.org.uk, vyasevich@gmail.com,
	willy@infradead.org
Subject: Re: general protection fault in ebitmap_destroy (2)
Date: Thu, 21 Mar 2019 15:20:00 -0700	[thread overview]
Message-ID: <0000000000009db4840584a223b9@google.com> (raw)
In-Reply-To: <20190321185835.GC11352@kmo-pixel>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger  
crash:

Reported-and-tested-by:  
syzbot+a57b2aff60832666fc28@syzkaller.appspotmail.com

Tested on:

commit:         9a03b23d selinux: fix calling ebitmap_destroy() on null ptr
git tree:       http://evilpiepirate.org/git/bcachefs.git syzbot-fix
kernel config:  https://syzkaller.appspot.com/x/.config?x=2f8e9856965eaf03
compiler:       gcc (GCC) 9.0.0 20190115 (experimental)

Note: testing is done by a robot and is best-effort only.

      parent reply	other threads:[~2019-03-21 22:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-14 20:52 general protection fault in ebitmap_destroy (2) syzbot
2019-03-21 18:58 ` Kent Overstreet
2019-03-21 19:01   ` Paul Moore
2019-03-21 22:20   ` 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=0000000000009db4840584a223b9@google.com \
    --to=syzbot+a57b2aff60832666fc28@syzkaller.appspotmail.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=dave.hansen@intel.com \
    --cc=eparis@parisplace.org \
    --cc=kent.overstreet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.leitner@gmail.com \
    --cc=nhorman@tuxdriver.com \
    --cc=paul@paul-moore.com \
    --cc=peter.enderborg@sony.com \
    --cc=pshelar@ovn.org \
    --cc=sds@tycho.nsa.gov \
    --cc=selinux@vger.kernel.org \
    --cc=shli@kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=vyasevich@gmail.com \
    --cc=willy@infradead.org \
    /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).