From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: Eric Sandeen <sandeen@sandeen.net>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Cyrill Gorcunov <gorcunov@gmail.com>
Subject: Re: [PATCH 2/2] Fix possible leakage of blocks in UDF
Date: Mon, 4 Jun 2007 19:53:16 +0400 [thread overview]
Message-ID: <20070604155316.GA10438@cvg> (raw)
In-Reply-To: <20070601211036.GA23975@duck.suse.cz>
[Jan Kara - Fri, Jun 01, 2007 at 11:10:36PM +0200]
| On Wed 30-05-07 16:46:28, Eric Sandeen wrote:
| > Jan Kara wrote:
| > > Hello,
| > >
| > > On Thu 24-05-07 19:05:54, Jan Kara wrote:
| > >> Hello,
| > >>
| > >> attached is a patch that fixes possible leakage of free blocks / use of
| > >> free blocks in UDF (which spilled nice assertion failures I've added in my
| > >> first round of patches). More details in the changelog. Andrew, please apply.
| > >> Both changes have survived some time of fsx and fsstress testing so they
| > >> should be reasonably safe.
| > > Sorry for replying to myself but this patch had a minor problem of
| > > printing some bogus warnings when directories were deleted (I wonder why
| > > fsstress didn't find it). Attached is a new version of the patch without
| > > this problem.
| >
| > Jan, something seems busted here. I'm getting lockups when testing udf
| > on a single cpu with this last patch in place...
| Hmm, strange, I was also testing on UP and without problems. And I didn't
| change any locking...
|
| > I think it's the BKL stumbling on itself.
| >
| > for example...
| >
| > static int udf_symlink(struct inode * dir, struct dentry * dentry, const
| > char * symname)
| > {
| > ...
| > lock_kernel();
| > ...
| > out:
| > unlock_kernel();
| > return err;
| >
| > out_no_entry:
| > inode_dec_link_count(inode);
| > iput(inode);
| > goto out;
| > }
| >
| > but iput goes
| > iput->iput_final->drop_inode->udf_drop_inode->lock_kernel() again
| As Andrew already wrote, BKL is free to recurse...
|
| > looking for the right way around it but figured I'd ping you early :)
| Thanks for info - I'm now mostly out of email for a few days but I'll
| have a look at it as soon as I return.
|
| Honza
| --
| Jan Kara <jack@suse.cz>
| SuSE CR Labs
|
Hi Jan,
why can't we combine udf_delete_inode() with udf_drop_inode()?
It'll avoid deadlock.
Cyrill
next prev parent reply other threads:[~2007-06-04 15:54 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
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 [this message]
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=20070604155316.GA10438@cvg \
--to=gorcunov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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