mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+eb5b4ef634a018917f3c@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, hdanton@sina.com, jack@suse.cz,
	 linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com, tytso@mit.edu,
	yun.zhou@windriver.com
Subject: Re: [syzbot] [ext4?] possible deadlock in ext4_writepages (2)
Date: Fri, 23 Oct 2026 11:41:04 -0700	[thread overview]
Message-ID: <6adbaa40.a6443767.132891.0000.GAE@google.com> (raw)
In-Reply-To: <67141631.050a0220.1e4b4d.002e.GAE@google.com>

syzbot suspects this issue was fixed by commit:

commit 2c3447a9c4fe17c713c014f79d2df485f3829c0e
Author: Yun Zhou <yun.zhou@windriver.com>
Date:   Fri Jul 24 10:02:55 2026 +0000

    ext4: validate EA inode i_nlink in ext4_xattr_inode_iget

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=13436931580000
start commit:   f5bbbfec59b4 Merge tag 'probes-fixes-v7.2-rc7' of git://gi..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=158601bb8cb292dd
dashboard link: https://syzkaller.appspot.com/bug?extid=eb5b4ef634a018917f3c
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=14fe5079580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=17e0d2c6580000

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

#syz fix: ext4: validate EA inode i_nlink in ext4_xattr_inode_iget

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

      parent reply	other threads:[~2026-10-23 18:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-19 20:27 syzbot
2025-09-09 23:28 ` syzbot
2025-09-10  0:46   ` Hillf Danton
2026-10-23 18:41 ` 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=6adbaa40.a6443767.132891.0000.GAE@google.com \
    --to=syzbot+eb5b4ef634a018917f3c@syzkaller.appspotmail.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=hdanton@sina.com \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tytso@mit.edu \
    --cc=yun.zhou@windriver.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
all inboxes | Powered by JetHome®