Re: The new invalidate_lock seems to cause a potential deadlock with fscache

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

 



Jan Kara <jack@xxxxxxx> wrote:

> We have filesystems F1 & F2, where F1 is the network fs and F2 is the cache
> fs.
> 
> Thread 1	Thread 2		Thread 3	Thread 4
> 		write (F2)
> 		  sb_start_write() (F2)
> 		  prepares write
> 		  copy_from_user()
> ...
> 		Thread 2 continues
> 		    fault()

cachefilesd is only doing I/O to/from kernel resident pages.  It shouldn't
fault there.  I'm not sure it's even going to call copy_from_user() since
it'll be using ITER_XARRAY.

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