All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+be8872fcb764bf9fea73@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com, bp@alien8.de,
	 linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	 ntfs3@lists.linux.dev, syzkaller-bugs@googlegroups.com,
	 viro@zeniv.linux.org.uk, yazen.ghannam@amd.com
Subject: Re: [syzbot] [ntfs3?] WARNING in path_openat
Date: Wed, 26 Jul 2023 22:33:28 -0700	[thread overview]
Message-ID: <000000000000ca24700601714dd2@google.com> (raw)
In-Reply-To: <000000000000a0d7f305eecfcbb9@google.com>

syzbot suspects this issue was fixed by commit:

commit 00e4feb8c0476bbde3c8bf4a593e0f82ca9a4df6
Author: Yazen Ghannam <yazen.ghannam@amd.com>
Date:   Fri Jan 27 17:04:03 2023 +0000

    EDAC/amd64: Rename debug_display_dimm_sizes()

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=157a6f81a80000
start commit:   c1649ec55708 Merge tag 'nfsd-6.2-4' of git://git.kernel.or..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=319a3509d25b0f85
dashboard link: https://syzkaller.appspot.com/bug?extid=be8872fcb764bf9fea73
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=17c604fe480000

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

#syz fix: EDAC/amd64: Rename debug_display_dimm_sizes()

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

  parent reply	other threads:[~2023-07-27  5:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02  3:18 [syzbot] WARNING in path_openat syzbot
2023-01-11  7:15 ` [syzbot] [vfs?] [ntfs3?] " syzbot
2023-01-26 23:55 ` syzbot
2023-07-27  5:33 ` syzbot [this message]
2023-07-27  6:47   ` [syzbot] " 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=000000000000ca24700601714dd2@google.com \
    --to=syzbot+be8872fcb764bf9fea73@syzkaller.appspotmail.com \
    --cc=almaz.alexandrovich@paragon-software.com \
    --cc=bp@alien8.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ntfs3@lists.linux.dev \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=yazen.ghannam@amd.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 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.