public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Cyrill Gorcunov <gorcunov@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH 2/2] Fix possible leakage of blocks in UDF
Date: Fri, 01 Jun 2007 12:17:53 -0500	[thread overview]
Message-ID: <466054C1.3040100@sandeen.net> (raw)
In-Reply-To: <20070601100425.89537dda.akpm@linux-foundation.org>

Andrew Morton wrote:

> Recursive lock_kernel() is OK.

Oh, it is?  Clearly I am not well versed in the BKL... that's probably a 
good thing.... :)

Ok, let me look into it further.  I changed lock_kernel to 
udf_lock_kernel to complain & backtrace if we re-lock, and it always 
immediately hung after that; I assumed that was it.  I'll investigate 
further.

-Eric

  parent reply	other threads:[~2007-06-01 17:18 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-24 16:59 [PATCH 1/2] Fix possible UDF data corruption Jan Kara
2007-05-24 17:05 ` [PATCH 2/2] Fix possible leakage of blocks in UDF Jan Kara
2007-05-24 20:36   ` Jan Kara
2007-05-30 21:46     ` Eric Sandeen
2007-05-30 22:22       ` Eric Sandeen
2007-05-31 16:48         ` Cyrill Gorcunov
2007-05-31 17:42         ` Cyrill Gorcunov
2007-05-31 17:46           ` Eric Sandeen
2007-06-01 16:49             ` Cyrill Gorcunov
2007-06-01 17:04               ` Andrew Morton
2007-06-01 17:15                 ` Cyrill Gorcunov
2007-06-01 17:17                 ` Eric Sandeen [this message]
2007-06-01 17:48                   ` Cyrill Gorcunov
2007-06-01 17:51                     ` Eric Sandeen
2007-06-01 17:52                       ` Cyrill Gorcunov
2007-06-01 18:20                       ` Cyrill Gorcunov
2007-06-01 21:10       ` Jan Kara
2007-06-01 21:05         ` Eric Sandeen
2007-06-01 22:37         ` Eric Sandeen
2007-06-01 22:48           ` Andrew Morton
2007-06-02  5:17             ` Eric Sandeen
2007-06-02  5:43               ` Andrew Morton
2007-06-02  6:34                 ` Cyrill Gorcunov
2007-06-02  6:54                   ` Andrew Morton
2007-06-02  6:59                     ` Cyrill Gorcunov
2007-06-02  7:06                       ` Andrew Morton
2007-06-02 14:06                         ` Cyrill Gorcunov
2007-06-02 17:32                           ` Andrew Morton
2007-06-02 18:57                             ` Cyrill Gorcunov
2007-06-02 19:16                               ` Andrew Morton
2007-06-02 20:01                                 ` Cyrill Gorcunov
2007-06-02 22:49                                   ` Andrew Morton
2007-06-03  6:28                                     ` Cyrill Gorcunov
2007-06-03  7:22                                       ` Cyrill Gorcunov
2007-06-04 15:53         ` Cyrill Gorcunov
2007-05-24 17:20 ` [PATCH 1/2] Fix possible UDF data corruption Cyrill Gorcunov
2007-05-24 18:35   ` Andrew Morton
2007-05-24 18:53     ` Cyrill Gorcunov
2007-05-24 19:23     ` Cyrill Gorcunov
2007-05-24 19:36       ` Andrew Morton
2007-05-24 19:49         ` 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=466054C1.3040100@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=akpm@linux-foundation.org \
    --cc=gorcunov@gmail.com \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    /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