From: Christian Brauner <brauner@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: "open list" <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
"Linux Regressions" <regressions@lists.linux.dev>,
linux-fsdevel@vger.kernel.org, "Jann Horn" <jannh@google.com>,
"Josef Bacik" <josef@toxicpanda.com>,
"Alexander Mikhalitsyn" <alexander@mihalicyn.com>,
"Jeff Layton" <jlayton@kernel.org>,
"Daan De Meyer" <daan.j.demeyer@gmail.com>,
"Lennart Poettering" <lennart@poettering.net>,
"Mike Yuan" <me@yhndnzj.com>,
"Zbigniew Jędrzejewski-Szmek" <zbyszek@in.waw.pl>,
"Arnd Bergmann" <arnd@arndb.de>,
"Dan Carpenter" <dan.carpenter@linaro.org>,
"Anders Roxell" <anders.roxell@linaro.org>
Subject: Re: next-20250623: arm64 devices kernel panic Internal error Oops at pidfs_free_pid (fs/pidfs.c:162)
Date: Tue, 24 Jun 2025 10:54:32 +0200 [thread overview]
Message-ID: <20250624-elastisch-errichten-a2aec974177e@brauner> (raw)
In-Reply-To: <CA+G9fYsfOg9uiwgYA1mHkBzwEkU6eLweneWJhFybt+X1Ekp55Q@mail.gmail.com>
On Mon, Jun 23, 2025 at 08:26:32PM +0530, Naresh Kamboju wrote:
> On Mon, 23 Jun 2025 at 18:26, Christian Brauner <brauner@kernel.org> wrote:
> >
> > On Mon, Jun 23, 2025 at 05:29:38PM +0530, Naresh Kamboju wrote:
> > > Regressions on arm64 devices and qemu-arm64 while running LTP controllers
> > > and selftests cgroup test cases the following kernel Panic Internal error oops
> > > found on the Linux next-20250623 tag.
> > >
> > > Regressions found on arm64 device
> > > - Kernel Panic Internal oops @ LTP controllers
> > > - Kernel Panic Internal oops @ selftest cgroups
> > >
> > > Test environments:
> > > - Dragonboard-410c
> > > - e850-96
> > > - FVP
> > > - Juno-r2
> > > - rk3399-rock-pi-4b
> > > - qemu-arm64
> > >
> > > Regression Analysis:
> > > - New regression? Yes
> > > - Reproducibility? Yes
> > >
> > > Boot regression: arm64 devices kernel panic Internal error Oops at
> > > pidfs_free_pid (fs/pidfs.c:162)
> > >
> > > Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> > >
> > > ## Test log
> > > [ 67.087303] Internal error: Oops: 0000000096000004 [#1] SMP
> > > [ 67.094021] Modules linked in: snd_soc_hdmi_codec venus_enc
> > > venus_dec videobuf2_dma_contig pm8916_wdt qcom_wcnss_pil
> > > coresight_cpu_debug coresight_tmc coresight_replicator qcom_camss
> > > coresight_stm snd_soc_lpass_apq8016 msm qrtr coresight_funnel
> > > snd_soc_msm8916_digital snd_soc_lpass_cpu coresight_tpiu
> > > snd_soc_msm8916_analog videobuf2_dma_sg stm_core coresight_cti
> > > snd_soc_lpass_platform snd_soc_apq8016_sbc venus_core
> > > snd_soc_qcom_common qcom_q6v5_mss v4l2_fwnode coresight snd_soc_core
> > > qcom_pil_info v4l2_async snd_compress llcc_qcom snd_pcm_dmaengine
> > > ocmem qcom_q6v5 v4l2_mem2mem videobuf2_memops snd_pcm qcom_sysmon
> > > drm_exec adv7511 snd_timer videobuf2_v4l2 gpu_sched qcom_common snd
> > > videodev drm_dp_aux_bus qcom_glink_smem soundcore qcom_spmi_vadc
> > > mdt_loader drm_display_helper qnoc_msm8916 qmi_helpers
> > > videobuf2_common qcom_vadc_common qcom_spmi_temp_alarm rtc_pm8xxx
> > > qcom_pon qcom_stats mc cec drm_client_lib qcom_rng rpmsg_ctrl
> > > display_connector rpmsg_char phy_qcom_usb_hs socinfo drm_kms_helper
> > > rmtfs_mem ramoops
> > > [ 67.094437] reed_solomon fuse drm backlight ip_tables x_tables
> > > [ 67.189084] CPU: 3 UID: 0 PID: 0 Comm: swapper/3 Not tainted
> > > 6.16.0-rc3-next-20250623 #1 PREEMPT
> > > [ 67.194810] Hardware name: Qualcomm Technologies, Inc. APQ 8016 SBC (DT)
> > > [ 67.234078] pc : pidfs_free_pid (fs/pidfs.c:162)
> >
> > Thanks, I see the issue. I'm pushing out a fix. Please let me know if
> > that reproduces in the next few days.
>
> Thanks. Please share the proposed fix patches.
> I would like to build and test in LKFT test framework.
It's in vfs-6.17.pidfs. Syzbot has a reproducer for the bug.
prev parent reply other threads:[~2025-06-24 8:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 11:59 next-20250623: arm64 devices kernel panic Internal error Oops at pidfs_free_pid (fs/pidfs.c:162) Naresh Kamboju
2025-06-23 12:56 ` Christian Brauner
2025-06-23 14:56 ` Naresh Kamboju
2025-06-24 8:54 ` Christian Brauner [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=20250624-elastisch-errichten-a2aec974177e@brauner \
--to=brauner@kernel.org \
--cc=alexander@mihalicyn.com \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=daan.j.demeyer@gmail.com \
--cc=dan.carpenter@linaro.org \
--cc=jannh@google.com \
--cc=jlayton@kernel.org \
--cc=josef@toxicpanda.com \
--cc=lennart@poettering.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=me@yhndnzj.com \
--cc=naresh.kamboju@linaro.org \
--cc=regressions@lists.linux.dev \
--cc=zbyszek@in.waw.pl \
/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