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  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:	Sun, 5 Jan 2014 10:33:53 +1100
From:	Stephen Rothwell <>
To:	Dave Hansen <>
Subject: Re: [PATCH 1/3] kconfig: consolidate arch-specific seccomp options

Hi Dave,

On Sat, 04 Jan 2014 11:04:20 -0800 Dave Hansen <> wrote:
> On 01/04/2014 07:38 AM, Stephen Rothwell wrote:
> > On Thu, 02 Jan 2014 12:20:14 -0800 Dave Hansen <> wrote:
> >> From: Dave Hansen <>
> >> There is *NOTHING* architecture-specific about SECCOMP except
> >> that the syscalls have per-architecture definitions, like every
> >> other syscall.  It is absurd to have the option in the
> >> arch-specific menus.
> > 
> > You seem to have (mostly) lost the dependency some of the architecture
> > versions of config SECCOMP had on PROC_FS ...
> I _believe_ the /proc interface has gone away.  I can't find any
> reference to /proc/<pid>/seccomp in any of the code.  Is there some
> /proc dependency that I'm missing outside of the removed
> /proc/<pid>/seccomp interface?

I don't know, but if it has gone then it is worth mentioning in the
commit message ... and you did preserve the dependency in the sparc64
Stephen Rothwell          

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists