From: Mike Snitzer <snitzer@kernel.org> To: Linus Torvalds <torvalds@linux-foundation.org> Cc: Joe Thornber <ejt@redhat.com>, linux-block@vger.kernel.org, dm-devel@redhat.com, Mikulas Patocka <mpatocka@redhat.com>, Yu Kuai <yukuai3@huawei.com>, Alasdair G Kergon <agk@redhat.com> Subject: [dm-devel] [git pull] device mapper fixes for 6.5-rc4 Date: Thu, 27 Jul 2023 16:41:38 -0400 [thread overview] Message-ID: <ZMLWgk816vYI3j11@redhat.com> (raw) Hi Linus, The following changes since commit fdf0eaf11452d72945af31804e2a1048ee1b574c: Linux 6.5-rc2 (2023-07-16 15:10:37 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-6.5/dm-fixes for you to fetch changes up to 1e4ab7b4c881cf26c1c72b3f56519e03475486fb: dm cache policy smq: ensure IO doesn't prevent cleaner policy progress (2023-07-25 11:55:50 -0400) Please pull, thanks. Mike ---------------------------------------------------------------- - Fix double free on memory allocation failure in DM integrity target's integrity_recalc() - Fix locking in DM raid target's raid_ctr() and around call to md_stop() - Fix DM cache target's cleaner policy to always allow work to be queued for writeback; even if cache isn't idle. -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEJfWUX4UqZ4x1O2wixSPxCi2dA1oFAmTC1UoACgkQxSPxCi2d A1pIGAgAhQjlNQ83DexvmMUoNDRGFxOBiOcL9DnVtiXsLd/wTXZTEDIDXJaH9hCq MAj7aqadBeHlWT+vNMOYH9ePPtySEKGs8VM/4/fwNtT6wMyqxZZk4JyN7z+YBVJV d/9lryVZYRWK7ICgRenR/VSxv8/JgVTBGZZqyl20SXhtlYxndxGcLeV0X8fP3G1Q pxdsNuE7TBclB8qrXiPIOlIK0HcSikz6CfQIar3zgip6fO+Wwb92CZ1DOGGi1RJz bsTmZXn08l3d1tMJ+y4umZm+Izq8gvWSgDBywRdWq/D6Ao1ScVqY4TExFSSkjDk0 PUY49vMF/FsKfNt5/VK0/i2U7QAKDQ== =92HI -----END PGP SIGNATURE----- ---------------------------------------------------------------- Joe Thornber (1): dm cache policy smq: ensure IO doesn't prevent cleaner policy progress Mikulas Patocka (1): dm integrity: fix double free on memory allocation failure Yu Kuai (3): dm raid: fix missing reconfig_mutex unlock in raid_ctr() error paths dm raid: clean up four equivalent goto tags in raid_ctr() dm raid: protect md_stop() with 'reconfig_mutex' drivers/md/dm-cache-policy-smq.c | 28 ++++++++++++++++++---------- drivers/md/dm-integrity.c | 1 + drivers/md/dm-raid.c | 20 +++++++++----------- drivers/md/md.c | 2 ++ 4 files changed, 30 insertions(+), 21 deletions(-) -- dm-devel mailing list dm-devel@redhat.com https://listman.redhat.com/mailman/listinfo/dm-devel
WARNING: multiple messages have this Message-ID (diff)
From: Mike Snitzer <snitzer@kernel.org> To: Linus Torvalds <torvalds@linux-foundation.org> Cc: dm-devel@redhat.com, linux-block@vger.kernel.org, Alasdair G Kergon <agk@redhat.com>, Benjamin Marzinski <bmarzins@redhat.com>, Joe Thornber <ejt@redhat.com>, Mikulas Patocka <mpatocka@redhat.com>, Yu Kuai <yukuai3@huawei.com> Subject: [git pull] device mapper fixes for 6.5-rc4 Date: Thu, 27 Jul 2023 16:41:38 -0400 [thread overview] Message-ID: <ZMLWgk816vYI3j11@redhat.com> (raw) Hi Linus, The following changes since commit fdf0eaf11452d72945af31804e2a1048ee1b574c: Linux 6.5-rc2 (2023-07-16 15:10:37 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-6.5/dm-fixes for you to fetch changes up to 1e4ab7b4c881cf26c1c72b3f56519e03475486fb: dm cache policy smq: ensure IO doesn't prevent cleaner policy progress (2023-07-25 11:55:50 -0400) Please pull, thanks. Mike ---------------------------------------------------------------- - Fix double free on memory allocation failure in DM integrity target's integrity_recalc() - Fix locking in DM raid target's raid_ctr() and around call to md_stop() - Fix DM cache target's cleaner policy to always allow work to be queued for writeback; even if cache isn't idle. -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEJfWUX4UqZ4x1O2wixSPxCi2dA1oFAmTC1UoACgkQxSPxCi2d A1pIGAgAhQjlNQ83DexvmMUoNDRGFxOBiOcL9DnVtiXsLd/wTXZTEDIDXJaH9hCq MAj7aqadBeHlWT+vNMOYH9ePPtySEKGs8VM/4/fwNtT6wMyqxZZk4JyN7z+YBVJV d/9lryVZYRWK7ICgRenR/VSxv8/JgVTBGZZqyl20SXhtlYxndxGcLeV0X8fP3G1Q pxdsNuE7TBclB8qrXiPIOlIK0HcSikz6CfQIar3zgip6fO+Wwb92CZ1DOGGi1RJz bsTmZXn08l3d1tMJ+y4umZm+Izq8gvWSgDBywRdWq/D6Ao1ScVqY4TExFSSkjDk0 PUY49vMF/FsKfNt5/VK0/i2U7QAKDQ== =92HI -----END PGP SIGNATURE----- ---------------------------------------------------------------- Joe Thornber (1): dm cache policy smq: ensure IO doesn't prevent cleaner policy progress Mikulas Patocka (1): dm integrity: fix double free on memory allocation failure Yu Kuai (3): dm raid: fix missing reconfig_mutex unlock in raid_ctr() error paths dm raid: clean up four equivalent goto tags in raid_ctr() dm raid: protect md_stop() with 'reconfig_mutex' drivers/md/dm-cache-policy-smq.c | 28 ++++++++++++++++++---------- drivers/md/dm-integrity.c | 1 + drivers/md/dm-raid.c | 20 +++++++++----------- drivers/md/md.c | 2 ++ 4 files changed, 30 insertions(+), 21 deletions(-)
next reply other threads:[~2023-07-27 20:41 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-27 20:41 Mike Snitzer [this message] 2023-07-27 20:41 ` [git pull] device mapper fixes for 6.5-rc4 Mike Snitzer 2023-07-28 18:39 ` pr-tracker-bot 2023-07-28 18:39 ` [dm-devel] " pr-tracker-bot
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=ZMLWgk816vYI3j11@redhat.com \ --to=snitzer@kernel.org \ --cc=agk@redhat.com \ --cc=dm-devel@redhat.com \ --cc=ejt@redhat.com \ --cc=linux-block@vger.kernel.org \ --cc=mpatocka@redhat.com \ --cc=torvalds@linux-foundation.org \ --cc=yukuai3@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: linkBe 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.