public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@cfl.rr.com>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: tty idle time and hooking inode_ops from a chardev
Date: Fri, 16 Dec 2011 13:22:02 -0500	[thread overview]
Message-ID: <4EEB8C4A.5080809@cfl.rr.com> (raw)
In-Reply-To: <20111216175735.GA5404@suse.de>

On 12/16/2011 12:57 PM, Greg KH wrote:
> Don't worry about it, as it's not really an important issue at all? :)

That's why it has been broken for years; because nobody cares enough 
about it to fix it, but that kind of thing irks me.

> It seems that your userspace programs aren't properly measuring the
> correct thing here, it's not that the kernel is doing something wrong,
> right?

I thought so at first, but it appears that the tty layer was originally 
written specifically to work this way.

> And atime on a character node is pretty undefined, isn't it?

Is it?  I would have thought so but after looking at all of this code, 
it looks like it is one of those things that has just been around for 
decades, but nobody knows about, kind of like FIONREAD.

I wonder if that's how who has always worked going back to AT&T Unix. 
If it is, then I'd like to stick with it ( but fix it ) rather than say, 
add an ioctl to read the idle time and change coreutils to use that instead.

  reply	other threads:[~2011-12-16 18:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-16 16:52 tty idle time and hooking inode_ops from a chardev Phillip Susi
2011-12-16 17:57 ` Greg KH
2011-12-16 18:22   ` Phillip Susi [this message]
2011-12-16 18:36     ` Greg KH
2011-12-16 19:09       ` Phillip Susi
2011-12-16 19:49       ` Phillip Susi

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=4EEB8C4A.5080809@cfl.rr.com \
    --to=psusi@cfl.rr.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    /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