All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [chrome-os:chromeos-5.10 114/1031] drivers/tty/sysrq.c:456:40: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Thu, 17 Dec 2020 12:39:40 +0800	[thread overview]
Message-ID: <202012171237.FtA7iciF-lkp@intel.com> (raw)

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

tree:   https://chromium.googlesource.com/chromiumos/third_party/kernel chromeos-5.10
head:   73dbeef4571d1037d5e03374fad31195f60956cf
commit: 264a61835373f3600e2eed6966ca6240a98af38f [114/1031] CHROMIUM: sysrq: Added Chrome OS specific 'x' key
config: ia64-randconfig-s032-20201217 (attached as .config)
compiler: ia64-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-184-g1b896707-dirty
        git remote add chrome-os https://chromium.googlesource.com/chromiumos/third_party/kernel
        git fetch --no-tags chrome-os chromeos-5.10
        git checkout 264a61835373f3600e2eed6966ca6240a98af38f
        # 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=ia64 

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 >>)"
>> drivers/tty/sysrq.c:456:40: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected char const * @@     got char [noderef] __rcu * @@
   drivers/tty/sysrq.c:456:40: sparse:     expected char const *
   drivers/tty/sysrq.c:456:40: sparse:     got char [noderef] __rcu *
   drivers/tty/sysrq.c:150:13: sparse: sparse: context imbalance in 'sysrq_handle_crash' - unexpected unlock

vim +456 drivers/tty/sysrq.c

   441	
   442	/* send a signal to a process named comm if it has a certain parent */
   443	/* if parent is NULL, send to the first matching process */
   444	static void sysrq_x_cros_signal_process(char *comm, char *parent, int sig)
   445	{
   446		struct task_struct *p;
   447	
   448		read_lock(&tasklist_lock);
   449		for_each_process(p) {
   450			if (p->flags & (PF_KTHREAD | PF_EXITING))
   451				continue;
   452			if (is_global_init(p))
   453				continue;
   454			if (strncmp(p->comm, comm, TASK_COMM_LEN))
   455				continue;
 > 456			if (parent && strncmp(p->parent->comm, parent, TASK_COMM_LEN))
   457				continue;
   458	
   459			printk(KERN_INFO "%s: signal %d %s pid %u tgid %u\n",
   460			       __func__, sig, comm, p->pid, p->tgid);
   461			do_send_sig_info(sig, SEND_SIG_PRIV, p, true);
   462		}
   463		read_unlock(&tasklist_lock);
   464	}
   465	

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

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

             reply	other threads:[~2020-12-17  4:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-17  4:39 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-12-17  7:18 [chrome-os:chromeos-5.10 114/1031] drivers/tty/sysrq.c:456:40: sparse: sparse: incorrect type in argument 1 (different address spaces) 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=202012171237.FtA7iciF-lkp@intel.com \
    --to=lkp@intel.com \
    --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.