From: syzbot <syzbot+ba3c0273042a898c230e@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, lizhi.xu@windriver.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [btrfs?] kernel BUG in __extent_writepage_io (2)
Date: Wed, 28 Aug 2024 21:19:02 -0700 [thread overview]
Message-ID: <000000000000435ccf0620cac605@google.com> (raw)
In-Reply-To: <20240829041320.3047873-1-lizhi.xu@windriver.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
fs/btrfs/inode.c:6961:75: error: no member named 'block_start' in 'struct extent_map'
fs/btrfs/inode.c:6963:89: error: no member named 'block_start' in 'struct extent_map'
Tested on:
commit: d5d547aa Merge tag 'random-6.11-rc6-for-linus' of git:..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=4fc2afd52fd008bb
dashboard link: https://syzkaller.appspot.com/bug?extid=ba3c0273042a898c230e
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=1230ffa3980000
next parent reply other threads:[~2024-08-29 4:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240829041320.3047873-1-lizhi.xu@windriver.com>
2024-08-29 4:19 ` syzbot [this message]
[not found] <20240829090643.2396576-1-lizhi.xu@windriver.com>
2024-08-29 9:30 ` [syzbot] [btrfs?] kernel BUG in __extent_writepage_io (2) syzbot
[not found] <20240829054235.3940345-1-lizhi.xu@windriver.com>
2024-08-29 5:57 ` syzbot
[not found] <20240829023517.2159902-1-lizhi.xu@windriver.com>
2024-08-29 2:50 ` syzbot
2024-08-28 22:34 syzbot
2024-08-28 22:59 ` Qu Wenruo
2024-08-29 11:49 ` Edward Adam Davis
2024-08-29 14:34 ` 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=000000000000435ccf0620cac605@google.com \
--to=syzbot+ba3c0273042a898c230e@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.xu@windriver.com \
--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