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: <CAOJsxLEY2YJv5G7nRKzM4UowVpPQrXKzmzP6eVShaXFYDySZ2A@mail.gmail.com>
Date:	Thu, 20 Oct 2011 12:14:06 +0300
From:	Pekka Enberg <penberg@...helsinki.fi>
To:	Ricardo Ribalda Delgado <ricardo.ribalda@...il.com>
Cc:	Cyrill Gorcunov <gorcunov@...il.com>, a.p.zijlstra@...llo.nl,
	paulus@...ba.org, mingo@...e.hu, acme@...stprotocols.net,
	anton@...ba.org, daahern@...co.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] tools/perf: Increase symbol KSYM_NAME_LEN size

On Thu, Oct 20, 2011 at 11:45 AM, Ricardo Ribalda Delgado
<ricardo.ribalda@...il.com> wrote:
> That is 4gb size :S..... I have tried making a dummy program
>
> int tttttt......ttttt (int a, int b){
> return a+b;
> }
>
> int main(int arg, char *[]argv){
>    return tttt....tttt(1,2);
> }
>
> and it has worked at least until t^16384 both in gcc and in gdb, and I
> guess it would have continue working until much more.
>
> Right now, I think we can increase it until 512, to be on the safe
> side, and keep it simple. What do you think?

If the limit is really 4G, I'm fine with whatever is the smallest
practical size. If 256 bytes works for you:

Acked-by: Pekka Enberg <penberg@...nel.org>
--
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