Re: Circular lock / deadlock in kernel client

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thursday 01 December 2011 wrote Amon Ott:
> On Thursday 01 December 2011 wrote Sage Weil:
> > On Thu, 1 Dec 2011, Amon Ott wrote:
> > > On Wednesday 30 November 2011 wrote Sage Weil:
> > > > I pushed a wip-i-ceph-lock branch to ceph-client.git that replaces
> > > > our (ab?)use of i_lock with a new i_ceph_lock in the ceph inode. 
> > > > This avoids being bitten by the lock ordering constraint imposed by
> > > > igrab(), which requires i_lock to safely take a reference to an inode
> > > > without racing with inode destruction.  This lets us keep two inode
> > > > list locks logically ordered inside i_ceph_lock (with i_lock as an
> > > > inner lock).
> > >
> > > I see the branch, but there is nothing new in it. Is that the right
> > > location? Maybe forgot to push?
> > >
> > > https://github.com/NewDreamNetwork/ceph-client/tree/wip-i-ceph-lock
> >
> > Oops, I pushed the wrong branch.  It's there now.
>
> Got the new commit, but it does not apply cleanly to my tree. I will try to
> get it merged tomorrow and retry. I cannot use kernel 3.2-pre here, the
> rest of the system needs to be stable.

Merged in and bug seems to be fixed. No more deadlock warnings today.

Amon Ott
-- 
Dr. Amon Ott
m-privacy GmbH           Tel: +49 30 24342334
Am Köllnischen Park 1    Fax: +49 30 24342336
10179 Berlin             http://www.m-privacy.de

Amtsgericht Charlottenburg, HRB 84946

Geschäftsführer:
 Dipl.-Kfm. Holger Maczkowsky,
 Roman Maczkowsky

GnuPG-Key-ID: 0x2DD3A649
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux