From: Florian Mickler <florian@mickler.org>
To: unlisted-recipients:; (no To-header on input)
Cc: Prasad Joshi <prasadjoshi124@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Joern <joern@logfs.org>,
logfs@logfs.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/1] LogFS: Kernel BUG at readwrite.c:1193
Date: Mon, 6 Dec 2010 18:09:22 +0100 [thread overview]
Message-ID: <20101206180922.5f7fa3c1@schatten.dmk.lab> (raw)
In-Reply-To: <AANLkTikfu-AZNbZDrGqhca8hGXMrOwA1yJdZJRs0qq-Y@mail.gmail.com>
Hi,
On Tue, 16 Nov 2010 16:54:17 +0000
Prasad Joshi <prasadjoshi124@gmail.com> wrote:
> This happens when __logfs_create() tries to write a new inode to the
> disk which is full.
>
> __logfs_create() associates the transaction pointer with inode. During
> the logfs_write_inode() function call chain this transaction pointer
> is moved from inode to page->private using function move_inode_to_page
> (do_write_inode() -> inode_to_page() -> move_inode_to_page)
>
> When the write inode fails, the transaction is aborted and iput is
> called on the failed inode. During delete_inode the same transaction
> pointer associated with the page is getting used. Thus causing kernel
> BUG.
>
> The patch checks for error in write_inode() and restores the
> page->private to NULL.
>
>
This fixes https://bugzilla.kernel.org/show_bug.cgi?id=20162 . Can
someone please review? Any comments?
> Signed-off-by: Prasad Joshi <prasadjoshi124@gmail.com>
> ---
> diff --git a/fs/logfs/readwrite.c b/fs/logfs/readwrite.c
> index 6127baf..ee99a9f 100644
> --- a/fs/logfs/readwrite.c
> +++ b/fs/logfs/readwrite.c
> @@ -1994,6 +1994,9 @@ static int do_write_inode(struct inode *inode)
>
> /* FIXME: transaction is part of logfs_block now. Is that enough? */
> err = logfs_write_buf(master_inode, page, 0);
> + if (err)
> + move_page_to_inode(inode, page);
> +
> logfs_put_write_page(page);
> return err;
> }
>
>
>
> ---------- Forwarded message ----------
> From: <bugzilla-daemon@bugzilla.kernel.org>
> Date: Tue, Nov 16, 2010 at 3:20 PM
> Subject: [Bug 20162] [LogFS][2.6.36.rc7+] Kernel BUG at readwrite.c:1193
> To: prasadjoshi124@gmail.com
>
>
> https://bugzilla.kernel.org/show_bug.cgi?id=20162
>
>
> Florian Mickler <florian@mickler.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Status|NEW |RESOLVED
> CC| |florian@mickler.org
> Resolution| |PATCH_ALREADY_AVAILABLE
>
>
>
>
> --- Comment #2 from Florian Mickler <florian@mickler.org> 2010-11-16
> 15:20:46 ---
> Can you submit that patch to lkml and cc the logfs maintainer and the logfs
> list?
> (Joern Engel <joern@logfs.org>, logfs@logfs.org, linux-kernel@vger.kernel.org)
>
> See Documentation/SubmittingPatches
>
> Patch: https://bugzilla.kernel.org/show_bug.cgi?id=20162#c1
>
> --
> Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug.
prev parent reply other threads:[~2010-12-06 17:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 16:54 Prasad Joshi
2010-12-06 17:09 ` Florian Mickler [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=20101206180922.5f7fa3c1@schatten.dmk.lab \
--to=florian@mickler.org \
--cc=akpm@linux-foundation.org \
--cc=joern@logfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=logfs@logfs.org \
--cc=prasadjoshi124@gmail.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
Powered by JetHome