linux-kernel - Re: [for-next][PATCH 14/14] tracing: Get trace_array ref counts when accessing trace files

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:	Tue, 8 Apr 2014 13:32:31 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Sasha Levin <sasha.levin@...cle.com>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	"H. Peter Anvin" <hpa@...or.com>, Al Viro <viro@...IV.linux.org.uk>
Subject: Re: [for-next][PATCH 14/14] tracing: Get trace_array ref counts
 when accessing trace files

On Tue, 08 Apr 2014 13:11:32 -0400
Sasha Levin <sasha.levin@...cle.com> wrote:

> >>
> >> Although when I mount everything for the fuzzer I do it with '-onoexec,nosuid'
> >> and the fuzzer is banned from testing mount(), so I'm not sure how it would
> >> do that thing on it's own.
> > 
> > What does the -onoexec do? Not change the exec flag of files?
> 
> It lets you set it as executable, but it won't let you actually exec it.
> 
> > Also, I wonder if this has something to do with the syscall being a
> > compat sys_exec and not a native one. Is userspace on your vm 32bit? Or
> > does the fuzzer just try the different compat calls?
> 
> Right, everything is 64bit but the fuzzer tries 32bit calls as well.

When this bug is triggered, is there a way to let the fuzzer tell us
what exactly the last syscall it sent was? That is, the syscall number
plus all its arguments?

-- Steve
--
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/