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: <20090802.131705.81498579.davem@davemloft.net>
Date:	Sun, 02 Aug 2009 13:17:05 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	jens.axboe@...cle.com
Cc:	linux-kernel@...r.kernel.org, a.p.zijlstra@...llo.nl,
	fweisbec@...il.com, mingo@...e.hu
Subject: Re: [PATCH] basic perf support for sparc

From: Jens Axboe <jens.axboe@...cle.com>
Date: Wed, 29 Jul 2009 13:25:10 +0200

> -#define NR_SYSCALLS		327
> +#define NR_SYSCALLS		328

When you increase this value, you have to add entries to all of the
syscall tables.  The syscall dispatch checks against this as a limit,
so if you don't explicitly add an entry to all the tables, it's
possible to deref garbage past the end of the table and try to jump to
it as a syscall.

And if you somehow arrange for adding a compat syscall entry here for
this, and build the perf tools 32-bit, you can forego all of these
rediculious issues with trying to get a 64-bit BFD library.  If the
perf tools are written portably and use types like u64 etc. for
holding addresses and similar things, this should not be an issue.

The 32-bit sparc BFD library has full support for all the 64-bit
binary formats and whatnot.
--
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