| 1 |
Am Dienstag, 25.10.2016 um 20:17 |
| 2 |
schrieb Miroslav Rovis <miro.rovis@××××××××××××××.hr>: |
| 3 |
|
| 4 |
> On 161025-19:35+0200, wabe wrote: |
| 5 |
> > Am Dienstag, 25.10.2016 um 18:24 |
| 6 |
> > schrieb Miroslav Rovis <miro.rovis@××××××××××××××.hr>: |
| 7 |
> > |
| 8 |
> > > The other correspondent in this thread, Michael Orlitzky, |
| 9 |
> > > mentioned how 4.7.10 already works fine for him. |
| 10 |
> > > |
| 11 |
> > > I'll paste and ask him here: |
| 12 |
> > > |
| 13 |
> > > > > I'm testing 4.7.10 and will have it stabilized soon. |
| 14 |
> > > > > |
| 15 |
> > > > |
| 16 |
> > > > FWIW, I've been panic-updating all of our x86/amd64 servers |
| 17 |
> > > > (mostly HP Proliant) to 4.7.10 and nothing has blown up yet. |
| 18 |
> > > |
| 19 |
> > > Michael, |
| 20 |
> > > |
| 21 |
> > > are you talking about that bug: |
| 22 |
> > > |
| 23 |
> > > =sys-kernel/hardened-sources-4.7.6: Kernel panic when starting KVM |
| 24 |
> > > guests |
| 25 |
> > > > > https://bugs.gentoo.org/show_bug.cgi?id=597554 |
| 26 |
> > > having been fixed in 4.7.10 |
| 27 |
> > |
| 28 |
> > Interesting. I'm using hardened-sources-4.7.6 and qemu-2.7.0-r4 and |
| 29 |
> > don't have any problems so far. I'm using qemu VMs with xubuntu |
| 30 |
> > 14.04 and 16.04. |
| 31 |
> You mean your hardened-sources-4.7.6 are set up as |
| 32 |
> grsecurity-hardened ? |
| 33 |
> |
| 34 |
> Or are they maybe SELinux hardened ? Or AppArmor hardened ? Or other? |
| 35 |
> (really not familiar much with all the options in the hardened) |
| 36 |
|
| 37 |
I'm using grsecurity but I don't have PAX_MEMORY_SANITIZE enabled. |
| 38 |
According to PaX Teams reply to my last message this is the reason why |
| 39 |
I don't have problems with qemu. |
| 40 |
|
| 41 |
-- |
| 42 |
Regards |
| 43 |
wabe |
Archives