All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+d222f4b7129379c3d5bc@syzkaller.appspotmail.com>
To: brauner@kernel.org, jack@suse.cz, jlbec@evilplan.org,
	 joseph.qi@linux.alibaba.com, linkinjeon@kernel.org,
	 linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	mark@fasheh.com,  mjguzik@gmail.com, ocfs2-devel@lists.linux.dev,
	sj1557.seo@samsung.com,  syzkaller-bugs@googlegroups.com,
	viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [exfat?] [ocfs2?] kernel BUG in link_path_walk
Date: Wed, 10 Dec 2025 14:09:03 -0800	[thread overview]
Message-ID: <6939ef7f.a70a0220.33cd7b.001b.GAE@google.com> (raw)
In-Reply-To: <20251210214730.GC1712166@ZenIV>

Hello,

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

Reported-by: syzbot+d222f4b7129379c3d5bc@syzkaller.appspotmail.com
Tested-by: syzbot+d222f4b7129379c3d5bc@syzkaller.appspotmail.com

Tested on:

commit:         0048fbb4 Merge tag 'locking-futex-2025-12-10' of git:/..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=107c7992580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=de48dccdf203ea90
dashboard link: https://syzkaller.appspot.com/bug?extid=d222f4b7129379c3d5bc
compiler:       Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch:          https://syzkaller.appspot.com/x/patch.diff?x=10c51a1a580000

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

  reply	other threads:[~2025-12-10 22:09 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-04  0:07 [syzbot] [exfat?] [ocfs2?] kernel BUG in link_path_walk syzbot
2025-12-04  0:46 ` Mateusz Guzik
2025-12-04  1:21   ` syzbot
2025-12-04  7:45     ` Mateusz Guzik
2025-12-04  8:21       ` Al Viro
2025-12-04  8:40         ` Mateusz Guzik
2025-12-10  9:45           ` [PATCH for 6.19-rc1] fs: preserve file type in make_bad_inode() unless invalid Tetsuo Handa
2025-12-10 10:09             ` Jan Kara
2025-12-10 10:24               ` Mateusz Guzik
2025-12-10 21:14                 ` Al Viro
2025-12-10 23:27                   ` Mateusz Guzik
2026-01-06 10:10               ` Tetsuo Handa
2026-01-07  9:36                 ` Jan Kara
2026-01-07  9:53                   ` Tetsuo Handa
2026-01-07 10:15                     ` Jan Kara
2025-12-10 10:09             ` Mateusz Guzik
2025-12-10 15:35               ` Al Viro
2025-12-10 20:43                 ` Al Viro
2025-12-10 20:55                   ` Al Viro
2025-12-10 21:33                 ` Al Viro
2025-12-04  9:09 ` [syzbot] [exfat?] [ocfs2?] kernel BUG in link_path_walk Mateusz Guzik
2025-12-04 10:13   ` syzbot
2025-12-04 10:15 ` Mateusz Guzik
2025-12-04 11:56   ` syzbot
2025-12-04 11:58     ` Mateusz Guzik
2025-12-10 11:00 ` Mateusz Guzik
2025-12-10 11:19   ` syzbot
2025-12-10 11:28     ` Mateusz Guzik
2025-12-10 19:44 ` Mateusz Guzik
2025-12-10 20:06   ` syzbot
2025-12-10 21:47   ` Al Viro
2025-12-10 22:09     ` syzbot [this message]
2025-12-11  9:00     ` Jan Kara

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=6939ef7f.a70a0220.33cd7b.001b.GAE@google.com \
    --to=syzbot+d222f4b7129379c3d5bc@syzkaller.appspotmail.com \
    --cc=brauner@kernel.org \
    --cc=jack@suse.cz \
    --cc=jlbec@evilplan.org \
    --cc=joseph.qi@linux.alibaba.com \
    --cc=linkinjeon@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@fasheh.com \
    --cc=mjguzik@gmail.com \
    --cc=ocfs2-devel@lists.linux.dev \
    --cc=sj1557.seo@samsung.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=viro@zeniv.linux.org.uk \
    /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.