From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.4 required=3.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,USER_IN_DEF_DKIM_WL autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 28A70C32771 for ; Fri, 10 Jan 2020 03:19:42 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id E1E2120721 for ; Fri, 10 Jan 2020 03:19:41 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="rF/TJsn0" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730973AbgAJDTl (ORCPT ); Thu, 9 Jan 2020 22:19:41 -0500 Received: from mail-qv1-f47.google.com ([209.85.219.47]:39882 "EHLO mail-qv1-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730952AbgAJDTk (ORCPT ); Thu, 9 Jan 2020 22:19:40 -0500 Received: by mail-qv1-f47.google.com with SMTP id y8so166776qvk.6 for ; Thu, 09 Jan 2020 19:19:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=WFfGhG9FXYFUnx3j3LlD5tdXXW7QcBTE9Rh6RB9Fn9A=; b=rF/TJsn0WhwuZCLQvzJIm3JYucQcKiHDGzlIdnHPmN1I/5qqBn24qTpjI8IyaIXF3c DxRhgs5oO99VZb4gTMZ+7uaJbe1RRlMPU+zH7LinK+i0UojQyodvEa848WxnFtnzm0e2 +nqWVSgcMentYXW0uQqXFQxJWwOsZ4UFEd8HNRfl/PTr95PHy3ZW9iM8/a3rWnJFz3eQ YLXzW5fwz1sY2Vupbe/AFoAI3mNtX8Mm6oapbGSrue+msdHN5XcAqU4TotSgHkBk4lmc 5PGfz3DgX/+7ruQJ1YWalingDRWuNjUxWfEzFTt/HXJQoMvmGiedVnELa2QBXj8eb3Iw l5xg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=WFfGhG9FXYFUnx3j3LlD5tdXXW7QcBTE9Rh6RB9Fn9A=; b=YSYDIAW9mzRG6iQZvvfYRzMLG8tM6F+GwGYf1n6gh33RIQhCE317rIMwmmobB8jFaz P1cd1TZi2CSGVLzQocJwctbXiANj2MuGFcdjv4k8rsSw6YoIJz4ntKJP8L2DMfIkvZDa DJDpgXxhC/K/dSsDriG8GaXqaQ5pPWeJDy97/mP6TwOTgmKrsKSOkADNO91aK2x+UWTe h1Z3D2qtmV2HwFa8SMu6dQFoeuv5ErNz4re5oNJjmeFC0p+V8WDLqWauqu4DE+Z/P+QZ kQ7SuWVXAOIlIc0Z/zuJodqaoIqyzmSiVd+UPOG3QXHAG2lo6JFkbaG5ILpHpxtd1t7s brqw== X-Gm-Message-State: APjAAAUNk/wjzkXGju2AOY6pLeAAw8D3ewV50IAc3g0E6tdiH59vsbnQ T1idsSm9dRqxDa9iRSDZ3XVKAxZkgxQNeMebNns7 X-Google-Smtp-Source: APXvYqwpzrYY11OpDZbAJer1PQrW1cQQ8ndOMkCZMNtUev4PhkUEDwofAXy3YrRjF11wFlDQx6BS4LDmGwg/cAnn4JY= X-Received: by 2002:a05:6214:11ab:: with SMTP id u11mr690224qvv.193.1578626379744; Thu, 09 Jan 2020 19:19:39 -0800 (PST) MIME-Version: 1.0 References: <20200109215444.95995-1-dima@arista.com> <20200109215444.95995-3-dima@arista.com> In-Reply-To: <20200109215444.95995-3-dima@arista.com> From: Iurii Zaikin Date: Thu, 9 Jan 2020 19:19:03 -0800 Message-ID: Subject: Re: [PATCH-next 2/3] sysctl/sysrq: Remove __sysrq_enabled copy To: Dmitry Safonov Cc: Linux Kernel Mailing List , Dmitry Safonov <0x7f454c46@gmail.com>, Greg Kroah-Hartman , Jiri Slaby , Vasiliy Khoruzhick , linux-serial@vger.kernel.org, Luis Chamberlain , Kees Cook , Linus FS Devel Mailing List Content-Type: text/plain; charset="UTF-8" Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org > Furthermore, the private copy isn't correct already in case > sysrq_always_enabled is true. So, remove __sysrq_enabled and use a > getter-helper for sysrq enabled status. Since the old way was known to be unreliable, the new way looks like a great candidate for a KUnit test. Off topic: I wonder if Magic Sysrq could be extended with reasonable effort to be triggered by a sequence of keystrokes which would be less likely to be generated by a noisy serial.