Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+0\/2\]\s+splice\:\s+i_mutex\s+vs\s+splice\s+write\s+deadlock\s+V2\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+0\/2\]\s+splice\:\s+i_mutex\s+vs\s+splice\s+write\s+deadlock\s+V2\s*$/: 2 ]

Total 2 documents matching your query.

1. [PATCH 0/2] splice: i_mutex vs splice write deadlock V2 (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Mon, 8 Aug 2011 16:45:25 +1000; generic_file_splice_write() takes the inode->i_mutex after the filesystem has taken whatever locks it needs to ensure sanity. however, this typically violates the locking order of filesystems with th; /archives/xfs/2011-08/msg00122.html (7,630 bytes)
2. Re: [PATCH 0/2] splice: i_mutex vs splice write deadlock V2 (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Wed, 10 Aug 2011 06:19:21 -0400; Another case is ocfs2, which looks like a perfect candidate to be converted over to your infrastructure.; /archives/xfs/2011-08/msg00170.html (9,170 bytes)

Current List: 1 - 2
Page: [1]