[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Ztrr10sxYvQQGonC@feng-clx.sh.intel.com>
Date: Fri, 6 Sep 2024 19:47:35 +0800
From: Feng Tang <feng.tang@...el.com>
To: John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>
CC: <akpm@...ux-foundation.org>, <bristot@...hat.com>, <bsegall@...gle.com>,
<dietmar.eggemann@....com>, <juri.lelli@...hat.com>,
<linux-kernel@...r.kernel.org>, <mgorman@...e.de>, <mingo@...hat.com>,
<peterz@...radead.org>, <rostedt@...dmis.org>, <vbabka@...e.cz>,
<vincent.guittot@...aro.org>, <vschneid@...hat.com>,
<sparclinux@...r.kernel.org>
Subject: Re: sched/debug: Dump end of stack when detected corrupted
Hi Andrian,
On Fri, Sep 06, 2024 at 10:45:46AM +0200, John Paul Adrian Glaubitz wrote:
> Hi Feng,
>
> > - if (task_stack_end_corrupted(prev))
> > + if (task_stack_end_corrupted(prev)) {
> > + unsigned long *ptr = end_of_stack(prev);
> > +
> > + /* Dump 16 ulong words around the corruption point */
> > +#ifdef CONFIG_STACK_GROWSUP
> > + ptr -= 15;
> > +#endif
> > + print_hex_dump(KERN_ERR, "Corrupted Stack: ",
> > + DUMP_PREFIX_ADDRESS, 16, 1, ptr, 16 * sizeof(*ptr), 1);
> > +
>
> I would recommend determining the buffer element size with sizeof(unsigned long) for
> better readability and using "true" instead of "1" to set the value of the ascii
> parameter to print_hex_dump(), see [1]. Otherwise looks good to me.
Thanks for the review! Yes, I can make that change.
> Reviewed-by: John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>
>
> PS: Please CC me for a potential v3.
Sure.
Thanks,
Feng
> Thanks,
> Adrian
>
> > [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/lib/hexdump.c#n252
Powered by blists - more mailing lists