Received: by 2002:a05:6a10:a841:0:0:0:0 with SMTP id d1csp613867pxy; Wed, 28 Apr 2021 10:29:18 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw7U3aUnSyr9fLUPy/CtMUj6ziUzRpxLuci0lNsTD+Dnp9CJ4BbkGk9umEl3qKdhQ2GOvaK X-Received: by 2002:a17:906:4049:: with SMTP id y9mr4206832ejj.344.1619630958011; Wed, 28 Apr 2021 10:29:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1619630958; cv=none; d=google.com; s=arc-20160816; b=qQgRvkkkd0iIiz9J3wUUxCn/zAtCWkyGK+/ToR4xhUALOY1yG+M2131m4jOdQdCyVD JXURVTlOHwtEY2mGs8ibfMZA8GU4BFamgH0a2lPMJVhES1BG5+IByDmOE7pH3JNC/NZz /rfdgKMRqDbYfOfdJhM4iJ5jrQxZsxXoSUUQ0xqkKJvYmb137TTwO2xQTu8+VVInOBTx 5TNWAnO8/AsMMLgF32O0z6MQk7Rw6lP0w40sSNtZ+w6o5+NSkMahQlyk76CMWxPr2A3x 8nnT3nmbyqO0bnzxKWOoqB9a5muR9fMrBW93zXGBJEZsgGKf19hVsSCS+sfmAiSqedMl /HDQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=Yzm4WxpneRJAjka6d6u6hB5NqVPyZheXRjCRS8mJPq8=; b=cqB96z4ln8RMwtZa9dWX8REwwW4xFGYE7nE0W7mN0qSVQIHyisTSvlUtu7C4yXwFfb Yz1zO0QwtbVkrk89g2U3UDcD0ECm8f6InSI1Byac52x9ueIQt6tR3PafdtUNWdfVa8FV LJTa0z/xhpdbAr6FqjqtL3tVrwVlLlUzangARF9WnMPLE7qStGlucsTFvbnz3DnVi8wr Bwwkm4HV5pb9JqIviXF5uqv8keZ5d+iqvpZ3oEArGGkHxz9j1qOY1fml1v5qtlkUi0Ve H9omnpC3yd2qisi1Ce+tzXqhHYr/dpDog0D07BlFAkuQh6TNBXs3EpAP/L9F180QqoQS +IBA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ibm.com header.s=pp1 header.b=thnUPFnU; 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=NONE sp=NONE dis=NONE) header.from=ibm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id m5si581743ejn.599.2021.04.28.10.28.53; Wed, 28 Apr 2021 10:29:17 -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=@ibm.com header.s=pp1 header.b=thnUPFnU; 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=NONE sp=NONE dis=NONE) header.from=ibm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238969AbhD1Nkg (ORCPT + 99 others); Wed, 28 Apr 2021 09:40:36 -0400 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:63078 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S229891AbhD1Nkf (ORCPT ); Wed, 28 Apr 2021 09:40:35 -0400 Received: from pps.filterd (m0098416.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 13SDXrZB045116; Wed, 28 Apr 2021 09:38:43 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ibm.com; h=date : from : to : cc : subject : message-id : references : mime-version : content-type : in-reply-to; s=pp1; bh=Yzm4WxpneRJAjka6d6u6hB5NqVPyZheXRjCRS8mJPq8=; b=thnUPFnUaWiyUOIAGuygCLOuxYSz16DuyN44IiskwaW8QEVlwVC4eu1+bMfLw2UqaMuF Crjn6za41iT8Jw90DkTcMNtJv3TdL+YGV9xzfnAGORs7PXhqA6oMQnr9HdXvclis3no/ +YlHe+9TAJLSAlM2Mf3zXPOe91l0LcljFoI6wk1gGvl9Fiqh1Lr2ceq94Lq3WA+u4ADB exLWns7+IQPaJ2ZpWRajKSI4GsWO9BDKahE/12TpuSjicwoF5vpOZsNDBrzsckzykOj1 ieQwCGhzBHkqorAP7W91/d/+TiT+ZAe7N5ILHuYsFzLSSn7fdTj+C+qm1h8IV9UVHLU5 7A== Received: from ppma04fra.de.ibm.com (6a.4a.5195.ip4.static.sl-reverse.com [149.81.74.106]) by mx0b-001b2d01.pphosted.com with ESMTP id 3877t5j45v-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 28 Apr 2021 09:38:43 -0400 Received: from pps.filterd (ppma04fra.de.ibm.com [127.0.0.1]) by ppma04fra.de.ibm.com (8.16.0.43/8.16.0.43) with SMTP id 13SDcfIB032418; Wed, 28 Apr 2021 13:38:41 GMT Received: from b06cxnps3074.portsmouth.uk.ibm.com (d06relay09.portsmouth.uk.ibm.com [9.149.109.194]) by ppma04fra.de.ibm.com with ESMTP id 384ay8h2qa-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 28 Apr 2021 13:38:41 +0000 Received: from d06av21.portsmouth.uk.ibm.com (d06av21.portsmouth.uk.ibm.com [9.149.105.232]) by b06cxnps3074.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id 13SDcb4g28311988 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 28 Apr 2021 13:38:37 GMT Received: from d06av21.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 8A96252052; Wed, 28 Apr 2021 13:38:37 +0000 (GMT) Received: from lynx.boeblingen.de.ibm.com (unknown [9.145.41.187]) by d06av21.portsmouth.uk.ibm.com (Postfix) with ESMTPS id 75C9E5204F; Wed, 28 Apr 2021 13:38:37 +0000 (GMT) Received: from brueckh by lynx.boeblingen.de.ibm.com with local (Exim 4.90_1) (envelope-from ) id 1lbkOi-0003Xu-Ee; Wed, 28 Apr 2021 15:38:36 +0200 Date: Wed, 28 Apr 2021 15:38:36 +0200 From: Hendrik Brueckner To: Valentin Vidic Cc: Christian Borntraeger , Heiko Carstens , Vasily Gorbik , linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org, Philipp Kern , Benjamin Zimmermann , debian-s390@lists.debian.org, Peter Oberparleiter Subject: Re: [PATCH v2] s390/sclp_vt220: Fix console name to match device Message-ID: <20210428133836.GD21939@linux.ibm.com> References: <20200519181654.16765-1-vvidic@valentin-vidic.from.hr> <20210427194010.9330-1-vvidic@valentin-vidic.from.hr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210427194010.9330-1-vvidic@valentin-vidic.from.hr> User-Agent: Mutt/1.5.21 (2010-09-15) X-TM-AS-GCONF: 00 X-Proofpoint-ORIG-GUID: DcekuhYotr_7hh_F4YXh-sdz3NMOpZbU X-Proofpoint-GUID: DcekuhYotr_7hh_F4YXh-sdz3NMOpZbU X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391,18.0.761 definitions=2021-04-28_06:2021-04-28,2021-04-28 signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 malwarescore=0 priorityscore=1501 mlxscore=0 phishscore=0 suspectscore=0 impostorscore=0 adultscore=0 bulkscore=0 clxscore=1011 spamscore=0 mlxlogscore=999 lowpriorityscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2104060000 definitions=main-2104280091 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Valentin, I just had the chance to look into this console topic yesterday. On Tue, Apr 27, 2021 at 09:40:10PM +0200, Valentin Vidic wrote: > Console name reported in /proc/consoles: > > ttyS1 -W- (EC p ) 4:65 It is been a while ago when working on consoles. However, consoles are typically devices without having a device node associated. There is special handling for /dev/console wrt. to the preferred console in the tty layer. A console device might be associated with a tty device but this is not a requirement. For example, consider the net console that streams console messages thru UDP and is not associated with a tty. Because console and tty are different devices, names can also be different which is, unfortunately, the case on s390. Therefore my suggestion here is not derive the tty device from the name of the console, but rather looking at the associated tty being reported as major minor number in /proc/console. > > does not match the char device name: > > crw--w---- 1 root root 4, 65 May 17 12:18 /dev/ttysclp0 In the example above, 4:65 excactly ends up in /dev/ttysclp0. I am also in contact with Christian and thanks to him to try this out internally. At least, there are options to bring this forward and let's figure out what the best solution will be. Thanks and kind regards, Hendrik -- Hendrik Brueckner brueckner@linux.ibm.com | IBM Deutschland Research & Development GmbH | Schoenaicher Str. 220, 71032 Boeblingen