>>>>> Andrew Morton (AM) writes: AM> What lock protects the fields in struct ext[234]_reserve_window from being AM> concurrently modified by two CPUs? None, it seems. Ditto AM> ext[234]_reserve_window_node. i_mutex will cover it for write(), but not AM> for pageout over a file hole. If we end up with a zero- or negative-sized AM> window then odd things might happen. truncate_mutex? thanks, Alex - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: Boot failure with ext2 and initrds
- From: Andrew Morton <[email protected]>
- Re: Boot failure with ext2 and initrds
- References:
- 2.6.19-rc5-mm2
- From: Andrew Morton <[email protected]>
- Boot failure with ext2 and initrds
- From: [email protected] (Mel Gorman)
- Re: Boot failure with ext2 and initrds
- From: Hugh Dickins <[email protected]>
- Re: Boot failure with ext2 and initrds
- From: Andrew Morton <[email protected]>
- Re: Boot failure with ext2 and initrds
- From: Hugh Dickins <[email protected]>
- Re: Boot failure with ext2 and initrds
- From: Hugh Dickins <[email protected]>
- Re: Boot failure with ext2 and initrds
- From: Andrew Morton <[email protected]>
- Re: Boot failure with ext2 and initrds
- From: Mingming Cao <[email protected]>
- Re: Boot failure with ext2 and initrds
- From: Andrew Morton <[email protected]>
- Re: Boot failure with ext2 and initrds
- From: Mingming Cao <[email protected]>
- Re: Boot failure with ext2 and initrds
- From: Andrew Morton <[email protected]>
- 2.6.19-rc5-mm2
- Prev by Date: [patch] hotplug CPU: clean up hotcpu_notifier() use
- Next by Date: Re: [patch, -rc6] x86_64: UP build fixes
- Previous by thread: Re: Boot failure with ext2 and initrds
- Next by thread: Re: Boot failure with ext2 and initrds
- Index(es):
 |