From: 胡连勤 <hulianqin@vivo.com>
To: Michael Nazzareno Trimarchi <michael@amarulasolutions.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"quic_prashk@quicinc.com" <quic_prashk@quicinc.com>,
"quic_jjohnson@quicinc.com" <quic_jjohnson@quicinc.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
opensource.kernel <opensource.kernel@vivo.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Subject: 答复: 答复: [PATCH v1] usb: gadget: u_serial: check Null pointer in EP callback
Date: Mon, 19 Aug 2024 08:48:22 +0000 [thread overview]
Message-ID: <TYUPR06MB62171FA07658FE6500DB855FD28C2@TYUPR06MB6217.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <CAOf5uwmdf+Vxes6+BQyghbiKByVC_i1RhmTE81_iix99U7HMmA@mail.gmail.com>
Hello linux community expert:
>> >>I think this has been reported previously, and different patches have been proposed, have you searched the archives?
>> > I haven't seen the patch given below before, I will read it carefully.
>> > I searched for Linux mainline commits before submitting, but I only compared them according to the crash stack information and did not notice the following commit.
>> I checked the stack trace again. The problem we encountered seems different from the problem reported in the link below, and they are not caused by the same reason.
>>
>Did you apply the patch? as suggested, is the test moving from one gadget to the other?
We apply the patch into kernel 5.15 and ran a stress test, and the problem did not recur.
Connect the phone to the PC via a USB cable and run the monkey test (run an apk and click on it at will on the phone interface).
Thanks
next prev parent reply other threads:[~2024-08-19 8:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 11:21 [PATCH v1] usb: gadget: u_serial: check Null pointer in EP callback 胡连勤
2024-08-16 11:57 ` gregkh
2024-08-16 12:16 ` Michael Nazzareno Trimarchi
2024-08-16 13:30 ` 答复: " 胡连勤
2024-08-16 13:38 ` Michael Nazzareno Trimarchi
2024-08-16 14:19 ` 答复: " 胡连勤
2024-08-16 14:42 ` gregkh
2024-08-16 15:17 ` 答复: " 胡连勤
2024-08-19 8:26 ` 胡连勤
2024-08-19 8:41 ` Michael Nazzareno Trimarchi
2024-08-19 8:48 ` 胡连勤 [this message]
2024-08-19 8:53 ` Michael Nazzareno Trimarchi
2024-08-19 9:00 ` 答复: " 胡连勤
2024-08-19 9:17 ` Michael Nazzareno Trimarchi
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=TYUPR06MB62171FA07658FE6500DB855FD28C2@TYUPR06MB6217.apcprd06.prod.outlook.com \
--to=hulianqin@vivo.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=michael@amarulasolutions.com \
--cc=opensource.kernel@vivo.com \
--cc=quic_jjohnson@quicinc.com \
--cc=quic_prashk@quicinc.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