From: Wu Fengguang <fengguang.wu@intel.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Avan Anishchuk <matimatik@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
Subject: Re: [PATCH] ramfs: fix double freeing s_fs_info on failed mount
Date: Tue, 7 Apr 2009 15:05:07 +0800 [thread overview]
Message-ID: <20090407070507.GA500@localhost> (raw)
In-Reply-To: <20090407065308.GA19470@elte.hu>
On Tue, Apr 07, 2009 at 02:53:08PM +0800, Ingo Molnar wrote:
>
> * Wu Fengguang <fengguang.wu@intel.com> wrote:
>
> > From: Ingo Molnar <mingo@elte.hu>
> >
> > If ramfs mount fails, s_fs_info will be freed twice in
> > ramfs_fill_super() and ramfs_kill_sb(), leading to kernel oops.
> >
> > Consolidate and beautify the code. Make sure s_fs_info and s_root
> > are in known good states.
> >
> > Acked-by: Wu Fengguang <fengguang.wu@intel.com>
> > Signed-off-by: Ingo Molnar <mingo@elte.hu>
>
> Nit: the commit is missing a Reported-by :)
>
> Linus might not insist on seeing his name mentioned yet another time
> in a commit, but it's generally good practice to always add bug
> report info and names.
>
> Note that in this case the really hard work was there: Linus had to
> spend at least 2 hours on tracking down and bisecting this bug. (and
> Linus probably did this super-fast compared to the average tester -
> most other bug reporters spend a day or more on bisection, limited
> by lack of practice and by the slowness of kernel builds on ordinary
> hardware.)
>
> So the real human effort was spent there, not in my 5 minutes on
> fixing the bug that Linus served on a plate - while the commit only
> credits me. That's not fair :)
Good point! Thank you very much for mentoring me on this whole process!
> See the tip:out-of-tree local commit i made and sent out.
Yes I've seen that, very comprehensive changelog and solid&pretty code!
Best regards,
Fengguang Wu
next prev parent reply other threads:[~2009-04-07 7:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-05 19:39 [GIT PULL] SLAB include file dependency fixes + kmemtrace updates Ingo Molnar
2009-04-05 19:56 ` Linus Torvalds
2009-04-05 20:02 ` Linus Torvalds
2009-04-07 1:51 ` Linus Torvalds
2009-04-07 3:51 ` Linus Torvalds
2009-04-07 4:20 ` Linus Torvalds
2009-04-07 4:45 ` Linus Torvalds
2009-04-07 5:02 ` Wu Fengguang
2009-04-07 5:28 ` [patch] ramfs: add support for "mode=" mount option, fix Ingo Molnar
2009-04-07 5:55 ` Wu Fengguang
2009-04-07 6:03 ` Ingo Molnar
2009-04-07 6:16 ` [PATCH] ramfs: fix double freeing s_fs_info on failed mount Wu Fengguang
2009-04-07 6:53 ` Ingo Molnar
2009-04-07 7:05 ` Wu Fengguang [this message]
2009-04-07 6:20 ` [PATCH] ramfs: add support for "mode=" mount option, fix Ingo Molnar
2009-04-07 5:30 ` [GIT PULL] SLAB include file dependency fixes + kmemtrace updates Wu Fengguang
2009-04-07 4:58 ` Ingo Molnar
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=20090407070507.GA500@localhost \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=eduard.munteanu@linux360.ro \
--cc=linux-kernel@vger.kernel.org \
--cc=matimatik@gmail.com \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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