From: Andreas Gruenbacher <agruenba@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] GFS2: Fix potential NULL dereference in gfs2_alloc_inode
Date: Mon, 02 Mar 2015 18:05:15 +0100 [thread overview]
Message-ID: <54F4984B.3090501@redhat.com> (raw)
In-Reply-To: <54F4900E.4060808@redhat.com>
On 03/02/2015 05:30 PM, Andrew Price wrote:
> On 02/03/15 16:17, Steven Whitehouse wrote:
>> Hi,
>>
>> On 02/03/15 16:15, Andrew Price wrote:
> Ah, so it is. Self-NACK then.
The patch itself is still worth it though, it's not self-evident ip and
&ip->i_inode are the same.
Andreas
next prev parent reply other threads:[~2015-03-02 17:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 16:15 [Cluster-devel] [PATCH] GFS2: Fix potential NULL dereference in gfs2_alloc_inode Andrew Price
2015-03-02 16:17 ` Steven Whitehouse
2015-03-02 16:30 ` Andrew Price
2015-03-02 17:05 ` Andreas Gruenbacher [this message]
2015-03-02 17:31 ` [Cluster-devel] [PATCH] GFS2: Improve readability of gfs2_alloc_inode Andrew Price
2015-03-03 14:57 ` Bob Peterson
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=54F4984B.3090501@redhat.com \
--to=agruenba@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).