Received: by 2002:a5d:925a:0:0:0:0:0 with SMTP id e26csp479461iol; Thu, 9 Jun 2022 07:36:24 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxdji9RB1Jz4G+kpF+CxTFOzXNFm+4FCl4PDFvuz+rx0OfZ3qWKFN18EBHVNJZQ4zsBKLXd X-Received: by 2002:a17:907:720a:b0:6ff:2e1c:f22f with SMTP id dr10-20020a170907720a00b006ff2e1cf22fmr36903928ejc.16.1654785373608; Thu, 09 Jun 2022 07:36:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1654785373; cv=none; d=google.com; s=arc-20160816; b=QmKbR6VtVcjH/wykinTwUdG4G9T8bYnUU08NiV7hPuyft4C2iiRCDkaf9l2wxsApal 9/m+EN6HxaH7MQfEGQvL0FVtrhTOKrcWlRQAVOWiOx8gpQYNip3SNrjJ05/8cdCbYA1E C+aZ0rdgjCdXZa3W/iKP0//ZeN4i4vxNu/GRyMrubthZsMak6uCi7sS4VvjxEFuLvrcQ bBt0awonbB/DrgpRK/+qynH6PG0mr9uo+KbB9slUhq4D58iIrUi3+kNTE5KKKU7dXcaS 26wzD5cumUpl+ZINPq93pn+AwVn8htT8AquFWibzKY5lpClC+kSkXYj3Ui9+xbbmCQ7K lY6g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:message-id:date:content-transfer-encoding :content-id:mime-version:subject:cc:to:references:in-reply-to:from :organization:dkim-signature; bh=4XBKvHmwR/IvhiCpGn2MggHZNtRmBYysvOLx4s1tsdc=; b=BSflUjrz1vDXyYQ9c1W+dbGqoOM5N4b5COOr6rir6815sxw3wRjkqS6O75fkOyI/lT 5NYZ/D/A8hD/p/encHGBXBwub0SdKR0FVOdD+tlp31JCH6W5/NlJ9GVXSspOVbbESESN FaefstLuWQtCUPBlIFYtIOyMY+uw0b7vp5OjQ3iUW59gTgG8DvjQ9l8exZ6nN+VXOzpt 0lOZpbOnr0ZUQ1uWOIDl08ribXEn+N5rOx4v60ljfZ/lmt9/xRDW0WgaXqtOYrPfzWpk CiIcy2kJ/nkVBJN/KGQsVQK6LUDzMl//kJajGpOqidhmJAZSNJSZVz/su/la0+I2dI++ mKVQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=aueGElee; 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=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id aj12-20020a1709069a4c00b006fef833c67dsi4403466ejc.168.2022.06.09.07.35.37; Thu, 09 Jun 2022 07:36:13 -0700 (PDT) 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; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=aueGElee; 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=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235161AbiFIOOy (ORCPT + 99 others); Thu, 9 Jun 2022 10:14:54 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47656 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233850AbiFIOOr (ORCPT ); Thu, 9 Jun 2022 10:14:47 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id A0351719C4 for ; Thu, 9 Jun 2022 07:14:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1654784085; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=4XBKvHmwR/IvhiCpGn2MggHZNtRmBYysvOLx4s1tsdc=; b=aueGElee75dC8Mfm4uP69yt9d85LiTMisnfjWUM/jqxkti4revIwXm8X0X5dRnnt8snYU1 8HXAfSK5Pq7g8EUNlXvQ+XvTxKuPdQMo0QzwQdCWTnwoDClt5Ry0Zha5Do5fHgtj+FZJhP IQdU+zvx0sOrF4ocPHyO4qbQJuwgorE= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-126-4mrVnexEO5OLtFd6GEWNSg-1; Thu, 09 Jun 2022 10:14:42 -0400 X-MC-Unique: 4mrVnexEO5OLtFd6GEWNSg-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 6C60F294EDEC; Thu, 9 Jun 2022 14:14:41 +0000 (UTC) Received: from warthog.procyon.org.uk (unknown [10.33.36.62]) by smtp.corp.redhat.com (Postfix) with ESMTP id C119F18EA6; Thu, 9 Jun 2022 14:14:39 +0000 (UTC) Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: References: <20220422134308.1613610-1-svens@linux.ibm.com> <202204221052.85D0C427@keescook> <202206081404.F98F5FC53E@keescook> To: Linus Torvalds Cc: dhowells@redhat.com, dchinner@redhat.com, Kees Cook , Philipp Zabel , Shawn Guo , Sascha Hauer , Fabio Estevam , Sven Schnelle , Heiko Carstens , Vasily Gorbik , Alexander Gordeev , Linux Kernel Mailing List Subject: Re: [PATCH] s390: disable -Warray-bounds MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4147482.1654784079.1@warthog.procyon.org.uk> Content-Transfer-Encoding: quoted-printable Date: Thu, 09 Jun 2022 15:14:39 +0100 Message-ID: <4147483.1654784079@warthog.procyon.org.uk> X-Scanned-By: MIMEDefang 2.79 on 10.11.54.5 X-Spam-Status: No, score=-3.3 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham 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 Linus Torvalds wrote: > > Yeah. Happily, this has already been solved, but it looks like David d= idn't do a pull yet for it? > > > > https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/= log/?h=3Dfscache-next > = > Good. Do you want it tagging and a pull req generating, even though it's a singl= e patch? Note that Dave Chinner would rather I converted code like: struct myfs_inode *myfsinode =3D xyz; myfsinode->netfs.inode.i_ino =3D 123; to something like: struct myfs_inode *myfsinode =3D xyz; struct inode *inode =3D VFS_I(myfsinode); inode->i_ino =3D 123; where the translation is wrapped inside a VFS_I() macro in every filesyste= m and wants this across all filesystems. I think the former looks cleaner, = but he has a point about how to deal with yet another layer of wrapping being inserted in the future. Do you have a preference? David