From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 1/2 v5.10] dm: rearrange core declarations for extended use from dm-zone.c
Date: Mon, 11 Aug 2025 18:30:24 -0400 [thread overview]
Message-ID: <1754925042-4d326ede@stable.kernel.org> (raw)
In-Reply-To: <20250811052702.145189-2-shivani.agarwal@broadcom.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: e2118b3c3d94289852417f70ec128c25f4833aad
WARNING: Author mismatch between patch and upstream commit:
Backport author: Shivani Agarwal <shivani.agarwal@broadcom.com>
Commit author: Damien Le Moal <damien.lemoal@wdc.com>
Status in newer kernel trees:
6.15.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (exact SHA1)
6.1.y | Present (exact SHA1)
5.15.y | Present (exact SHA1)
Note: The patch differs from the upstream commit:
---
1: e2118b3c3d94 ! 1: e83906552e29 dm: rearrange core declarations for extended use from dm-zone.c
@@ Metadata
## Commit message ##
dm: rearrange core declarations for extended use from dm-zone.c
+ commit e2118b3c3d94289852417f70ec128c25f4833aad upstream.
+
Move the definitions of struct dm_target_io, struct dm_io and the bits
of the flags field of struct mapped_device from dm.c to dm-core.h to
make them usable from dm-zone.c. For the same reason, declare
@@ Commit message
Reviewed-by: Hannes Reinecke <hare@suse.de>
Reviewed-by: Himanshu Madhani <himanshu.madhani@oracle.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
+ [Shivani: Modified to apply on 5.10.y]
+ Signed-off-by: Shivani Agarwal <shivani.agarwal@broadcom.com>
## drivers/md/dm-core.h ##
@@ drivers/md/dm-core.h: struct mapped_device {
@@ drivers/md/dm-core.h: struct mapped_device {
void disable_write_same(struct mapped_device *md);
void disable_write_zeroes(struct mapped_device *md);
@@ drivers/md/dm-core.h: struct dm_table {
- #endif
+ struct dm_md_mempools *mempools;
};
+/*
@@ drivers/md/dm.c: struct clone_info {
- struct dm_target_io tio;
-};
-
- #define DM_TARGET_IO_BIO_OFFSET (offsetof(struct dm_target_io, clone))
- #define DM_IO_BIO_OFFSET \
- (offsetof(struct dm_target_io, clone) + offsetof(struct dm_io, tio))
+ void *dm_per_bio_data(struct bio *bio, size_t data_size)
+ {
+ struct dm_target_io *tio = container_of(bio, struct dm_target_io, clone);
@@ drivers/md/dm.c: EXPORT_SYMBOL_GPL(dm_bio_get_target_bio_nr);
#define MINOR_ALLOCED ((void *)-1)
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| origin/linux-5.10.y | Success | Success |
next prev parent reply other threads:[~2025-08-11 22:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 5:27 [PATCH 0/2 v5.10] Fix CVE-2021-47498 Shivani Agarwal
2025-08-11 5:27 ` [PATCH 1/2 v5.10] dm: rearrange core declarations for extended use from dm-zone.c Shivani Agarwal
2025-08-11 22:30 ` Sasha Levin [this message]
2025-08-11 5:27 ` [PATCH 2/2 v5.10] dm rq: don't queue request to blk-mq during DM suspend Shivani Agarwal
2025-08-11 22:30 ` Sasha Levin
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=1754925042-4d326ede@stable.kernel.org \
--to=sashal@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox