public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org,
	Michael Halcrow <mhalcrow@us.ibm.com>,
	Eric Sandeen <sandeen@redhat.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [v2.6.26-rc1] possible circular locking in ecryptfs
Date: Sun, 18 May 2008 17:27:41 +0400	[thread overview]
Message-ID: <20080518132741.GL6948@cvg> (raw)
In-Reply-To: <20080518114020.GA14889@elte.hu>

[Ingo Molnar - Sun, May 18, 2008 at 01:40:20PM +0200]
| 
| * Cyrill Gorcunov <gorcunov@gmail.com> wrote:
| 
| > [Ingo Molnar - Fri, May 09, 2008 at 11:44:23AM +0200]
| > | 
| > | * Ingo Molnar <mingo@elte.hu> wrote:
| > | 
| > | > x86.git testing found the following "possible circular locking" 
| > | > lockdep warning, generated by the ecryptfs code:
| > | 
| > | the correct URL for the config is:
| > | 
| > |   http://redhat.com/~mingo/misc/config-Wed_May__7_16_17_31_CEST_2008.bad
| > | 
| > | this is reproducible, it happened a second time since i originally 
| > | reported it.
| > | 
| > | 	Ingo
| > 
| > Hi Ingo, I've just sent patch, could you test it, please?
| > 
| > http://lkml.org/lkml/2008/5/10/20
| 
| 

well, i've found one missed unlock and a few a bit wrong lock pathes,
will fix them soon (seems one of that pathes is my fault)

		- Cyrill -

  parent reply	other threads:[~2008-05-18 13:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-07 20:02 [v2.6.26-rc1] possible circular locking in ecryptfs Ingo Molnar
2008-05-09  9:44 ` Ingo Molnar
2008-05-10  8:47   ` Cyrill Gorcunov
2008-05-18 11:40     ` Ingo Molnar
2008-05-18 11:46       ` Cyrill Gorcunov
2008-05-18 13:27       ` Cyrill Gorcunov [this message]
2008-05-18 15:10       ` Cyrill Gorcunov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080518132741.GL6948@cvg \
    --to=gorcunov@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhalcrow@us.ibm.com \
    --cc=mingo@elte.hu \
    --cc=sandeen@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox