[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFA6WYN===hi_6w=zhXKT=iCAyMkXvi0OwvZb3bbsZpUeeFg-A@mail.gmail.com>
Date: Fri, 26 Feb 2021 12:26:58 +0530
From: Sumit Garg <sumit.garg@...aro.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Doug Anderson <dianders@...omium.org>,
kgdb-bugreport@...ts.sourceforge.net,
Masami Hiramatsu <mhiramat@...nel.org>,
Steven Rostedt <rostedt@...dmis.org>,
Daniel Thompson <daniel.thompson@...aro.org>,
Jason Wessel <jason.wessel@...driver.com>,
Peter Zijlstra <peterz@...radead.org>, stefan.saecherl@....de,
qy15sije@....cs.fau.de, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] kgdb: Fix to kill breakpoints on initmem after boot
On Wed, 24 Feb 2021 at 23:50, Andrew Morton <akpm@...ux-foundation.org> wrote:
>
> On Wed, 24 Feb 2021 10:09:25 -0800 Doug Anderson <dianders@...omium.org> wrote:
>
> > On Wed, Feb 24, 2021 at 12:17 AM Sumit Garg <sumit.garg@...aro.org> wrote:
> > >
> > > Currently breakpoints in kernel .init.text section are not handled
> > > correctly while allowing to remove them even after corresponding pages
> > > have been freed.
> > >
> > > Fix it via killing .init.text section breakpoints just prior to initmem
> > > pages being freed.
> >
> > It might be worth it to mention that HW breakpoints aren't handled by
> > this patch but it's probably not such a big deal.
>
> I added that to the changelog, thanks.
>
Thanks Andrew for picking this up.
-Sumit
> I'll take your response to be the coveted acked-by :)
Powered by blists - more mailing lists