mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+d8f000c609f05f52d9b5@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [iomap?] [erofs?] WARNING in iomap_iter (5)
Date: Fri, 13 Jun 2025 20:54:04 -0700	[thread overview]
Message-ID: <684cf25c.a00a0220.279073.001b.GAE@google.com> (raw)
In-Reply-To: <tencent_5164697F63AFA45C5776B771A6C83368C305@qq.com>

Hello,

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

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

Tested on:

commit:         4774cfe3 Merge tag 'scsi-fixes' of git://git.kernel.or..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10a48e82580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=162faeb2d1eaefb4
dashboard link: https://syzkaller.appspot.com/bug?extid=d8f000c609f05f52d9b5
compiler:       Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
patch:          https://syzkaller.appspot.com/x/patch.diff?x=13c88e82580000

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

  reply	other threads:[~2025-06-14  3:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-13 23:30 syzbot
2025-06-14  3:06 ` Edward Adam Davis
2025-06-14  3:54   ` syzbot [this message]
2025-06-14  9:46 ` syzbot
2025-06-15  5:05   ` [PATCH] erofs: confirm big pcluster before setting extents Edward Adam Davis
2025-06-15  5:49     ` Gao Xiang
2025-06-19  3:53   ` [syzbot] [iomap?] [erofs?] WARNING in iomap_iter (5) Gao Xiang
2025-06-19  4:29     ` syzbot
2025-06-15  3:26 ` Edward Adam Davis
2025-06-15  4:02   ` syzbot
2025-06-15  3:56 ` Edward Adam Davis
2025-06-15  4:24   ` syzbot
2025-06-19  3:28 ` [PATCH] erofs: refuse crafted out-of-file-range encoded extents Gao Xiang

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=684cf25c.a00a0220.279073.001b.GAE@google.com \
    --to=syzbot+d8f000c609f05f52d9b5@syzkaller.appspotmail.com \
    --cc=eadavis@qq.com \
    --cc=linux-kernel@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
all inboxes | Powered by JetHome®