From: Lovekesh Solanki <lovekeshsolanki00@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: jjy600901@snu.ac.kr, brauner@kernel.org, eulgyukim@snu.ac.kr,
gregkh@linuxfoundation.org, jack@suse.cz, kees@kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
mjguzik@gmail.com, viro@zeniv.linux.org.uk,
stable@vger.kernel.org
Subject: Re: [PATCH] USB: gadget: fix NULL pointer dereference in gadget_dev_ioctl()
Date: Tue, 25 Aug 2026 22:46:40 +0530 [thread overview]
Message-ID: <ao2-6IlxkmQbf96H@eggarch> (raw)
In-Reply-To: <13476f66-13e2-4625-9169-61af0596f6e0@rowland.harvard.edu>
On Tue, Aug 25, 2026 at 11:40:21AM -0400, Alan Stern wrote:
> But those facts would remain true even if gadgetfs_bind() were to write
> dev->gadget while holding the lock, wouldn't they? So the fact that the
> lock isn't held during the write makes no difference to your patch.
I understand now, I've dropped these irrelavant parts from the commit
message and removed the NULL check in v2.
Here is the link to v2:
https://lore.kernel.org/all/20260825171343.459630-1-lovekeshsolanki00@gmail.com/T/#u
Regards,
Lovekesh
next prev parent reply other threads:[~2026-08-25 17:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 11:35 [BUG] general protection fault in gadget_dev_ioctl Jaeyoung Chung
2026-08-25 10:58 ` [PATCH] USB: gadget: fix NULL pointer dereference in gadget_dev_ioctl() Lovekesh Solanki
2026-08-25 11:07 ` Lovekesh Solanki
2026-08-25 13:14 ` Alan Stern
2026-08-25 14:29 ` Lovekesh Solanki
2026-08-25 15:40 ` Alan Stern
2026-08-25 17:16 ` Lovekesh Solanki [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-08-24 16:00 [BUG] general protection fault in path_put Jaeyoung Chung
2026-08-25 10:46 ` [PATCH] USB: gadget: fix NULL pointer dereference in gadget_dev_ioctl() Lovekesh Solanki
2026-08-25 11:15 ` Lovekesh Solanki
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=ao2-6IlxkmQbf96H@eggarch \
--to=lovekeshsolanki00@gmail.com \
--cc=brauner@kernel.org \
--cc=eulgyukim@snu.ac.kr \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=jjy600901@snu.ac.kr \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mjguzik@gmail.com \
--cc=stable@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=viro@zeniv.linux.org.uk \
/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