On 03/10/2015, 11:41 PM, One Thousand Gnomes wrote:
> On Mon, 09 Mar 2015 11:01:12 +0100
> Jiri Slaby wrote:
>
>> On 03/06/2015, 02:16 PM, Raymond Jennings wrote:
>>> 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
On 03/10/2015, 11:41 PM, One Thousand Gnomes wrote:
On Mon, 09 Mar 2015 11:01:12 +0100
Jiri Slaby jsl...@suse.cz wrote:
On 03/06/2015, 02:16 PM, Raymond Jennings wrote:
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
On Mon, 09 Mar 2015 11:01:12 +0100
Jiri Slaby wrote:
> On 03/06/2015, 02:16 PM, Raymond Jennings wrote:
> > 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
On Mon, 09 Mar 2015 11:01:12 +0100
Jiri Slaby jsl...@suse.cz wrote:
On 03/06/2015, 02:16 PM, Raymond Jennings wrote:
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
On 03/06/2015, 02:16 PM, Raymond Jennings wrote:
> 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
On 03/06/2015, 02:16 PM, Raymond Jennings wrote:
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
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
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
1/1] tty: fix up atime/mtime mess, take four
On Fri, Feb 27, 2015 at 06:40:31PM +0100, Jiri Slaby wrote:
> This problem was taken care of three times already in
> * b0de59b5733d18b0d1974a060860a8b5c1b36a2e (TTY: do not update
> atime/mtime on r
On Fri, Feb 27, 2015 at 06:40:31PM +0100, Jiri Slaby wrote:
> This problem was taken care of three times already in
> * b0de59b5733d18b0d1974a060860a8b5c1b36a2e (TTY: do not update
> atime/mtime on read/write),
> * 37b7f3c76595e23257f61bd80b223de8658617ee (TTY: fix atime/mtime
> regression),
Looks sane,
On Fri, Feb 27, 2015 at 9:40 AM, Jiri Slaby wrote:
> Cc: Linus Torvalds
Acked-by: Linus Torvalds
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
This problem was taken care of three times already in
* b0de59b5733d18b0d1974a060860a8b5c1b36a2e (TTY: do not update
atime/mtime on read/write),
* 37b7f3c76595e23257f61bd80b223de8658617ee (TTY: fix atime/mtime
regression), and
* b0b885657b6c8ef63a46bc9299b2a7715d19acde (tty: fix up atime/mtime
This problem was taken care of three times already in
* b0de59b5733d18b0d1974a060860a8b5c1b36a2e (TTY: do not update
atime/mtime on read/write),
* 37b7f3c76595e23257f61bd80b223de8658617ee (TTY: fix atime/mtime
regression), and
* b0b885657b6c8ef63a46bc9299b2a7715d19acde (tty: fix up atime/mtime
Looks sane,
On Fri, Feb 27, 2015 at 9:40 AM, Jiri Slaby jsl...@suse.cz wrote:
Cc: Linus Torvalds torva...@linux-foundation.org
Acked-by: Linus Torvalds torva...@linux-foundation.org
Linus
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the
On Fri, Feb 27, 2015 at 06:40:31PM +0100, Jiri Slaby wrote:
This problem was taken care of three times already in
* b0de59b5733d18b0d1974a060860a8b5c1b36a2e (TTY: do not update
atime/mtime on read/write),
* 37b7f3c76595e23257f61bd80b223de8658617ee (TTY: fix atime/mtime
regression), and
*
1/1] tty: fix up atime/mtime mess, take four
On Fri, Feb 27, 2015 at 06:40:31PM +0100, Jiri Slaby wrote:
This problem was taken care of three times already in
* b0de59b5733d18b0d1974a060860a8b5c1b36a2e (TTY: do not update
atime/mtime on read/write),
* 37b7f3c76595e23257f61bd80b223de8658617ee
16 matches
Mail list logo