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]
Message-ID: <CAErSpo6NgwTt0o0u651ojN_xH=5qqVN1o0POTEeK+eV6Y68p7A@mail.gmail.com>
Date:	Fri, 12 Aug 2011 10:24:50 -0600
From:	Bjorn Helgaas <bhelgaas@...gle.com>
To:	Wang Shaoyan <stufever@...il.com>
Cc:	Adam M Belay <abelay@....edu>, linux-kernel@...r.kernel.org,
	Wang Shaoyan <wangshaoyan.pt@...bao.com>,
	linux-acpi@...r.kernel.org
Subject: Re: [PATCH] pnp: replace deprecated __check_region to request_region

On Thu, Aug 11, 2011 at 10:03 PM, Wang Shaoyan <stufever@...il.com> wrote:
> I can understand your worry, but back to beginning, just as the
> subject of the patch: "replace deprecated __check_region to
> request_region", I think this patch is still need, although it can't
> solve the problems both you guys mentioned. Do you agree it?

Your patch is presented as "no functional change," but in fact, the
current code does not leave the region reserved, while with your patch
it does.  This is quite a large change and I think it will break
things.

I would like to see the PNP core reserve resources, but it should be
done for all resources of all device.  Your patch only affects ioports
(I think we should do memory as well), and it only affects the
assignment path (I don't think we do this for every device we
enumerate).  And it effectively adds a region reservation without
adding a corresponding release.

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