| Summary: | [abrt] kernel: kernel BUG at security/selinux/avc.c:162!: TAINTED Die | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Todor <yodor1> |
| Component: | kernel | Assignee: | Eric Paris <eparis> |
| Status: | CLOSED CANTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 15 | CC: | frank.mehnert, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, sdsmall |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | abrt_hash:71c5680cdf6afd954ef8d87c9a656a85f2859b5f | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-10-07 17:33:31 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Todor
2011-05-28 09:19:12 UTC
kernel BUG at security/selinux/avc.c:162!
BUG_ON(tclass >= ARRAY_SIZE(secclass_map));
Filesystem type? Sounds like we have a filesystem that isn't correctly initializing its inodes and thus we have garbage in inode->i_security. tclass was 0xe04 and the valid range for tclass is 0 through 0x31 I'm not sure if we'll be able to find out what kind of filesystem it was. Todor, can you post the output of the "mount" command? note the vbox modules are loaded. these have been known to corrupt kernel memory. unless this can be reproduced without them having been loaded, I'd close this as a problem in vbox. Not sure if vbox is problem here, as at that time I was not using vbox. If I remember correctly I was transfering some files under usb ethernet emulation (usb0 was running) and the issue was reproduceable. I'm sorry I can not access this machine under fedora now so I can not help further. If you dont see anything wrong close this bug on your decision. Regards, even having the modules loaded seems to be enough to cause problems, even if it wasn't in use at the time of the crash. if it does happen again without vbox having been loaded, feel free to reopen or file a new bug. thanks. Chuck, which version of VirtualBox are you using? |