All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: ./include/linux/sched/signal.h:83:28: error: field 'dumpable' has incomplete type
Date: Sun, 16 Aug 2026 18:01:04 +0200	[thread overview]
Message-ID: <202608161756.9RDdh6kA-lkp@intel.com> (raw)

:::::: 
:::::: Manual check reason: "low confidence bisect report"
:::::: 

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: "Eric W. Biederman" <ebiederm@xmission.com>
CC: 0day robot <lkp@intel.com>

tree:   https://github.com/intel-lab-lkp/linux/commits/Eric-W-Biederman/signal-Generalize-posixtimer_queue_sigqueue-into-enqueue_signal/20260815-092530
head:   abc0c99c9e0b38872512681cc481b9b3e90b46ca
commit: 4ac29929e23ac8ad0a07a62755058da989a62f5f signal: Use the thread killing in get_signal for coredumps
date:   2 days ago
:::::: branch date: 2 days ago
:::::: commit date: 2 days ago
config: arm64-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260816/202608161756.9RDdh6kA-lkp@intel.com/config)
compiler: aarch64-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260816/202608161756.9RDdh6kA-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/r/202608161756.9RDdh6kA-lkp@intel.com/

All errors (new ones prefixed by >>):

   In file included from ./include/linux/ptrace.h:7,
                    from ./include/linux/audit.h:13,
                    from kernel/capability.c:13:
>> ./include/linux/sched/signal.h:83:28: error: field 'dumpable' has incomplete type
      83 |         enum task_dumpable dumpable;
         |                            ^~~~~~~~


vim +/dumpable +83 ./include/linux/sched/signal.h

0258b5fd7c7124 Eric W. Biederman 2021-09-22  80  
0258b5fd7c7124 Eric W. Biederman 2021-09-22  81  struct core_state {
0258b5fd7c7124 Eric W. Biederman 2021-09-22  82  	atomic_t nr_threads;
4ac29929e23ac8 Eric W. Biederman 2026-07-03 @83  	enum task_dumpable dumpable;
0258b5fd7c7124 Eric W. Biederman 2021-09-22  84  	struct core_thread dumper;
0258b5fd7c7124 Eric W. Biederman 2021-09-22  85  	struct completion startup;
0258b5fd7c7124 Eric W. Biederman 2021-09-22  86  };
0258b5fd7c7124 Eric W. Biederman 2021-09-22  87  

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

                 reply	other threads:[~2026-08-16 16:01 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=202608161756.9RDdh6kA-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild@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 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.