public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+0bc698a422b5e4ac988c@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, dan.j.williams@intel.com,
	djwong@kernel.org, hch@lst.de, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, linux-xfs@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [xfs?] KASAN: stack-out-of-bounds Read in xfs_buf_lock
Date: Sat, 21 Jan 2023 12:19:19 -0800	[thread overview]
Message-ID: <0000000000008016d805f2cbe102@google.com> (raw)
In-Reply-To: <0000000000004ab8ac05ef9b1578@google.com>

syzbot has bisected this issue to:

commit 679a99495b8fda800037b25af8cd990eb7dd72c9
Author: Christoph Hellwig <hch@lst.de>
Date:   Mon Nov 29 10:21:41 2021 +0000

    xfs: factor out a xfs_setup_dax_always helper

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=17708805480000
start commit:   7dd4b804e080 Merge tag 'nfsd-6.2-3' of git://git.kernel.or..
git tree:       upstream
final oops:     https://syzkaller.appspot.com/x/report.txt?x=14f08805480000
console output: https://syzkaller.appspot.com/x/log.txt?x=10f08805480000
kernel config:  https://syzkaller.appspot.com/x/.config?x=2b6ecad960fc703e
dashboard link: https://syzkaller.appspot.com/bug?extid=0bc698a422b5e4ac988c
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=10c58bd2480000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=11cc664a480000

Reported-by: syzbot+0bc698a422b5e4ac988c@syzkaller.appspotmail.com
Fixes: 679a99495b8f ("xfs: factor out a xfs_setup_dax_always helper")

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

  parent reply	other threads:[~2023-01-21 20:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-12  5:50 [syzbot] KASAN: stack-out-of-bounds Read in xfs_buf_lock syzbot
2023-01-11 15:09 ` [syzbot] [xfs?] " syzbot
2023-01-21 20:19 ` syzbot [this message]
     [not found] <20230123082114.4291-1-hdanton@sina.com>
2023-01-23 11:42 ` syzbot
2023-01-27  7:18   ` Dmitry Vyukov
2023-01-27  9:29     ` Aleksandr Nogikh

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=0000000000008016d805f2cbe102@google.com \
    --to=syzbot+0bc698a422b5e4ac988c@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=dan.j.williams@intel.com \
    --cc=djwong@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    /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