From: Eric Dumazet <edumazet@google.com>
To: kernel test robot <oliver.sang@intel.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>, 0day robot <lkp@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org, "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev <netdev@vger.kernel.org>
Subject: Re: [net] 72fd55c0db: invoked_oom-killer:gfp_mask=0x
Date: Fri, 6 May 2022 01:15:40 -0700 [thread overview]
Message-ID: <CANn89iLkpsri3CxxP3Xc-jLJ_9V4K5pCHPRhdWEL69Z78VWCjw@mail.gmail.com> (raw)
In-Reply-To: <20220506064439.GC23061@xsang-OptiPlex-9020>
On Thu, May 5, 2022 at 11:44 PM kernel test robot <oliver.sang@intel.com> wrote:
>
>
>
> Greeting,
>
> FYI, we noticed the following commit (built with gcc-11):
>
> commit: 72fd55c0dbb1ad5ba283ca80abc9546702815a33 ("[PATCH v2 net-next] net: generalize skb freeing deferral to per-cpu lists")
> url: https://github.com/intel-lab-lkp/linux/commits/Eric-Dumazet/net-generalize-skb-freeing-deferral-to-per-cpu-lists/20220423-060710
> base: https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git c78c5a660439d4d341a03b651541fda3ebe76160
> patch link: https://lore.kernel.org/netdev/20220422201237.416238-1-eric.dumazet@gmail.com
>
I think this commit had two follow up fixes.
Make sure to test the tree after the fixes are included, otherwise
this is adding unneeded noise.
Thank you.
commit f3412b3879b4f7c4313b186b03940d4791345534
Author: Eric Dumazet <edumazet@google.com>
Date: Wed Apr 27 13:41:47 2022 -0700
net: make sure net_rx_action() calls skb_defer_free_flush()
And:
commit 783d108dd71d97e4cac5fe8ce70ca43ed7dc7bb7
Author: Eric Dumazet <edumazet@google.com>
Date: Fri Apr 29 18:15:23 2022 -0700
tcp: drop skb dst in tcp_rcv_established()
> in testcase: xfstests
> version: xfstests-x86_64-46e1b83-1_20220414
> with following parameters:
>
> disk: 4HDD
> fs: ext4
> fs2: smbv3
> test: generic-group-10
> ucode: 0xec
>
> test-description: xfstests is a regression test suite for xfs and other files ystems.
> test-url: git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
>
>
> on test machine: 8 threads Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz with 16G memory
>
> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>
>
>
> If you fix the issue, kindly add following tag
> Reported-by: kernel test robot <oliver.sang@intel.com>
>
>
>
> [ 80.428226][ T1836] Attempt to set a LOCK_MAND lock via flock(2). This support has been removed and the request ignored.
> [ 80.739189][ T370] generic/207 0s
> [ 80.739198][ T370]
> [ 80.785302][ T1696] run fstests generic/208 at 2022-05-06 02:42:26
> [ 81.143444][ T1836] Attempt to set a LOCK_MAND lock via flock(2). This support has been removed and the request ignored.
> [ 89.609627][ T58] kworker/u16:5 invoked oom-killer: gfp_mask=0xcd0(GFP_KERNEL|__GFP_RECLAIMABLE), order=0, oom_score_adj=0
> [ 89.620805][ T58] CPU: 0 PID: 58 Comm: kworker/u16:5 Not tainted 5.18.0-rc3-00568-g72fd55c0dbb1 #1
> [ 89.629899][ T58] Hardware name: HP HP Z240 SFF Workstation/802E, BIOS N51 Ver. 01.63 10/05/2017
> [ 89.638822][ T58] Workqueue: writeback wb_workfn (flush-8:16)
> [ 89.644727][ T58] Call Trace:
> [ 89.647863][ T58] <TASK>
> [ 89.650649][ T58] dump_stack_lvl (kbuild/src/consumer/lib/dump_stack.c:107 (discriminator 1))
> [ 89.654992][ T58] dump_header (kbuild/src/consumer/mm/oom_kill.c:73 kbuild/src/consumer/mm/oom_kill.c:461)
> [ 89.659250][ T58] oom_kill_process.cold (kbuild/src/consumer/mm/oom_kill.c:979)
> [ 89.664110][ T58] out_of_memory (kbuild/src/consumer/mm/oom_kill.c:1119 (discriminator 4))
>
>
> To reproduce:
>
> git clone https://github.com/intel/lkp-tests.git
> cd lkp-tests
> sudo bin/lkp install job.yaml # job file is attached in this email
> bin/lkp split-job --compatible job.yaml # generate the yaml file for lkp run
> sudo bin/lkp run generated-yaml-file
>
> # if come across any failure that blocks the test,
> # please remove ~/.lkp and /lkp dir to run from a clean state.
>
>
>
> --
> 0-DAY CI Kernel Test Service
> https://01.org/lkp
>
>
prev parent reply other threads:[~2022-05-06 8:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 20:12 [PATCH v2 net-next] net: generalize skb freeing deferral to per-cpu lists Eric Dumazet
2022-04-26 7:38 ` Paolo Abeni
2022-04-26 13:11 ` Eric Dumazet
2022-04-26 15:28 ` Paolo Abeni
2022-04-26 16:13 ` Eric Dumazet
2022-04-27 0:50 ` patchwork-bot+netdevbpf
2022-04-27 15:34 ` Ido Schimmel
2022-04-27 16:53 ` Eric Dumazet
2022-04-27 17:11 ` Eric Dumazet
2022-04-27 17:59 ` Eric Dumazet
2022-04-27 18:54 ` Eric Dumazet
2022-04-29 16:18 ` Qian Cai
2022-04-29 16:23 ` Eric Dumazet
2022-04-29 20:44 ` Qian Cai
2022-05-06 6:44 ` [net] 72fd55c0db: invoked_oom-killer:gfp_mask=0x kernel test robot
2022-05-06 8:15 ` Eric Dumazet [this message]
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=CANn89iLkpsri3CxxP3Xc-jLJ_9V4K5pCHPRhdWEL69Z78VWCjw@mail.gmail.com \
--to=edumazet@google.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=netdev@vger.kernel.org \
--cc=oliver.sang@intel.com \
--cc=pabeni@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).