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: <CANxBZFpjtGyk3CO0ViFJF8em_hBFLq7tErjMJrcq5vC7n9cy4g@mail.gmail.com>
Date:	Fri, 12 Aug 2011 12:03:34 +0800
From:	Wang Shaoyan <stufever@...il.com>
To:	Adam M Belay <abelay@....edu>
Cc:	Bjorn Helgaas <bhelgaas@...gle.com>, 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

Hi Adam,

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?

2011/8/12 Adam M Belay <abelay@....edu>:
> Hi Wang,
>
> Yes, I think your description of the race condition is right. However, as
> Bjorn
> mentioned, there are many x86 init paths that will try to reserve the same
> resources as those reported by pnp/acpi. There needs to be a better way to
> coordinate legacy device enumeration. Otherwise, the request_region() calls
> could fail when there isn't an actual resource conflict.
>
> IF we could find a good way to clean up the legacy users of request_region()
> then we could probably make pnp behave more like pci with regard to resource
> reservations.
>
> Cheers,
> Adam


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