Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: linux-btrfs@vger.kernel.org
Cc: sensille@gmx.net
Subject: re: btrfs: initial readahead code and prototypes
Date: Thu, 17 May 2012 10:14:46 +0300	[thread overview]
Message-ID: <20120517071446.GI14660@elgon.mountain> (raw)

Hi, I'm working on some new Smatch code and it complains about this
patch from last year. -Dan

----
This is a semi-automatic email about new static checker warnings.

The patch 7414a03fbf9e: "btrfs: initial readahead code and 
prototypes" from May 23, 2011, leads to the following Smatch 
complaint:

fs/btrfs/reada.c:147 __readahead_hook()
	 error: we previously assumed 'eb' could be null (see line 122)

fs/btrfs/reada.c
   121	
   122		if (eb)
                   ^^^^
Checked here.

   123			level = btrfs_header_level(eb);
   124	
   125		/* find extent */
   126		spin_lock(&fs_info->reada_lock);
   127		re = radix_tree_lookup(&fs_info->reada_tree, index);
   128		if (re)
   129			kref_get(&re->refcnt);
   130		spin_unlock(&fs_info->reada_lock);
   131	
   132		if (!re)
   133			return -1;
   134	
   135		spin_lock(&re->lock);
   136		/*
   137		 * just take the full list from the extent. afterwards we
   138		 * don't need the lock anymore
   139		 */
   140		list_replace_init(&re->extctl, &list);
   141		for_dev = re->scheduled_for;
   142		re->scheduled_for = NULL;
   143		spin_unlock(&re->lock);
   144	
   145		if (err == 0) {
   146			nritems = level ? btrfs_header_nritems(eb) : 0;
                                  ^^^^^
Checked here again indirectly.

   147			generation = btrfs_header_generation(eb);
                                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^
Dereferenced inside function without checking.

   148			/*
   149			 * FIXME: currently we just set nritems to 0 if this is a leaf,

regards,
dan carpenter


             reply	other threads:[~2012-05-17  7:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-17  7:14 Dan Carpenter [this message]
2012-05-17 13:31 ` btrfs: initial readahead code and prototypes Arne Jansen
2012-05-17 13:46   ` Dan Carpenter
2012-05-17 15:33     ` Arne Jansen

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=20120517071446.GI14660@elgon.mountain \
    --to=dan.carpenter@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sensille@gmx.net \
    /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