stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Sriharsha Allenki <sallenki@codeaurora.org>
To: balbi@kernel.org, gregkh@linuxfoundation.org
Cc: peter.chen@nxp.com, stable@vger.kernel.org, mgautam@codeaurora.org
Cc: stable <stable@vger.kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH v2] usb: gadget: f_fs: Fix use after free issue as part of queue failure
Date: Fri, 27 Mar 2020 15:03:40 +0000	[thread overview]
Message-ID: <20200327150340.EFAF62072F@mail.kernel.org> (raw)
In-Reply-To: <20200326115620.12571-1-sallenki@codeaurora.org>

Hi

[This is an automated email]

This commit has been processed because it contains a "Fixes:" tag
fixing commit: 2e4c7553cd6f ("usb: gadget: f_fs: add aio support").

The bot has tested the following trees: v5.5.11, v5.4.27, v4.19.112, v4.14.174, v4.9.217, v4.4.217.

v5.5.11: Build OK!
v5.4.27: Build OK!
v4.19.112: Build OK!
v4.14.174: Build OK!
v4.9.217: Build OK!
v4.4.217: Failed to apply! Possible dependencies:
    3163c79efa65 ("usb: f_fs: fix ffs_epfile_io returning success on req alloc failure")
    3de4e2056817 ("usb: f_fs: fix memory leak when ep changes during transfer")
    ae76e13477d8 ("usb: f_fs: refactor ffs_epfile_io")


NOTE: The patch will not be queued to stable trees until it is upstream.

How should we proceed with this patch?

-- 
Thanks
Sasha

      reply	other threads:[~2020-03-27 15:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26 11:56 [PATCH v2] usb: gadget: f_fs: Fix use after free issue as part of queue failure Sriharsha Allenki
2020-03-27 15:03 ` Sasha Levin [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=20200327150340.EFAF62072F@mail.kernel.org \
    --to=sashal@kernel.org \
    --cc=mgautam@codeaurora.org \
    --cc=peter.chen@nxp.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;
as well as URLs for NNTP newsgroup(s).