linux-kernel - Re: [RFC PATCH 1/2] kernel/fork.c: add a function to calculate page address from thread

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]

Date:	Thu, 28 May 2015 00:19:44 +0900
From:	Jungseok Lee <jungseoklee85@...il.com>
To:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	"linux-mm@...ck.org" <linux-mm@...ck.org>, barami97@...il.com,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [RFC PATCH 1/2] kernel/fork.c: add a function to calculate page address from thread_info

On May 27, 2015, at 12:49 PM, KOSAKI Motohiro wrote:

Hello, KOSAKI,

> On Sun, May 24, 2015 at 12:01 PM, Jungseok Lee <jungseoklee85@...il.com> wrote:
>> A current implementation assumes thread_info address is always correctly
>> calculated via virt_to_page. It restricts a different approach, such as
>> thread_info allocation from vmalloc space.
>> 
>> This patch, thus, introduces an independent function to calculate page
>> address from thread_info one.
>> 
>> Suggested-by: Sungjinn Chung <barami97@...il.com>
>> Signed-off-by: Jungseok Lee <jungseoklee85@...il.com>
>> Cc: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
>> Cc: linux-arm-kernel@...ts.infradead.org
>> ---
>> kernel/fork.c | 7 ++++++-
>> 1 file changed, 6 insertions(+), 1 deletion(-)
> 
> I haven't receive a path [2/2] and haven't review whole patches. But
> this patch itself is OK to me.
> Acked-by: KOSAKI Motohiro <kosaki.motohiro@...itsu.com>

Thanks!

I didn't add you to Cc list since [PATCH 2/2] is architecture specific.
According to the feedbacks, it is needed to figure out fundamental solutions:
1) reduce stack size and 2) focus on a generic anti-fragmentation logic.

Please refer to https://lkml.org/lkml/2015/5/24/121 for [PATCH 2/2].

Best Regards
Jungseok Lee--
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/