From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.0 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 88861C433DF for ; Wed, 5 Aug 2020 02:08:02 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 7467420842 for ; Wed, 5 Aug 2020 02:08:02 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725981AbgHECIB (ORCPT ); Tue, 4 Aug 2020 22:08:01 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51722 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725904AbgHECIB (ORCPT ); Tue, 4 Aug 2020 22:08:01 -0400 Received: from ZenIV.linux.org.uk (zeniv.linux.org.uk [IPv6:2002:c35c:fd02::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4238FC06174A; Tue, 4 Aug 2020 19:08:01 -0700 (PDT) Received: from viro by ZenIV.linux.org.uk with local (Exim 4.92.3 #3 (Red Hat Linux)) id 1k38qH-009WtO-2V; Wed, 05 Aug 2020 02:07:45 +0000 Date: Wed, 5 Aug 2020 03:07:45 +0100 From: Al Viro To: Palmer Dabbelt Cc: macro@wdc.com, linux-riscv@lists.infradead.org, Paul Walmsley , aou@eecs.berkeley.edu, linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: Re: [PATCH 1/2] riscv: ptrace: Use the correct API for `fcsr' access Message-ID: <20200805020745.GL1236603@ZenIV.linux.org.uk> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Tue, Aug 04, 2020 at 07:01:01PM -0700, Palmer Dabbelt wrote: > > We currently have @start_pos fixed at 0 across all calls, which works as > > a result of the implementation, in particular because we have no padding > > between the FP general registers and the FP control and status register, > > but appears not to have been the intent of the API and is not what other > > ports do, requiring one to study the copy handlers to understand what is > > going on here. start_pos *is* fixed at 0 and it's going to go away, along with the sodding user_regset_copyout() very shortly. ->get() is simply a bad API. See vfs.git#work.regset for replacement. And ->put() is also going to be taken out and shot (next cycle, most likely).