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, 12 Aug 2008 20:31:28 +0200
From:	Wim Van Sebroeck <wim@...ana.be>
To:	Rene Herman <rene.herman@...access.nl>
Cc:	Ingo Molnar <mingo@...hat.com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Andrew Morton <akpm@...l.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] WATCHDOG: don't auto-grab eurotechwdt.

Hi Rene,

> >I'm going over a list of drivers that break the boot of randconfig 
> >kernels by keeping resources busy:
> >
> >http://lkml.org/lkml/2008/8/1/96
> >
> >and eurotechwdt and plain wdt are in that list. Below is an eurotechwdt 
> >that makes passing in io and irq values mandatory as to keep that from 
> >happening.
> >
> >I saw pcwd was already isafied and followed that -- due to the comment 
> >in eurwdt_release() though, I'm not sure about a .shutdown() method.

The Berkshire PC-Watchdog card is indeed allready isafied. This is (just
like the mixcom and the ICS WDT50x watchdog cards) an ISA card that can
be inserted into an ISA slot. (The other two will be isafied also).
The shutdown notifier does the same thing then the reboot_notifier.

Most of the other drivers (except the 2 PCI cards and 1 USB card)
are however directly attached to the motherboard of the system. These
are thus in my opinion more platform devices then isa device drivers.

The problem with a lott of these devices (however) is that they can not
be probed. You either have the hardware or you don't. Some can't even be
stopped once started, some are allready active on boot.
My feeling: If you have the hardware, you will compile and load the driver
of these "platform" watchdog devices, if not you won't.

What we do best, however, to avoid problems at boot with random kernels
looks to be another issue to me.

Kind regards,
Wim.

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