From: syzbot <syzbot+1fa947e7f09e136925b8@syzkaller.appspotmail.com>
To: axboe@kernel.dk, brauner@kernel.org, david@fromorbit.com,
djwong@kernel.org, hare@suse.de, hch@infradead.org, hch@lst.de,
johannes.thumshirn@wdc.com, linux-block@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-xfs@vger.kernel.org, mcgrof@kernel.org, nogikh@google.com,
p.raghav@samsung.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [block] INFO: task hung in clean_bdev_aliases
Date: Mon, 25 Sep 2023 01:58:23 -0700 [thread overview]
Message-ID: <0000000000001a28c006062b292e@google.com> (raw)
In-Reply-To: <ZRFKBxoRjVQclPS0@infradead.org>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
fs/buffer.c:2068:40: error: 'return' with a value, in function returning void [-Werror=return-type]
Tested on:
commit: b8908de1 iomap: add a workaround for racy i_size updat..
git tree: git://git.infradead.org/users/hch/misc.git bdev-iomap-fix
kernel config: https://syzkaller.appspot.com/x/.config?x=999148c170811772
dashboard link: https://syzkaller.appspot.com/bug?extid=1fa947e7f09e136925b8
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
Note: no patches were applied.
next prev parent reply other threads:[~2023-09-25 8:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000e534bb0604959011@google.com>
2023-09-05 21:14 ` [syzbot] [xfs?] INFO: task hung in clean_bdev_aliases Dave Chinner
2023-09-06 17:20 ` Aleksandr Nogikh
2023-09-06 18:04 ` Darrick J. Wong
2023-09-08 8:28 ` Christoph Hellwig
2023-09-20 8:56 ` Aleksandr Nogikh
2023-09-21 0:38 ` Dave Chinner
2023-09-17 15:35 ` [syzbot] [block] " syzbot
2023-09-19 14:00 ` Ricardo B. Marliere
2023-09-19 14:38 ` syzbot
2023-09-19 2:52 ` syzbot
2023-09-25 8:51 ` Christoph Hellwig
2023-09-25 8:58 ` syzbot [this message]
2023-09-25 9:08 ` Christoph Hellwig
2023-09-25 9:35 ` 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=0000000000001a28c006062b292e@google.com \
--to=syzbot+1fa947e7f09e136925b8@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=nogikh@google.com \
--cc=p.raghav@samsung.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;
as well as URLs for NNTP newsgroup(s).