linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 67/7280] fs/mount_notify.c:130:1: sparse: sparse: Using plain integer as NULL pointer
Date: Mon, 23 Nov 2020 10:59:35 +0800	[thread overview]
Message-ID: <202011231034.A5IR8f8M-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2181 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   95065cb54210eba86bed10cb2118041524d54573
commit: 4cd92d064cb0be72e56913d5213a3f9782d80e76 [67/7280] watch_queue: Implement mount topology and attribute change notifications
config: s390-randconfig-s032-20201123 (attached as .config)
compiler: s390-linux-gcc (GCC) 9.3.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # apt-get install sparse
        # sparse version: v0.6.3-134-gb59dbdaf-dirty
        # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=4cd92d064cb0be72e56913d5213a3f9782d80e76
        git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
        git fetch --no-tags linux-next master
        git checkout 4cd92d064cb0be72e56913d5213a3f9782d80e76
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=s390 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>


"sparse warnings: (new ones prefixed by >>)"
>> fs/mount_notify.c:130:1: sparse: sparse: Using plain integer as NULL pointer
>> fs/mount_notify.c:130:1: sparse: sparse: Using plain integer as NULL pointer
   fs/mount_notify.c:31:9: sparse: sparse: context imbalance in 'post_mount_notification' - different lock contexts for basic block

vim +130 fs/mount_notify.c

   121	
   122	/**
   123	 * sys_watch_mount - Watch for mount topology/attribute changes
   124	 * @dfd: Base directory to pathwalk from or fd referring to mount.
   125	 * @filename: Path to mount to place the watch upon
   126	 * @at_flags: Pathwalk control flags
   127	 * @watch_fd: The watch queue to send notifications to.
   128	 * @watch_id: The watch ID to be placed in the notification (-1 to remove watch)
   129	 */
 > 130	SYSCALL_DEFINE5(watch_mount,

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 16242 bytes --]

                 reply	other threads:[~2020-11-23  3:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202011231034.A5IR8f8M-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dhowells@redhat.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.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).