linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [bug report] btrfs: error out if btrfs_attach_transaction() fails
Date: Fri, 13 Oct 2017 09:59:19 +0800	[thread overview]
Message-ID: <e15a3b37-f56b-abb5-2f75-4030d25e058f@oracle.com> (raw)
In-Reply-To: <20171012203900.dqdsfcpbfjyl7bea@mwanda>



   Thanks Dan! You are right. Will fix it.

Anand


On 10/13/2017 04:39 AM, Dan Carpenter wrote:
> Hello Anand Jain,
> 
> The patch 1eea2715ca9b: "btrfs: error out if
> btrfs_attach_transaction() fails" from Sep 28, 2017, leads to the
> following static checker warning:
> 
> 	fs/btrfs/volumes.c:2502 btrfs_init_new_device()
> 	error: 'trans' dereferencing possible ERR_PTR()
> 
> fs/btrfs/volumes.c
>    2479                  ret = btrfs_relocate_sys_chunks(fs_info);
>    2480                  if (ret < 0)
>    2481                          btrfs_handle_fs_error(fs_info, ret,
>    2482                                      "Failed to relocate sys chunks after device initialization. This can be fixed using the \"btrfs balance\" command.");
>    2483                  trans = btrfs_attach_transaction(root);
>    2484                  if (IS_ERR(trans)) {
>    2485                          if (PTR_ERR(trans) == -ENOENT)
>    2486                                  return 0;
>    2487                          ret = PTR_ERR(trans);
>    2488                          goto error_sysfs;
>                                  ^^^^^^^^^^^^^^^^
> We used to have a direct return here.
> 
>    2489                  }
>    2490                  ret = btrfs_commit_transaction(trans);
>    2491          }
>    2492
>    2493          /* Update ctime/mtime for libblkid */
>    2494          update_dev_time(device_path);
>    2495          return ret;
>    2496
>    2497  error_sysfs:
>    2498          btrfs_sysfs_rm_device_link(fs_info->fs_devices, device);
>    2499  error_trans:
>    2500          if (seeding_dev)
>    2501                  sb->s_flags |= MS_RDONLY;
>    2502          btrfs_end_transaction(trans);
>                                        ^^^^^^
> But now it's dereferencing an error pointer inside this function.
> 
>    2503          rcu_string_free(device->name);
>    2504          kfree(device);
>    2505  error:
>    2506          blkdev_put(bdev, FMODE_EXCL);
>    2507          if (seeding_dev && !unlocked) {
>    2508                  mutex_unlock(&uuid_mutex);
>    2509                  up_write(&sb->s_umount);
>    2510          }
>    2511          return ret;
>    2512  }
> 
> regards,
> dan carpenter
> 

  reply	other threads:[~2017-10-13  1:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-12 20:39 [bug report] btrfs: error out if btrfs_attach_transaction() fails Dan Carpenter
2017-10-13  1:59 ` Anand Jain [this message]
2017-10-13  2:16 ` [PATCH] btrfs: fix call to btrfs_end_transaction without a transaction handler Anand Jain
2017-10-16 14:07   ` David Sterba

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=e15a3b37-f56b-abb5-2f75-4030d25e058f@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=dan.carpenter@oracle.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;
as well as URLs for NNTP newsgroup(s).