linux-kernel - Re: [PATCH] Use __kernel_long_t/__kernel_ulong

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]

Date:	Thu, 26 Dec 2013 05:54:10 -0800
From:	"H.J. Lu" <hjl.tools@...il.com>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	"H. Peter Anvin" <hpa@...or.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Use __kernel_long_t/__kernel_ulong_t in <linux/resource.h>

On Thu, Dec 26, 2013 at 5:52 AM, H.J. Lu <hjl.tools@...il.com> wrote:
> On Thu, Dec 26, 2013 at 2:03 AM, Christoph Hellwig <hch@...radead.org> wrote:
>> On Wed, Dec 25, 2013 at 06:54:47AM -0800, H.J. Lu wrote:
>>> Both x32 and x86-64 use the same struct rusage and struct rlimit for
>>> system calls.  But x32 log is 32-bit.  This patch change uapi
>>> <linux/resource.h> to use __kernel_long_t in struct rusage and
>>> __kernel_ulong_t in and struct rlimit.
>>
>>  a) please send all your related patches as a series
>
> My patches are independent of each other.  They can
> be applied in order.
>

I meant to say "they can be applied in any order."


-- 
H.J.
--
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/