From: Johannes Berg <johannes@sipsolutions.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Bob Copeland <me@bobcopeland.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] nl80211: use GFP_ATOMIC for michael mic failure message
Date: Tue, 02 Jun 2009 15:54:17 +0200 [thread overview]
Message-ID: <1243950857.4516.0.camel@johannes.local> (raw)
In-Reply-To: <20090602131222.GA30509@tuxdriver.com>
[-- Attachment #1: Type: text/plain, Size: 488 bytes --]
On Tue, 2009-06-02 at 09:12 -0400, John W. Linville wrote:
> On Tue, Jun 02, 2009 at 12:05:04AM -0400, Bob Copeland wrote:
> > nl80211_michael_mic_failure can be called in atomic context but
> > does a GFP_KERNEL allocation. Fixes the error below:
>
> This is not the first one of these. Anyone care to audit nl80211.c for others?
We should just make them all take a gfp_t argument and use that instead
so the caller gets to specify it... Anyone want to do that?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
prev parent reply other threads:[~2009-06-02 13:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 4:05 [PATCH] nl80211: use GFP_ATOMIC for michael mic failure message Bob Copeland
2009-06-02 13:12 ` John W. Linville
2009-06-02 13:54 ` Johannes Berg [this message]
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=1243950857.4516.0.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=me@bobcopeland.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;
as well as URLs for NNTP newsgroup(s).