Received: by 2002:a05:6a10:17d3:0:0:0:0 with SMTP id hz19csp1744211pxb; Mon, 12 Apr 2021 05:53:40 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwgUvAuCjc5VI4Nbd2snwOHk8J+KgcEZ8fEZMZBnQ0Wbt00ty5M6tvqAeP3cpuEhG5wuPly X-Received: by 2002:a05:6402:1350:: with SMTP id y16mr29009600edw.309.1618232020557; Mon, 12 Apr 2021 05:53:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1618232020; cv=none; d=google.com; s=arc-20160816; b=ipicWTZWb75TbXGQ7k9ltDzMLUPdkUtkN5eUM37vvi9GO77U33O/akyGRx4ezrPis2 isanKhFqZi+wNeNaQtfCOHGJpr6K/50D03I5iAZmg+vjSxrvCcxk0HClYKf9/+ru12x0 /PvzABB+OnlXvQwblq/wwACn+h3pgMDEIr28cjKpzHbLVrekeCC7nb8uy2vdqlKCAz5M LCUOkDA2BkYKZxHhQy1i81lzKQfefHOaJjlGOBRH+/mDI4Bmc2nYj5nPCtV/mM5erbC9 AgfcLU9dRMcZTf9PWdDLapwlHzkQfgJkS1kgcKLGibTX1BMLwJQgV7m2ujwUlNnkQMhM tjTQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id :dkim-signature; bh=ZvaWmx0R+9f/AndZFW3qVAH+dwdyOgz0YB8hfgB60ks=; b=cJ5pzNy0MI3MWtzmCr/z8vXtj9TV8okKcW8A8tNvKm9iVb09qmcy0ylVrCq1EG6Wmb xi0zAuepEXsSNGWHalpi71/1uN5cwBuiwNp1ZlFnyaTJ4QF4Yw/Lg+47XQ2dr3LyVJUf hLNEIoQrQoTIcNtxhrLJ7UcSWHioSCqycCS5hvJcRderwvzbgk6UgNY4n4XRXnsCvX/W tGXnHqF5/M5PflK49T7luBMyseSYzZyil98T8ZeGbfbxAKVAJ8uCcTUka8tQx/YGq1aC T8xE3Lp1PsmtBGbpEkMLgEpZhOAkv72ypZd2ibLQs0UARHbNKs3rE9ZLfg81tFzIhxFK QWPg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@t-2.net header.s=smtp-out-2 header.b=r3XN6zbf; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=REJECT dis=NONE) header.from=t-2.net Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id w3si3661942eju.181.2021.04.12.05.53.17; Mon, 12 Apr 2021 05:53:40 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@t-2.net header.s=smtp-out-2 header.b=r3XN6zbf; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=REJECT dis=NONE) header.from=t-2.net Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241314AbhDLMuY (ORCPT + 99 others); Mon, 12 Apr 2021 08:50:24 -0400 Received: from smtp-good-out-4.t-2.net ([93.103.246.70]:58932 "EHLO smtp-good-out-4.t-2.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238534AbhDLMuX (ORCPT ); Mon, 12 Apr 2021 08:50:23 -0400 X-Greylist: delayed 483 seconds by postgrey-1.27 at vger.kernel.org; Mon, 12 Apr 2021 08:50:22 EDT Received: from smtp-1.t-2.net (smtp-1.t-2.net [IPv6:2a01:260:1:4::1e]) by smtp-good-out-4.t-2.net (Postfix) with ESMTP id 4FJpK41DD6z1VPs; Mon, 12 Apr 2021 14:42:00 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=t-2.net; s=smtp-out-2; t=1618231320; bh=an0I2Pi77+7RFQeYVkdJg3pvIoAezOsYDpfl+GxO9Q0=; h=Subject:From:To:Cc:Date:In-Reply-To:References; b=r3XN6zbfILHQ+PiBr06WKJ3LmzmL/v92jsxQW7h6stnXhR4VYzk42A+hzdfadJRu4 cYnYIR3wqM+XRq6W+aFY5A6jZZT3KA1Z9DrboBzULiBanHqpP8ApipR0e7irrufr/U +rwCPbJm4x9A/Lna4BH+6k9HKxndqsD1F54jvsAw= Received: from localhost (localhost [127.0.0.1]) by smtp-1.t-2.net (Postfix) with ESMTP id 4FJpK413JKzTmgvW; Mon, 12 Apr 2021 14:42:00 +0200 (CEST) X-Virus-Scanned: amavisd-new at t-2.net Received: from smtp-1.t-2.net ([127.0.0.1]) by localhost (smtp-1.t-2.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z6KjXUtJEyly; Mon, 12 Apr 2021 14:41:59 +0200 (CEST) Received: from hpg3.u2up.net (89-212-91-172.static.t-2.net [89.212.91.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp-1.t-2.net (Postfix) with ESMTPS; Mon, 12 Apr 2021 14:41:28 +0200 (CEST) Message-ID: Subject: Re: How to handle concurrent access to /dev/ttyprintk ? From: Samo =?UTF-8?Q?Poga=C4=8Dnik?= To: Tetsuo Handa Cc: Petr Mladek , Jiri Slaby , Sergey Senozhatsky , Steven Rostedt , John Ogness , linux-kernel@vger.kernel.org, Greg Kroah-Hartman Date: Mon, 12 Apr 2021 14:41:27 +0200 In-Reply-To: References: <20210403041444.4081-1-penguin-kernel@I-love.SAKURA.ne.jp> <3c15d32f-c568-7f6f-fa7e-af4deb9b49f9@i-love.sakura.ne.jp> <051b550c-1cdd-6503-d2b7-0877bf0578fc@i-love.sakura.ne.jp> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5-0ubuntu0.18.04.2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Dne 12.04.2021 (pon) ob 19:39 +0900 je Tetsuo Handa napisal(a): > What is the intended usage of /dev/ttyprintk ? > The intended use of 'ttyprintk' is to redirect console to /dev/ttyprintk via the TIOCCONS ioctl. After successfull redirection, all console messages get "merged" with kernel messages and as such automatically processed (stored/transferred) by the syslog service for example. best regards, Samo