From: Edward Adam Davis <eadavis@qq.com>
To: johannes@sipsolutions.net
Cc: eadavis@qq.com, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
syzbot+064815c6cd721082a52a@syzkaller.appspotmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH] wifi: mac80211_hwsim: Prevent tsf from setting if beacon is disabled
Date: Wed, 23 Apr 2025 22:10:57 +0800 [thread overview]
Message-ID: <tencent_FEF364E367496283BA444AD771577226CA05@qq.com> (raw)
In-Reply-To: <ff63580712b8f20b4be7b38a31bc3bb9d69a4820.camel@sipsolutions.net>
On Wed, 23 Apr 2025 16:04:04 +0200, Johannes Berg wrote:
> On Wed, 2025-04-23 at 21:56 +0800, Edward Adam Davis wrote:
> > On Wed, 23 Apr 2025 14:53:53 +0200, Johannes Berg wrote:
> > > > --- a/drivers/net/wireless/virtual/mac80211_hwsim.c
> > > > +++ b/drivers/net/wireless/virtual/mac80211_hwsim.c
> > > > @@ -1226,6 +1226,11 @@ static void mac80211_hwsim_set_tsf(struct ieee80211_hw *hw,
> > > > {
> > > > struct mac80211_hwsim_data *data = hw->priv;
> > > > u64 now = mac80211_hwsim_get_tsf(hw, vif);
> > > > + struct ieee80211_bss_conf *conf = link_conf_dereference_protected(vif,
> > > > + data->link_data[0].link_id);
> > > > +
> > > > + if (conf && !conf->enable_beacon)
> > > > + return;
> > > > /* MLD not supported here */
> > > > u32 bcn_int = data->link_data[0].beacon_int;
> > > > u64 delta = abs(tsf - now);
> > >
> > > Please keep kernel coding style - the line break there is awful (but
> > > with "conf = ..." on a line by itself it can be just one line), and you
> > > shouldn't have code before variable declarations.
> > like this?
>
> Looks good I guess, not sure you wanted bcn_int/delta to be calculated
> before or after.
It will be all right.
I will send V2 patch.
>
> > > The comment should probably also move because it's relevant for your new
> > > [0] as well.
> > I don't understand what you mean.
>
> The "/* MLD not supported here */" comment refers to the [0] - it
> explains why the [0] (rather than link id) is OK. So it also applies to
> your [0], if you're going to put it before the comment then IMHO it
> makes sense to move the comment. With what you did now the comment is
> still earlier though, of course.
Oh, Got it.
Edward
next prev parent reply other threads:[~2025-04-23 14:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-12 20:14 [syzbot] [wireless?] divide error in mac80211_hwsim_set_tsf syzbot
2025-04-13 5:35 ` Edward Adam Davis
2025-04-13 5:54 ` syzbot
2025-04-13 6:11 ` [PATCH] wifi: mac80211_hwsim: Prevent tsf from setting if beacon is disabled Edward Adam Davis
2025-04-23 12:53 ` Johannes Berg
2025-04-23 13:56 ` Edward Adam Davis
2025-04-23 14:04 ` Johannes Berg
2025-04-23 14:10 ` Edward Adam Davis [this message]
2025-04-23 14:15 ` [PATCH V2] " Edward Adam Davis
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=tencent_FEF364E367496283BA444AD771577226CA05@qq.com \
--to=eadavis@qq.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+064815c6cd721082a52a@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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
all inboxes | Powered by JetHome®