Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp3341252yba; Mon, 8 Apr 2019 16:57:45 -0700 (PDT) X-Google-Smtp-Source: APXvYqzfA/dmX+46CQYBF1yBarezkpjwLf8PIMpoHq67+YMTljdZY1uUMJWwcOnE64Bpa9kDttgy X-Received: by 2002:a63:c746:: with SMTP id v6mr30629372pgg.401.1554767864852; Mon, 08 Apr 2019 16:57:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554767864; cv=none; d=google.com; s=arc-20160816; b=KzttTWyPlrdyq2Tu+sn1WlQ+LIc6EQcyyR2difMZgRaxmIbehU59H55q7rk8rwvelL tlw9Q4wfHqmpFrPYRwfD5l47Tf983/i/T0B5qKLSf9y+2HHOMrb5OSyGV/jRBHG7CDaG 5APG1CO+/J+7X4TyPoL6R78b4kCGhs09xuf1zTWh5G+6uTnXBY4pN5LCsrBUTH6gNS/u ZaTAtzILbz4vL6iDqDyPpOM/j+JWWzLqGdC8BbEusIIEyIJ42rmeFaJ7Yp9G6yQwXccr Y1fXaWOpVQe/mJmMpp6Zq9fgXtkOnKBdOXc0+lFYvuVX76tkNRvMo/DzaV17vPAGy4iA /IJg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature:dkim-signature; bh=hlrG1h5r/gtTe9wlG2O5Vs6sRSaHOgL/v3YX7qAdA4k=; b=ZJqbweDUk02z7qEqI6I6l62fj33PaBedg7VsjA+PBngHplGBVj7p6ods64txqsC+zy 9UQTkhr6UCuXdStp+PZhFkCC2+Jp9bNSjztHYvCJA67o63TbPIayr0qrjP2eRM+qrozH 1tz5POchBSuKJGz74ikoNM3JmJEE0q+6C89fGLQOb5661Grds66mU11PKejFYZcyw5ir lIXanRP0cUWUPCES0dVTtnzSjKM2ssoOIG9mW2ZpLX/ErBcMy2tQfhzNNEkNNRSJuuzf UNi9ro5bCXoBqRZ7OkaYE6JFjAwvDONHk/WbNTYpJ5M7dBxhAPQ/oZ35uzIqX/IIW8/Q EmDw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@tobin.cc header.s=fm2 header.b="w/av7o+I"; dkim=pass header.i=@messagingengine.com header.s=fm2 header.b="OCovG6R/"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q13si28186914pfi.208.2019.04.08.16.57.28; Mon, 08 Apr 2019 16:57:44 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@tobin.cc header.s=fm2 header.b="w/av7o+I"; dkim=pass header.i=@messagingengine.com header.s=fm2 header.b="OCovG6R/"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726693AbfDHXmX (ORCPT + 99 others); Mon, 8 Apr 2019 19:42:23 -0400 Received: from out5-smtp.messagingengine.com ([66.111.4.29]:52987 "EHLO out5-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726228AbfDHXmW (ORCPT ); Mon, 8 Apr 2019 19:42:22 -0400 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 7D5EE238DF; Mon, 8 Apr 2019 19:42:19 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Mon, 08 Apr 2019 19:42:19 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tobin.cc; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm2; bh=hlrG1h5r/gtTe9wlG2O5Vs6sRSa HOgL/v3YX7qAdA4k=; b=w/av7o+IwXSGj1V70Q3QWVcKDR60fRQL5+aswcuOwpg XaRQmcLlNHYv7bV4dfZ6wogqqK5DFkO9Fw+b5f9uvhEXIojNsCoL7kZBmeH5zozO gw2WGf3XScadCUS7tdzh+D8FVVRim5hCxkaDUnWQrSTJDdK/wae/hbQKnAe/U2SO 6zyiJriT5Jaot3G2toKJWSOLP2NZ9+K0iL3bFNMG0hOFop0StbEWGw4JlOtxzKsN 8mG7R92+ywMuR6/KNVLBXmg0uJbkSMsaKhHKn4a7CNA+0h7w98HzmqJkh87N2Fm5 +fN4oAVefabaGT1+WSkkf5mG57fkQPwaPnICiCTHU7g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=hlrG1h 5r/gtTe9wlG2O5Vs6sRSaHOgL/v3YX7qAdA4k=; b=OCovG6R/WvyuxOYGYf4fth CHKmiPCgH3DrJJL3gbmJL7YUFy1yieQ6yRJhk4PxZwfompZZpbgDrx0PbbHCWle2 Ew4LjCxF36vqm3pChXQ7v/euATtfwa1CRGEJl3+Puy/7l78LTibLvHHz+VTrDY5C VWx0jK/LCAHAq/B9RVCJJTAtohj0W4mJiSIW/PeUiH0uE/KLRzQkDR2fcOAk89o1 yzFJia4z19S9cS8lNTAkMAqYB1Bk1WlNp5zssKPrKT+ZAzBUlB0Wn4UTYFaVx70t Dv7JVPMRd3VQoIUB6/uEzGUcWQFjJR9Zsd/PuFNOWfOO0zWFxg0WFCSdvDbZOjZQ == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudeggddvgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenfg hrlhcuvffnffculdeftddmnecujfgurhepfffhvffukfhfgggtuggjofgfsehttdertdfo redvnecuhfhrohhmpedfvfhosghinhcuvedrucfjrghrughinhhgfdcuoehmvgesthhosg hinhdrtggtqeenucfkphepuddvuddrgeegrddvudejrdehtdenucfrrghrrghmpehmrghi lhhfrhhomhepmhgvsehtohgsihhnrdgttgenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from localhost (ppp121-44-217-50.bras1.syd2.internode.on.net [121.44.217.50]) by mail.messagingengine.com (Postfix) with ESMTPA id 552E310394; Mon, 8 Apr 2019 19:42:17 -0400 (EDT) Date: Tue, 9 Apr 2019 09:41:47 +1000 From: "Tobin C. Harding" To: Linus Torvalds Cc: Qian Cai , Andrew Morton , Christoph Lameter , penberg@kernel.org, David Rientjes , iamjoonsoo.kim@lge.com, Tejun Heo , Linux-MM , Linux List Kernel Mailing Subject: Re: [PATCH] slab: fix a crash by reading /proc/slab_allocators Message-ID: <20190408234147.GA14359@eros.localdomain> References: <20190406225901.35465-1-cai@lca.pw> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Mailer: Mutt 1.11.4 (2019-03-13) User-Agent: Mutt/1.11.4 (2019-03-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Apr 07, 2019 at 07:35:34PM -1000, Linus Torvalds wrote: > On Sat, Apr 6, 2019 at 12:59 PM Qian Cai wrote: > > > > The commit 510ded33e075 ("slab: implement slab_root_caches list") > > changes the name of the list node within "struct kmem_cache" from > > "list" to "root_caches_node", but leaks_show() still use the "list" > > which causes a crash when reading /proc/slab_allocators. > > The patch does seem to be correct, and I have applied it. > > However, it does strike me that apparently this wasn't caught for two > years. Which makes me wonder whether we should (once again) discuss > just removing SLAB entirely, or at least removing the > /proc/slab_allocators file. Apparently it has never been used in the > last two years. At some point a "this can't have worked if anybody > ever tried to use it" situation means that the code should likely be > excised. The bug doesn't trigger on every read of /proc/slab_allocators (as noted later in this thread by Qian). I tried to repro it with a bunch of different configs and often `cat /proc/slab_allocators` just returns empty. I've got a patchset ready to go sitting in my tree that removes SLAB, I could just send it to start the conversation :) Tobin