From: Ping-Ke Shih <pkshih@realtek.com>
To: "Guilherme G. Piccoli" <gpiccoli@igalia.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: "kvalo@kernel.org" <kvalo@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kernel@gpiccoli.net" <kernel@gpiccoli.net>,
"kernel-dev@igalia.com" <kernel-dev@igalia.com>,
"rtl8821cerfe2@gmail.com" <rtl8821cerfe2@gmail.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"syzbot+edd9fe0d3a65b14588d5@syzkaller.appspotmail.com"
<syzbot+edd9fe0d3a65b14588d5@syzkaller.appspotmail.com>
Subject: RE: [PATCH V3] wifi: rtlwifi: Drastically reduce the attempts to read efuse in case of failures
Date: Fri, 1 Nov 2024 02:26:56 +0000 [thread overview]
Message-ID: <ae95544aabe74d1da801fed6cc73896e@realtek.com> (raw)
In-Reply-To: <20241031155731.1253259-1-gpiccoli@igalia.com>
>
> [0] Commit 15fffc6a5624 ("driver core: Fix uevent_show() vs driver detach race").
>
> [1] A note about that: this syzkaller report presents multiple reproducers
> that differs by the type of emulated USB device. For this specific case,
> check the entry from 2024/08/08 06:23 in the list of crashes; the C repro
> is available at https://syzkaller.appspot.com/text?tag=ReproC&x=1521fc83980000.
Have you run checkpatch before submission? Above two information can be in
formal form as suggestions of checkpatch.
WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#55:
in case of failures, restricted to USB devices (given that they're inherently
WARNING: Reported-by: should be immediately followed by Closes: with a URL to the report
#72:
Reported-by: syzbot+edd9fe0d3a65b14588d5@syzkaller.appspotmail.com
Signed-off-by: Guilherme G. Piccoli <gpiccoli@igalia.com>
WARNING: The commit message has 'syzkaller', perhaps it also needs a 'Fixes:' tag?
total: 0 errors, 3 warnings, 0 checks, 28 lines checked
>
> Cc: stable@vger.kernel.org # v6.1+
> Reported-by: syzbot+edd9fe0d3a65b14588d5@syzkaller.appspotmail.com
> Signed-off-by: Guilherme G. Piccoli <gpiccoli@igalia.com>
next prev parent reply other threads:[~2024-11-01 2:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 15:55 [PATCH V3] wifi: rtlwifi: Drastically reduce the attempts to read efuse in case of failures Guilherme G. Piccoli
2024-11-01 2:26 ` Ping-Ke Shih [this message]
2024-11-01 19:29 ` Guilherme G. Piccoli
2024-11-01 4:22 ` Ping-Ke Shih
2024-11-01 19:38 ` Guilherme G. Piccoli
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=ae95544aabe74d1da801fed6cc73896e@realtek.com \
--to=pkshih@realtek.com \
--cc=gpiccoli@igalia.com \
--cc=kernel-dev@igalia.com \
--cc=kernel@gpiccoli.net \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rtl8821cerfe2@gmail.com \
--cc=stable@vger.kernel.org \
--cc=syzbot+edd9fe0d3a65b14588d5@syzkaller.appspotmail.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