From: Andrew Morton <akpm@zip.com.au>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: William Lee Irwin III <wli@holomorphy.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.31 kmap_atomic copy_*_user benefits
Date: Thu, 15 Aug 2002 23:33:59 -0700 [thread overview]
Message-ID: <3D5C9CD7.55287BCB@zip.com.au> (raw)
In-Reply-To: 3D5C5F05.7080004@us.ibm.com
Dave Hansen wrote:
>
> William Lee Irwin III wrote:
> > With and without kmap_atomic() -based copy_*_user() patches from akpm.
> > Taken on a 16x/16GB box.
>
> Have you seen any instability with these things applied? I seem to be
> getting a fair amount of these BUG()s. But, I imagine that it could
> be a race uncovered because of the serialization that highmem locks
> caused.
>
> kernel BUG at softirq.c:229!
I just hit it. No kmap patches though.
> ...
>
> >>EIP; 8011c8dd <tasklet_hi_action+5d/c4> <=====
>
> >>ebx; 80374f54 <bh_task_vec+14/280>
> >>ecx; 8037e194 <tv1+14/804>
> >>ebp; 80357560 <__bss_start+0/0>
>
> Trace; 8011c62a <do_softirq+5a/ac>
> Trace; 801092e1 <do_IRQ+f1/100>
> Trace; 80105334 <poll_idle+0/48>
> Trace; 80107d28 <common_interrupt+18/20>
> Trace; 80105334 <poll_idle+0/48>
> Trace; 8010535d <poll_idle+29/48>
> Trace; 801053b3 <cpu_idle+37/48>
#0 tasklet_hi_action (a=0xc03671a0) at softirq.c:230
#1 0xc011e74d in do_softirq () at softirq.c:89
#2 0xc0112b53 in smp_apic_timer_interrupt (regs=
{ebx = -1056148556, ecx = 8, edx = 1024, esi = 134587171, edi = -997773344, ebp = -870006964, eax = 0, xds = -870055832, xes = -1072562072, orig_eax = -17, eip = -1072501662, xcs = 96, eflags = 66054, esp = -965588688, xss = 63491})
at apic.c:1091
#3 0xc0107f7a in apic_timer_interrupt () at stats.c:204
#4 0xc012ee3f in generic_file_write (file=0xcb90d5e0, buf=0x804b340 '\001' <repeats 200 times>..., count=63491,
ppos=0xcb90d600) at filemap.c:2085
#5 0xc013e210 in vfs_write (file=0xcb90d5e0, buf=0x804b340 '\001' <repeats 200 times>..., count=63491, pos=0xcb90d600)
(gdb) p t->func
$1 = (void (*)()) 0xc011eb90 <bh_action>
(gdb) p t->data
$2 = 0
(gdb) p bh_base[0]
$3 = (void (*)()) 0xc0121c94 <timer_bh>
prev parent reply other threads:[~2002-08-16 6:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-15 23:21 2.5.31 kmap_atomic copy_*_user benefits William Lee Irwin III
2002-08-15 23:26 ` William Lee Irwin III
2002-08-15 23:27 ` William Lee Irwin III
2002-08-15 23:30 ` William Lee Irwin III
2002-08-15 23:31 ` William Lee Irwin III
2002-08-15 23:35 ` William Lee Irwin III
2002-08-18 8:36 ` Daniel Phillips
2002-08-16 2:10 ` Dave Hansen
2002-08-16 2:44 ` William Lee Irwin III
2002-08-16 2:52 ` Dave Hansen
2002-08-16 6:33 ` Andrew Morton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3D5C9CD7.55287BCB@zip.com.au \
--to=akpm@zip.com.au \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox