From: kernel test robot <oliver.sang@intel.com>
To: Namjae Jeon <linkinjeon@kernel.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>, Christoph Hellwig <hch@lst.de>,
"Darrick J. Wong" <djwong@kernel.org>,
<linux-fsdevel@vger.kernel.org>, <ltp@lists.linux.it>,
<oliver.sang@intel.com>
Subject: [linus:master] [exfat] 82a81a7352: invoked_oom-killer:gfp_mask=0x
Date: Fri, 10 Jul 2026 16:27:16 +0800 [thread overview]
Message-ID: <202607101054.8da4ec23-lkp@intel.com> (raw)
Hello,
this report is just FYI.
seems 82a81a7352 causes more memory footprint in our ltp tests on a 16G memory
Skylake desktop machine.
parent can always pass without the issues.
kernel test robot noticed "invoked_oom-killer:gfp_mask=0x" on:
commit: 82a81a7352bcf5f2756ac33d47ee0582737e9a85 ("exfat: add iomap buffered I/O support")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master 2c7c88a412aa6d09cd04b414211b4ef8553b5309]
[test failed on linux-next/master 34cf6dafc47441dfb6b356a095b89c3585a93714]
[test failed on fix commit 5362e7aedd113bb8b042e47e385103fe98274764]
in testcase: ltp
version:
with following parameters:
disk: 1SSD
fs: f2fs
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/202607101054.8da4ec23-lkp@intel.com
[ 430.386383][T10010] BTRFS info (device loop0): last unmount of filesystem 5e76d402-936a-4bbd-a5ab-c986cca03967
[ 430.422556][T10105] Adding 1020k swap on mntpoint/swapfile01. Priority:-1 extents:1 across:1020k SS
[ 431.662145][T10105] Adding 131068k swap on mntpoint/swapfile01. Priority:-1 extents:1 across:131068k SS
[ 432.662740][T10115] swapon: swapfile has holes
[ 432.678788][T10115] swapon: swapfile has holes
[ 432.769811][T10115] swapon01 invoked oom-killer: gfp_mask=0xcc0(GFP_KERNEL), order=0, oom_score_adj=0
[ 432.770508][T10115] CPU: 3 UID: 0 PID: 10115 Comm: swapon01 Tainted: G OE 7.1.0+ #1 PREEMPT(lazy)
[ 432.770513][T10115] Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
[ 432.770515][T10115] Hardware name: System manufacturer System Product Name/Z170I PRO GAMING, BIOS 3805 05/16/2018
[ 432.770529][T10115] Call Trace:
[ 432.770531][T10115] <TASK>
[ 432.770533][T10115] dump_stack_lvl (kbuild/src/lib/dump_stack.c:94 kbuild/src/lib/dump_stack.c:120)
[ 432.770539][T10115] dump_header (kbuild/src/mm/oom_kill.c:464)
[ 432.770542][T10115] oom_kill_process.cold (kbuild/src/mm/oom_kill.c:1031)
[ 432.770545][T10115] 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/20260710/202607101054.8da4ec23-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-10 8:27 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=202607101054.8da4ec23-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=linux-kernel@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