Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+18\/27\]\s+xfs\:\s+Convert\s+to\s+new\s+freezing\s+code\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+18\/27\]\s+xfs\:\s+Convert\s+to\s+new\s+freezing\s+code\s*$/: 7 ]

Total 7 documents matching your query.

1. [PATCH 18/27] xfs: Convert to new freezing code (score: 1): Author: Jan Kara <jack@xxxxxxx>; Date: Mon, 16 Apr 2012 18:13:56 +0200; Generic code now blocks all writers from standard write paths. So we add blocking of all writers coming from ioctl (we get a protection of ioctl against racing remount read-only as a bonus) and conve; /archives/xfs/2012-04/msg00824.html (21,187 bytes)
2. [PATCH 18/27] xfs: Convert to new freezing code (score: 1): Author: Jan Kara <jack@xxxxxxx>; Date: Sat, 2 Jun 2012 00:30:32 +0200; Generic code now blocks all writers from standard write paths. So we add blocking of all writers coming from ioctl (we get a protection of ioctl against racing remount read-only as a bonus) and conve; /archives/xfs/2012-06/msg00015.html (22,565 bytes)
3. Re: [PATCH 18/27] xfs: Convert to new freezing code (score: 1): Author: Dave Chinner <dchinner@xxxxxxxxxx>; Date: Tue, 5 Jun 2012 14:15:46 +1000; I don't think this will apply to a current TOT XFS - the end_io context hunks look wrong. Perhaps your rebased this before the XFS tree was merged? Oh, that's rather ugly. If this is necessary where; /archives/xfs/2012-06/msg00027.html (11,324 bytes)
4. Re: [PATCH 18/27] xfs: Convert to new freezing code (score: 1): Author: Jan Kara <jack@xxxxxxx>; Date: Tue, 5 Jun 2012 10:43:21 +0200; Umm, doesn't look like that. I've based my patches on top of 51eab603f5c86dd1eae4c525df3e7f7eeab401d6 which is after XFS merge. This lockdep magic is necessary because lockdep freaks out if you acqui; /archives/xfs/2012-06/msg00034.html (12,853 bytes)
5. [PATCH 18/27] xfs: Convert to new freezing code (score: 1): Author: Jan Kara <jack@xxxxxxx>; Date: Tue, 12 Jun 2012 16:20:39 +0200; Generic code now blocks all writers from standard write paths. So we add blocking of all writers coming from ioctl (we get a protection of ioctl against racing remount read-only as a bonus) and conve; /archives/xfs/2012-06/msg00159.html (23,136 bytes)
6. Re: [PATCH 18/27] xfs: Convert to new freezing code (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Tue, 12 Jun 2012 10:23:47 -0400; I'll need some time to get through the whole series, but repeated use of constructs like this really screams for a helper abstracting it out and documenting it.; /archives/xfs/2012-06/msg00161.html (8,589 bytes)
7. Re: [PATCH 18/27] xfs: Convert to new freezing code (score: 1): Author: Jan Kara <jack@xxxxxxx>; Date: Tue, 12 Jun 2012 16:32:20 +0200; It's there twice and only in XFS because XFS needs to pass the freeze protection (along with a transaction) to a worker thread. I'm not against a helper but then it should probably be in a form to al; /archives/xfs/2012-06/msg00162.html (9,332 bytes)

Current List: 1 - 7
Page: [1]