linux-kernel - Re: [PATCH v2 01/11] ntfsplus: in-memory, on-disk structures and headers

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] [day] [month] [year] [list]

Message-ID: <aS2AAKmGcNYgJzx6@casper.infradead.org>
Date: Mon, 1 Dec 2025 11:46:08 +0000
From: Matthew Wilcox <willy@...radead.org>
To: Christoph Hellwig <hch@...radead.org>
Cc: Namjae Jeon <linkinjeon@...nel.org>, viro@...iv.linux.org.uk,
	brauner@...nel.org, hch@....de, tytso@....edu, jack@...e.cz,
	djwong@...nel.org, josef@...icpanda.com, sandeen@...deen.net,
	rgoldwyn@...e.com, xiang@...nel.org, dsterba@...e.com,
	pali@...nel.org, ebiggers@...nel.org, neil@...wn.name,
	amir73il@...il.com, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org, iamjoonsoo.kim@....com,
	cheol.lee@....com, jay.sim@....com, gunho.lee@....com
Subject: Re: [PATCH v2 01/11] ntfsplus: in-memory, on-disk structures and
 headers

On Mon, Dec 01, 2025 at 03:22:43AM -0800, Christoph Hellwig wrote:
> On Mon, Dec 01, 2025 at 07:13:49PM +0900, Namjae Jeon wrote:
> > CPU intensive spinning only occurs if signals are delivered extremely
> > frequently...
> > Are there any ways to improve this EINTR handling?
> > Thanks!
> 
> Have an option to not abort when fatal signals are pending?

I'd rather not add a sixth argument to do_read_cache_folio().

And I'm not sure the right question is being asked here.  Storage can
disappear at any moment -- somebody unplugs the USB device, the NBD
device that's hosting the filesystem experiences a network outage, etc.

So every filesystem _should_ handle fatal signals gracefully.  The task
must die, even if it's in the middle of reading metadata.  I know that's
not always the easiest thing to do, but it is the right thing to do.