Re: [PATCH] kernel: debug: Handle breakpoints in kernel .init.text section

On Tue, 23 Feb 2021 at 18:24, Daniel Thompson wrote: > > On Tue, Feb 23, 2021 at 02:33:50PM +0530, Sumit Garg wrote: > > Thanks Doug for your comments. > > > > On Tue, 23 Feb 2021 at 05:28, Doug Anderson wrote: > > > > To be clear there is still a very small window between call to > > > >

Re: [PATCH] kernel: debug: Handle breakpoints in kernel .init.text section

On Tue, Feb 23, 2021 at 02:33:50PM +0530, Sumit Garg wrote: > Thanks Doug for your comments. > > On Tue, 23 Feb 2021 at 05:28, Doug Anderson wrote: > > > To be clear there is still a very small window between call to > > > free_initmem() and system_state = SYSTEM_RUNNING which can lead to > > >

Re: [PATCH] kernel: debug: Handle breakpoints in kernel .init.text section

Thanks Doug for your comments. On Tue, 23 Feb 2021 at 05:28, Doug Anderson wrote: > > Hi, > > On Fri, Feb 19, 2021 at 12:03 AM Sumit Garg wrote: > > > > Currently breakpoints in kernel .init.text section are not handled > > correctly while allowing to remove them even after corresponding pages

Re: [PATCH] kernel: debug: Handle breakpoints in kernel .init.text section

Hi, On Fri, Feb 19, 2021 at 12:03 AM Sumit Garg wrote: > > Currently breakpoints in kernel .init.text section are not handled > correctly while allowing to remove them even after corresponding pages > have been freed. > > In order to keep track of .init.text section breakpoints, add another >

[PATCH] kernel: debug: Handle breakpoints in kernel .init.text section

Currently breakpoints in kernel .init.text section are not handled correctly while allowing to remove them even after corresponding pages have been freed. In order to keep track of .init.text section breakpoints, add another breakpoint state as BP_ACTIVE_INIT and don't try to free these