From: Jan Kara <jack@suse.cz>
To: Suzuki K P <suzuki@in.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>,
vs@namesys.com, lkml <linux-kernel@vger.kernel.org>,
Dale Mosby <k7fw@us.ibm.com>
Subject: Re: [RFC] Patch to fix reiserfs bad path release panic on 2.6.19-rc1
Date: Wed, 18 Oct 2006 10:05:47 +0200 [thread overview]
Message-ID: <20061018080547.GD19879@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <45357F73.9010302@in.ibm.com>
Hello,
> * fix reiserfs/inode.c : restart_transaction() to release the path in all cases.
>
> The restart_transaction() doesn't release the path when the the
> journal handle has a refcount > 1. This would trigger a
> reiserfs_panic() if we encounter an -ENOSPC / -EDQUOT in
> reiserfs_get_block().
Yes, your analysis seems to be correct. I've looked at places where
restart_transaction() is called and all expect path to be released.
> Signed-off-by: Suzuki K P <suzuki@in.ibm.com>
You can add:
Signed-off-by: Jan Kara <jack@suse.cz>
BTW: The more appropriate audience for this patch is at
reiserfs-list@namesys.com.
Honza
> Index: linux-2.6.19-rc1/fs/reiserfs/inode.c
> ===================================================================
> --- linux-2.6.19-rc1.orig/fs/reiserfs/inode.c 2006-10-12 02:13:12.000000000 -0700
> +++ linux-2.6.19-rc1/fs/reiserfs/inode.c 2006-10-13 16:38:32.000000000 -0700
> @@ -216,11 +216,12 @@
> BUG_ON(!th->t_trans_id);
> BUG_ON(!th->t_refcount);
>
> + pathrelse(path);
> +
> /* we cannot restart while nested */
> if (th->t_refcount > 1) {
> return 0;
> }
> - pathrelse(path);
> reiserfs_update_sd(th, inode);
> err = journal_end(th, s, len);
> if (!err) {
--
Jan Kara <jack@suse.cz>
SuSE CR Labs
prev parent reply other threads:[~2006-10-18 8:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 1:12 Suzuki K P
2006-10-18 8:05 ` Jan Kara [this message]
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=20061018080547.GD19879@atrey.karlin.mff.cuni.cz \
--to=jack@suse.cz \
--cc=akpm@osdl.org \
--cc=k7fw@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=suzuki@in.ibm.com \
--cc=vs@namesys.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
all inboxes | Powered by JetHome®