From: Andrew Morton <akpm@linux-foundation.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Sumit Garg <sumit.garg@linaro.org>,
kgdb-bugreport@lists.sourceforge.net,
Masami Hiramatsu <mhiramat@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Daniel Thompson <daniel.thompson@linaro.org>,
Jason Wessel <jason.wessel@windriver.com>,
Peter Zijlstra <peterz@infradead.org>,
stefan.saecherl@fau.de, qy15sije@cip.cs.fau.de,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kgdb: Fix to kill breakpoints on initmem after boot
Date: Wed, 24 Feb 2021 10:20:52 -0800 [thread overview]
Message-ID: <20210224102052.009aaa27dd5b530d7e7ef599@linux-foundation.org> (raw)
In-Reply-To: <CAD=FV=VOdf1TyXWQOyP=y2xaLxY6_c+xm-VSSUkFasJD1Cbgpw@mail.gmail.com>
On Wed, 24 Feb 2021 10:09:25 -0800 Doug Anderson <dianders@chromium.org> wrote:
> On Wed, Feb 24, 2021 at 12:17 AM Sumit Garg <sumit.garg@linaro.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.
I'll take your response to be the coveted acked-by :)
next prev parent reply other threads:[~2021-02-24 18:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 8:16 Sumit Garg
2021-02-24 18:09 ` Doug Anderson
2021-02-24 18:20 ` Andrew Morton [this message]
2021-02-26 6:56 ` Sumit Garg
2021-02-26 6:56 ` Sumit Garg
2021-02-25 15:56 ` Daniel Thompson
2021-02-26 7:02 ` Sumit Garg
2021-02-26 7:31 ` Greg KH
2021-02-26 9:32 ` Sumit Garg
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=20210224102052.009aaa27dd5b530d7e7ef599@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=daniel.thompson@linaro.org \
--cc=dianders@chromium.org \
--cc=jason.wessel@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=peterz@infradead.org \
--cc=qy15sije@cip.cs.fau.de \
--cc=rostedt@goodmis.org \
--cc=stefan.saecherl@fau.de \
--cc=sumit.garg@linaro.org \
/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
all inboxes | Powered by JetHome®