linux-kernel - 回复: 回复: [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:
 <BL1PR11MB5979CBE5243379E686674B1C869FA@BL1PR11MB5979.namprd11.prod.outlook.com>
Date: Tue, 20 May 2025 06:59:14 +0000
From: "Xu, Lizhi" <Lizhi.Xu@...driver.com>
To: "hch@...radead.org" <hch@...radead.org>
CC: Christian Hesse <mail@...rm.de>, "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:
 回复: 回复: [PATCH V5] loop: Add sanity check for read/write_iter

No, isofs does not support read_iter.

________________________________________
发件人: hch@...radead.org <hch@...radead.org>
发送时间: 2025年5月20日 14:46
收件人: Xu, Lizhi
抄送: Christian Hesse; axboe@...nel.dk; christian@...sel.eu; hch@...radead.org; linux-block@...r.kernel.org; linux-kernel@...r.kernel.org; ming.lei@...hat.com; syzbot+6af973a3b8dfd2faefdc@...kaller.appspotmail.com; syzkaller-bugs@...glegroups.com
主题: Re: 回复: [PATCH V5] loop: Add sanity check for read/write_iter

CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know the content is safe.

On Tue, May 20, 2025 at 06:29:48AM +0000, Xu, Lizhi wrote:
> I figured out your steps to reproduce, and yes, this problem will occur if you do losetup with a file in a filesystem that does not support read_iter, which is what this patch does.

isofs does support read_iter, without that it would not have worked
before either. That is not the problem.  It must be related to
the FMODE_WRITE check - i.e. we have a writable FD here, but a file
system that does not actually supports writes.  Which honestly feels
weird, but we'll have to figure it out to unbreak these setups.