On Thu, 12 Oct 2006 14:28:20 +0200 Jan Kara <[email protected]> wrote: > Where can we call > journal_dirty_data() without PageLock? block_write_full_page() will unlock the page, so ext3_writepage() will run journal_dirty_data_fn() against an unlocked page. I haven't looked into the exact details of the race, but it should be addressable via jbd_lock_bh_state() or j_list_lock coverage. - 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: 2.6.18 ext3 panic.
- From: Eric Sandeen <[email protected]>
- Re: 2.6.18 ext3 panic.
- From: Eric Sandeen <[email protected]>
- Re: 2.6.18 ext3 panic.
- References:
- Re: 2.6.18 ext3 panic.
- From: Dave Jones <[email protected]>
- Re: 2.6.18 ext3 panic.
- From: Jan Kara <[email protected]>
- Re: 2.6.18 ext3 panic.
- From: Eric Sandeen <[email protected]>
- Re: 2.6.18 ext3 panic.
- From: Badari Pulavarty <[email protected]>
- Re: 2.6.18 ext3 panic.
- From: Eric Sandeen <[email protected]>
- Re: 2.6.18 ext3 panic.
- From: Jan Kara <[email protected]>
- Re: 2.6.18 ext3 panic.
- From: Eric Sandeen <[email protected]>
- Re: 2.6.18 ext3 panic.
- From: Jan Kara <[email protected]>
- Re: 2.6.18 ext3 panic.
- From: Badari Pulavarty <[email protected]>
- Re: 2.6.18 ext3 panic.
- From: Eric Sandeen <[email protected]>
- Re: 2.6.18 ext3 panic.
- From: Jan Kara <[email protected]>
- Re: 2.6.18 ext3 panic.
- Prev by Date: Re: [PATCH] ocfs2: delete redundant memcmp()
- Next by Date: Re: [stable] [patch 00/67] 2.6.18-stable review
- Previous by thread: Re: 2.6.18 ext3 panic.
- Next by thread: Re: 2.6.18 ext3 panic.
- Index(es):
 |