public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	Jens Axboe <axboe@kernel.dk>, Eric Biggers <ebiggers@google.com>,
	Jan Kara <jack@suse.cz>
Subject: fs/super.c:1785:15: sparse: sparse: Using plain integer as NULL pointer
Date: Tue, 5 Dec 2023 01:32:30 +0800	[thread overview]
Message-ID: <202312050045.w3LqhNoX-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   33cc938e65a98f1d29d0a18403dbbee050dcad9a
commit: 439bc39b3cf0014b1b75075812f7ef0f8baa9674 fs: move sb_init_dio_done_wq out of direct-io.c
date:   10 months ago
config: hexagon-randconfig-r121-20231117 (https://download.01.org/0day-ci/archive/20231205/202312050045.w3LqhNoX-lkp@intel.com/config)
compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project.git 4a5ac14ee968ff0ad5d2cc1ffa0299048db4c88a)
reproduce: (https://download.01.org/0day-ci/archive/20231205/202312050045.w3LqhNoX-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202312050045.w3LqhNoX-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> fs/super.c:1785:15: sparse: sparse: Using plain integer as NULL pointer

vim +1785 fs/super.c

  1767	
  1768	/*
  1769	 * Create workqueue for deferred direct IO completions. We allocate the
  1770	 * workqueue when it's first needed. This avoids creating workqueue for
  1771	 * filesystems that don't need it and also allows us to create the workqueue
  1772	 * late enough so the we can include s_id in the name of the workqueue.
  1773	 */
  1774	int sb_init_dio_done_wq(struct super_block *sb)
  1775	{
  1776		struct workqueue_struct *old;
  1777		struct workqueue_struct *wq = alloc_workqueue("dio/%s",
  1778							      WQ_MEM_RECLAIM, 0,
  1779							      sb->s_id);
  1780		if (!wq)
  1781			return -ENOMEM;
  1782		/*
  1783		 * This has to be atomic as more DIOs can race to create the workqueue
  1784		 */
> 1785		old = cmpxchg(&sb->s_dio_done_wq, NULL, wq);

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

             reply	other threads:[~2023-12-04 17:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-04 17:32 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-17 18:54 fs/super.c:1785:15: sparse: sparse: Using plain integer as NULL pointer kernel test robot

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=202312050045.w3LqhNoX-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=axboe@kernel.dk \
    --cc=ebiggers@google.com \
    --cc=hch@lst.de \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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