From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Kalle Valo <kvalo@kernel.org>
Cc: Ubisectech Sirius <bugreport@ubisectech.com>,
linux-trace-kernel <linux-trace-kernel@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
johannes <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Subject: Re: 回复：general protection fault in ath9k_wmi_event_tasklet
Date: Thu, 25 Jan 2024 15:22:08 +0100 [thread overview]
Message-ID: <87ttn1333j.fsf@toke.dk> (raw)
In-Reply-To: <87plxp1p05.fsf@kernel.org>
Kalle Valo <kvalo@kernel.org> writes:
> Toke Høiland-Jørgensen <toke@toke.dk> writes:
>
>> "Ubisectech Sirius" <bugreport@ubisectech.com> writes:
>>
>>>>Hmm, so from eyeballing the code in question, this looks like it is
>>>>another initialisation race along the lines of the one fixed in commit:
>>>>8b3046abc99e ("ath9k_htc: fix NULL pointer dereference at
>>>> ath9k_htc_tx_get_packet()")
>>>>Could you please test the patch below and see if you can still reproduce
>>>>this issue with that applied?
>>> Hello.
>>> I can not reproduce the issue on the Linux with the patch applied
>>> Ubisectech Sirius Team
>>
>> Great, thank you for testing! I'll send a proper patch. How would you
>> like to be credited with reporting? Just as 'Ubisectech Sirius
>> <bugreport@ubisectech.com>' ?
>
> Ubisectech, please CC linux-wireless on any wireless issues and don't
> use HTML format in emails. More info in the wiki below.
Doh, didn't even notice that linux-wireless was not in Cc. Sorry about
that! :(
-Toke
next prev parent reply other threads:[~2024-01-25 14:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ed1d2c66-1193-4c81-9542-d514c29ba8b8.bugreport@ubisectech.com>
[not found] ` <878r4e4q69.fsf@toke.dk>
[not found] ` <fb3ea26f-f9b6-4107-bb03-ca4893f0495f.bugreport@ubisectech.com>
[not found] ` <87wmrx34np.fsf@toke.dk>
2024-01-25 14:11 ` 回复：general protection fault in ath9k_wmi_event_tasklet Kalle Valo
2024-01-25 14:22 ` Toke Høiland-Jørgensen [this message]
[not found] ` <0320fac8-68dd-40a6-bb38-1da0d71d0dbd.>
2024-01-26 1:14 ` 回复：回复：general " Ubisectech Sirius
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=87ttn1333j.fsf@toke.dk \
--to=toke@toke.dk \
--cc=bugreport@ubisectech.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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).