On Wed, 2014-04-09 at 21:22 +0200, Jean Delvare wrote:
> On Wed, 9 Apr 2014 17:59:03 +0000, Matthew Garrett wrote:
> > So... why add the driver at all? Refusing to permit the kernel to touch
> > these resources is a deliberate design choice, because of the potential
> > for these races. (...)
>
> So it is a deliberate design choice to prevent the user from accessing
> his/her own hardware? I want to be able to read the SPD EEPROMs and the
> temperature sensors on my memory modules, and this requires SMBus
> access.
Sure, and if you have made a conscious decision that it's safe to do so
in your specific use case then you can pass the kernel parameter that
allows you to. But it's unsafe in the general case, and so the
appropriate thing is for the kernel to forbid it.
--
Matthew Garrett <matthew.garrett@xxxxxxxxxx>
��.n��������+%������w��{.n�����{�����ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
