Re: [syzbot] [xfs?] [ext4?] kernel BUG in __block_write_begin_int

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: [syzbot] [xfs?] [ext4?] kernel BUG in __block_write_begin_int
From: Christoph Hellwig <hch@xxxxxx>
Date: Mon, 4 Sep 2023 15:26:49 +0200
Cc: syzbot <syzbot+4a08ffdf3667b36650a1@xxxxxxxxxxxxxxxxxxxxxxxxx>, adilger.kernel@xxxxxxxxx, djwong@xxxxxxxxxx, linux-ext4@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxxxxxx, song@xxxxxxxxxx, syzkaller-bugs@xxxxxxxxxxxxxxxx, tytso@xxxxxxx, yukuai3@xxxxxxxxxx, zhang_shurong@xxxxxxxxxxx, linux-block@xxxxxxxxxxxxxxx, axboe@xxxxxxxxx, hch@xxxxxx
In-reply-to: <ZPWWZeWliX7RhOAZ@dread.disaster.area>
References: <000000000000e76944060483798d@google.com> <ZPWWZeWliX7RhOAZ@dread.disaster.area>
User-agent: Mutt/1.5.17 (2007-11-01)

On Mon, Sep 04, 2023 at 06:33:41PM +1000, Dave Chinner wrote:
> It appears that 0010:__block_write_begin_int() has iterated beyond
> the iomap that was passed in, triggering the BUG_ON() check in
> iomap_to_bh().

Yes, I'll look into it.

References:
- [syzbot] [xfs?] [ext4?] kernel BUG in __block_write_begin_int
  - From: syzbot
- Re: [syzbot] [xfs?] [ext4?] kernel BUG in __block_write_begin_int
  - From: Dave Chinner

Prev by Date: [PATCH v2 1/2] JBD2: print io_block if check data block checksum failed when do recovery
Next by Date: Re: [e2fsprogs PATCH] libext2fs: fix ext2fs_get_device_size2() return value on Windows
Previous by thread: Re: [syzbot] [xfs?] [ext4?] kernel BUG in __block_write_begin_int
Next by thread: Re: [syzbot] [xfs?] [ext4?] kernel BUG in __block_write_begin_int
Index(es):
- Date
- Thread

[Index of Archives] [Reiser Filesystem Development] [Ceph FS] [Kernel Newbies] [Security] [Netfilter] [Bugtraq] [Linux FS] [Yosemite National Park] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Samba] [Device Mapper] [Linux Media]