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: seccomp_notif_inject.c:(.text+0x3405): warning: the use of `mktemp' is dangerous, better use `mkstemp' or `mkdtemp'
Date: Sat, 16 May 2026 01:54:00 +0200	[thread overview]
Message-ID: <202605160129.SPNAAVNH-lkp@intel.com> (raw)

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

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Cong Wang <cwang@multikernel.io>
CC: 0day robot <lkp@intel.com>

tree:   https://github.com/intel-lab-lkp/linux/commits/Cong-Wang/seccomp-add-SECCOMP_IOCTL_NOTIF_INJECT-for-race-free-unotify/20260515-180940
head:   d097e2ffff248ce5ca6256ff90f5a33c3f99d970
commit: 7aff4bdbdf27d35bb39c8ee1eea18ef3e4bbc23f selftests/seccomp: add seccomp_notif_inject coverage
date:   14 hours ago
:::::: branch date: 14 hours ago
:::::: commit date: 14 hours ago
config: i386-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260516/202605160129.SPNAAVNH-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260516/202605160129.SPNAAVNH-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/202605160129.SPNAAVNH-lkp@intel.com/

All warnings (new ones prefixed by >>):

   /usr/bin/ld: /tmp/ccLVDGuk.o: in function `notif_inject_bind':
>> seccomp_notif_inject.c:(.text+0x3405): warning: the use of `mktemp' is dangerous, better use `mkstemp' or `mkdtemp'

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

                 reply	other threads:[~2026-05-15 23:54 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=202605160129.SPNAAVNH-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.