linux-kernel - Re: [PATCH] x86: mm: introduce helper function in fault.c

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: <20090205002402.GF15680@elte.hu>
Date:	Thu, 5 Feb 2009 01:24:02 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Hiroshi Shimamoto <h-shimamoto@...jp.nec.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: mm: introduce helper function in fault.c


* H. Peter Anvin <hpa@...or.com> wrote:

> Ingo Molnar wrote:
>> * H. Peter Anvin <hpa@...or.com> wrote:
>>
>>> Hiroshi Shimamoto wrote:
>>>> From: Hiroshi Shimamoto <h-shimamoto@...jp.nec.com>
>>>>
>>>> Impact: cleanup
>>>>
>>>> Introduce helper function fault_in_kernel_address() to make editors happy.
>>>>
>>>> Signed-off-by: Hiroshi Shimamoto <h-shimamoto@...jp.nec.com>
>>> Applied to tip:x86/mm, however, I had to apply the patch manually.
>>
>> that's because the patch was against tip:master - so that's fine, we 
>> have some other topics that interact. (tip:core/locking in this case) I 
>> resolved the conflict in tip/master and pushed it out.
>>
>
> Of course.  I mentioned it just as a warning for screwups on my part (in  
> fact, I briefly pushed a totally bogus version since I had made an edit  
> but forgotten to "git add" it.)

ok :) Hiroshi, please double-check the end result in tip:master if you have 
some time.

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