Dave,
When I ran "bt" against a process running in a user mode, I got
an odd backtrace result:
===8<===
crash> ps
...
> 1324 1223 2 80002018be80 RU 0.0 960468 dhry
1325 2 1 800021089900 IN 0.0 0 0 [kworker/u16:0]
crash> bt 1324
PID: 1324 TAS
On Wed, Jun 01, 2016 at 11:41:04AM -0400, Dave Anderson wrote:
>
> - Original Message -
>
> > > >
> > > > case PRE_GDB:
> > > > + /* This check is somewhat redundant */
> > > > + if (kernel_symbol_exists("kimage_voffset"))
> > > > +
On Wed, Jun 01, 2016 at 10:32:56AM -0400, Dave Anderson wrote:
>
> - Original Message -
> > On Tue, May 31, 2016 at 03:30:44PM -0400, Dave Anderson wrote:
> > >
> > > This patch looks good -- if it wasn't layered on top of the KASLR patch,
> > > I would check it into github.
> >
> > This
- Original Message -
> > >
> > > case PRE_GDB:
> > > + /* This check is somewhat redundant */
> > > + if (kernel_symbol_exists("kimage_voffset"))
> > > + machdep->flags |= NEW_VMEMMAP;
> > > +
> >
> > Certainly not redundant on a live system without C
- Original Message -
> On Tue, May 31, 2016 at 03:30:44PM -0400, Dave Anderson wrote:
> >
> > This patch looks good -- if it wasn't layered on top of the KASLR patch,
> > I would check it into github.
>
> This patch is almost independent from KASLR support, except that
> adding new flag
On Tue, May 31, 2016 at 03:29:01PM -0400, Dave Anderson wrote:
>
> - Original Message -
> > In kernel v4.6, Kernel ASLR (KASLR) is supported on arm64, and the start
> > address of the kernel image can be randomized if CONFIG_RANDOMIZE_BASE is
> > enabled.
> > Even worse, the kernel image
