From: David Sterba <dsterba@suse.cz>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: nborisov@suse.com, linux-btrfs@vger.kernel.org
Subject: Re: [bug report] btrfs: remove err variable from btrfs_get_extent
Date: Thu, 3 Sep 2020 17:12:39 +0200 [thread overview]
Message-ID: <20200903151239.GV28318@twin.jikos.cz> (raw)
In-Reply-To: <20200903092705.GA392335@mwanda>
On Thu, Sep 03, 2020 at 12:27:05PM +0300, Dan Carpenter wrote:
> Hello Nikolay Borisov,
>
> The patch 85b1eebdaf1d: "btrfs: remove err variable from
> btrfs_get_extent" from Aug 3, 2020, leads to the following static
> checker warning:
>
> fs/btrfs/inode.c:6737 btrfs_get_extent()
> error: passing non negative 1 to ERR_PTR
Thanks for the report, Nikolay sent a fixup and that's been folded to
the original patch.
prev parent reply other threads:[~2020-09-03 15:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 9:27 [bug report] btrfs: remove err variable from btrfs_get_extent Dan Carpenter
2020-09-03 15:12 ` David Sterba [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=20200903151239.GV28318@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=dan.carpenter@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.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).