linux-kernel - Re: [dm-devel] [PATCH v2] dm pref-path: provides preferred path load balance policy

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20160130233228.GF24960@octiron.msp.redhat.com>
Date:	Sat, 30 Jan 2016 17:32:28 -0600
From:	"Benjamin Marzinski" <bmarzins@...hat.com>
To:	Hannes Reinecke <hare@...e.de>
Cc:	"dm-devel@...hat.com" <dm-devel@...hat.com>,
	"corbet@....net" <corbet@....net>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Mike Snitzer <snitzer@...hat.com>,
	"Nalla, Ravikanth" <ravikanth.nalla@....com>
Subject: Re: [dm-devel] [PATCH v2] dm pref-path: provides preferred path load
 balance policy

On Sat, Jan 30, 2016 at 02:25:25PM -0600, Benjamin Marzinski wrote:
> Before this commit, it always used the pref bit. Again, like I said
> before, I'm saying that this was the wrong thing to do.  The Spec is

Oops. I meant: "I'm NOT saying that this was the wrong thing to do".

I am also fine with changing the default back to making the pref bit
always create it's own path group. As long there is a way for users to
get either behavior, I'm happy.

-Ben

> pretty vague on what you should expect to happen when you set to pref
> bit.  When the path was in a group by itself, I got complaints. Now that
> the path is is a group with other active/optimized paths, I get
> complaints.  The only answer is to allow the user to say what they want
> the pref bit to mean.
> 
> -Ben