On Wed, Sep 23, 2020 at 09:27:32PM -0400, Mike Snitzer wrote:
> You've clearly done a nice job with these changes. Looks clean.
>
> BUT, I'm struggling to just accept that dm-crypt needs to go to these
> extra lengths purely because of one bad apple usecase.
>
> These alignment constraints aren'
Add failback code to get the uid for dasd devices from sysfs. Copied
from dasdinfo
Reviewed-by: Martin Wilck
Signed-off-by: Benjamin Marzinski
---
libmultipath/defaults.h | 1 +
libmultipath/discovery.c | 37 -
2 files changed, 37 insertions(+), 1 deletion(
The main part of the this patchset is the first patch, which adds a
new library interface to check whether devices are valid paths. This
was designed for use in the Storage Instantiation Daemon (SID).
https://github.com/sid-project
Hopefully, I've removed all the controvertial bits from the last
If uid_attribute is explicitly set to an empty string, multipath should
log the uid at the default log level, since using the fallback code is
the expected behavior.
Signed-off-by: Benjamin Marzinski
---
libmultipath/discovery.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
This library allows other programs to check if a path should be claimed
by multipath. It exports an init function, that needs to be called
before and after all other library calls, an exit function, that needs
to be called after all library calls, a function to reread the multipath
configuration fi
files changed, 17 insertions(+), 26 deletions(-)
>
>
> Hi,
>
> Curious on the state of this patchset? Not seeing it in next-20200923
>
> The dm-bufio cleanup looks desirable.
I've been busy with THPs and haven't pushed this patchset for this window.
It'
You've clearly done a nice job with these changes. Looks clean.
BUT, I'm struggling to just accept that dm-crypt needs to go to these
extra lengths purely because of one bad apple usecase.
These alignment constraints aren't new. Are there other portions of
Linux's crypto subsystem that needed c
On Wed, Sep 09 2020 at 7:44pm -0400,
Satya Tangirala wrote:
> From: Eric Biggers
>
> Update the device-mapper core to support exposing the inline crypto
> support of the underlying device(s) through the device-mapper device.
>
> This works by creating a "passthrough keyslot manager" for the d
On Mon, Sep 21 2020 at 8:32pm -0400,
Eric Biggers wrote:
> On Wed, Sep 09, 2020 at 11:44:21PM +, Satya Tangirala wrote:
> > From: Eric Biggers
> >
> > Update the device-mapper core to support exposing the inline crypto
> > support of the underlying device(s) through the device-mapper devic
On Tue, Sep 15 2020 at 11:53pm -0400,
Eric Biggers wrote:
> From: Eric Biggers
>
> blk_crypto_rq_bio_prep() assumes its gfp_mask argument always includes
> __GFP_DIRECT_RECLAIM, so that the mempool_alloc() will always succeed.
>
> However, blk_crypto_rq_bio_prep() might be called with GFP_ATOM
On Tue, Sep 15 2020 at 11:53pm -0400,
Eric Biggers wrote:
> From: Eric Biggers
>
> bio_crypt_clone() assumes its gfp_mask argument always includes
> __GFP_DIRECT_RECLAIM, so that the mempool_alloc() will always succeed.
>
> However, bio_crypt_clone() might be called with GFP_ATOMIC via
> setup
e)
> ---
> drivers/md/dm-bufio.c| 30 --
> include/linux/sched.h| 1 +
> include/linux/sched/mm.h | 12
> 3 files changed, 17 insertions(+), 26 deletions(-)
Hi,
Curious on the state of this patchset? Not seeing it in next-2
The pull request you sent on Wed, 23 Sep 2020 13:30:24 -0400:
> git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git
> tags/for-5.9/dm-fixes-2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/a969324fe7cc38e4af05eea44fde385a2853c91e
Thank you!
--
Could someone review this patch set, please?
Thanks
Sudhakar
> -Original Message-
> From: Sudhakar Panneerselvam
> Sent: Wednesday, September 16, 2020 12:40 PM
> To: a...@redhat.com; snit...@redhat.com; dm-devel@redhat.com
> Cc: Shirley Ma ; ssudhak...@gmail.com; Martin
> Petersen
> Subj
Add QUEUE_FLAG_NOWAIT to allow a block device to advertise support for
REQ_NOWAIT. Bio-based devices may set QUEUE_FLAG_NOWAIT where
applicable.
Update QUEUE_FLAG_MQ_DEFAULT to include QUEUE_FLAG_NOWAIT. Also
update submit_bio_checks() to verify it is set for REQ_NOWAIT bios.
Reported-by: Konsta
From: Konstantin Khlebnikov
Add DM target feature flag DM_TARGET_NOWAIT which advertises that
target works with REQ_NOWAIT bios.
Add dm_table_supports_nowait() and update dm_table_set_restrictions()
to set/clear QUEUE_FLAG_NOWAIT accordingly.
Signed-off-by: Konstantin Khlebnikov
Signed-off-by:
Hi,
I got guilted into this by this Twitter exchange:
https://twitter.com/axboe/status/1308778488011337728
Started with this patchset from June and revised it:
https://patchwork.kernel.org/project/dm-devel/list/?series=297693
(dropped MD patch while doing so_.
Tested these changes with this test
Hi Linus,
The following changes since commit beaeb4f39bc31d5a5eb6d05465a86af4fe147732:
Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm
(2020-09-21 08:53:48 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm
On 9/21/20 8:32 PM, Mike Snitzer wrote:
> Hi,
>
> Patches 1 and 2 are queued for me to send to Linus later this week.
>
> Patches 3 and 4 are block core and should get picked up for 5.10.
> Jens, please pick them up. I revised the header for patch 4 to give
> better context for use-case where non
On Wed, Sep 23, 2020 at 10:16:48AM +0200, Martin Wilck wrote:
> On Mon, 2020-09-21 at 15:10 -0500, Benjamin Marzinski wrote:
> >
> > After calling libmultipath_exit(), you can never reinitialized the
> > udev
> > device. That seems fine, but it should probably set udev to null, so
> > that future
On Tue, Sep 22, 2020 at 10:49:54AM +0200, Jan Kara wrote:
> On Mon 21-09-20 10:07:26, Christoph Hellwig wrote:
> > Set up a readahead size by default, as very few users have a good
> > reason to change it.
> >
> > Signed-off-by: Christoph Hellwig
> > Acked-by: David Sterba [btrfs]
> > Acked-by:
This change adds a new configuration option allow_usb_devices. It is
disabled by default, so that the behavior of existing setups is not
changed. If enabled (via multipath.conf), USB devices will be found
during device discovery and can be used for multipath setups.
Without this option, multipath
On Mon, 2020-09-21 at 15:10 -0500, Benjamin Marzinski wrote:
>
> After calling libmultipath_exit(), you can never reinitialized the
> udev
> device. That seems fine, but it should probably set udev to null, so
> that future calls to libmultipath_init() don't return success. Either
> that or multi
23 matches
Mail list logo
