linux-kernel - Re: [patch 1/5] Staging: VME Framework for the Linux Kernel

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: <20090812095436.GC2604@braap.org>
Date:	Wed, 12 Aug 2009 11:54:36 +0200
From:	"Emilio G. Cota" <cota@...ap.org>
To:	Martyn Welch <martyn.welch@...anuc.com>
Cc:	Greg K-H <gregkh@...e.de>, linux-kernel@...r.kernel.org,
	devel@...uxdriverproject.org,
	Sebastien Dugue <sebastien.dugue@...l.net>
Subject: Re: [patch 1/5] Staging: VME Framework for the Linux Kernel

Martyn Welch wrote:
> There is a further device situated between the two.
> > How do you now protect the registers of this device from
> > > accidental/malicous/buggy behaviour from your board, since
> this region of the VME bus is now enabled for transfers
> in the PCI IO Mem space?

The kernel is not designed to work with buggy hardware--that
would be insane, we've got more than enough dealing with our
own bugs. However when there's no other solution (e.g.
hardware can't be fixed for whatever reason), fixes on a
per-case basis may be applied.

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