[git pull] device mapper changes to add VDO target for 6.9

2024-03-11 Thread Mike Snitzer
Hi Linus, The following changes since commit 54be6c6c5ae8e0d93a6c4641cb7528eb0b6ba478: Linux 6.8-rc3 (2024-02-04 12:20:36 +) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-6.9/dm-vdo for you to fetch changes

[git pull] device mapper changes to switch to BH workqueue for 6.9

2024-03-11 Thread Mike Snitzer
Hi Linus, The following changes since commit c6df327501b9dc064a419f25daf99eebdf8fc815: Merge remote-tracking branch 'tejun/for-6.9' into dm-6.9-bh-wq (2024-03-02 10:29:40 -0500) are available in the Git repository at:

[git pull] device mapper changes for 6.9

2024-03-11 Thread Mike Snitzer
Hi Linus, Please note there will be 2 additional DM pull requests that will follow this one (for BH workqueue changes and the VDO dm target). The following changes since commit 0e0c50e85a364bb7f1c52c84affe7f9e88c57da7: dm-crypt, dm-integrity, dm-verity: bump target version (2024-02-20

[PATCH] dm: call the resume method on internal suspend

2024-03-11 Thread Mikulas Patocka
There is this reported crash when experimenting with the lvm2 testsuite. The list corruption is caused by the fact that the postsuspend and resume methods were not paired correctly; there were two consecutive calls to the origin_postsuspend function. The second call attempts to remove the

Re: LVM-on-LVM: error while submitting device barriers

2024-03-11 Thread Ming Lei
On Sun, Mar 10, 2024 at 02:11:11PM -0400, Patrick Plenefisch wrote: > On Sun, Mar 10, 2024 at 11:27 AM Mike Snitzer wrote: > > > > On Sun, Mar 10 2024 at 7:34P -0400, > > Ming Lei wrote: > > > > > On Sat, Mar 09, 2024 at 03:39:02PM -0500, Patrick Plenefisch wrote: > > > > On Wed, Mar 6, 2024 at

Re: dm: set the correct discard_sectors limit

2024-03-11 Thread Christoph Hellwig
On Sat, Mar 09, 2024 at 01:33:04PM -0500, Mike Snitzer wrote: > That 2015 commit (0034af036554) was really ham-handed, not sure how > I've remained unaware of this duality (with soft and hard discard > limits) until now BUT there is quite a bit of DM code that only > concerns itself with