patch: boots and fixes the testcase I reported (core dump
on ecrypt).
Tested-by: Nate Eldredge
diff --git a/arch/x86/kernel/i387.c b/arch/x86/kernel/i387.c
index 4e5f770..670bba1 100644
--- a/arch/x86/kernel/i387.c
+++ b/arch/x86/kernel/i387.c
@@ -87,10 +87,19 @@ EXPORT_SYMBOL(__kernel_fpu_begin
From: Nate Eldredge
Make math_state_restore() save and restore the interrupt flag, rather
than always disabling interrupts.
If math_state_restore() is called in a task that has not used math, it
needs to allocate some memory (via init_fpu()). Since this can sleep,
it enables interrupts first
n I have a chance I will write something up and send it in, and
maybe having it as a formal patch submission will get more attention.
Thanks, George!
--
Nate Eldredge
n...@thatsmathematics.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a m
ts on
entry to turn around and enable interrupts itself. I agree that it would
really help for a guru to take a look...
On which note, Suresh's email bounced :-(
--
Nate Eldredge
n...@thatsmathematics.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
__thread_fpu_begin(tsk);
I tested it briefly: the kernel still boots fine, and it fixes the problem
I was seeing (BUG() when core dumping on ecryptfs). George, does it help
your problem?
Thanks everyone!
(Search October-December LKML archives for "3.11.4: kernel BUG at
fs/buff
rrupt flag? Or are we not
supposed to call it with interrupts enabled?
Given the intimidating comment preceding math_state_restore() ("Don't
touch unless you *really* know how it works"), it's entirely possible I am
missing something...
Any suggestions appreciated
. I eventually traced it to buggy motherboard cache.
(32 bytes is the size of a cache line.) A memory tester might be
something to try (I wrote a simple program that seemed to show the
error better than memtest86; can send it if desired.)
--
Nate Eldredge
[EMAIL PROTECTED]
-
To unsubscribe
myself a martian packet, to
see if it is logged?) I considered the possibility that the option
really is on, and sysctl just doesn't report it, but I didn't know how
to find out.
This is kernel 2.4.2-ac7.
--
Nate Eldredge
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line
Jens Axboe writes:
> On Sun, Feb 25 2001, Nate Eldredge wrote:
> > Nate Eldredge writes:
> > > Kernel 2.4.2-ac3.
> > >
> > > FLAGS UID PID PPID PRI NI SIZE RSS WCHAN STA TTY TIME COMMAND
> > > 40 0 425 1
Nate Eldredge writes:
> Kernel 2.4.2-ac3.
>
> FLAGS UID PID PPID PRI NI SIZE RSS WCHAN STA TTY TIME COMMAND
> 40 0 425 1 -1 -20 0 0 downDW< ? 0:00 (loop0)
It looks like this has been addressed in the thread "242-ac3 lo
it's still cosmetically annoying,
because it throws off the load average (a D state process is counted
as "running" for the loadavg calculation).
My loopback-mounted fs seems to be working fine, nevertheless, which
is a nice change from previous kernels.
--
Nate Eldredge
[EMAIL PROTEC
on
(no loopback involved). I can post the oops if anyone cares, but I
presume that loop-3 and 2.4.1ac17 are just incompatible.
--
Nate Eldredge
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
I can only read the list through a web
gateway, which is slow.
--
Nate Eldredge
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-inf
13 matches
Mail list logo
