[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <634cde01c2ab0cf00f7c82791dd93fec07aef976.camel@sipsolutions.net>
Date: Wed, 13 Feb 2019 15:55:12 +0100
From: Johannes Berg <johannes@...solutions.net>
To: Herbert Xu <herbert@...dor.apana.org.au>,
David Miller <davem@...emloft.net>,
linux-wireless@...r.kernel.org, netdev@...r.kernel.org, j@...fi,
tgraf@...g.ch
Subject: Re: [v2 PATCH 0/4] mac80211: Fix incorrect usage of rhashtable walk
API
On Wed, 2019-02-13 at 22:38 +0800, Herbert Xu wrote:
> Hi:
>
> The first two patches in this series are bug fixes and should be
> backported to stable.
>
> They fixes a number of issues with the use of the rhashtable API
> in mac80211. First of all it converts the use of rashtable walks over
> to a simple linked list. This is because an rhashtable walk is
> inherently unstable and not meant for uses that require stability,
> e.g., when you're trying to lookup an object to delete.
>
> It also fixes a potential memory leak when the rhashtable insertion
> fails (which can occur due to OOM).
Thanks a lot Herbert! That looks simpler than I thought it would be.
johannes
Powered by blists - more mailing lists