devfs
[Top] [All Lists]

Re: [PATCH][2.5.74] devfs lookup deadlock/stack corruption combined patc

To: Andrey Borzenkov <arvidjaar@xxxxxxx>
Subject: Re: [PATCH][2.5.74] devfs lookup deadlock/stack corruption combined patch
From: Andrew Morton <akpm@xxxxxxxx>
Date: Mon, 7 Jul 2003 14:00:10 -0700
Cc: linux-kernel@xxxxxxxxxxxxxxx, devfs@xxxxxxxxxxx
In-reply-to: <200307072306.15995.arvidjaar@mail.ru>
References: <E198K0q-000Am8-00.arvidjaar-mail-ru@f23.mail.ru> <20030706120315.261732bb.akpm@osdl.org> <20030706175405.518f680d.akpm@osdl.org> <200307072306.15995.arvidjaar@mail.ru>
Sender: devfs-bounce@xxxxxxxxxxx
Andrey Borzenkov <arvidjaar@xxxxxxx> wrote:
>
> I finally hit a painfully trivial way to reproduce another long standing 
> devfs 
> problem - deadlock between devfs_lookup and devfs_d_revalidate_wait.

uh.

> The current fix is to move re-acquire of i_sem after all 
> devfs_d_revalidate_wait waiters have been waked up.

Directory modifications appear to be under write_lock(&dir->u.dir.lock); so
that obvious problem is covered.  Your patch might introduce a race around
_devfs_get_vfs_inode() - two CPUs running that against the same inode at
the same time?

> Andrew, I slightly polished original stack corruption version to look more 
> consistent with the rest of devfs;

I think it's Lindent time.



<Prev in Thread] Current Thread [Next in Thread>