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=-4.1 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS 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 2900AC433E7 for ; Wed, 2 Sep 2020 13:10:04 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id F144D2078E for ; Wed, 2 Sep 2020 13:10:03 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=yadro.com header.i=@yadro.com header.b="hIB8qVeU" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726140AbgIBNJ5 (ORCPT ); Wed, 2 Sep 2020 09:09:57 -0400 Received: from mta-02.yadro.com ([89.207.88.252]:41982 "EHLO mta-01.yadro.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726310AbgIBNJa (ORCPT ); Wed, 2 Sep 2020 09:09:30 -0400 Received: from localhost (unknown [127.0.0.1]) by mta-01.yadro.com (Postfix) with ESMTP id 0F011574E9; Wed, 2 Sep 2020 13:01:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yadro.com; h= content-transfer-encoding:mime-version:user-agent:content-type :content-type:organization:date:date:from:from:subject:subject :message-id:received:received:received; s=mta-01; t=1599051709; x=1600866110; bh=dxrkS/aX5yeChGiqu1IMF0Fne/EsfHUnIkOcp1B4TN8=; b= hIB8qVeU9aSDbCq8oo0SIymw3RagNFW6M8y0CevJWdj6qJHNFbfjvYoItoHAPotU jwQvYfbRuBxCR6gk2jAaTvdkXK9vSFRsCE1qV2pdvieXQKYXdU9jqtRbWac8E0TI hmghWAjnIL2ldcv2/HAn45mNx2kaAzFCh4qVSkg13cg= X-Virus-Scanned: amavisd-new at yadro.com Received: from mta-01.yadro.com ([127.0.0.1]) by localhost (mta-01.yadro.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9t_TD-qV_gA5; Wed, 2 Sep 2020 16:01:49 +0300 (MSK) Received: from T-EXCH-02.corp.yadro.com (t-exch-02.corp.yadro.com [172.17.10.102]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mta-01.yadro.com (Postfix) with ESMTPS id 65A6B574FE; Wed, 2 Sep 2020 15:59:33 +0300 (MSK) Received: from localhost.localdomain (10.199.3.6) by T-EXCH-02.corp.yadro.com (172.17.10.102) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.669.32; Wed, 2 Sep 2020 15:59:32 +0300 Message-ID: Subject: watchdog start on restart From: Ivan Mikhaylov CC: Wim Van Sebroeck , Guenter Roeck , , , Ivan Mikhaylov Date: Wed, 2 Sep 2020 16:02:53 +0300 Organization: YADRO Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.32.5 (3.32.5-1.fc30) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Originating-IP: [10.199.3.6] X-ClientProxiedBy: T-EXCH-01.corp.yadro.com (172.17.10.101) To T-EXCH-02.corp.yadro.com (172.17.10.102) To: unlisted-recipients:; (no To-header on input) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello everyone. Currently, the watchdog interface only has "stop watchdog on restart" but lacks a "start watchdog on restart" one. Is there a way to achieve such functionality? I'd like to know why "stop watchdog on restart" wasn't implemented via ioctl interface? It would be more convenient from user perspective and you can control that behavior whenever you want from application layer. I have some thoughts on this problem that solve the aforementioned issue with "start watchdog on restart" but I don't think that my solution is correct. Looking forward for your feedback. Thanks.