public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Petko Manolov <petko.manolov@konsulko.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, kuba@kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] net: usb: pegasus: fix memory leak on usb_submit_urb() failure
Date: Fri, 2 Jan 2026 14:10:11 +0200	[thread overview]
Message-ID: <20260102121011.GA25015@carbon.k.g> (raw)
In-Reply-To: <b3d2a2fa-35cb-48ad-ad2e-de997e9b2395@redhat.com>

On 25-12-23 12:44:53, Paolo Abeni wrote:
> On 12/16/25 7:41 PM, Petko Manolov wrote:
> > In update_eth_regs_async() neither the URB nor the request structure are being
> > freed if usb_submit_urb() fails.  The patch fixes this long lurking bug in the
> > error path.
> > 
> > Signed-off-by: Petko Manolov <petko.manolov@konsulko.com>
> 
> Please:
> - include the targed tree in the subj prefix ('net' in this case)
> - include a suitable Fixes tag

Sure, will do.  However, my v2 patch makes use of __free() cleanup
functionality, which in turn only applies back to v6.6 stable kernels.

I guess i shall make another version of the patch that is suitable only for v5.4
to v6.1 stable releases, right?  How shall i format the patch so that it targets
only these old versions?


cheers,
Petko

  reply	other threads:[~2026-01-02 12:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-16 18:41 [PATCH] net: usb: pegasus: fix memory leak on usb_submit_urb() failure Petko Manolov
2025-12-16 18:43 ` kernel test robot
2025-12-23 11:44 ` Paolo Abeni
2026-01-02 12:10   ` Petko Manolov [this message]
2026-01-02 22:02     ` Andrew Lunn
2026-01-06  9:15       ` Petko Manolov

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=20260102121011.GA25015@carbon.k.g \
    --to=petko.manolov@konsulko.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=stable@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