From: Bob Copeland <me@bobcopeland.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, Thomas Graf <tgraf@suug.ch>,
netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] rhashtable: accept GFP flags in rhashtable_walk_init
Date: Thu, 3 Mar 2016 10:41:52 -0500 [thread overview]
Message-ID: <20160303154152.GE19848@localhost> (raw)
In-Reply-To: <1457018779.2044.22.camel@sipsolutions.net>
On Thu, Mar 03, 2016 at 04:26:19PM +0100, Johannes Berg wrote:
> On Wed, 2016-03-02 at 10:09 -0500, Bob Copeland wrote:
> > In certain cases, the 802.11 mesh pathtable code wants to
> > iterate over all of the entries in the forwarding table from
> > the receive path, which is inside an RCU read-side critical
> > section. Enable walks inside atomic sections by allowing
> > GFP_ATOMIC allocations for the walker state.
> >
> > Change all existing callsites to pass in GFP_KERNEL.
>
> Applied both. You missed 3 callsites, I've fixed those. I hope I got
> them all :)
Ouch, thanks for the catch, I must've grepped only in net.
And now I added those files to my build config. :)
--
Bob Copeland %% http://bobcopeland.com/
prev parent reply other threads:[~2016-03-03 15:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 15:09 [PATCH 1/2] rhashtable: accept GFP flags in rhashtable_walk_init Bob Copeland
2016-03-02 15:09 ` [PATCH 2/2] mac80211: mesh: convert path table to rhashtable Bob Copeland
2016-03-02 19:43 ` David Miller
2016-03-03 9:37 ` Johannes Berg
2016-03-03 15:26 ` [PATCH 1/2] rhashtable: accept GFP flags in rhashtable_walk_init Johannes Berg
2016-03-03 15:41 ` Bob Copeland [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=20160303154152.GE19848@localhost \
--to=me@bobcopeland.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
/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).