Re: races in ipathfs

2012-03-18 Thread Al Viro
On Sun, Mar 18, 2012 at 06:45:47PM +, Al Viro wrote: > On Thu, Jan 19, 2012 at 08:20:04PM +, Al Viro wrote: > > Use of qib_super is seriously racy. qibfs_add() (and worse, > > qibfs_remove()) can happen during qibfs_mount() and qibfs_kill_super(). > > [snip] > > FWIW, I've put a comp

Re: races in ipathfs

2012-03-18 Thread Al Viro
On Thu, Jan 19, 2012 at 08:20:04PM +, Al Viro wrote: > Use of qib_super is seriously racy. qibfs_add() (and worse, > qibfs_remove()) can happen during qibfs_mount() and qibfs_kill_super(). [snip] FWIW, I've put a completely untested patchset into git.kernel.org/pub/scm/linux/kernel/git

RE: races in ipathfs

2012-01-20 Thread Mike Marciniszyn
ath > Cc: linux-rdma@vger.kernel.org; linux-kernel > Subject: races in ipathfs > > Use of qib_super is seriously racy. qibfs_add() (and worse, > qibfs_remove()) can happen during qibfs_mount() and qibfs_kill_super(). > > 1) CPU1: qib_init_one(). The sucker is alloc

races in ipathfs

2012-01-19 Thread Al Viro
Use of qib_super is seriously racy. qibfs_add() (and worse, qibfs_remove()) can happen during qibfs_mount() and qibfs_kill_super(). 1) CPU1: qib_init_one(). The sucker is allocated and placed on the list. CPU2: ipathfs is mounted, directory created. CPU1: finally gets around to