All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Hagar Hemdan <hagarhem@amazon.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.4] net: xen-netback: hash.c: Use built-in RCU list checking
Date: Wed, 22 Jan 2025 17:38:52 -0500	[thread overview]
Message-ID: <20250122143830-2c63e93d0cc2d07f@stable.kernel.org> (raw)
In-Reply-To: <20250122174344.10000-1-hagarhem@amazon.com>

[ Sasha's backport helper bot ]

Hi,

The upstream commit SHA1 provided is correct: f3265971ded98a069ad699b51b8a5ab95e9e5be1

WARNING: Author mismatch between patch and upstream commit:
Backport author: Hagar Hemdan<hagarhem@amazon.com>
Commit author: Madhuparna Bhowmik<madhuparnabhowmik04@gmail.com>


Status in newer kernel trees:
6.12.y | Present (exact SHA1)
6.6.y | Present (exact SHA1)
6.1.y | Present (exact SHA1)
5.15.y | Present (exact SHA1)
5.10.y | Present (exact SHA1)
5.4.y | Not found

Note: The patch differs from the upstream commit:
---
1:  f3265971ded98 ! 1:  3a1397498ef8f net: xen-netback: hash.c: Use built-in RCU list checking
    @@ Metadata
      ## Commit message ##
         net: xen-netback: hash.c: Use built-in RCU list checking
     
    +    commit f3265971ded98a069ad699b51b8a5ab95e9e5be1 upstream.
    +
         list_for_each_entry_rcu has built-in RCU and lock checking.
         Pass cond argument to list_for_each_entry_rcu.
     
         Signed-off-by: Madhuparna Bhowmik <madhuparnabhowmik04@gmail.com>
         Acked-by: Wei Liu <wei.liu@kernel.org>
         Signed-off-by: David S. Miller <davem@davemloft.net>
    +    Signed-off-by: Hagar Hemdan <hagarhem@amazon.com>
     
      ## drivers/net/xen-netback/hash.c ##
     @@ drivers/net/xen-netback/hash.c: static void xenvif_add_hash(struct xenvif *vif, const u8 *tag,
---

Results of testing on various branches:

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

      parent reply	other threads:[~2025-01-22 22:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-22 17:43 [PATCH 5.4] net: xen-netback: hash.c: Use built-in RCU list checking Hagar Hemdan
2025-01-22 17:43 ` [PATCH 5.4] net/xen-netback: prevent UAF in xenvif_flush_hash() Hagar Hemdan
2025-01-22 22:38   ` Sasha Levin
2025-01-22 22:38 ` 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=20250122143830-2c63e93d0cc2d07f@stable.kernel.org \
    --to=sashal@kernel.org \
    --cc=hagarhem@amazon.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 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.