From: sashiko-bot@kernel.org
To: "Ingo Rohloff" <ingo.rohloff@lauterbach.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb: gadget: f_fs: Fix mmgrab()/mmdrop() balance.
Date: Mon, 09 Nov 2026 10:41:53 +0000 [thread overview]
Message-ID: <sashiko-outbox-204833@kernel.org> (raw)
In-Reply-To: <20261109103714.4000-1-ingo.rohloff@lauterbach.com>
> This fixes commit 5eb5c72c72fe ("USB: gadget: ffs: fix mm lifetime
> handling"). The problem is that the previous patch calls mmgrab() for
> reads and writes, but it only calls mmdrop() for reads. So with each
> completed async IO write (via an USB IN endpoint) the number of mm_count
> increases.
>
> Signed-off-by: Ingo Rohloff <ingo.rohloff@lauterbach.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261109103714.4000-1-ingo.rohloff@lauterbach.com?part=1
prev parent reply other threads:[~2026-11-09 10:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 10:37 [PATCH] usb: gadget: f_fs: Fix mmgrab()/mmdrop() balance Ingo Rohloff
2026-11-09 10:41 ` sashiko-bot [this message]
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=sashiko-outbox-204833@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=ingo.rohloff@lauterbach.com \
--cc=linux-usb@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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