From: Maninder Singh <maninder1.s@samsung.com>
To: Christian Brauner <brauner@kernel.org>
Cc: "viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"elver@google.com" <elver@google.com>,
"jack@suse.cz" <jack@suse.cz>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Rohit Thapliyal <r.thapliyal@samsung.com>
Subject: RE: [PATCH 1/1] lib/list_debug.c: add object information in case of invalid object
Date: Wed, 08 Jan 2025 08:47:23 +0530 [thread overview]
Message-ID: <20250108031723epcms5p6903c4e62f2e8ca63f18724cdfbfa492d@epcms5p6> (raw)
In-Reply-To: <20250107-grade-entgiften-74e459edf9ce@brauner>
Hi,
>>
>> [ 14.243055] slab kmalloc-32 start ffff0000cda19320 data offset 32 pointer offset 8 size 32 allocated at add_to_list+0x28/0xb0
>> [ 14.245259] __kmalloc_cache_noprof+0x1c4/0x358
>> [ 14.245572] add_to_list+0x28/0xb0
>> ...
>> [ 14.248632] do_el0_svc_compat+0x1c/0x34
>> [ 14.249018] el0_svc_compat+0x2c/0x80
>> [ 14.249244] Free path:
>> [ 14.249410] kfree+0x24c/0x2f0
>> [ 14.249724] do_force_corruption+0xbc/0x100
>> ...
>> [ 14.252266] el0_svc_common.constprop.0+0x40/0xe0
>> [ 14.252540] do_el0_svc_compat+0x1c/0x34
>> [ 14.252763] el0_svc_compat+0x2c/0x80
>> [ 14.253071] ------------[ cut here ]------------
>> [ 14.253303] list_del corruption. next->prev should be ffff0000cda192a8, but was 6b6b6b6b6b6b6b6b. (next=ffff0000cda19348)
>> [ 14.254255] WARNING: CPU: 3 PID: 84 at lib/list_debug.c:65 __list_del_entry_valid_or_report+0x158/0x164
>>
>> moved prototype of mem_dump_obj() to bug.h, as mm.h can not be included
>> in bug.h.
>>
>> Signed-off-by: Maninder Singh <maninder1.s@samsung.com>
>> ---
>
> Can you please base this on either the latest mainline tag or
> vfs-6.14.misc and resend, please?
It is already applied to latest mainline (linux-next)
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=6fffae498b254b20cbaa9e754d793df9c4effc4d
Thanks,
Maninder Singh
prev parent reply other threads:[~2025-01-08 3:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20241230101102epcas5p1c879ea11518951971c8f1bf3dbc3fe39@epcas5p1.samsung.com>
2024-12-30 10:10 ` Maninder Singh
2025-01-06 9:13 ` Jan Kara
2025-01-07 14:53 ` Christian Brauner
[not found] ` <CGME20241230101102epcas5p1c879ea11518951971c8f1bf3dbc3fe39@epcms5p6>
2025-01-08 3:17 ` Maninder Singh [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=20250108031723epcms5p6903c4e62f2e8ca63f18724cdfbfa492d@epcms5p6 \
--to=maninder1.s@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=elver@google.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=r.thapliyal@samsung.com \
--cc=viro@zeniv.linux.org.uk \
/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