linux-kernel - Re: [PATCH] misc: use a proper range for minor number dynamic allocation

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20091103120502.GA8304@mail.gnudd.com>
Date:	Tue, 3 Nov 2009 13:05:03 +0100
From:	Alessandro Rubini <rubini@...dd.com>
To:	cascardo@...oscopio.com
Cc:	linux-kernel@...r.kernel.org, device@...ana.org, gregkh@...e.de
Subject: Re: [PATCH] misc: use a proper range for minor number dynamic
	allocation

Hello.
Please forgive my delay.

> First of all, the range for dynamic numbers include some statically
> allocated numbers. It goes from 63 to 0, and we have numbers in the
> range from 1 to 15 already allocated.

Yes, I wrote it ages ago. The "same as major numbers" testifies it.

I think your changes are sane, howver "git am" complains that
"patch doesn't apply". However, plain "patch -p1" liked it, so
I could test the result.

I think you need to rebase on current upstream, but apart from
that

Acked-By: Alessandro Rubini <rubini@...ion.unipv.it>

/alessandro
--
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/