From: Manfred Spraul <manfred@colorfullife.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: kuznet@ms2.inr.ac.ru, "David S. Miller" <davem@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: more tcpdumpinfo for nfs3 problem: aix-server --- linux 2.4.15pre5 client
Date: Wed, 21 Nov 2001 20:09:04 +0100 [thread overview]
Message-ID: <3BFBFBD0.D7923E9B@colorfullife.com> (raw)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
> IOW:
> Either we must demand that CPU 2 uses irq-safe spinlocks in order to
> protect against sk->write_space(), or we must demand that CPU 1 should drop
> 'lock1' before being allowed to call dev_kfree_skb_any().
Or dev_kfree_skb_any() should consider disabled local interrupts as
'in_irq()' and call dev_kfree_skb_irq() in this case, or the driver
could call dev_kfree_irq() if it really wants to free while holding an
irq spinlock.
But that's a known problem:
http://groups.google.com/groups?q=dev_kfree_skb_any&hl=en&rnum=1&selm=linux.net.20010905.184245.94554736.davem%40redhat.com
--
Manfred
next reply other threads:[~2001-11-21 19:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-21 19:09 Manfred Spraul [this message]
2001-11-21 19:23 ` more tcpdumpinfo for nfs3 problem: aix-server --- linux 2.4.15pre5 kuznet
2001-11-21 20:33 ` Manfred Spraul
-- strict thread matches above, loose matches on Subject: below --
2001-11-19 11:16 IPV4 socket layer, was: nfs problem: aix-server --- linux 2.4.15pre5 client Alan Cox
2001-11-19 10:20 ` Birger Lammering
2001-11-19 16:37 ` more tcpdumpinfo for nfs3 " Birger Lammering
2001-11-20 9:26 ` Birger Lammering
2001-11-19 18:22 ` Trond Myklebust
2001-11-19 18:49 ` kuznet
2001-11-19 18:55 ` Trond Myklebust
2001-11-19 19:09 ` kuznet
2001-11-19 19:29 ` Trond Myklebust
2001-11-19 19:52 ` kuznet
2001-11-19 20:38 ` Trond Myklebust
2001-11-19 21:17 ` Trond Myklebust
2001-11-20 17:42 ` kuznet
2001-11-20 19:39 ` Trond Myklebust
2001-11-20 19:45 ` kuznet
2001-11-20 20:29 ` Trond Myklebust
2001-11-21 10:07 ` Trond Myklebust
2001-11-21 17:05 ` kuznet
2001-11-20 20:05 ` Trond Myklebust
2001-11-20 20:18 ` David S. Miller
2001-11-20 17:41 ` kuznet
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=3BFBFBD0.D7923E9B@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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®