mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Raymond Jennings <shentino@gmail.com>
To: Jiri Slaby <jslaby@suse.cz>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	john_paul.perry@alcatel-lucent.com, stable@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 1/1] tty: fix up atime/mtime mess, take four
Date: Fri, 06 Mar 2015 05:16:14 -0800	[thread overview]
Message-ID: <1425647774.14441.1.camel@avalar.dragonrealms> (raw)
In-Reply-To: <1425058831-13923-1-git-send-email-jslaby@suse.cz>

On Fri, 2015-02-27 at 18:40 +0100, Jiri Slaby wrote:
> So check the absolute difference of times and if it large than "8
> seconds or so", always update the time. That means we will update
> immediatelly when changing time. Ergo, CAP_SYS_TIME can foul the
> check, but it was always that way.

If I may ask, what is supposed to happen normally when you write to a
tty device?  I always thought the tty device was treated just like a
normal file wrt. timestamps.

Now I see a patch for 8 seconds something.
> 
> Thanks John for serving me this so nicely debugged.
> 
> Signed-off-by: Jiri Slaby <jslaby@suse.cz>
> Reported-by: John Paul Perry <john_paul.perry@alcatel-lucent.com>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: <stable@vger.kernel.org> # all, as b0b885657 was backported
> Cc: Linus Torvalds <torvalds@linux-foundation.org>
> ---
>  drivers/tty/tty_io.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/tty/tty_io.c b/drivers/tty/tty_io.c
> index e07f35e14fa2..e31b18a6d576 100644
> --- a/drivers/tty/tty_io.c
> +++ b/drivers/tty/tty_io.c
> @@ -1032,8 +1032,8 @@ EXPORT_SYMBOL(start_tty);
>  /* We limit tty time update visibility to every 8 seconds or so. */
>  static void tty_update_time(struct timespec *time)
>  {
> -	unsigned long sec = get_seconds() & ~7;
> -	if ((long)(sec - time->tv_sec) > 0)
> +	unsigned long sec = get_seconds();
> +	if (abs(sec - time->tv_sec) & ~7)
>  		time->tv_sec = sec;
>  }
>  



  parent reply	other threads:[~2015-03-06 13:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-27 17:40 Jiri Slaby
2015-02-27 18:33 ` Linus Torvalds
2015-02-27 19:23 ` Greg KH
2015-02-27 21:27   ` Perry, John Paul G (John Paul)** CTR **
2015-03-06 13:16 ` Raymond Jennings [this message]
2015-03-09 10:01   ` Jiri Slaby
2015-03-10 22:41     ` One Thousand Gnomes
2015-03-11  8:09       ` Jiri Slaby

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=1425647774.14441.1.camel@avalar.dragonrealms \
    --to=shentino@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=john_paul.perry@alcatel-lucent.com \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

Powered by JetHome