linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+4a39a025912b265cacef@syzkaller.appspotmail.com>
To: a@unstable.cc, adilger.kernel@dilger.ca, afd@ti.com,
	b.a.t.m.a.n@lists.open-mesh.org, chris@lapa.com.au,
	davem@davemloft.net, linux-ext4@vger.kernel.org,
	linux-kernel@vger.kernel.org, mareklindner@neomailbox.ch,
	netdev@vger.kernel.org, pali.rohar@gmail.com, sre@kernel.org,
	sw@simonwunderlich.de, syzkaller-bugs@googlegroups.com,
	tytso@mit.edu
Subject: Re: KASAN: use-after-free Read in ext4_xattr_set_entry (2)
Date: Sat, 14 Dec 2019 22:52:01 -0800	[thread overview]
Message-ID: <0000000000002a99070599b888dd@google.com> (raw)
In-Reply-To: <20191215063020.GA11512@mit.edu>

Hello,

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

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

Tested on:

commit:         dfdeeb41 Merge branch 'tt/misc' into dev
git tree:        
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git master
kernel config:  https://syzkaller.appspot.com/x/.config?x=be3b077056d26622
dashboard link: https://syzkaller.appspot.com/bug?extid=4a39a025912b265cacef
compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
patch:          https://syzkaller.appspot.com/x/patch.diff?x=11b02546e00000

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

  reply	other threads:[~2019-12-15  6:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-02 15:39 KASAN: use-after-free Read in ext4_xattr_set_entry (2) syzbot
2019-12-13 18:21 ` syzbot
2019-12-15  1:27 ` syzbot
2019-12-15  6:30   ` Theodore Y. Ts'o
2019-12-15  6:52     ` syzbot [this message]
2019-12-16  8:09     ` Dmitry Vyukov

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=0000000000002a99070599b888dd@google.com \
    --to=syzbot+4a39a025912b265cacef@syzkaller.appspotmail.com \
    --cc=a@unstable.cc \
    --cc=adilger.kernel@dilger.ca \
    --cc=afd@ti.com \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=chris@lapa.com.au \
    --cc=davem@davemloft.net \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mareklindner@neomailbox.ch \
    --cc=netdev@vger.kernel.org \
    --cc=pali.rohar@gmail.com \
    --cc=sre@kernel.org \
    --cc=sw@simonwunderlich.de \
    --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).