Just happened to stumble across a lengthy thread on LKML/stable related
to this. To me it looks to be settling down to have two proposed
patches:
* Re: [PATCH] Make math_state_restore() save and restore the interrupt flag
- x86, fpu: remove the logic of non-eager fpu mem allocation at the first
Thanks for the great bug report, Maarten. I've linked it into the
upstream eCryptfs tracker (also hosted on Launchpad) and I'll start
looking into it.
It initially feels like a bug in the aesni module, but that's just an
early guess.
** Also affects: ecryptfs
Importance: Undecided
Tyler, before you spend any time on this, I've already investigated and
think it may actually be a bug in the core kernel FPU code. I reported it
on LKML with a tentative patch: https://lkml.org/lkml/2014/1/19/86 I
haven't yet received any feedback or discussion from LKML; when I have a
I am able to reproduce this bug as well, using Ubuntu saucy (13.10) with
kernel 3.11.0-15-generic #23-Ubuntu SMP. The machine is an HP Folio13
laptop. I am happy to provide more info and/or test patches.
I actually encountered it independently. When you run latex from emacs,
it spawns evince
I don't know, the cause is apparently that IRQs are disabled, but I
don't know whether that's considered an error. The aesni_intel module is
needed to trigger the bug, but that doesn't imply that it contains the
bug. It's possible that ecryptfs is using it wrong, or that the fallback
code (which
For what it's worth, here is the backtrace from when I reproduced the
bug using emacs/evince. Maybe it is helpful to look for similarities in
the code path, though it certainly sounds like the crypto code in
ecryptfs is the place to begin. I may try putting in lots of
WARN_ON(irqs_disabled()).
Done:
http://permalink.gmane.org/gmane.comp.file-systems.ecryptfs.general/487
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1265841
Title:
kernel BUG at
I can do it if you really want, but I think I already know the result.
According to this:
http://www.phoronix.com/scan.php?page=news_itempx=MTM2OTg
... ecryptfs AES-NI support was only added in kernel 3.10. Both quantal and
raring use older kernels, so they will not load the aesni_intel module
The tests I did confirmed what I suspected:
* kernel 3.13 is affected (if aesni_intel is loaded)
* kernel 3.11 is affected (if aesni_intel is loaded)
* kernel 3.10 is affected (if aesni_intel is loaded)
* kernel 3.9 is NOT affected (ecryptfs doesn't use aesni_intel so it doesn't
matter whether
Maarten Baert, the issue you are reporting is an upstream one. Could you
please report this problem through the appropriate channel by following
the instructions _verbatim_ at
https://wiki.ubuntu.com/Bugs/Upstream/kernel ?
Please provide a direct URL to your e-mail to the mailing list once you
Maarten Baert, thank you for providing the requested information. Could
you please provide the information following
https://help.ubuntu.com/community/DebuggingIRQProblems and advise if it
changes anything?
** Summary changed:
- Kernel crash in ext4/ecryptfs after core dump in encrypted folder
+
I tried kernel 3.13.0-rc6 with:
* noapic
* pci=routeirq
* pci=noacpi
* acpi=off
In all cases I can still reproduce the bug, nothing changes.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Maarten Baert, thank you for providing the requested information. Did
this problem not occur in a release prior to Saucy?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1265841
Title:
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1265841
Title:
kernel BUG at /build/buildd/linux-3.11.0/fs/buffer.c:1268!; RIP:
0010:[816e3efd]
Oh, and for what it's worth, I have run memtest86+ and mprime to
eliminate the most obvious hardware problems, and both tests didn't find
any errors.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I don't know, this is a new computer. But on my older computer I had an
identical setup that I have used for months with kernels 3.9 up to 3.12
with no issues at all. On the new computer it happened twice in just one
week. So I suspect it is hardware-related somehow.
--
You received this bug
Maarten Baert, thank you for your comments. For regression testing
purposes, could you please test for this in Precise 3.2.x kernel series
via http://old-releases.ubuntu.com/releases/precise/ and advise to the
results?
--
You received this bug notification because you are a member of Kernel
I tried to install 12.04 but I ran into some issues. The installer seems
buggy, it used the wrong EFI partition and failed to install grub, but I
was still able to boot it by re-using the 13.10 grub install, and I
think the install is okay. Unfortunately 12.04 doesn't seem to have
drivers for my
Maarten Baert, thank you for performing the requested test. Would
Quantal allow a proper test via http://releases.ubuntu.com/quantal/ ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
19 matches
Mail list logo
