Re: [syzbot] [block] kernel BUG in __block_write_begin_int

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

To: syzbot <syzbot+4a08ffdf3667b36650a1@xxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: [syzbot] [block] kernel BUG in __block_write_begin_int
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue, 5 Sep 2023 05:26:55 -0700
Cc: adilger.kernel@xxxxxxxxx, djwong@xxxxxxxxxx, hch@xxxxxxxxxxxxx, linux-ext4@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxxxxxx, nogikh@xxxxxxxxxx, song@xxxxxxxxxx, syzkaller-bugs@xxxxxxxxxxxxxxxx, tytso@xxxxxxx, yukuai3@xxxxxxxxxx, zhang_shurong@xxxxxxxxxxx
In-reply-to: <000000000000d9daf4060499c0c9@google.com>

On Tue, Sep 05, 2023 at 03:04:32AM -0700, syzbot wrote:
> Hello,
> 
> syzbot has tested the proposed patch but the reproducer is still triggering an issue:
> WARNING in __kthread_create_on_node

Well, that is


 a) a different issue in ext4
 b) just a warning

References:
- Re: [syzbot] [xfs?] [ext4?] kernel BUG in __block_write_begin_int
  - From: Aleksandr Nogikh
- Re: [syzbot] [block] kernel BUG in __block_write_begin_int
  - From: syzbot

Prev by Date: [PATCH 3/5] fscrypt: use s_maxbytes instead of filesystem lblk_bits
Next by Date: Re: [PATCH] iomap: handle error conditions more gracefully in iomap_to_bh
Previous by thread: Re: [syzbot] [block] kernel BUG in __block_write_begin_int
Next by thread: [syzbot] Monthly ntfs report (Sep 2023)
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [NTFS 3] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [NTFS 3] [Samba] [Device Mapper] [CEPH Development]

Powered by Linux