On Fri, 2 Feb 2024 at 12:22, David Howells <dhowells@xxxxxxxxxx> wrote: > > Miklos Szeredi <miklos@xxxxxxxxxx> wrote: > > > Just making inode_lock() interruptible would break everything. > > Why? Obviously, you'd need to check the result of the inode_lock(), which I > didn't put in my very rough example code, but why would taking the lock at the > front of a vfs op like mkdir be a problem? No problem in theory. It just looks like a tedious job doing all that. But please go for it, it's a worthy goal in my opinion. Thanks, Miklos
