linux-kernel - Re: [PATCH] hpet, allow user controlled mmap for user processes

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: <51487B59.6010607@ladisch.de>
Date:	Tue, 19 Mar 2013 15:51:05 +0100
From:	Clemens Ladisch <clemens@...isch.de>
To:	Prarit Bhargava <prarit@...hat.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] hpet, allow user controlled mmap for user processes

Prarit Bhargava wrote:
> On 03/19/2013 03:43 AM, Clemens Ladisch wrote:
>> Prarit Bhargava wrote:
>>> +	int "Enable HPET MMAP access by default"
>>> +	default 0
>>
>> This breaks backwards compatibility.
>
> Does backwards compatibility matter for something like?  I have no problem
> setting it to 1 but I'm more curious from a general kernel point of view.

When somebody updates from some old kernel where HPET mmap was
explicitly enabled, this default value will now disable it.  The
default behaviour should always be to be compatible with older
kernels.


Regards,
Clemens
--
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/