From: Christoph Hellwig <hch@lst.de>
To: kbuild-all@lists.01.org
Subject: Re: [linux-next:master 2079/2594] fs/btrfs/volumes.c:6546 __btrfs_map_block() error: we previously assumed 'mirror_num_p' could be null (see line 6373)
Date: Wed, 24 Aug 2022 07:35:27 +0200 [thread overview]
Message-ID: <20220824053527.GA18584@lst.de> (raw)
In-Reply-To: <202208240734.u4Y7Q6sW-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 896 bytes --]
On Wed, Aug 24, 2022 at 08:28:26AM +0300, Dan Carpenter wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 05477f3653b82d8b3bcf39d2937d9893124976db
> commit: 51bf2819055847ce90006a368f8d2c07f408dd33 [2079/2594] btrfs: make the btrfs_io_context allocation in __btrfs_map_block optional
> config: nios2-randconfig-m031-20220824 (https://download.01.org/0day-ci/archive/20220824/202208240734.u4Y7Q6sW-lkp(a)intel.com/config)
> compiler: nios2-linux-gcc (GCC) 12.1.0
>
> If you fix the issue, kindly add following tag where applicable
> Reported-by: kernel test robot <lkp@intel.com>
> Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
>
> New smatch warnings:
The calling convention implies that either smap and mirror_num_p are both
NULL or neither. We could add an extra check to shut up the validator
if this really helps.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: kbuild@lists.01.org, Christoph Hellwig <hch@lst.de>,
lkp@intel.com, kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
David Sterba <dsterba@suse.com>,
Nikolay Borisov <nborisov@suse.com>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>
Subject: Re: [linux-next:master 2079/2594] fs/btrfs/volumes.c:6546 __btrfs_map_block() error: we previously assumed 'mirror_num_p' could be null (see line 6373)
Date: Wed, 24 Aug 2022 07:35:27 +0200 [thread overview]
Message-ID: <20220824053527.GA18584@lst.de> (raw)
In-Reply-To: <202208240734.u4Y7Q6sW-lkp@intel.com>
On Wed, Aug 24, 2022 at 08:28:26AM +0300, Dan Carpenter wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 05477f3653b82d8b3bcf39d2937d9893124976db
> commit: 51bf2819055847ce90006a368f8d2c07f408dd33 [2079/2594] btrfs: make the btrfs_io_context allocation in __btrfs_map_block optional
> config: nios2-randconfig-m031-20220824 (https://download.01.org/0day-ci/archive/20220824/202208240734.u4Y7Q6sW-lkp@intel.com/config)
> compiler: nios2-linux-gcc (GCC) 12.1.0
>
> If you fix the issue, kindly add following tag where applicable
> Reported-by: kernel test robot <lkp@intel.com>
> Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
>
> New smatch warnings:
The calling convention implies that either smap and mirror_num_p are both
NULL or neither. We could add an extra check to shut up the validator
if this really helps.
next prev parent reply other threads:[~2022-08-24 5:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 23:42 [linux-next:master 2079/2594] fs/btrfs/volumes.c:6546 __btrfs_map_block() error: we previously assumed 'mirror_num_p' could be null (see line 6373) kernel test robot
2022-08-24 5:28 ` Dan Carpenter
2022-08-24 5:28 ` Dan Carpenter
2022-08-24 5:35 ` Christoph Hellwig [this message]
2022-08-24 5:35 ` Christoph Hellwig
2022-08-24 6:21 ` Dan Carpenter
2022-08-24 6:21 ` Dan Carpenter
2022-08-24 6:21 ` Dan Carpenter
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=20220824053527.GA18584@lst.de \
--to=hch@lst.de \
--cc=kbuild-all@lists.01.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.