linux-kernel - 答复: 答复: [PATCH v1] usb: gadget: u_serial: check Null pointer in EP callback

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID:
 <TYUPR06MB62175889B121F542869856E4D28C2@TYUPR06MB6217.apcprd06.prod.outlook.com>
Date: Mon, 19 Aug 2024 09:00:13 +0000
From: 胡连勤 <hulianqin@...o.com>
To: Michael Nazzareno Trimarchi <michael@...rulasolutions.com>
CC: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
	"quic_prashk@...cinc.com" <quic_prashk@...cinc.com>,
	"quic_jjohnson@...cinc.com" <quic_jjohnson@...cinc.com>,
	"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	opensource.kernel <opensource.kernel@...o.com>, "akpm@...ux-foundation.org"
	<akpm@...ux-foundation.org>
Subject:
 答复: 答复: [PATCH v1] usb: gadget: u_serial: check Null pointer in EP callback

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.

>It means that does not happen again?
 Yes.

>>  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).

>Yes I know but this monkey test is running a stress test moving from usb storage, to other configfs right?
 From the crash information, it can be seen that the switch is from mtp mode to vivo industrial mode port (adb+diag+cser_tty+gser_tty+rmnet)

Thanks