linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+bca9799bf129256190da@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, akpm@linux-foundation.org,
	 dan.j.williams@intel.com, jack@suse.cz,
	linux-ext4@vger.kernel.org,  linux-kernel@vger.kernel.org,
	linux-mm@kvack.org,  syzkaller-bugs@googlegroups.com,
	tytso@mit.edu
Subject: Re: BUG: unable to handle kernel NULL pointer dereference in generic_perform_write (2)
Date: Tue, 14 Apr 2020 21:55:04 -0700	[thread overview]
Message-ID: <00000000000098a5d505a34d1e48@google.com> (raw)
In-Reply-To: <20200415043553.GH90651@mit.edu>

Hello,

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

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

Tested on:

commit:         5b8b9d0c Merge branch 'akpm' (patches from Andrew)
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel config:  https://syzkaller.appspot.com/x/.config?x=23c5a352e32a1944
dashboard link: https://syzkaller.appspot.com/bug?extid=bca9799bf129256190da
compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
patch:          https://syzkaller.appspot.com/x/patch.diff?x=15524a00100000

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


  reply	other threads:[~2020-04-15  4:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-14  6:11 BUG: unable to handle kernel NULL pointer dereference in generic_perform_write (2) syzbot
2020-04-15  4:35 ` Theodore Y. Ts'o
2020-04-15  4:55   ` syzbot [this message]
2020-06-10 21:10 ` Theodore Y. Ts'o
2020-06-10 21:16   ` syzbot
2020-06-10 21:41 ` Theodore Y. Ts'o
2020-06-10 21:56   ` syzbot
2020-06-10 22:07 ` Theodore Y. Ts'o
2020-06-11  0:25   ` syzbot

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=00000000000098a5d505a34d1e48@google.com \
    --to=syzbot+bca9799bf129256190da@syzkaller.appspotmail.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=akpm@linux-foundation.org \
    --cc=dan.j.williams@intel.com \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tytso@mit.edu \
    /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).