From: kernel test robot <oliver.sang@intel.com>
To: Namjae Jeon <linkinjeon@kernel.org>
Cc: lkp@intel.com, "Darrick J. Wong" <djwong@kernel.org>,
linux-fsdevel@vger.kernel.org, oliver.sang@intel.com,
oe-lkp@lists.linux.dev, Christoph Hellwig <hch@lst.de>,
ltp@lists.linux.it
Subject: [LTP] [linux-next:master] [exfat] 07d67f3e90: invoked_oom-killer:gfp_mask=0x
Date: Thu, 11 Jun 2026 15:28:35 +0800 [thread overview]
Message-ID: <202606110923.2d2a1a13-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "invoked_oom-killer:gfp_mask=0x" on:
commit: 07d67f3e9083bc976b34d5d9183f87f0afc7deed ("exfat: add iomap buffered I/O support")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master a87737435cfa134f9cdcc696ba3080759d04cf72]
in testcase: ltp
version:
with following parameters:
disk: 1SSD
fs: ext4
test: syscalls-06
config: x86_64-rhel-9.4-ltp
compiler: gcc-14
test machine: 8 threads Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz (Skylake) with 16G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
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 <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202606110923.2d2a1a13-lkp@intel.com
kern :info : [ 465.291318] [ T10063] BTRFS info (device loop0): last unmount of filesystem 4c3cfb15-a618-4082-907b-517e4751b46d
kern :info : [ 465.335911] [ T10157] Adding 1020k swap on mntpoint/swapfile01. Priority:-1 extents:1 across:1020k SS
kern :info : [ 466.585441] [ T10157] Adding 131068k swap on mntpoint/swapfile01. Priority:-1 extents:1 across:131068k SS
kern :err : [ 467.591291] [ T10170] swapon: swapfile has holes
kern :err : [ 467.608966] [ T10170] swapon: swapfile has holes
kern :warn : [ 467.703015] [ T10170] swapon01 invoked oom-killer: gfp_mask=0xcc0(GFP_KERNEL), order=0, oom_score_adj=0
kern :warn : [ 467.712815] [ T10170] CPU: 1 UID: 0 PID: 10170 Comm: swapon01 Tainted: G OE 7.1.0-rc4+ #1 PREEMPT(lazy)
kern :warn : [ 467.712821] [ T10170] Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
kern :warn : [ 467.712822] [ T10170] Hardware name: System manufacturer System Product Name/Z170I PRO GAMING, BIOS 3805 05/16/2018
kern :warn : [ 467.712824] [ T10170] Call Trace:
kern :warn : [ 467.712826] [ T10170] <TASK>
kern :warn : [ 467.712827] [ T10170] dump_stack_lvl (kbuild/src/lib/dump_stack.c:94 kbuild/src/lib/dump_stack.c:120)
kern :warn : [ 467.712833] [ T10170] dump_header (kbuild/src/mm/oom_kill.c:464)
kern :warn : [ 467.712836] [ T10170] oom_kill_process.cold (kbuild/src/mm/oom_kill.c:1031)
kern :warn : [ 467.712839] [ T10170] out_of_memory (kbuild/src/mm/oom_kill.c:1169 (discriminator 4))
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260611/202606110923.2d2a1a13-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
--
Mailing list info: https://lists.linux.it/listinfo/ltp
reply other threads:[~2026-06-11 7:29 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=202606110923.2d2a1a13-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=ltp@lists.linux.it \
--cc=oe-lkp@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox