Re: [LSF/MM/BPF TOPIC] Replacing TASK_(UN)INTERRUPTIBLE with regions of uninterruptibility

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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?

> For overlayfs it doesn't really make sense, but for network fs and
> fuse I guess it could be interesting.

But overlayfs calls down into other filesystems - and those might be, say,
network filesystems that want to be interruptible.

David





[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [NTFS 3]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [NTFS 3]     [Samba]     [Device Mapper]     [CEPH Development]

  Powered by Linux