Re: [PATCH 6.1 08/16] xfs: match lock mode in xfs_buffered_write_iomap_begin()

[Sasha Levin <sashal@kernel.org>]

[ 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: bb712842a85d595525e72f0e378c143e620b3ea2

WARNING: Author mismatch between patch and upstream commit:
Backport author: Leah Rumancik<leah.rumancik@gmail.com>
Commit author: Zhang Yi<yi.zhang@huawei.com>

Status in newer kernel trees:
6.14.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (different SHA1: f24ba2183148)

Note: The patch differs from the upstream commit:
---
1:  bb712842a85d5 ! 1:  359664e60e303 xfs: match lock mode in xfs_buffered_write_iomap_begin()
    @@ Metadata
      ## Commit message ##
         xfs: match lock mode in xfs_buffered_write_iomap_begin()
     
    +    [ Upstream commit bb712842a85d595525e72f0e378c143e620b3ea2 ]
    +
         Commit 1aa91d9c9933 ("xfs: Add async buffered write support") replace
         xfs_ilock(XFS_ILOCK_EXCL) with xfs_ilock_for_iomap() when locking the
         writing inode, and a new variable lockmode is used to indicate the lock
    @@ Commit message
         Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
         Reviewed-by: Christoph Hellwig <hch@lst.de>
         Signed-off-by: Chandan Babu R <chandanbabu@kernel.org>
    +    Signed-off-by: Leah Rumancik <leah.rumancik@gmail.com>
    +    Acked-by: "Darrick J. Wong" <djwong@kernel.org>
     
      ## fs/xfs/xfs_iomap.c ##
     @@ fs/xfs/xfs_iomap.c: xfs_buffered_write_iomap_begin(
---

Results of testing on various branches:

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