Bug#330592: init segfault when /selinux exists but a policy can't be loaded

tags 330592 -unreproducible +etch -help severity 330592 critical found 330592 2.86.ds1-20 thanks The reason for the critical level is that this bug has the potential to render the entire system unbootable unless glibc catches the invalid free() calls. See description below for further details.

Bug#330592: init segfault when /selinux exists but a policy can't be loaded

On Wed, November 1, 2006 23:08, James Westby said: It seems clear that the actions I described do not trigger a segfault like the original report, however it is not clear to me that these actions are the ones from the original report. Ernest has stated that he did not have a policy installed,

Bug#330592:

tags 330592 +unreproducible thanks James Westby wrote: So I managed to get the above message (for policy version 20) by # rm -rf /etc/selinux However it did not cause a segfault, and I got a completed boot. I did however get *** glibc detected *** free(): invalid pointer: 0x0804feb5 ***

Bug#330592: init segfault when /selinux exists but a policy can't be loaded

On (01/11/06 13:53), David Härdeman wrote: tags 330592 +unreproducible thanks James Westby wrote: So I managed to get the above message (for policy version 20) by # rm -rf /etc/selinux However it did not cause a segfault, and I got a completed boot. I did however get *** glibc

Bug#330592: sysvinit: init panic after creating directory /selinux/

Hi, I have managed to get some more information on this bug. I have included my findings below, but the short story is that I think it might be somewhat fixed. Can you still reproduce this bug? If so it would be interesting to get a bit more information, for instance a full log of the crashing

Bug#330592: sysvinit: init panic after creating directory /selinux/

Hi, On Sunday 22 October 2006 16:11, you wrote: Can you still reproduce this bug? If so it would be interesting to get a bit more information, for instance a full log of the crashing startup. No, I cannot. I checked, but could not find, if a /selinux/ not found error was still given during

Bug#330592: sysvinit: init panic after creating directory /selinux/

Package: sysvinit Version: 2.86.ds1-3 Severity: normal this bug is related to minor bugs : #328474 #329328 but might be more serious. A few days ago, during boot, just before init startup, I too noticed the same message which claimed directory /selinux/ was not found. thinking selinux was