linux-kernel - pnp_assign_resources() issue

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]

Message-Id: <46960319.76E4.0078.0@novell.com>
Date:	Thu, 12 Jul 2007 09:31:53 +0100
From:	"Jan Beulich" <jbeulich@...ell.com>
To:	<ambx1@....rr.com>
Cc:	<linux-kernel@...r.kernel.org>
Subject: pnp_assign_resources() issue

Adam,

I'm having some difficulty understanding why failure to probe for a resource
(in the given case, a DMA channel, but the issue is perhaps more generic) must
always result in failure of the probing of the requesting device. In any case,
the driver is required to call request_dma(), and in many cases the driver may
know how to deal with the device even if that call fails (in the given case,
parport_pc can be used as an example). Shouldn't therefore pnp_assign_dma()
be made never fail, and just mark the resource as unset/disabled if none of
the options were available? I realize drivers may not really look at these flags,
but I'd think this is a driver issue then and shouldn't keep the framework
from supporting as many different systems as possible.

Thanks, Jan

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