From: "Jörn Engel" <joern@logfs.org>
To: Kevin Cernekee <cernekee@gmail.com>
Cc: linux-kernel@vger.kernel.org, logfs@logfs.org
Subject: Re: [PATCH] LogFS: Fix oops on failed mount
Date: Thu, 15 Apr 2010 08:16:15 +0200 [thread overview]
Message-ID: <20100415061615.GA2382@logfs.org> (raw)
In-Reply-To: <621ed5fa50005b6ea02cff222037d3702a4d59b0@localhost.localdomain>
On Wed, 14 April 2010 17:56:10 -0700, Kevin Cernekee wrote:
>
> logfs_kill_sb() calls mempool_destroy() on super->s_alias_pool . But if
> logfs_kill_sb() is being called because the mount failed (e.g.
> __logfs_read_sb() returned -EIO) this pointer will still be NULL,
> resulting in a kernel oops.
>
> Signed-off-by: Kevin Cernekee <cernekee@gmail.com>
> ---
> fs/logfs/super.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/fs/logfs/super.c b/fs/logfs/super.c
> index b60bfac..f817713 100644
> --- a/fs/logfs/super.c
> +++ b/fs/logfs/super.c
> @@ -517,7 +517,8 @@ static void logfs_kill_sb(struct super_block *sb)
> __free_page(super->s_erase_page);
> super->s_devops->put_device(sb);
> mempool_destroy(super->s_btree_pool);
> - mempool_destroy(super->s_alias_pool);
> + if (super->s_alias_pool)
> + mempool_destroy(super->s_alias_pool);
> kfree(super);
> log_super("LogFS: Finished unmounting\n");
> }
That shouldn't have happened. I fixed this bug in a patch from almost
exactly one month ago. But when moving patches from a test tree, this
one patch got lost. Added to my release tree now - finally:
git://git.kernel.org/pub/scm/linux/kernel/git/joern/logfs.git
Sorry that you had to step into that turd and thank you for shoving my
nose into it. I'll try to be a good dog and not do it again.
Jörn
--
When you close your hand, you own nothing. When you open it up, you
own the whole world.
-- Li Mu Bai in Tiger & Dragon
prev parent reply other threads:[~2010-04-15 6:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-15 0:56 [PATCH] LogFS: Fix oops on failed mount Kevin Cernekee
2010-04-15 6:16 ` Jörn Engel [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=20100415061615.GA2382@logfs.org \
--to=joern@logfs.org \
--cc=cernekee@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=logfs@logfs.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