From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754593AbdKCJj7 (ORCPT ); Fri, 3 Nov 2017 05:39:59 -0400 Received: from ozlabs.org ([103.22.144.67]:41741 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750762AbdKCJj6 (ORCPT ); Fri, 3 Nov 2017 05:39:58 -0400 From: Michael Ellerman To: Andi Kleen , akpm@linux-foundation.org Cc: linux-kernel@vger.kernel.org, Andi Kleen Subject: Re: [PATCH] Support resetting WARN*_ONCE In-Reply-To: <20171017214017.22708-1-andi@firstfloor.org> References: <20171017214017.22708-1-andi@firstfloor.org> Date: Fri, 03 Nov 2017 20:39:56 +1100 Message-ID: <8760ar7lar.fsf@concordia.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Andi Kleen writes: > diff --git a/kernel/panic.c b/kernel/panic.c > index bdd18afa19a4..b2d872fa16de 100644 > --- a/kernel/panic.c > +++ b/kernel/panic.c > @@ -587,6 +588,32 @@ void warn_slowpath_null(const char *file, int line) > EXPORT_SYMBOL(warn_slowpath_null); > #endif > > +#ifdef CONFIG_BUG > + > +/* Support resetting WARN*_ONCE state */ > + > +static int clear_warn_once_set(void *data, u64 val) > +{ > + memset(__start_once, 0, __end_once - __start_once); > + return 0; > +} > + > +DEFINE_SIMPLE_ATTRIBUTE(clear_warn_once_fops, > + NULL, > + clear_warn_once_set, > + "%lld\n"); > + > +static __init int register_warn_debugfs(void) > +{ > + /* Don't care about failure */ > + debugfs_create_file("clear_warn_once", 0644, NULL, ^ Wouldn't 0200 be more appropriate if it's only writable? Otherwise it appears readable, but cat'ing it gives you an error. cheers