On Tue, May 09 2017 at 3:10pm -0400,
Andy Grover wrote:
> Hi Mike,
>
> We've been working off-list to develop a method of getting DM events
> that is reliable, and also can monitor events from multiple DM devices
> from a single thread.
>
> In short, these enable an open file descriptor to /de
From: Mikulas Patocka
This patch reports the event numbers for all the devices, so that the
user doesn't have to ask them one by one. The event number is reported
after the name field in the dm_name_list structure.
The location of the next record is specified in the dm_name_list->next
field, tha
From: Mikulas Patocka
This ioctl will record the current global event number in the structure
dm_file, so that next select or poll call will wait until new events
arrived since this ioctl.
The DM_DEV_ARM_POLL ioctl has the same effect as closing and reopening the
handle.
This patch is optional
Hi Mike,
We've been working off-list to develop a method of getting DM events
that is reliable, and also can monitor events from multiple DM devices
from a single thread.
In short, these enable an open file descriptor to /dev/mapper/control
to be polled. If the fd indicates POLLIN, some DM device
From: Mikulas Patocka
This is the very simple patch for polling on the /dev/mapper/control
device. The select or poll function waits until any event happens on any
dm device since opening the /dev/mapper/control device. When select or
poll returns the device as readable, we must close and reopen
When multipath reloads a device, it can either fail while loading the
new table or while resuming the device. If it fails while resuming the
device, the device can get stuck in the suspended state. To fix this,
multipath needs to resume the device again so that it can continue using
the old table.
There are a couple of places in the mpath_persist code that were calling
pthread join, even if the pthread_create call failed, and the thread id
was undefined. This can cause crashes, so don't do it.
Signed-off-by: Benjamin Marzinski
---
libmpathpersist/mpath_persist.c | 34 +
Here are a number of small multipath fixes. These patches are based on
top of my and Martin's previous patch sets.
Benjamin Marzinski (6):
libmultipath: print alias with no_path_retry message
multipathd: force reload device on all resizes
libmultipath: refactor calls to get dm device info
There are a number of issues in the the kpartx device checking code.
First, it accepts files that are neither regular files or a block device
nodes (you can run kpartx on character devices or directories, and it
will treat them as block devices). When trying to figure out the
basename of a device,
Multipath has a number of functions that all do basically the same
thing to get members of the dm_info structure. This just refactors them
to use common code to do it.
Signed-off-by: Benjamin Marzinski
---
libmultipath/devmapper.c | 171 +-
libmultipa
My previous patch missed setting force_udev_reload on resizes initiated
by
multipathd resize map
Signed-off-by: Benjamin Marzinski
---
multipathd/cli_handlers.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/multipathd/cli_handlers.c b/multipathd/cli_handlers.c
index efc12dd..d598039 1006
the "flush_on_last_del in progress" message in select_no_path_retry
should print the device alias.
Signed-off-by: Benjamin Marzinski
---
libmultipath/propsel.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libmultipath/propsel.c b/libmultipath/propsel.c
index 09fe728..d3937
On Tue, May 09, 2017 at 03:19:31PM +0530, Neeraj Soni wrote:
>+ Alasdair and dm-devel for awareness and inputs.
>
>On 5/9/2017 12:26 PM, Neeraj Soni wrote:
>
> Hi Keith/Snitzer,
>
> I have recently started using kernel 4.4 on a Android device and ran
> Androbench to check
On Tue, 2017-05-09 at 10:50 -0400, Mike Snitzer wrote:
> On Mon, May 08 2017 at 7:40pm -0400,
> Bart Van Assche wrote:
>
> > From: Damien Le Moal
> >
> > [ Note: I'm resending this patch series on Damien's behalf because Damien's
> > ]
> > [ e-mails apparently do not reach the dm-devel mailin
On Mon, May 08 2017 at 7:40pm -0400,
Bart Van Assche wrote:
> From: Damien Le Moal
>
> [ Note: I'm resending this patch series on Damien's behalf because Damien's ]
> [ e-mails apparently do not reach the dm-devel mailing list - Bart. ]
That isn't true. The v2 patchset is in dm-deve
Hi Greg,
I'm resending rebased patch with updated date and kernel version in
sysfs-uevent ABI documentation. There were no further comments and
feedback for a month, will you consider the patch for inclusion?
This patch makes it possible to pass additional arguments in addition
to uevent action
On 05/06/2017 06:25 PM, Wols Lists wrote:
> On 03/05/17 15:13, Peter Rajnoha wrote:
>> There's a difference though - when you're *creating* a completely new
>> device that is an abstraction over existing devices, you (most of the
>> time) expect that new device to be initialized. For those corner c
+ Alasdair and dm-devel for awareness and inputs.
On 5/9/2017 12:26 PM, Neeraj Soni wrote:
Hi Keith/Snitzer,
I have recently started using kernel 4.4 on a Android device and ran
Androbench to check storage read/write performance. I found that the
Random Read (RR) and Random write(RW) perform
On 05/06/2017 06:25 PM, Wols Lists wrote:
> On 03/05/17 15:13, Peter Rajnoha wrote:
>> There's a difference though - when you're *creating* a completely new
>> device that is an abstraction over existing devices, you (most of the
>> time) expect that new device to be initialized. For those corner c
On 05/06/2017 12:25 PM, Wols Lists wrote:
> On 03/05/17 15:13, Peter Rajnoha wrote:
>> There's a difference though - when you're *creating* a completely new
>> device that is an abstraction over existing devices, you (most of the
>> time) expect that new device to be initialized. For those corner c
On Sun, 2017-05-07 at 11:22 +0200, h...@lst.de wrote:
> On Tue, May 02, 2017 at 08:33:15PM -0700, Nicholas A. Bellinger wrote:
> > The larger target/iblock conversion patch looks like post v4.12 material
> > at this point, so to avoid breakage wrt to existing LBPRZ behavior, I'll
> > plan to push t
To make the code clearer, use rb_entry() instead of container_of() to
deal with rbtree.
Signed-off-by: Geliang Tang
Acked-by: Coly Li
---
Changes in v2:
- Apply to dm-bio-prison-v1.c and dm-bio-prison-v2.c
---
drivers/md/dm-bio-prison-v1.c | 2 +-
drivers/md/dm-bio-prison-v2.c | 2 +-
2 files
2017-05-06 5:59 GMT-07:00 Gilad Ben-Yossef :
> cifs starts an async. crypto op and waits for their completion.
> Move it over to generic code doing the same.
>
> Signed-off-by: Gilad Ben-Yossef
> ---
> fs/cifs/smb2ops.c | 30 --
> 1 file changed, 4 insertions(+), 26 de
The code sample is waiting for an async. crypto op completion.
Adapt sample to use the new generic infrastructure to do the same.
Signed-off-by: Gilad Ben-Yossef
---
Documentation/crypto/api-samples.rst | 52 +++-
1 file changed, 10 insertions(+), 42 deletions(-)
On 05/05/2017 01:16 AM, NeilBrown wrote:
As pointed out by Peter Rajnoha, the correct usage in udev is
TEST=="file", not TEST="file".
Also improve a related comment which was a bit informal.
Reported-by: Peter Rajnoha
Fixes: cd6cbb08c458 ("Create: tell udev md device is not ready when first
25 matches
Mail list logo
