On Tue, Jul 18, 2017 at 02:11:35PM +0200, Thomas Gleixner wrote:
> On Tue, 18 Jul 2017, Piotr Gregor wrote:
> >
> > Dmesg reports insecure W+X mapping found at address
> > 8805f000/0x8805f000
> >
> > on 4.4.70 kernel patched with -rt83 patch:
>
> Does the same problem happen
On Tue, Jul 18, 2017 at 02:11:35PM +0200, Thomas Gleixner wrote:
> On Tue, 18 Jul 2017, Piotr Gregor wrote:
> >
> > Dmesg reports insecure W+X mapping found at address
> > 8805f000/0x8805f000
> >
> > on 4.4.70 kernel patched with -rt83 patch:
>
> Does the same problem happen
On Tue, 18 Jul 2017, Piotr Gregor wrote:
>
> Dmesg reports insecure W+X mapping found at address
> 8805f000/0x8805f000
>
> on 4.4.70 kernel patched with -rt83 patch:
Does the same problem happen with a plain 4.4.70? as well?
Thanks,
tglx
On Tue, 18 Jul 2017, Piotr Gregor wrote:
>
> Dmesg reports insecure W+X mapping found at address
> 8805f000/0x8805f000
>
> on 4.4.70 kernel patched with -rt83 patch:
Does the same problem happen with a plain 4.4.70? as well?
Thanks,
tglx
Hi Thomas,
Dmesg reports insecure W+X mapping found at address
8805f000/0x8805f000
on 4.4.70 kernel patched with -rt83 patch:
# uname -a
Linux piotrpc 4.4.70-rt83 #1 SMP PREEMPT RT Thu Jul 13 08:42:02 BST 2017 x86_64
GNU/Linux
[4.888146] Serial: 8250/16550 driver, 4 ports,
Hi Thomas,
Dmesg reports insecure W+X mapping found at address
8805f000/0x8805f000
on 4.4.70 kernel patched with -rt83 patch:
# uname -a
Linux piotrpc 4.4.70-rt83 #1 SMP PREEMPT RT Thu Jul 13 08:42:02 BST 2017 x86_64
GNU/Linux
[4.888146] Serial: 8250/16550 driver, 4 ports,
6 matches
Mail list logo