linux-kernel - Re: [PATCH 1/1] posix-timers: Show clock ID in proc file

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130517155916.GA24976@kroah.com>
Date:	Fri, 17 May 2013 08:59:16 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Pavel Tikhomirov <snorcht@...il.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	Michael Kerrisk <mtk.manpages@...il.com>,
	Matthew Helsley <matt.helsley@...il.com>,
	linux-api@...r.kernel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Pavel Emelyanov <xemul@...allels.com>
Subject: Re: [PATCH 1/1] posix-timers: Show clock ID in proc file

On Fri, May 17, 2013 at 02:12:03AM +0400, Pavel Tikhomirov wrote:
> Expand information about posix-timers in /proc/<pid>/timers by adding
> info about clock, with which the timer was created. I.e. in the forth
> line of timer info after "notify:" line go "ClockID: <clock_id>".
> 
> Signed-off-by: Pavel Tikhomirov <snorcht@...il.com>
> ---
>  fs/proc/base.c |    1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/fs/proc/base.c b/fs/proc/base.c
> index 2dad4a9..8a38eef 100644
> --- a/fs/proc/base.c
> +++ b/fs/proc/base.c
> @@ -2079,6 +2079,7 @@ static int show_timer(struct seq_file *m, void *v)
>  		nstr[notify & ~SIGEV_THREAD_ID],
>  		(notify & SIGEV_THREAD_ID) ? "tid" : "pid",
>  		pid_nr_ns(timer->it_pid, tp->ns));
> +	seq_printf(m, "ClockID: %d\n", timer->it_clock);

What userspace tool just broke by adding a new field to this file?

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/