Re: [Oops] vfree abort in bpf_jit_free with memcg_data value 0xffff

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Peng Fan <peng.fan@xxxxxxx>
Subject: Re: [Oops] vfree abort in bpf_jit_free with memcg_data value 0xffff
From: Roman Gushchin <roman.gushchin@xxxxxxxxx>
Date: Mon, 3 Jun 2024 17:50:46 -0700
Cc: "linux-mm@xxxxxxxxx" <linux-mm@xxxxxxxxx>, "bpf@xxxxxxxxxxxxxxx" <bpf@xxxxxxxxxxxxxxx>, "daniel@xxxxxxxxxxxxx" <daniel@xxxxxxxxxxxxx>, "ast@xxxxxxxxxx" <ast@xxxxxxxxxx>, "zlim.lnx@xxxxxxxxx" <zlim.lnx@xxxxxxxxx>, "cgroups@xxxxxxxxxxxxxxx" <cgroups@xxxxxxxxxxxxxxx>, "hannes@xxxxxxxxxxx" <hannes@xxxxxxxxxxx>, "mhocko@xxxxxxxxxx" <mhocko@xxxxxxxxxx>, "shakeelb@xxxxxxxxxx" <shakeelb@xxxxxxxxxx>, "muchun.song@xxxxxxxxx" <muchun.song@xxxxxxxxx>
In-reply-to: <DU0PR04MB941765BD4422D30FBDCFC1C388FF2@DU0PR04MB9417.eurprd04.prod.outlook.com>
References: <DU0PR04MB941765BD4422D30FBDCFC1C388FF2@DU0PR04MB9417.eurprd04.prod.outlook.com>

On Mon, Jun 03, 2024 at 09:10:43AM +0000, Peng Fan wrote:
> Hi All,
> 
> We are running 6.6 kernel on NXP i.MX95 platform, and meet an issue very
> hard to reproduce. Panic log in the end. I check the registers and source code.

Hi!

Do you know by a chance if the issue is reproducible on newer kernels?

Follow-Ups:
- RE: [Oops] vfree abort in bpf_jit_free with memcg_data value 0xffff
  - From: Peng Fan

References:
- [Oops] vfree abort in bpf_jit_free with memcg_data value 0xffff
  - From: Peng Fan

Prev by Date: Re: [PATCH v1 1/1] treewide: Align match_string() with sysfs_match_string()
Next by Date: [no subject]
Previous by thread: [Oops] vfree abort in bpf_jit_free with memcg_data value 0xffff
Next by thread: RE: [Oops] vfree abort in bpf_jit_free with memcg_data value 0xffff
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Security] [Bugtraq] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API] [Monitors]