From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: ronny.meeus@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH] [PATCH] Fix deadlock in af_packet while stressing raw ethernet socket interface
Date: Tue, 12 Jul 2011 00:19:53 -0700 (PDT) [thread overview]
Message-ID: <20110712.001953.709404117315345178.davem@davemloft.net> (raw)
In-Reply-To: <1310453928.2860.32.camel@edumazet-laptop>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Tue, 12 Jul 2011 08:58:48 +0200
> This seems a bug, but in softirq handling in your arch
That's not the problem, it's the dev_queue_xmit_nit() code
path that interrupt is interrupting.
next prev parent reply other threads:[~2011-07-12 7:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-11 5:04 [PATCH] [PATCH] Fix deadlock in af_packet while stressing raw ethernet socket interface Ronny Meeus
2011-07-12 3:27 ` David Miller
2011-07-12 6:38 ` Ronny Meeus
2011-07-12 6:42 ` David Miller
2011-07-12 6:58 ` Eric Dumazet
2011-07-12 7:19 ` David Miller [this message]
2011-07-12 8:23 ` Eric Dumazet
2011-07-12 8:26 ` David Miller
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=20110712.001953.709404117315345178.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=ronny.meeus@gmail.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