linux-kernel - Re: [PATCH V5] loop: Add sanity check for read/write

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID:
 <BL1PR11MB5979A7C34945BDB66BA84A5F869FA@BL1PR11MB5979.namprd11.prod.outlook.com>
Date: Tue, 20 May 2025 13:12:16 +0000
From: "Xu, Lizhi" <Lizhi.Xu@...driver.com>
To: "hch@...radead.org" <hch@...radead.org>, Christian Hesse <mail@...rm.de>
CC: "axboe@...nel.dk" <axboe@...nel.dk>,
        "christian@...sel.eu"
	<christian@...sel.eu>,
        "linux-block@...r.kernel.org"
	<linux-block@...r.kernel.org>,
        "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>,
        "ming.lei@...hat.com" <ming.lei@...hat.com>,
        "syzbot+6af973a3b8dfd2faefdc@...kaller.appspotmail.com"
	<syzbot+6af973a3b8dfd2faefdc@...kaller.appspotmail.com>,
        "syzkaller-bugs@...glegroups.com" <syzkaller-bugs@...glegroups.com>
Subject: Re: [PATCH V5] loop: Add sanity check for read/write_iter

> We historically allow a writable fd on block devices even when they
> are read-only.  I suspect your use case is doing that and the new
> check for write_iter is interfering with that:
After deleting the "if ((mode & BLK_OPEN_WRITE) && !file->f_op->write_iter)",
everything should be normal.