Received: by 2002:a05:6a10:9afc:0:0:0:0 with SMTP id t28csp2516099pxm; Mon, 28 Feb 2022 00:08:02 -0800 (PST) X-Google-Smtp-Source: ABdhPJxATkINDkV1ynCAwMPkHJ9bvkGo9U0U4av7lCcO9fnUCKPzcK0TCmb/e7kXz2aEevX5tzi+ X-Received: by 2002:a63:1c15:0:b0:372:ffcd:4d21 with SMTP id c21-20020a631c15000000b00372ffcd4d21mr16261532pgc.450.1646035682738; Mon, 28 Feb 2022 00:08:02 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1646035682; cv=none; d=google.com; s=arc-20160816; b=k/Ch3LcYQIfQWzKMJLCO5nnnXaGIhZtkRtomU8D/7uRk57TYEuq95UUkUmoywfbq2N 30MMUmUlcA0QVJxlfITCp+6tjQmW0ha5B/rgggUK9MDzW9ojX6I07O2e4lcOBiz5v5vh XRJ9ZJdfjUQCoJpGZV/Z/3uxL2BOkDMqsAXGaKreFLi3VgTfITxz6I0tNxe0mI/yoPPG AKUfaHreJ53sxOGP9YvOvKiw7mfVO4OkpYdzPHZbug0nR2KzPgDe/wnmyR5PRiR8pil+ Ec69YS00MJBApSJLHLZvICa/c9j6i7h2VNLKLP6lBxMTwgjqJx9Kd9AOhtxGm10ihuJX sVYg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :mime-version:accept-language:in-reply-to:references:message-id:date :thread-index:thread-topic:subject:cc:to:from; bh=iXr1Zp2O/AKkuc80U71ncXPXsVm9WhTmiDob9bo+qjs=; b=bbO3l07m7WpFdAxne7DBp+45W8oDOjYMgo6HgqvPLNXGsRv3cMkXBxsnZoMuGXFFVx 5PcXLUAfitNUCZyvkNhogndiTT9enmejilUS1OrLXWEEAxG2QBrAl9TD2N9q9EQBnGPy SSnTEWplpNPnPDBQ4IVMYel0UehQ6j+gERN964S/l9UTdiRxfgyCaC4JMkymVA0ziZYO mRfKcOkBJwaxQU8cWCthBh+DxKeUL6wEnsi+JF4xBGcFbkf9Pua/nFfQ+EZqxnEPtouG zdPZnqd+Ir2hsajSl17n3PzVkfOVAjzsd5I4WSn2FMPGW81CS8fYXQszZ6PaqIFsnhmo 2tPA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=aculab.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id e1-20020a656781000000b00378b905af35si1267953pgr.417.2022.02.28.00.07.48; Mon, 28 Feb 2022 00:08:02 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=aculab.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233318AbiB1Gkx convert rfc822-to-8bit (ORCPT + 99 others); Mon, 28 Feb 2022 01:40:53 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44156 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233319AbiB1Gks (ORCPT ); Mon, 28 Feb 2022 01:40:48 -0500 Received: from eu-smtp-delivery-151.mimecast.com (eu-smtp-delivery-151.mimecast.com [185.58.86.151]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 1D0E03D1D6 for ; Sun, 27 Feb 2022 22:40:09 -0800 (PST) Received: from AcuMS.aculab.com (156.67.243.121 [156.67.243.121]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id uk-mta-127-ln2z8qc2NY6O0etIBpyffg-1; Mon, 28 Feb 2022 06:40:07 +0000 X-MC-Unique: ln2z8qc2NY6O0etIBpyffg-1 Received: from AcuMS.Aculab.com (fd9f:af1c:a25b:0:994c:f5c2:35d6:9b65) by AcuMS.aculab.com (fd9f:af1c:a25b:0:994c:f5c2:35d6:9b65) with Microsoft SMTP Server (TLS) id 15.0.1497.28; Mon, 28 Feb 2022 06:40:04 +0000 Received: from AcuMS.Aculab.com ([fe80::994c:f5c2:35d6:9b65]) by AcuMS.aculab.com ([fe80::994c:f5c2:35d6:9b65%12]) with mapi id 15.00.1497.028; Mon, 28 Feb 2022 06:40:04 +0000 From: David Laight To: "'guoren@kernel.org'" , "palmer@dabbelt.com" , "arnd@arndb.de" , "anup@brainfault.org" , "gregkh@linuxfoundation.org" , "liush@allwinnertech.com" , "wefu@redhat.com" , "drew@beagleboard.org" , "wangjunqiang@iscas.ac.cn" , "hch@lst.de" CC: "linux-arch@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-riscv@lists.infradead.org" , "linux-csky@vger.kernel.org" , "linux-s390@vger.kernel.org" , "sparclinux@vger.kernel.org" , "linuxppc-dev@lists.ozlabs.org" , "linux-parisc@vger.kernel.org" , "linux-mips@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "x86@kernel.org" Subject: RE: [PATCH V7 03/20] compat: consolidate the compat_flock{,64} definition Thread-Topic: [PATCH V7 03/20] compat: consolidate the compat_flock{,64} definition Thread-Index: AQHYK/ctkLOBFN5NzkqkonsQCyvC26yogbZg Date: Mon, 28 Feb 2022 06:40:04 +0000 Message-ID: References: <20220227162831.674483-1-guoren@kernel.org> <20220227162831.674483-4-guoren@kernel.org> In-Reply-To: <20220227162831.674483-4-guoren@kernel.org> Accept-Language: en-GB, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.202.205.107] MIME-Version: 1.0 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=C51A453 smtp.mailfrom=david.laight@aculab.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: aculab.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT X-Spam-Status: No, score=-3.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H5,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: guoren@kernel.org > Sent: 27 February 2022 16:28 > > From: Christoph Hellwig > > Provide a single common definition for the compat_flock and > compat_flock64 structures using the same tricks as for the native > variants. Another extra define is added for the packing required on > x86. ... > diff --git a/arch/x86/include/asm/compat.h b/arch/x86/include/asm/compat.h ... > /* > - * IA32 uses 4 byte alignment for 64 bit quantities, > - * so we need to pack this structure. > + * IA32 uses 4 byte alignment for 64 bit quantities, so we need to pack the > + * compat flock64 structure. > */ ... > +#define __ARCH_NEED_COMPAT_FLOCK64_PACKED > > struct compat_statfs { > int f_type; > diff --git a/include/linux/compat.h b/include/linux/compat.h > index 1c758b0e0359..a0481fe6c5d5 100644 > --- a/include/linux/compat.h > +++ b/include/linux/compat.h > @@ -258,6 +258,37 @@ struct compat_rlimit { > compat_ulong_t rlim_max; > }; > > +#ifdef __ARCH_NEED_COMPAT_FLOCK64_PACKED > +#define __ARCH_COMPAT_FLOCK64_PACK __attribute__((packed)) > +#else > +#define __ARCH_COMPAT_FLOCK64_PACK > +#endif ... > +struct compat_flock64 { > + short l_type; > + short l_whence; > + compat_loff_t l_start; > + compat_loff_t l_len; > + compat_pid_t l_pid; > +#ifdef __ARCH_COMPAT_FLOCK64_PAD > + __ARCH_COMPAT_FLOCK64_PAD > +#endif > +} __ARCH_COMPAT_FLOCK64_PACK; > + Provided compat_loff_t are correctly defined with __aligned__(4) marking the structure packed isn't needed. I believe compat_u64 and compat_s64 both have aligned(4). It is also wrong, consider: struct foo { char x; struct compat_flock64 fl64; }; There should be 3 bytes of padding after 'x'. But you've removed it. David - Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK Registration No: 1397386 (Wales)