mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: Bob Gill <gillb4@telusplanet.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	akepner@sgi.com
Subject: Re: [2.6.7-bk] NFS-related kernel panic
Date: Mon, 21 Jun 2004 20:35:21 -0700	[thread overview]
Message-ID: <20040621203520.H22989@build.pdx.osdl.net> (raw)
In-Reply-To: <1087872607.4066.13.camel@localhost.localdomain>; from gillb4@telusplanet.net on Mon, Jun 21, 2004 at 08:50:08PM -0600

* Bob Gill (gillb4@telusplanet.net) wrote:
> Ok.  I get (a very similar) error with 2.6.7-bk4.
> The error message I get is:
> Starting portmapper:                            [OK]
> Starting NFS statd: Kernel panic: Aiee, killing interrupt handler!
> bad: scheduling while atomic!
>  [<c02a2c37>] schedule+0x483/0x488
>  [<c0133298>] __get_free_pages+0x33/0x3f
>  [<c026974c>] tcp_poll+0x34/0x15a
>  [<c02a30b5>] schedule_timeout+0xb5/0xb7
>  [<c0248fb3>] sock_poll+0x29/0x31
>  [<c015da2e>] do_pollfd+0x4f/0x90
>  [<c015db10>] do_poll+0xa1/0xc0
>  [<c016dc7e>] sys_poll+0x14f/0x211
>  [<c015d09d>] __pollwait+0x0/0xc6
>  [<c014afd2>] sys_close+0x63/0x96
>  [<c0103eb1>] sysenter_past_esp+0x52/0x71
> In interrupt handler - not syncing

The lockless loopback transmission patch mucks up the preempt count.
Can you give this patch a try?

thanks,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

===== loopback.c 1.15 vs edited =====
--- 1.15/drivers/net/loopback.c	2004-06-20 17:35:52 -07:00
+++ edited/loopback.c	2004-06-21 20:23:06 -07:00
@@ -143,10 +143,11 @@
 
 	dev->last_rx = jiffies;
 	if (likely(loopback_stats)) {
-		get_cpu_ptr(loopback_stats)->rx_bytes += skb->len;
-		get_cpu_ptr(loopback_stats)->tx_bytes += skb->len;
-		get_cpu_ptr(loopback_stats)->rx_packets++;
-		get_cpu_ptr(loopback_stats)->tx_packets++;
+		struct net_device_stats *stats = get_cpu_ptr(loopback_stats);
+		stats->rx_bytes += skb->len;
+		stats->tx_bytes += skb->len;
+		stats->rx_packets++;
+		stats->tx_packets++;
 		put_cpu_ptr(loopback_stats);
 	}
 

  reply	other threads:[~2004-06-22  3:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-22  2:50 Bob Gill
2004-06-22  3:35 ` Chris Wright [this message]
2004-06-22 13:37   ` Stewart Smith
2004-06-22 14:01     ` Grzegorz Kulewski
2004-06-22 16:11   ` Arthur Kepner
     [not found] <fa.l7nhc0k.1k1oepm@ifi.uio.no>
     [not found] ` <fa.gh5h9hv.b2sm3v@ifi.uio.no>
2004-06-22 21:14   ` walt
2004-06-22 21:27     ` Chris Wright
2004-06-23 13:58 walt
2004-06-21 18:39 ` Grzegorz Kulewski

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=20040621203520.H22989@build.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=akepner@sgi.com \
    --cc=gillb4@telusplanet.net \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®