linux-kernel - Why is max_part default value 0 for loop devices ?

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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 01 Oct 2014 17:01:57 +0200
From:	Francis Moreau <francis.moro@...il.com>
To:	LKML <linux-kernel@...r.kernel.org>
Subject: Why is max_part default value  0 for loop devices ?

Hello,

I'm wondering why max_part parameter for loop device is 0 by default.

Also would it make sense to allow one to change this default value at
kernel build time ?

Thanks.
--
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/