From: Helmut Schaa <helmut.schaa@googlemail.com>
To: Jouni Malinen <j@w1.fi>
Cc: netdev@vger.kernel.org, "Zhu, Yi" <yi.zhu@intel.com>,
"ipw2100-devel@lists.sourceforge.net"
<ipw2100-devel@lists.sourceforge.net>
Subject: Re: [Ipw2100-devel] ipw2100: race between isr_indicate_associated and rx path
Date: Tue, 24 Feb 2009 08:36:42 +0100 [thread overview]
Message-ID: <200902240836.42948.helmut.schaa@gmail.com> (raw)
In-Reply-To: <20090223180801.GA29290@jm.kir.nu>
Am Montag, 23. Februar 2009 schrieb Jouni Malinen:
> On Mon, Feb 23, 2009 at 11:38:57AM +0100, Helmut Schaa wrote:
>
> > Jouni, would you accept a patch for wpa_supplicant that adds some retries
> > to l2_packet_send when the network stack returns an error?
[...]
> I did not fully understand the details of the issue and why noop_qdisc
> is used at the point when a frame is delivered to user space, so I may
> be missing some details here. Anyway, I would highly prefer the kernel
> to avoid delivering EAPOL frames into user space if it is not ready to
> transmit a response to them.
Sounds reasonable to me.
Helmut
next prev parent reply other threads:[~2009-02-24 8:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200901211734.48625.helmut.schaa@gmail.com>
[not found] ` <200901271521.24395.helmut.schaa@gmail.com>
[not found] ` <200902051511.31268.helmut.schaa@gmail.com>
2009-02-23 10:38 ` [Ipw2100-devel] ipw2100: race between isr_indicate_associated and rx path Helmut Schaa
2009-02-23 18:08 ` Jouni Malinen
2009-02-24 7:36 ` Helmut Schaa [this message]
2009-02-24 3:34 ` Zhu Yi
2009-02-24 3:34 ` Zhu Yi
2009-02-24 12:15 ` Helmut Schaa
2009-02-25 1:18 ` Zhu Yi
2009-02-25 1:18 ` Zhu Yi
2009-02-25 12:39 ` Helmut Schaa
2009-02-25 12:39 ` Helmut Schaa
2009-02-27 0:55 ` Zhu Yi
2009-02-27 0:55 ` Zhu Yi
2009-03-03 11:33 ` Helmut Schaa
2009-03-03 11:33 ` Helmut Schaa
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=200902240836.42948.helmut.schaa@gmail.com \
--to=helmut.schaa@googlemail.com \
--cc=ipw2100-devel@lists.sourceforge.net \
--cc=j@w1.fi \
--cc=netdev@vger.kernel.org \
--cc=yi.zhu@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.