linux-kernel - Re: [PATCH] Make clocksource name const

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: <alpine.LFD.2.00.1104022107520.5929@localhost6.localdomain6>
Date:	Sat, 2 Apr 2011 21:08:13 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Russell King - ARM Linux <linux@....linux.org.uk>
cc:	John Stultz <johnstul@...ibm.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Make clocksource name const

On Sat, 2 Apr 2011, Russell King - ARM Linux wrote:

> Has this patch been rejected?

No, I think it just got lost. Will pick it up.
 
> On Sat, Feb 19, 2011 at 03:34:50PM +0000, Russell King - ARM Linux wrote:
> > As nothing should be writing to the clocksource name string, make the
> > clocksource name pointer const.  Build-tested on ARM Versatile Express.
> > 
> > Signed-off-by: Russell King <rmk+kernel@....linux.org.uk>
> > ---
> >  include/linux/clocksource.h |    2 +-
> >  1 files changed, 1 insertions(+), 1 deletions(-)
> > 
> > diff --git a/include/linux/clocksource.h b/include/linux/clocksource.h
> > index c37b21a..94c1f38 100644
> > --- a/include/linux/clocksource.h
> > +++ b/include/linux/clocksource.h
> > @@ -161,7 +161,7 @@ struct clocksource {
> >  	/*
> >  	 * First part of structure is read mostly
> >  	 */
> > -	char *name;
> > +	const char *name;
> >  	struct list_head list;
> >  	int rating;
> >  	cycle_t (*read)(struct clocksource *cs);
> 
--
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/