On 2/19/21 10:17 PM, Mikulas Patocka wrote:
>
>
> On Mon, 8 Feb 2021, Jeffle Xu wrote:
>
>> diff --git a/drivers/md/dm.c b/drivers/md/dm.c
>> index c2945c90745e..8423f1347bb8 100644
>> --- a/drivers/md/dm.c
>> +++ b/drivers/md/dm.c
>> @@ -1657,6 +1657,68 @@ static blk_qc_t
On 2/24/21 4:54 AM, Mike Snitzer wrote:
> On Mon, Feb 22 2021 at 10:55pm -0500,
> JeffleXu wrote:
>
>>
>>
>> On 2/20/21 7:06 PM, Jeffle Xu wrote:
>>> [Changes since v3]
>>> - newly add patch 7 and patch 11, as a new optimization improving
>>> performance of multiple polling processes. Now
Signed-off-by: Benjamin Marzinski
---
libmultipath/discovery.c | 11 ---
1 file changed, 4 insertions(+), 7 deletions(-)
diff --git a/libmultipath/discovery.c b/libmultipath/discovery.c
index 9be94cd1..3a06f319 100644
--- a/libmultipath/discovery.c
+++ b/libmultipath/discovery.c
@@
There are cases where the wwid of a path changes due to LUN remapping
without triggering uevent for the changed path. Multipathd has no method
for trying to catch these cases, and corruption has resulted because of
it.
In order to have a better chance at catching these cases, multipath now
has a
This patchset adds a new config option, recheck_wwid, to help deal with
devices getting remapped. It's based on Chongyun's patch. Unlike
Chongyun's patch, it doesn't issue a remove uevent. I'm not actually
sure what the purpose of the remove uevent was, since it doesn't cause
the path to be
In get_uid(), if pp->getuid is NULL, multipath will check the
pp->uid_attribute to get the wwid. If pp->uid_attribute is NULL,
nothing will happen in that block of code, because both udev_available
and has_uid_fallback() are false if pp->uid_attribute is NULL. So
instead of multiple checks if
If "kpartx -l" is run on a file that doesn't already have a loop device
associated with it, it will create a loop device to run the command.
Starting with da59d15c6 ("Fix loopback file with kpartx -av"), it will
not free the loop device when exitting. This is because it checks if the
the file it
Applied, thanks.
--
Jens Axboe
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
Hi Petr,
On 2021-02-23 4:43 p.m., Mimi Zohar wrote:
Hi Petr,
On Tue, 2021-02-23 at 23:59 +0100, Petr Vorel wrote:
Hi!
I updated Tushar's patchset to speedup things.
Thank you. :)
Changes v2->v3
* rename function s/check_ima_ascii_log_for_policy/test_policy_measurement/
* move tst_res
Hi Petr,
On Tue, 2021-02-23 at 23:59 +0100, Petr Vorel wrote:
> Hi!
>
> I updated Tushar's patchset to speedup things.
>
> Changes v2->v3
> * rename function s/check_ima_ascii_log_for_policy/test_policy_measurement/
> * move tst_res TPASS/TFAIL into test_policy_measurement()
> * drop
On Tue, Feb 23, 2021 at 11:28:27AM -0500, Mikulas Patocka wrote:
>
>
> On Tue, 23 Feb 2021, Ming Lei wrote:
>
> > I'd suggest to add a helper(such as, blk_round_down_sectors()) to
> > round_down each
> > one.
>
> Yes - Here I'm sending the updated patch.
>
> > --
> > Ming
>
> From: Mikulas
From: Tushar Sugandhi
Refactor check_keys_policy() and test1() implemented in ima_keys.sh to
make it generic, and move the functionality to ima_setup.sh,
to be used for measurements in other tests in the future.
Suggested-by: Petr Vorel
Reviewed-by: Petr Vorel
Signed-off-by: Tushar Sugandhi
Hi!
I updated Tushar's patchset to speedup things.
Changes v2->v3
* rename function s/check_ima_ascii_log_for_policy/test_policy_measurement/
* move tst_res TPASS/TFAIL into test_policy_measurement()
* drop template=ima-buf (see Lakshmi's patch [1] and discussion about
it, it will be removed
From: Tushar Sugandhi
New functionality is being added to IMA to measure data provided by
kernel components. With this feature, IMA policy can be set to enable
measuring data provided by device-mapper targets. Currently one such
device-mapper target - dm-crypt, is being updated to use this
Hi Tushar,
> Thanks for your review.
> My sincere apologies for missing this email and not responding in time.
> The device mapper measurement work is being revisited - to cover aspects
> like more DM targets (not just dm-crypt), better memory management,
> more relevant attributes from the DM
On Mon, Feb 22 2021 at 10:55pm -0500,
JeffleXu wrote:
>
>
> On 2/20/21 7:06 PM, Jeffle Xu wrote:
> > [Changes since v3]
> > - newly add patch 7 and patch 11, as a new optimization improving
> > performance of multiple polling processes. Now performance of multiple
> > polling processes can be
Optional Forward Error Correction (FEC) code in dm-verity uses
Reed-Solomon code and should support roots from 2 to 24.
The error correction parity bytes (of roots lengths per RS block) are stored
on a separate device in sequence without any padding.
Currently, to access FEC device, the
From: Mikulas Patocka
dm_bufio_get_device_size returns returns the device size in blocks. Before
returning the value, we must subtract the nubmer of starting sectors. The
number of starting sectos may not be divisible by block size.
Note that currently, no target is using
On Tue, 23 Feb 2021, Ming Lei wrote:
> I'd suggest to add a helper(such as, blk_round_down_sectors()) to round_down
> each
> one.
Yes - Here I'm sending the updated patch.
> --
> Ming
From: Mikulas Patocka
We get I/O errors when we run md-raid1 on the top of dm-integrity on the
top of
dm_bufio_get_device_size returns returns the device size in blocks. Before
returning the value, we must subtract the nubmer of starting sectors. The
number of starting sectos may not be divisible by block size.
Note that currently, no target is using dm_bufio_set_sector_offset and
On 23/02/2021 04:00, Jérôme Carretero wrote:
> Tested-by: Jérôme Carretero
>
>
> I smoke-tested by fuzzing contiguous ranges of user data (not hash
> tree) and correction works up to the amount of added correction (since
> erasures are identified by hashes).
Thanks for testing!
> Since the
On 2/20/21 7:06 PM, Jeffle Xu wrote:
> [Changes since v3]
> - newly add patch 7 and patch 11, as a new optimization improving
> performance of multiple polling processes. Now performance of multiple
> polling processes can be as scalable as single polling process (~30%).
> Refer to the
Dave,
copy_file_range() is work under progress. FALLOC_FL_UNSHARE of fallocate()
use case sounds interesting. I will try to address both of them in the
next series.
Adding SCSI_XCOPY() support is not in the scope of this patchset. However
blkdev_issue_copy() interface is made generic so that it
Thanks Su Yue. I'll update the link in the next series.
On Mon, Feb 22, 2021 at 12:23 PM Su Yue wrote:
>
>
> On Fri 19 Feb 2021 at 20:45, SelvaKumar S
> wrote:
>
> > This patchset tries to add support for TP4065a ("Simple Copy
> > Command"),
> > v2020.05.04 ("Ratified")
> >
> > The
24 matches
Mail list logo
