From: Jakub Kicinski <kuba@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "david s. miller\" <davem@davemloft.net>,
eric dumazet <edumazet@google.com>,
paolo abeni <pabeni@redhat.com>,
netdev <netdev@vger.kernel.org>,
linux-kernel-mentees
<linux-kernel-mentees@lists.linuxfoundation.org>"@osuosl.org
Subject: Re: [PATCH v2] wifi: cfg80211: Fix UAF in ieee80211_scan_rx()
Date: Mon, 15 Aug 2022 17:51:14 -0700 [thread overview]
Message-ID: <20220815175114.5152bac5@kernel.org> (raw)
In-Reply-To: <18fd9b89d45aedc1504d0cbd299ffb289ae96438.camel@sipsolutions.net>
On Mon, 15 Aug 2022 21:58:24 +0200 Johannes Berg wrote:
> Yeah, that's slower, but scanning is still a relatively infrequent (and
> slow anyway) operation, and this way we can stick to "this is not used
> once you call cfg80211_scan_done()" which just makes much more sense?
SGTM, FWIW.
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next prev parent reply other threads:[~2022-09-02 16:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 12:39 [PATCH v2] wifi: cfg80211: Fix UAF in ieee80211_scan_rx() Siddh Raman Pant via Linux-kernel-mentees
2022-08-12 9:51 ` Siddh Raman Pant via Linux-kernel-mentees
2022-08-12 12:15 ` Greg KH
2022-08-12 14:33 ` Siddh Raman Pant via Linux-kernel-mentees
2022-08-12 15:27 ` Greg KH
2022-08-12 16:27 ` Siddh Raman Pant via Linux-kernel-mentees
2022-08-12 19:25 ` Jakub Kicinski
2022-08-13 16:19 ` Siddh Raman Pant via Linux-kernel-mentees
2022-08-15 16:47 ` Jakub Kicinski
2022-08-15 19:58 ` Johannes Berg
2022-08-16 0:51 ` Jakub Kicinski [this message]
2022-08-16 8:52 ` Siddh Raman Pant via Linux-kernel-mentees
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=20220815175114.5152bac5@kernel.org \
--to=kuba@kernel.org \
--cc="david s. miller\" <davem@davemloft.net>, eric dumazet <edumazet@google.com>, paolo abeni <pabeni@redhat.com>, netdev <netdev@vger.kernel.org>, linux-kernel-mentees <linux-kernel-mentees@lists.linuxfoundation.org>"@osuosl.org \
--cc=johannes@sipsolutions.net \
/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