Received: by 2002:a05:6a10:7420:0:0:0:0 with SMTP id hk32csp3422983pxb; Sun, 20 Feb 2022 19:40:10 -0800 (PST) X-Google-Smtp-Source: ABdhPJyt6ZVNK+u5tLizUkevMraYmkITHHsRdTdk+A9TWi8TysZvKaRzF5x78rit0Su+QLJ3cw0g X-Received: by 2002:a63:d63:0:b0:36c:670d:b6c9 with SMTP id 35-20020a630d63000000b0036c670db6c9mr14391804pgn.343.1645414809837; Sun, 20 Feb 2022 19:40:09 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1645414809; cv=none; d=google.com; s=arc-20160816; b=p0lkssd9IUXOCOXQQl76i1FEj1YunyLa/HBpuoqx8ap2I6EAypcZxrLTl/JhU+rI8L gYHw5nV935QuNj5aRYJK3sxYRmCpykbGlcSEDuKihAVxmhOqJ4KbhQ2mq5W8/HDhBfIT 7tyqyilsPFmDAEOdT/k/vGZTHuAZSsnQH+MsCRIuMuKzHIOvCYWnbeIBWhYKqo21d9Aj 4p4Rwp7M1Hjyyzkb9mZegT+aUnK1wVESqJAO+KDNSk7M2nTNTqbkcUIpriYYMX33xFA0 BrLGYQIMzPbKX+AkGpuw/XYzFhSMQ3iyPu+T879b5qROghXNwA49aoQ7Ve8ifdIyAx2x luWA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:references:message-id:in-reply-to :subject:cc:to:from:date:dkim-signature; bh=9s/ZIHrGES7feK2tz5dP1rmrFQ/RLT8GNy7zBmf9EgA=; b=FnzAXJ8i3wcwnS1Wt6Yf/2CQsIzGlMC3oVLyBZvNRpUFWrdI2GsSCoZDkr8HxtvAT/ 69O2JnsJQ6raWItQO4FsCcarBZ32ZZq0dk47NumIrF2cZvTg+iApa4Kd0t9LRdOpmXvc VD3HlaHI/K0KIGv588b9zL4T+vcFfQCZeeKkq/nRnpUuLbUBXehDoHXMkrVbMXkkFobL KRJxfatvIVis+mtUsHotZcTHx1EA8Bssh6bigOjesjQnMtEvrAef2sse4Aj570dLF++t hJNW/XThDyYuXOpecNtnRUArLkbABPTdixkx4nPT3592uGXvNIU/3AILPghrjV6ZruJ+ ul5Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=f0H3TVA9; 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=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id x10si3201327pgq.520.2022.02.20.19.39.52; Sun, 20 Feb 2022 19:40:09 -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; dkim=pass header.i=@google.com header.s=20210112 header.b=f0H3TVA9; 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=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239035AbiBRSrv (ORCPT + 99 others); Fri, 18 Feb 2022 13:47:51 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:43942 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237417AbiBRSrt (ORCPT ); Fri, 18 Feb 2022 13:47:49 -0500 Received: from mail-pf1-x434.google.com (mail-pf1-x434.google.com [IPv6:2607:f8b0:4864:20::434]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id ABE2F13E10 for ; Fri, 18 Feb 2022 10:47:32 -0800 (PST) Received: by mail-pf1-x434.google.com with SMTP id g1so3009628pfv.1 for ; Fri, 18 Feb 2022 10:47:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=date:from:to:cc:subject:in-reply-to:message-id:references :mime-version; bh=9s/ZIHrGES7feK2tz5dP1rmrFQ/RLT8GNy7zBmf9EgA=; b=f0H3TVA9AOk2uGP+1p95rEv5SaFwf75XopgpbmOxZY8zZsMWRS7/ilyAzemq42ESPm wlFR7t4VyV+eB83JWky1FqzO4CdSZjDePKhOC5uuKA42mL9nd98/EVdL9zpuiudJCRHG E/569cf/0s3ZM93xiPP35gjTOIeT6l97ECf0fifUKeerHnYhMsaBs/uZnBlqlDJvqtX8 9zyEy2gnZm6ck0iYurd/2iReR+k7ZeFKo/nzibUUGYQkf6MeYCCb7CUMpRqjEUOum+zH z0+tIlA6QCpa+mIRTL/DQP/NDl3xZeu/8IIub+8KNEX5t30zXH6yiACac5mO3G2kSuAH 2HyA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:in-reply-to:message-id :references:mime-version; bh=9s/ZIHrGES7feK2tz5dP1rmrFQ/RLT8GNy7zBmf9EgA=; b=AV2dc4k04/htbUf5ci/ZIUPPdAzY/xfn1Qhrgu39GXRXaX8miEa3cHwiPGaTBUYrAr OIHINzd88GD/94AYpA9As08BVfu48cBDOnnABAanoyft/m4iNHNVewO328xg0b8HglW0 XLdF3WuuWQACiVM+3JRXba88KEPQshU4VHj7b6fTH2H8ukihBKp5QxEVjh/AdGIxVOjd lXgG4z+oEci770Vt34ZYM8crxM5i/+EHrVfpwpGZvX6db2zyjPFvSAyGj/qF23C19tTH dqnZ1vG4Y3zrg4ZKdybyPcCQNytSSXHnlxJPL1/W2G9mvW/rXtk76jzM0wCXKAb1j7EF If6g== X-Gm-Message-State: AOAM5333OivMc/OWvit/+PIo0sW7OrPXZ08kCZ8Ft0qPDcN2mfWp2c5M dSwKFqfSdOpr8qDuCvZv79pGqQ== X-Received: by 2002:a62:3085:0:b0:4e0:1218:6d03 with SMTP id w127-20020a623085000000b004e012186d03mr9053021pfw.19.1645210051404; Fri, 18 Feb 2022 10:47:31 -0800 (PST) Received: from [2620:15c:29:204:701:472c:4005:6710] ([2620:15c:29:204:701:472c:4005:6710]) by smtp.gmail.com with ESMTPSA id h5sm3534755pfc.118.2022.02.18.10.47.30 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 18 Feb 2022 10:47:30 -0800 (PST) Date: Fri, 18 Feb 2022 10:47:30 -0800 (PST) From: David Rientjes To: Greg Kroah-Hartman cc: linux-kernel@vger.kernel.org, stable , Kees Cook , Daniel Micay , Nick Desaulniers , Christoph Lameter , Pekka Enberg , Joonsoo Kim , Andrew Morton , Vlastimil Babka , Nathan Chancellor , linux-mm@kvack.org, llvm@lists.linux.dev Subject: Re: [PATCH] slab: remove __alloc_size attribute from __kmalloc_track_caller In-Reply-To: <20220218131358.3032912-1-gregkh@linuxfoundation.org> Message-ID: References: <20220218131358.3032912-1-gregkh@linuxfoundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-17.6 required=5.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF, ENV_AND_HDR_SPF_MATCH,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE,USER_IN_DEF_DKIM_WL,USER_IN_DEF_SPF_WL 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 On Fri, 18 Feb 2022, Greg Kroah-Hartman wrote: > Commit c37495d6254c ("slab: add __alloc_size attributes for better > bounds checking") added __alloc_size attributes to a bunch of kmalloc > function prototypes. Unfortunately the change to __kmalloc_track_caller > seems to cause clang to generate broken code and the first time this is > called when booting, the box will crash. > > While the compiler problems are being reworked and attempted to be > solved, let's just drop the attribute to solve the issue now. Once it > is resolved it can be added back. > > Fixes: c37495d6254c ("slab: add __alloc_size attributes for better bounds checking") > Cc: stable > Cc: Kees Cook > Cc: Daniel Micay > Cc: Nick Desaulniers > Cc: Christoph Lameter > Cc: Pekka Enberg > Cc: David Rientjes > Cc: Joonsoo Kim > Cc: Andrew Morton > Cc: Vlastimil Babka > Cc: Nathan Chancellor > Cc: linux-mm@kvack.org > Cc: linux-kernel@vger.kernel.org > Cc: llvm@lists.linux.dev > Signed-off-by: Greg Kroah-Hartman Acked-by: David Rientjes