From: Uladzislau Rezki <urezki@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: liuye <liuye@kylinos.cn>,
Andrew Morton <akpm@linux-foundation.org>,
oe-lkp@lists.linux.dev, lkp@intel.com,
Christop Hellwig <hch@infradead.org>,
linux-mm@kvack.org
Subject: Re: [linux-next:master] [mm/vmalloc] ff6f2b81ea: WARNING:at_kernel/fork.c:#vm_area_init_from
Date: Tue, 11 Mar 2025 13:43:44 +0100 [thread overview]
Message-ID: <Z9AwAKYI92AgIJ8M@pc636> (raw)
In-Reply-To: <Z9APeowHOXe-MkV2@pc636>
Hello, Andrew!
> > >
> > >>
> > >> Hello,
> > >>
> > >> kernel test robot noticed "WARNING:at_kernel/fork.c:#vm_area_init_from" on:
> > >>
> > >> commit: ff6f2b81eaa8a9fe5d158c6e7b1e58d3929c32c1 ("mm/vmalloc: move free_vm_area(area) from the __vmalloc_area_node function to the __vmalloc_node_range_noprof function")
> > >> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
> > >>
> > >> [test failed on linux-next/master 0a2f889128969dab41861b6e40111aa03dc57014]
> > >>
> > >> in testcase: trinity
> > >> version:
> > >> with following parameters:
> > >>
> > >> runtime: 300s
> > >> group: group-02
> > >> nr_groups: 5
> > >>
> > >>
> > >>
> > >> config: x86_64-randconfig-101-20250306
> > >> compiler: gcc-12
> > >> test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
> > >>
> > >> (please refer to attached dmesg/kmsg for entire log/backtrace)
> > >>
>
Could you please share your view what we should do with the patch in
question? I mean we can drop it, since it is broken and there is also
another option - it is to fix the broken patch.
Thank you in advance!
--
Uladzislau Rezki
next prev parent reply other threads:[~2025-03-11 12:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 12:52 kernel test robot
2025-03-10 16:52 ` Uladzislau Rezki
2025-03-11 7:26 ` liuye
2025-03-11 10:24 ` Uladzislau Rezki
2025-03-11 12:43 ` Uladzislau Rezki [this message]
2025-03-11 18:18 ` Andrew Morton
2025-03-11 20:26 ` Uladzislau Rezki
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=Z9AwAKYI92AgIJ8M@pc636 \
--to=urezki@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=linux-mm@kvack.org \
--cc=liuye@kylinos.cn \
--cc=lkp@intel.com \
--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