Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752154AbdIMQA4 (ORCPT ); Wed, 13 Sep 2017 12:00:56 -0400 Received: from mail-io0-f176.google.com ([209.85.223.176]:43651 "EHLO mail-io0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751043AbdIMQAy (ORCPT ); Wed, 13 Sep 2017 12:00:54 -0400 X-Google-Smtp-Source: AOwi7QCTTbSdhpAVyxw0etWQPEQbFR/oQjfJ8Wa/kL0sDFONdsDyC3OwKCsQBf3bhjsh7BlMeMWtug== From: Vince Weaver X-Google-Original-From: Vince Weaver Date: Wed, 13 Sep 2017 12:00:44 -0400 (EDT) X-X-Sender: vince@macbook-air To: linux-kernel@vger.kernel.org cc: "Eric W. Biederman" , Peter Zijlstra , Ingo Molnar , Arnaldo Carvalho de Melo Subject: perf: weird si_code results on overflow signal Message-ID: User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 396 Lines: 13 Hello I just compiled up a fresh git kernel and all of the perf_event_test overflow tests are failing. The reason is that instead of getting POLL_IN or POLL_HUP sources as expected, they are getting weird results in si_code of "-5". I haven't had time to bisect this, but I do notice that some major changes to si_code handling went in with 64a76d0d64bea159da997c002a916ffc03f98bfc Vince