Am 18.09.2014 um 16:06 hat Markus Armbruster geschrieben:
> Eric Blake writes:
>
> > On 09/18/2014 03:57 AM, Kevin Wolf wrote:
> >> While thinking about precedence of conflicting block device options from
> >> different sources, I noticed that you can specify both an option and its
> >> legacy al
Eric Blake writes:
> On 09/18/2014 03:57 AM, Kevin Wolf wrote:
>> While thinking about precedence of conflicting block device options from
>> different sources, I noticed that you can specify both an option and its
>> legacy alias at the same time (e.g. readonly=on,read-only=off). Rather
>> than
On 09/18/2014 03:57 AM, Kevin Wolf wrote:
> While thinking about precedence of conflicting block device options from
> different sources, I noticed that you can specify both an option and its
> legacy alias at the same time (e.g. readonly=on,read-only=off). Rather
> than specifying the order of pre
While thinking about precedence of conflicting block device options from
different sources, I noticed that you can specify both an option and its
legacy alias at the same time (e.g. readonly=on,read-only=off). Rather
than specifying the order of precedence, we should simply forbid such
combinations