stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Charan Teja Reddy <charante@codeaurora.org>
To: sumit.semwal@linaro.org, ghackmann@google.com, fengc@google.com
Cc: linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH v2] dma-buf: fix use-after-free in dmabuffs_dname
Date: Sat, 09 May 2020 12:30:55 +0000	[thread overview]
Message-ID: <20200509123055.B7CF9218AC@mail.kernel.org> (raw)
In-Reply-To: <1588920063-17624-1-git-send-email-charante@codeaurora.org>

Hi

[This is an automated email]

This commit has been processed because it contains a "Fixes:" tag
fixing commit: bb2bb9030425 ("dma-buf: add DMA_BUF_SET_NAME ioctls").

The bot has tested the following trees: v5.6.11, v5.4.39.

v5.6.11: Build OK!
v5.4.39: Failed to apply! Possible dependencies:
    15fd552d186c ("dma-buf: change DMA-buf locking convention v3")


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-05-09 12:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-08  6:41 [PATCH v2] dma-buf: fix use-after-free in dmabuffs_dname Charan Teja Reddy
2020-05-09 12:30 ` Sasha Levin [this message]
2020-05-12  8:52 ` Greg KH
2020-05-13 12:10   ` Charan Teja Kalla
2020-05-13 12:51     ` Greg KH
2020-05-13 15:46       ` Daniel Vetter
2020-05-13 16:03         ` Sumit Semwal
2020-05-14 13:00           ` Charan Teja Kalla
  -- strict thread matches above, loose matches on Subject: below --
2020-05-08  6:23 Charan Teja Reddy

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=20200509123055.B7CF9218AC@mail.kernel.org \
    --to=sashal@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-media@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).