All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Eric Sandeen <sandeen@redhat.com>, zippel@linux-m68k.org
Cc: linux-kernel@vger.kernel.org
Subject: fs/hfs/btree.c: new NULL dereference
Date: Mon, 14 Jan 2008 23:13:05 +0200	[thread overview]
Message-ID: <20080114211305.GI9847@does.not.exist> (raw)

The Coverity checker spotted the following NULL dereference introduced 
by commit cf0594625083111ae522496dc1c256f7476939c2:

<--  snip  -->

...
struct hfs_btree *hfs_btree_open(struct super_block *sb, u32 id, btree_keycmp keycmp)
{
...
        if (!tree->inode)
                goto free_tree;
...
 free_tree:
        tree->inode->i_mapping->a_ops = &hfs_aops;
...

<--  snip  -->

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


             reply	other threads:[~2008-01-14 21:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-14 21:13 Adrian Bunk [this message]
2008-01-14 21:35 ` fs/hfs/btree.c: new NULL dereference Eric Sandeen

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=20080114211305.GI9847@does.not.exist \
    --to=bunk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=zippel@linux-m68k.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.