From: kernel test robot <lkp@intel.com>
To: Oleg Nesterov <oleg@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Kusaram Devineni <kusaram@devineni.in>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Jens Axboe <axboe@kernel.dk>, Kees Cook <kees@kernel.org>,
linux-kernel@vger.kernel.org, io-uring@vger.kernel.org
Subject: Re: [PATCH] signalfd: don't dequeue the forced fatal signals
Date: Wed, 8 Apr 2026 04:10:03 +0800 [thread overview]
Message-ID: <202604080450.mkKRp9Mk-lkp@intel.com> (raw)
In-Reply-To: <adKJMRkQJXEwHs-j@redhat.com>
Hi Oleg,
kernel test robot noticed the following build warnings:
[auto build test WARNING on brauner-vfs/vfs.all]
[also build test WARNING on akpm-mm/mm-everything kees/for-next/pstore kees/for-next/kspp linus/master v7.0-rc7 next-20260406]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Oleg-Nesterov/signalfd-don-t-dequeue-the-forced-fatal-signals/20260407-131556
base: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git vfs.all
patch link: https://lore.kernel.org/r/adKJMRkQJXEwHs-j%40redhat.com
patch subject: [PATCH] signalfd: don't dequeue the forced fatal signals
config: x86_64-randconfig-123-20260407 (https://download.01.org/0day-ci/archive/20260408/202604080450.mkKRp9Mk-lkp@intel.com/config)
compiler: gcc-13 (Debian 13.3.0-16) 13.3.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260408/202604080450.mkKRp9Mk-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/202604080450.mkKRp9Mk-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> fs/signalfd.c:53:40: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected struct k_sigaction *k @@ got struct k_sigaction [noderef] __rcu * @@
fs/signalfd.c:53:40: sparse: expected struct k_sigaction *k
fs/signalfd.c:53:40: sparse: got struct k_sigaction [noderef] __rcu *
fs/signalfd.c:69:33: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected struct wait_queue_head [usertype] *wait_address @@ got struct wait_queue_head [noderef] __rcu * @@
fs/signalfd.c:69:33: sparse: expected struct wait_queue_head [usertype] *wait_address
fs/signalfd.c:69:33: sparse: got struct wait_queue_head [noderef] __rcu *
fs/signalfd.c:71:31: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct spinlock [usertype] *lock @@ got struct spinlock [noderef] __rcu * @@
fs/signalfd.c:71:31: sparse: expected struct spinlock [usertype] *lock
fs/signalfd.c:71:31: sparse: got struct spinlock [noderef] __rcu *
fs/signalfd.c:76:33: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct spinlock [usertype] *lock @@ got struct spinlock [noderef] __rcu * @@
fs/signalfd.c:76:33: sparse: expected struct spinlock [usertype] *lock
fs/signalfd.c:76:33: sparse: got struct spinlock [noderef] __rcu *
fs/signalfd.c:110:32: sparse: sparse: cast removes address space '__user' of expression
fs/signalfd.c:128:33: sparse: sparse: cast removes address space '__user' of expression
fs/signalfd.c:131:33: sparse: sparse: cast removes address space '__user' of expression
fs/signalfd.c:135:33: sparse: sparse: cast removes address space '__user' of expression
fs/signalfd.c:151:32: sparse: sparse: cast removes address space '__user' of expression
fs/signalfd.c:155:38: sparse: sparse: cast removes address space '__user' of expression
fs/signalfd.c:175:31: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct spinlock [usertype] *lock @@ got struct spinlock [noderef] __rcu * @@
fs/signalfd.c:175:31: sparse: expected struct spinlock [usertype] *lock
fs/signalfd.c:175:31: sparse: got struct spinlock [noderef] __rcu *
fs/signalfd.c:185:41: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct spinlock [usertype] *lock @@ got struct spinlock [noderef] __rcu * @@
fs/signalfd.c:185:41: sparse: expected struct spinlock [usertype] *lock
fs/signalfd.c:185:41: sparse: got struct spinlock [noderef] __rcu *
fs/signalfd.c:189:32: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct wait_queue_head *wq_head @@ got struct wait_queue_head [noderef] __rcu * @@
fs/signalfd.c:189:32: sparse: expected struct wait_queue_head *wq_head
fs/signalfd.c:189:32: sparse: got struct wait_queue_head [noderef] __rcu *
fs/signalfd.c:199:41: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct spinlock [usertype] *lock @@ got struct spinlock [noderef] __rcu * @@
fs/signalfd.c:199:41: sparse: expected struct spinlock [usertype] *lock
fs/signalfd.c:199:41: sparse: got struct spinlock [noderef] __rcu *
fs/signalfd.c:201:39: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct spinlock [usertype] *lock @@ got struct spinlock [noderef] __rcu * @@
fs/signalfd.c:201:39: sparse: expected struct spinlock [usertype] *lock
fs/signalfd.c:201:39: sparse: got struct spinlock [noderef] __rcu *
fs/signalfd.c:204:33: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct spinlock [usertype] *lock @@ got struct spinlock [noderef] __rcu * @@
fs/signalfd.c:204:33: sparse: expected struct spinlock [usertype] *lock
fs/signalfd.c:204:33: sparse: got struct spinlock [noderef] __rcu *
fs/signalfd.c:206:35: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct wait_queue_head *wq_head @@ got struct wait_queue_head [noderef] __rcu * @@
fs/signalfd.c:206:35: sparse: expected struct wait_queue_head *wq_head
fs/signalfd.c:206:35: sparse: got struct wait_queue_head [noderef] __rcu *
fs/signalfd.c:305:39: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct spinlock [usertype] *lock @@ got struct spinlock [noderef] __rcu * @@
fs/signalfd.c:305:39: sparse: expected struct spinlock [usertype] *lock
fs/signalfd.c:305:39: sparse: got struct spinlock [noderef] __rcu *
fs/signalfd.c:307:41: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct spinlock [usertype] *lock @@ got struct spinlock [noderef] __rcu * @@
fs/signalfd.c:307:41: sparse: expected struct spinlock [usertype] *lock
fs/signalfd.c:307:41: sparse: got struct spinlock [noderef] __rcu *
fs/signalfd.c:309:17: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct wait_queue_head *wq_head @@ got struct wait_queue_head [noderef] __rcu * @@
fs/signalfd.c:309:17: sparse: expected struct wait_queue_head *wq_head
fs/signalfd.c:309:17: sparse: got struct wait_queue_head [noderef] __rcu *
vim +53 fs/signalfd.c
50
51 static void mk_sigmask(struct signalfd_ctx *ctx, sigset_t *sigmask)
52 {
> 53 struct k_sigaction *k = current->sighand->action;
54 int n;
55
56 *sigmask = ctx->sigmask;
57 for (n = 1; n <= _NSIG; ++n, ++k) {
58 if (k->sa.sa_flags & SA_IMMUTABLE)
59 sigaddset(sigmask, n);
60 }
61 }
62
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-04-07 20:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-05 16:09 [PATCH] signalfd: don't dequeue the forced fatal signals Oleg Nesterov
2026-04-06 4:39 ` Kees Cook
2026-04-06 13:32 ` Oleg Nesterov
2026-04-06 13:37 ` [PATCH v2] " Oleg Nesterov
2026-04-07 20:10 ` kernel test robot [this message]
2026-04-07 21:22 ` [PATCH] " Oleg Nesterov
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=202604080450.mkKRp9Mk-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=kees@kernel.org \
--cc=kusaram@devineni.in \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=oleg@redhat.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 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.