From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: "Ted Ts'o" <tytso@mit.edu>, Christoph Hellwig <hch@infradead.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Li Zefan <lizf@cn.fujitsu.com>,
Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-ext4@vger.kernel.org,
Frederic Weisbecker <fweisbec@gmail.com>
Cc: kosaki.motohiro@jp.fujitsu.com
Subject: Re: [BUG] ext4 trace events cause NULL pointer dereferences
Date: Fri, 23 Jul 2010 14:47:33 +0900 (JST) [thread overview]
Message-ID: <20100723144549.88BA.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <20100723011315.GC16373@thunk.org>
> On Thu, Jul 22, 2010 at 01:49:57AM -0400, Christoph Hellwig wrote:
> >
> > I think ext4 is simply using an incorrectly typed tracepoint here.
> > If you want it to be useful in any way it needs a sb paramter and
> > an optional inode paramter, not the allocation context.
>
> I agree; this is the patch that I had whipped up to fix the problem.
> (See below)
I'm not familiar ext4 so much. but you patch seems very nice!
thank you :)
>
> > Also the whole ext4_mb_release_group_pa function seems to be a bit
> > misdesigned. The code using ac is a totally separate block at the
> > end of the function and does work that's unrelated to the rest
> > of the function. Just making it a separate helper can calling it
> > only from those places that have the allocation context would make
> > the code more clear.
>
> I need to look more closely at this. If I had time there would be a
> lot of things that I'd be refactoring and cleaning up in mballoc.c....
next prev parent reply other threads:[~2010-07-23 5:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 8:48 Li Zefan
2010-07-21 13:31 ` KOSAKI Motohiro
2010-07-21 14:16 ` Steven Rostedt
2010-07-21 14:21 ` Frederic Weisbecker
2010-07-22 5:45 ` Li Zefan
2010-07-22 5:49 ` Christoph Hellwig
2010-07-23 1:13 ` Ted Ts'o
2010-07-23 5:47 ` KOSAKI Motohiro [this message]
2010-07-23 9:11 ` Theodore Tso
2010-07-23 9:19 ` Li Zefan
2010-07-26 2:20 ` Li Zefan
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=20100723144549.88BA.A69D9226@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=fweisbec@gmail.com \
--cc=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=rostedt@goodmis.org \
--cc=tytso@mit.edu \
/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®