From: Chris Mason <chris.mason@oracle.com>
To: Dan Carpenter <error27@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [patch] avoid null deref in unpin_extent_cache()
Date: Wed, 11 Nov 2009 16:26:32 -0500 [thread overview]
Message-ID: <20091111212632.GB2898@think> (raw)
In-Reply-To: <alpine.DEB.2.00.0911072313580.30287@bicker>
On Tue, Nov 10, 2009 at 11:01:43AM +0200, Dan Carpenter wrote:
> I re-orderred the checks to avoid dereferencing "em" if it was null.
Thanks, I've put this into the master branch of the btrfs unstable tree.
-chris
prev parent reply other threads:[~2009-11-11 21:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 9:01 [patch] avoid null deref in unpin_extent_cache() Dan Carpenter
2009-11-11 21:26 ` Chris Mason [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=20091111212632.GB2898@think \
--to=chris.mason@oracle.com \
--cc=error27@gmail.com \
--cc=linux-btrfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox