From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/2] mac80211: protect skb_queue_len(&ps->bc_buf) by lock
Date: Thu, 20 Feb 2014 08:56:40 +0100 [thread overview]
Message-ID: <20140220075639.GA23439@redhat.com> (raw)
In-Reply-To: <1392827818.4733.27.camel@jlt4.sipsolutions.net>
On Wed, Feb 19, 2014 at 05:36:58PM +0100, Johannes Berg wrote:
> Well, OK, so there's some small window of time where the drop code isn't
> perfect. Does it matter? I'd argue it doesn't - if you're getting close
> to the drop case then the client is probably misbehaving anyway.
Ok, let drop those patches. Do you want me to repost first patch with
just if(old) check to fix kaboom, or you prefer to problem be solved
properly at once ?
Stanislaw
next prev parent reply other threads:[~2014-02-20 7:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 12:28 [PATCH 1/2] mac80211: fix calling ieee80211_free_txskb with NULL skb Stanislaw Gruszka
2014-02-19 12:28 ` [PATCH 2/2] mac80211: protect skb_queue_len(&ps->bc_buf) by lock Stanislaw Gruszka
2014-02-19 13:14 ` Johannes Berg
2014-02-19 13:35 ` Stanislaw Gruszka
2014-02-19 14:51 ` Johannes Berg
2014-02-19 15:09 ` Stanislaw Gruszka
2014-02-19 16:36 ` Johannes Berg
2014-02-20 7:56 ` Stanislaw Gruszka [this message]
2014-02-20 7:59 ` Johannes Berg
2014-02-20 8:17 ` Stanislaw Gruszka
2014-02-19 12:33 ` [PATCH 1/2] mac80211: fix calling ieee80211_free_txskb with NULL skb Johannes Berg
2014-02-19 12:39 ` Grumbach, Emmanuel
2014-02-19 12:46 ` Grumbach, Emmanuel
2014-02-19 13:21 ` Stanislaw Gruszka
2014-02-19 14:48 ` Stanislaw Gruszka
2014-02-19 14:50 ` Johannes Berg
2014-02-19 15:00 ` Stanislaw Gruszka
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=20140220075639.GA23439@redhat.com \
--to=sgruszka@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).