public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Yu Kuai <yukuai1@huaweicloud.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.6 1/6] md/raid5: recheck if reshape has finished with device_lock held
Date: Mon, 27 Jan 2025 06:25:17 -0500	[thread overview]
Message-ID: <20250127043040-429aec38a5285030@stable.kernel.org> (raw)
In-Reply-To: <20250127085351.3198083-2-yukuai1@huaweicloud.com>

[ Sasha's backport helper bot ]

Hi,

The upstream commit SHA1 provided is correct: 25b3a8237a03ec0b67b965b52d74862e77ef7115

WARNING: Author mismatch between patch and upstream commit:
Backport author: Yu Kuai<yukuai1@huaweicloud.com>
Commit author: Benjamin Marzinski<bmarzins@redhat.com>


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

Note: The patch differs from the upstream commit:
---
1:  25b3a8237a03e ! 1:  64000dbb8dcf7 md/raid5: recheck if reshape has finished with device_lock held
    @@ Metadata
      ## Commit message ##
         md/raid5: recheck if reshape has finished with device_lock held
     
    +    commit 25b3a8237a03ec0b67b965b52d74862e77ef7115 upstream.
    +
         When handling an IO request, MD checks if a reshape is currently
         happening, and if so, where the IO sector is in relation to the reshape
         progress. MD uses conf->reshape_progress for both of these tasks.  When
    @@ Commit message
         Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com>
         Signed-off-by: Song Liu <song@kernel.org>
         Link: https://lore.kernel.org/r/20240702151802.1632010-1-bmarzins@redhat.com
    +    Signed-off-by: Yu Kuai <yukuai3@huawei.com>
     
      ## drivers/md/raid5.c ##
    -@@ drivers/md/raid5.c: static int add_all_stripe_bios(struct r5conf *conf,
    - 	return ret;
    +@@ drivers/md/raid5.c: static bool reshape_disabled(struct mddev *mddev)
    + 	return is_md_suspended(mddev) || !md_is_rdwr(mddev);
      }
      
     +enum reshape_loc {
---

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.6.y        |  Success    |  Success   |
| stable/linux-6.1.y        |  Failed     |  N/A       |

  reply	other threads:[~2025-01-27 11:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-27  8:53 [PATCH 6.6 0/6] md/md-bitmap: move bitmap_{start, end}write to md upper layer Yu Kuai
2025-01-27  8:53 ` [PATCH 6.6 1/6] md/raid5: recheck if reshape has finished with device_lock held Yu Kuai
2025-01-27 11:25   ` Sasha Levin [this message]
2025-01-27  8:53 ` [PATCH 6.6 2/6] md/md-bitmap: factor behind write counters out from bitmap_{start/end}write() Yu Kuai
2025-02-04 11:38   ` Greg KH
2025-01-27  8:53 ` [PATCH 6.6 3/6] md/md-bitmap: remove the last parameter for bimtap_ops->endwrite() Yu Kuai
2025-01-27  8:53 ` [PATCH 6.6 4/6] md: add a new callback pers->bitmap_sector() Yu Kuai
2025-01-27  8:53 ` [PATCH 6.6 5/6] md/raid5: implement pers->bitmap_sector() Yu Kuai
2025-01-27  8:53 ` [PATCH 6.6 6/6] md/md-bitmap: move bitmap_{start, end}write to md upper layer Yu Kuai
2025-02-04 11:40 ` [PATCH 6.6 0/6] " Greg KH
2025-02-06  1:53   ` Yu Kuai

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=20250127043040-429aec38a5285030@stable.kernel.org \
    --to=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=yukuai1@huaweicloud.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox