[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<BL1PR11MB5979C08BC3D25571F3E7DEA8869FA@BL1PR11MB5979.namprd11.prod.outlook.com>
Date: Tue, 20 May 2025 06:49:47 +0000
From: "Xu, Lizhi" <Lizhi.Xu@...driver.com>
To: Christian Hesse <mail@...rm.de>
CC: "axboe@...nel.dk" <axboe@...nel.dk>,
"christian@...sel.eu"
<christian@...sel.eu>,
"hch@...radead.org" <hch@...radead.org>,
"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
It was designed that way. But for now, if such files from a filesystem
that does not support read_iter are mounted to the loop device without
performing read operations, it may be safe.
It would be best if Christoph Hellwig could give some comments.
BR,
Lizhi
Powered by blists - more mailing lists