From: Ted Ts'o <tytso@mit.edu>
To: Dan Carpenter <error27@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: smatch stuff: -next: null dereference in ext4_readdir()
Date: Sun, 2 Jan 2011 18:11:22 -0500 [thread overview]
Message-ID: <20110102231122.GA11955@thunk.org> (raw)
In-Reply-To: <20110101134013.GI1886@bicker>
On Sat, Jan 01, 2011 at 04:40:13PM +0300, Dan Carpenter wrote:
> Hi Ted,
>
> There is a NULL dereference introduced in linux-next "ext4: Use
> ext4_error_file() to print the pathname to the corrupted inode"
Thanks for catching this! I'll fix up the bad patch in the ext4 patch
tree and regen the tree.
- Ted
prev parent reply other threads:[~2011-01-03 2:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-01 13:40 smatch stuff: -next: null dereference in ext4_readdir() Dan Carpenter
2011-01-02 23:11 ` Ted Ts'o [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=20110102231122.GA11955@thunk.org \
--to=tytso@mit.edu \
--cc=error27@gmail.com \
--cc=linux-ext4@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.