Received: by 2002:a05:6a10:a852:0:0:0:0 with SMTP id d18csp1452863pxy; Thu, 6 May 2021 08:16:23 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyksDGGhAN+uaG9Ee1xfa/7c6P3upKx/idNRDblTS1Wj2mxlQPEmYka+XNO5J6dkApvKuOV X-Received: by 2002:a17:902:e891:b029:ee:fa93:9546 with SMTP id w17-20020a170902e891b02900eefa939546mr4880750plg.23.1620314182815; Thu, 06 May 2021 08:16:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1620314182; cv=none; d=google.com; s=arc-20160816; b=LcFVYkx3+sJzzCS6/l93IXTy/RRkJLxoA+PkcVqNyy5H5YOgoirRNBM3OF1hbp0Aua vljpTMSEq2Avfc9VCCQefRu/HDgY3iQ8u8tEri3nPrr2GS6e+KVRuDCtSAWpwxiV6Zw2 ai9eyZytQrODxPKf5v4Zf2jLg+yQuNWuxQ/y4aI4iW7iCsS2NVvjxk1SrgnLu0TnRV3+ 6cCJHpOlpeaVqoEFYz026Awm+Rtr/gUo6Kvv7+V+DANqgQRk6oNM2xb7yW1/hG3SOb00 +mlCcU78OFKJEnVMEGC2tZlAd1O6KRBZUkOruArXVvhEeTYryDPPZDjcm5Nt0yMyIFt0 jNPw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:subject:mime-version:user-agent:message-id :in-reply-to:date:references:cc:to:from; bh=BTNXyN4dfSarE5eCvY/K6m9Q71mz9PaEDwoUtQgM1eI=; b=I/Z5u6Iesl+dnteVJ8QtgfVZq4ZGSkgg9lu0o2MNXvzzXH3S2N3OnyZ7eH/fpsskPe cOB+45fKmOmraxyMrsuLfTF7LFKV45rHHetzJuqnrILKBVD9i3jmJ0vXz93JJ3gAqglX IDaJiUwosqvKyhGv6a1xRKlpiNssaAkb1N/dc81qfF8heUX4miWs5d6CiWPsqtUE97yE YK6ha5NBpuFn4f0jhJioKM1XNEngm1EPbc2Q1bbQXp3sVDEghxNFDnGVnh7b0pBw+Zwm 09+OYbv4vwZjTI3Lyc1yDSR1/UciIefn1WEWCZ9/i0mEusJ3TlkVtSmErOS9K6cEEp3w o4sA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=xmission.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id h7si3631142plk.89.2021.05.06.08.16.09; Thu, 06 May 2021 08:16:22 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=xmission.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235063AbhEFPPa (ORCPT + 99 others); Thu, 6 May 2021 11:15:30 -0400 Received: from out02.mta.xmission.com ([166.70.13.232]:45168 "EHLO out02.mta.xmission.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234977AbhEFPP3 (ORCPT ); Thu, 6 May 2021 11:15:29 -0400 Received: from in01.mta.xmission.com ([166.70.13.51]) by out02.mta.xmission.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.93) (envelope-from ) id 1lefhp-005MIv-LY; Thu, 06 May 2021 09:14:25 -0600 Received: from ip68-227-160-95.om.om.cox.net ([68.227.160.95] helo=fess.xmission.com) by in01.mta.xmission.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.87) (envelope-from ) id 1lefhl-0000RC-E9; Thu, 06 May 2021 09:14:22 -0600 From: ebiederm@xmission.com (Eric W. Biederman) To: Geert Uytterhoeven Cc: Marco Elver , Arnd Bergmann , Florian Weimer , "David S. Miller" , Peter Zijlstra , Ingo Molnar , Thomas Gleixner , Peter Collingbourne , Dmitry Vyukov , Alexander Potapenko , sparclinux , linux-arch , Linux Kernel Mailing List , Linux API , kasan-dev References: Date: Thu, 06 May 2021 10:14:17 -0500 In-Reply-To: (Geert Uytterhoeven's message of "Thu, 6 May 2021 09:00:59 +0200") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-XM-SPF: eid=1lefhl-0000RC-E9;;;mid=;;;hst=in01.mta.xmission.com;;;ip=68.227.160.95;;;frm=ebiederm@xmission.com;;;spf=neutral X-XM-AID: U2FsdGVkX19LyVyCtQprDRirlYQLwegi4JFnnMVJ0N8= X-SA-Exim-Connect-IP: 68.227.160.95 X-SA-Exim-Mail-From: ebiederm@xmission.com X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on sa02.xmission.com X-Spam-Level: X-Spam-Status: No, score=-0.2 required=8.0 tests=ALL_TRUSTED,BAYES_50, DCC_CHECK_NEGATIVE,T_TM2_M_HEADER_IN_MSG,T_TooManySym_01 autolearn=disabled version=3.4.2 X-Spam-Virus: No X-Spam-Report: * -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP * 0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60% * [score: 0.4275] * 0.0 T_TM2_M_HEADER_IN_MSG BODY: No description available. * -0.0 DCC_CHECK_NEGATIVE Not listed in DCC * [sa02 1397; Body=1 Fuz1=1 Fuz2=1] * 0.0 T_TooManySym_01 4+ unique symbols in subject X-Spam-DCC: XMission; sa02 1397; Body=1 Fuz1=1 Fuz2=1 X-Spam-Combo: ;Geert Uytterhoeven X-Spam-Relay-Country: X-Spam-Timing: total 635 ms - load_scoreonly_sql: 0.03 (0.0%), signal_user_changed: 3.7 (0.6%), b_tie_ro: 2.6 (0.4%), parse: 0.69 (0.1%), extract_message_metadata: 13 (2.1%), get_uri_detail_list: 1.75 (0.3%), tests_pri_-1000: 18 (2.8%), tests_pri_-950: 1.07 (0.2%), tests_pri_-900: 0.79 (0.1%), tests_pri_-90: 202 (31.8%), check_bayes: 200 (31.6%), b_tokenize: 8 (1.2%), b_tok_get_all: 9 (1.4%), b_comp_prob: 1.72 (0.3%), b_tok_touch_all: 179 (28.2%), b_finish: 0.76 (0.1%), tests_pri_0: 385 (60.7%), check_dkim_signature: 0.41 (0.1%), check_dkim_adsp: 2.3 (0.4%), poll_dns_idle: 0.81 (0.1%), tests_pri_10: 1.71 (0.3%), tests_pri_500: 7 (1.0%), rewrite_mail: 0.00 (0.0%) Subject: Re: [PATCH v3 00/12] signal: sort out si_trapno and si_perf X-Spam-Flag: No X-SA-Exim-Version: 4.2.1 (built Thu, 05 May 2016 13:38:54 -0600) X-SA-Exim-Scanned: Yes (on in01.mta.xmission.com) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Geert Uytterhoeven writes: > Hi Eric, > > On Tue, May 4, 2021 at 11:14 PM Eric W. Biederman wrote: >> This set of changes sorts out the ABI issues with SIGTRAP TRAP_PERF, and >> hopefully will can get merged before any userspace code starts using the >> new ABI. >> >> The big ideas are: >> - Placing the asserts first to prevent unexpected ABI changes >> - si_trapno becomming ordinary fault subfield. >> - struct signalfd_siginfo is almost full >> >> This set of changes starts out with Marco's static_assert changes and >> additional one of my own that enforces the fact that the alignment of >> siginfo_t is also part of the ABI. Together these build time >> checks verify there are no unexpected ABI changes in the changes >> that follow. >> >> The field si_trapno is changed to become an ordinary extension of the >> _sigfault member of siginfo. >> >> The code is refactored a bit and then si_perf_type is added along side >> si_perf_data in the _perf subfield of _sigfault of siginfo_t. >> >> Finally the signalfd_siginfo fields are removed as they appear to be >> filling up the structure without userspace actually being able to use >> them. > > Thanks for your series, which is now in next-20210506. > >> arch/alpha/include/uapi/asm/siginfo.h | 2 - >> arch/alpha/kernel/osf_sys.c | 2 +- >> arch/alpha/kernel/signal.c | 4 +- >> arch/alpha/kernel/traps.c | 24 ++--- >> arch/alpha/mm/fault.c | 4 +- >> arch/arm/kernel/signal.c | 39 +++++++ >> arch/arm64/kernel/signal.c | 39 +++++++ >> arch/arm64/kernel/signal32.c | 39 +++++++ >> arch/mips/include/uapi/asm/siginfo.h | 2 - >> arch/sparc/include/uapi/asm/siginfo.h | 3 - >> arch/sparc/kernel/process_64.c | 2 +- >> arch/sparc/kernel/signal32.c | 37 +++++++ >> arch/sparc/kernel/signal_64.c | 36 +++++++ >> arch/sparc/kernel/sys_sparc_32.c | 2 +- >> arch/sparc/kernel/sys_sparc_64.c | 2 +- >> arch/sparc/kernel/traps_32.c | 22 ++-- >> arch/sparc/kernel/traps_64.c | 44 ++++---- >> arch/sparc/kernel/unaligned_32.c | 2 +- >> arch/sparc/mm/fault_32.c | 2 +- >> arch/sparc/mm/fault_64.c | 2 +- >> arch/x86/kernel/signal_compat.c | 15 ++- > > No changes needed for other architectures? > All m68k configs are broken with Thanks. I hadn't realized that si_perf asserts existed on m68k. Thankfully linux-next caught this these. Looking a little more deeply, it is strange that this is tested on m68k. The architecture does not implement HAVE_PERF_EVENTS so it is impossible for this signal to be generated. On the off chance this these new signals will appear on m68k someday I will update the assertion. > arch/m68k/kernel/signal.c:626:35: error: 'siginfo_t' {aka 'struct > siginfo'} has no member named 'si_perf'; did you mean 'si_errno'? > > See e.g. http://kisskb.ellerman.id.au/kisskb/buildresult/14537820/ > > There are still a few more references left to si_perf: > > $ git grep -n -w si_perf > Next/merge.log:2902:Merging userns/for-next (4cf4e48fff05 signal: sort > out si_trapno and si_perf) > arch/m68k/kernel/signal.c:626: BUILD_BUG_ON(offsetof(siginfo_t, > si_perf) != 0x10); > include/uapi/linux/perf_event.h:467: * siginfo_t::si_perf, e.g. to > permit user to identify the event. > tools/testing/selftests/perf_events/sigtrap_threads.c:46:/* Unique > value to check si_perf is correctly set from > perf_event_attr::sig_data. */ I will sweep them up as well. Eric