Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp53654pxk; Tue, 22 Sep 2020 18:26:14 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzAWy5cBvtnSzV+NpuYvkoDabWMkag4AKpsZrIpUz21X+qI1Ro8XzFvK1FMwq7OEknJdSYe X-Received: by 2002:a50:8e17:: with SMTP id 23mr6956224edw.42.1600824374667; Tue, 22 Sep 2020 18:26:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1600824374; cv=none; d=google.com; s=arc-20160816; b=zOzINOX/re+EaCkP+OYGkqt6IJt3ughaZnmEfya/HgRIGK8COJLsJmp+/tL9+vfzVM 1oDmnTP7nhfijTOC4kxjg2GTs9MnCuCpJgOsjT79zFNgt25GacBdFAiuFGSgyo1oVogx avt9hscBH7rnf0o0aE/B0kSRFkea0wsNibOD1Zv4uB6eG5PA2NKtpn2er8XjlFatGFbf 1LPXJiIPiLLbWDhH49lZhXNkK4z/lz2qHOeoCB9emYrIAhI8Qowk/jKpU7OT10Ep76rT 5k5HCBklD3rnpCIt1IevpOuP8nHYBoFnJbUvhx4CRYpBtzMUOjc5h28E4+L8v8HhqLYr pVNQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=yGf2ieA48dUvPprfXZgAqjFLts8iLAO10gQcFAOLQmM=; b=CW/vyzH8kYnT6GDTUsa1H3wgh+7H+VFXd5Nw3YQZF4yVUxhBC1l1Lc/eGJRC0oFcc2 GCm7SHQ5DOOIqwYyNaOo9QbNLbaDA/HfXQBRbIg56XLqYnXOOJKH3mWNiEeJGMZxX1G2 QW1YyGFiCKeEhSelqOTM4qmHDcH4Z+21jQ+p+M4KZzwVDqWgwynfBOLaz3biE1T6UKOu lQkue+557zQUDd5u2dr8DoXXa5IWh/AdJ6UlNmB79cOIj7lqlZ4qx2iS36vODOYagI6C DMiXCJrig3Y38SU6iMjotrJvf9l0odxI8Is2qacgSv/gBlJNLZ91I84pfMsqoEcv+/L5 EjXg== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id n13si11261566eju.705.2020.09.22.18.25.51; Tue, 22 Sep 2020 18:26:14 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727054AbgIWAXS (ORCPT + 99 others); Tue, 22 Sep 2020 20:23:18 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44374 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727034AbgIWAXS (ORCPT ); Tue, 22 Sep 2020 20:23:18 -0400 Received: from ZenIV.linux.org.uk (zeniv.linux.org.uk [IPv6:2002:c35c:fd02::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3DFA4C061755; Tue, 22 Sep 2020 17:23:18 -0700 (PDT) Received: from viro by ZenIV.linux.org.uk with local (Exim 4.92.3 #3 (Red Hat Linux)) id 1kKsZ1-004BGH-0x; Wed, 23 Sep 2020 00:23:15 +0000 Date: Wed, 23 Sep 2020 01:23:15 +0100 From: Al Viro To: Guo Ren Cc: Zhenzhong Duan , Linux Kernel Mailing List , linux-csky@vger.kernel.org, Oleg Nesterov Subject: Re: [PATCH] csky: Fix a size determination in gpr_get() Message-ID: <20200923002315.GC3421308@ZenIV.linux.org.uk> References: <20200922091505.471-1-zhenzhong.duan@gmail.com> <20200922162901.GA3421308@ZenIV.linux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: Al Viro Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Sep 23, 2020 at 08:03:20AM +0800, Guo Ren wrote: > Thx Duan, > > Acked-by: Guo Ren > > Hi AI, > > I found the broken commit still has a question: > > > commit dcad7854fcce6a2d49b6a3ead5bbefeff047e559 > > Author: Al Viro > > Date: Tue Jun 16 15:28:29 2020 -0400 > > > csky: switch to ->regset_get() > > > NB: WTF "- what the fuck :(" is fpregs_get() playing at??? > The fpregs_get() is for REGSET_FPR regset used by ptrace (gdb) and all > fp regs are stored in threads' context. > So, WTF question for? The part under #if defined(CONFIG_CPU_HAS_FPUV2) && !defined(CONFIG_CPU_HAS_VDSP) What's going on there? The mapping is really weird - assuming you had v0..v31 in the first 32 elements of regs->vr[], you end up with v0 v1 v2 v3 v2 v3 v6 v7 v4 v5 v10 v11 v6 v7 v14 v15 v8 v9 v18 v19 v10 v11 v22 v23 v12 v13 v26 v27 v14 v15 v30 v31 in the beginning of the output. Assuming it is the intended behaviour, it's probably worth some comments...