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>] [day] [month] [year] [list]
Date:	Mon, 07 Apr 2008 00:25:56 +0200
From:	Ferenc Wagner <wferi@...f.hu>
To:	linux-raid@...r.kernel.org
Cc:	linux-kernel@...r.kernel.org, wferi@...f.hu
Subject: Re: how to disable partition search?

Luca Berra <bluca@...edia.it> writes:

> On Wed, Mar 26, 2008 at 12:43:41PM +0100, Ferenc Wagner wrote:
>
>> I use an FC SAN, which provides multiple pathes to multiple LUNs.
>> These all come up as different sd* devices, exhausting single letter
>> names.  I mean they are a LOT.  Using the md mulitpath driver
>> everything works perfectly, no problems there.  However, during boot,
>> the kernel tries to read the partition table from each device,
>> spitting out hundreds of lines of error messages: most of the devices
>> aren't even readable, and those which are, don't contain a valid
>> partition table.  They never will.  So I'd like to disable partition
>> detection, because these messages overflow the kernel message buffer,
>> depriving syslog of gathering any useful boot messages, and also
>> needlessly lengthening the boot process.  (Of course the noise alone
>> is disturbing enough when one tries to troubleshoot a boot problem.)
>> However, looking at the kernel sources didn't give me any hint.  Is
>> this possible to disable at all?
>
> you could try bugging lkml until it dawns on them that partition
> detection code should belong in userspace by default :)

:) Very well put.  Thanks for strenghtening my belief.

> anyway you can rebuild your own kernel disabling it
> just set PARTITION_ADVANCED, and disable all partition types.

Sounds like a good idea, will try that!  This makes bugging lkml
unnecessary, if not for changing the default...  But that's more a
distribution issue, I think.  And now that we have udev and kpartx,
things will probably drift in this direction.

> you should be aware that doing this will disable partition detection on
> all drives, so if you have partitioned drives (eg boot drives) you have
> to run partx in initramfs or it wont be able to access them.

Not in this case.  I'm netbooting and getting / and co. from the SAN
via multipath and LVM, not a single partition on the whole cluster...
-- 
Thanks for the tip!
Feri.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ