All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+19b469021157c136116a@syzkaller.appspotmail.com>
To: anton@tuxera.com, daniel@iogearbox.net, deller@gmx.de,
	dvyukov@google.com, jejb@parisc-linux.org, keescook@chromium.org,
	linux-kernel@vger.kernel.org,
	linux-ntfs-dev@lists.sourceforge.net,
	linux-parisc@vger.kernel.org, luto@amacapital.net,
	sdf@google.com, songliubraving@fb.com,
	syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk,
	wad@chromium.org
Subject: Re: KASAN: use-after-free Read in ntfs_read_locked_inode
Date: Wed, 26 Aug 2020 03:37:06 -0700	[thread overview]
Message-ID: <000000000000b636f005adc56621@google.com> (raw)
In-Reply-To: <001a11441b6c6cb96c0569120042@google.com>

syzbot suspects this issue was fixed by commit:

commit f7c6cb1d9728dea9d9f131ef57303d6821afb0f8
Author: Stanislav Fomichev <sdf@google.com>
Date:   Wed Jul 29 00:31:03 2020 +0000

    bpf: Expose socket storage to BPF_PROG_TYPE_CGROUP_SOCK

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=16480fa9900000
start commit:   3e968c9f Merge tag 'ext4_for_linus' of git://git.kernel.or..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=7e8c053ac965e0dd
dashboard link: https://syzkaller.appspot.com/bug?extid=19b469021157c136116a
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=142d219b800000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=143029db800000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: bpf: Expose socket storage to BPF_PROG_TYPE_CGROUP_SOCK

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

      parent reply	other threads:[~2020-08-26 10:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-05  4:02 KASAN: use-after-free Read in ntfs_read_locked_inode syzbot
2019-11-27 13:20 ` syzbot
2019-11-27 14:02   ` Dmitry Vyukov
2020-08-26 10:37 ` 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=000000000000b636f005adc56621@google.com \
    --to=syzbot+19b469021157c136116a@syzkaller.appspotmail.com \
    --cc=anton@tuxera.com \
    --cc=daniel@iogearbox.net \
    --cc=deller@gmx.de \
    --cc=dvyukov@google.com \
    --cc=jejb@parisc-linux.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-ntfs-dev@lists.sourceforge.net \
    --cc=linux-parisc@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=sdf@google.com \
    --cc=songliubraving@fb.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=wad@chromium.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 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.