linux-kernel - Re: Why minor is still 8 bit?

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]

Date:	Tue, 05 Jun 2012 15:13:44 +0400
From:	George Shuklin <george.shuklin@...il.com>
To:	Paul Bolle <pebolle@...cali.nl>
CC:	"H. Peter Anvin" <hpa@...or.com>,
	Casey Schaufler <casey@...aufler-ca.com>,
	Al Viro <viro@...IV.linux.org.uk>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Why minor is still 8 bit?

On 05.06.2012 13:49, Paul Bolle wrote:
> On Tue, 2012-06-05 at 13:36 +0400, George Shuklin wrote:
>> This is a limitaiton of LMV itself. I'm talking about making those LV
>> active (visible in system). When you trying to activate too much LV, you
>> will get 'device io ctl failed' message.
> What is the exact text of that message? Where is it found (stderr,
> dmesg, ...)? Do you know what prints it (kernel, user space)? Do you run
> into this issue when trying to activate the 256th LV, or later, or
> earlier?
>
>
> Paul Bolle
>
Ooops, I was deeply wrong. Sorry, the problem was related to LVM 
behavior in 2.6.32-12-xs (XenServer kernel).

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/