public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: systemd Mailing List <systemd-devel@lists.freedesktop.org>,
	dh.herrmann@gmail.com, linux-kernel@vger.kernel.org,
	Lennart Poettering <lennart@poettering.net>,
	Kay Sievers <kay@vrfy.org>, Jiri Slaby <jslaby@suse.cz>,
	Werner Fink <werner@suse.de>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: [PATCHv2] tty: Set correct tty name in 'active' sysfs attribute
Date: Thu, 06 Feb 2014 16:44:20 +0100	[thread overview]
Message-ID: <52F3ADD4.7020907@suse.de> (raw)
In-Reply-To: <20140206152947.GA19335@kroah.com>

On 02/06/2014 04:29 PM, Greg Kroah-Hartman wrote:
> On Thu, Feb 06, 2014 at 03:27:43PM +0100, Hannes Reinecke wrote:
>> The 'active' sysfs attribute should refer to the currently
>> active tty devices the console is running on, not the currently
>> active console.
> 
> That's not what Documentation/ABI/sysfs-tty says:
>                  Shows the list of currently configured                         
>                  console devices, like 'tty1 ttyS0'.                            
>                  The last entry in the file is the active                       
>                  device connected to /dev/console.                              
>                  The file supports poll() to detect virtual                     
>                  console switches.                         
> 
The problem is indeed with 'console devices'. There is no such
thing; you only have tty devices where the console is running on.

>> The console structure doesn't refer to any device in sysfs,
>> only the tty the console is running on has.
> 
> That sentance doesn't make sense.
> 
>> So we need to print out the tty names in 'active', not
>> the console names.
> 
> But that doesn't match the documentation.
> 
> What exactly are you trying to "fix" here?  What is the problem that the
> current file has that is broken?  And as you are changing what this file
> means, what will break if the information in the file changes?
> 
systemd is using the 'active' sysfs attribute to figure out on which
_tty_ device to start a getty on.
As soon as the console name and the tty name are different
you have no means of figuring out which _device_ to open.
AFAICS the console 'device' (ie the current entry in 'active')
doesn't have _any_ equivalent in sysfs; it just so happens that for
most console drivers the tty driver name is identical.
But this is not a requirement, and fails for drivers which have a
different device for the console and the tty.

EG on S/390 the 3270 tty has the devices

/dev/3270/tty1

but the console driver announces the name 'tty3270'.
So as per current rules the 'active' attribute contains

tty32700

which correct as per documentation, but doesn't have _any_
equivalent in sysfs.

Martin has the grubby details here.

But of course, the documentation should be updated to match the new
behavior.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)

  reply	other threads:[~2014-02-06 15:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-06 14:27 [PATCHv2] tty: Set correct tty name in 'active' sysfs attribute Hannes Reinecke
2014-02-06 15:29 ` Greg Kroah-Hartman
2014-02-06 15:44   ` Hannes Reinecke [this message]
2014-02-06 16:29     ` Greg Kroah-Hartman
2014-02-07  9:02       ` Kay Sievers
2014-02-10 11:21         ` One Thousand Gnomes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52F3ADD4.7020907@suse.de \
    --to=hare@suse.de \
    --cc=dh.herrmann@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.cz \
    --cc=kay@vrfy.org \
    --cc=lennart@poettering.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=systemd-devel@lists.freedesktop.org \
    --cc=werner@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox