From: Gabriel Prostitis <prostitisgabriel@gmail.com>
To: gregkh@linuxfoundation.org
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] USB: gadget: fix mm lifetime use-after-free in async read paths
Date: Tue, 30 Jun 2026 17:02:45 +0200 [thread overview]
Message-ID: <20260630150245.2730992-1-prostitisgabriel@gmail.com> (raw)
In-Reply-To: <20260601-mm-uaf-fix-v2-0-3c942a707bce@gmail.com>
Hi,
Just a gentle ping on this series.
I noticed that it has not shown up in -next yet, so I wanted to check
whether there is anything else I should address.
Thanks,
Gabriel
next prev parent reply other threads:[~2026-06-30 15:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 6:44 [PATCH v2 0/2] USB: gadget: fix mm lifetime use-after-free in async read paths Gabriel Prostitis via B4 Relay
2026-06-01 6:44 ` [PATCH v2 1/2] USB: gadget: ffs: fix mm lifetime handling Gabriel Prostitis via B4 Relay
2026-06-01 6:44 ` [PATCH v2 2/2] USB: gadget: inode: " Gabriel Prostitis via B4 Relay
2026-06-30 15:02 ` Gabriel Prostitis [this message]
2026-07-01 5:40 ` [PATCH v2 0/2] USB: gadget: fix mm lifetime use-after-free in async read paths Greg KH
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=20260630150245.2730992-1-prostitisgabriel@gmail.com \
--to=prostitisgabriel@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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