All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+ee90502d5c8fd1d0dd93@syzkaller.appspotmail.com>
To: clm@fb.com, dsterba@suse.com, hch@infradead.org,
	josef@toxicpanda.com, linux-btrfs@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [btrfs?] WARNING in btrfs_split_ordered_extent
Date: Thu, 08 Jun 2023 01:55:27 -0700	[thread overview]
Message-ID: <000000000000e8650e05fd9a6902@google.com> (raw)
In-Reply-To: <ZIF9v+qcdhhuYsMr@infradead.org>

Hello,

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

Reported-and-tested-by: syzbot+ee90502d5c8fd1d0dd93@syzkaller.appspotmail.com

Tested on:

commit:         8176a54b btrfs: fix iomap_begin length for nocow writes
git tree:       git://git.infradead.org/users/hch/misc.git btrfs-dio-nocow-fix
console output: https://syzkaller.appspot.com/x/log.txt?x=11d17a43280000
kernel config:  https://syzkaller.appspot.com/x/.config?x=7474de833c217bf4
dashboard link: https://syzkaller.appspot.com/bug?extid=ee90502d5c8fd1d0dd93
compiler:       Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.

  reply	other threads:[~2023-06-08  8:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-22  6:26 [syzbot] [btrfs?] WARNING in btrfs_split_ordered_extent syzbot
2023-06-07 23:45 ` syzbot
2023-06-08  7:05   ` Christoph Hellwig
2023-06-08  8:55     ` syzbot [this message]
2023-06-08  8:40 ` syzbot

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=000000000000e8650e05fd9a6902@google.com \
    --to=syzbot+ee90502d5c8fd1d0dd93@syzkaller.appspotmail.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=hch@infradead.org \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --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 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.