linux-kernel - Re: [tip:perf/core] perf/core: Check return value of the perf_event

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: <20160822071737.GF4349@krava>
Date:   Mon, 22 Aug 2016 09:17:37 +0200
From:   Jiri Olsa <jolsa@...hat.com>
To:     Vegard Nossum <vegard.nossum@...il.com>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        Stephane Eranian <eranian@...gle.com>,
        Vince Weaver <vincent.weaver@...ne.edu>,
        Ingo Molnar <mingo@...nel.org>,
        David Carrillo-Cisneros <davidcc@...gle.com>,
        Peter Zijlstra <peterz@...radead.org>,
        "H. Peter Anvin" <hpa@...or.com>, Kan Liang <kan.liang@...el.com>,
        Arnaldo Carvalho de Melo <acme@...hat.com>,
        Paul Turner <pjt@...gle.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
        linux-tip-commits@...r.kernel.org
Subject: Re: [tip:perf/core] perf/core: Check return value of the
 perf_event_read() IPI

On Sun, Aug 21, 2016 at 02:10:07PM +0200, Vegard Nossum wrote:

SNIP

> [<ffffffff816d1577>] ? __fget+0x47/0x270
> [<ffffffff81676d5b>] vfs_readv+0x8b/0xc0
> [<ffffffff81676e6e>] do_readv+0xde/0x230
> [<ffffffff81676d90>] ? vfs_readv+0xc0/0xc0
> [<ffffffff81002b60>] ? exit_to_usermode_loop+0x190/0x190
> [<ffffffff82001b07>] ? check_preemption_disabled+0x37/0x1e0
> [<ffffffff81677617>] SyS_readv+0x27/0x30
> [<ffffffff816775f0>] ? do_pwritev+0x1a0/0x1a0
> [<ffffffff81005524>] do_syscall_64+0x1c4/0x4e0
> [<ffffffff83c3286a>] entry_SYSCALL64_slow_path+0x25/0x25
> 
> I don't think WARN() is the right interface for signalling errors to
> userspace programs?

any special way to trigger that?

thanks,
jirka