All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Xinyu Zheng <zhengxinyu6@huawei.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH v5.10] vhost-scsi: protect vq->log_used with vq->mutex
Date: Thu,  3 Jul 2025 14:34:43 -0400	[thread overview]
Message-ID: <20250703112547-6bc1d2921101421a@stable.kernel.org> (raw)
In-Reply-To: <20250702082945.4164475-1-zhengxinyu6@huawei.com>

[ Sasha's backport helper bot ]

Hi,

✅ All tests passed successfully. No issues detected.
No action required from the submitter.

The upstream commit SHA1 provided is correct: f591cf9fce724e5075cc67488c43c6e39e8cbe27

WARNING: Author mismatch between patch and upstream commit:
Backport author: Xinyu Zheng<zhengxinyu6@huawei.com>
Commit author: Dongli Zhang<dongli.zhang@oracle.com>

Status in newer kernel trees:
6.15.y | Present (exact SHA1)
6.12.y | Present (different SHA1: bd8c9404e44a)
6.6.y | Present (different SHA1: ca85c2d0db5f)
6.1.y | Not found
5.15.y | Not found

Note: The patch differs from the upstream commit:
---
1:  f591cf9fce724 < -:  ------------- vhost-scsi: protect vq->log_used with vq->mutex
-:  ------------- > 1:  4cd7a98212613 vhost-scsi: protect vq->log_used with vq->mutex
---

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.10.y       |  Success    |  Success   |

  reply	other threads:[~2025-07-03 18:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-02  8:29 [PATCH v5.10] vhost-scsi: protect vq->log_used with vq->mutex Xinyu Zheng
2025-07-03 18:34 ` Sasha Levin [this message]
2025-07-10 13:41 ` Greg KH
2025-07-14  9:42   ` zhengxinyu (E)

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=20250703112547-6bc1d2921101421a@stable.kernel.org \
    --to=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=zhengxinyu6@huawei.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.