linux-kernel - Re: [PATCH 1/2 -tip] sched: Clean unused fields from struct rq

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]

Date:	Wed, 18 Mar 2009 00:23:27 +0000
From:	Luis Henriques <henrix@...o.pt>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
	Gregory Haskins <ghaskins@...ell.com>
Subject: Re: [PATCH 1/2 -tip] sched: Clean unused fields from struct rq

On Wed, Mar 18, 2009 at 01:09:29AM +0100, Peter Zijlstra wrote:
> On Wed, 2009-03-18 at 00:03 +0000, Luis Henriques wrote:
> > Since they are used on in statistics and are always set to zero, the following
> > frields from struct rq have been removed: yld_exp_empty, yld_act_empty and
> > yld_both_empty.
> > 
> > Signed-off-by: Luis Henriques <henrix@...o.pt>
> > ---
> 
> > +++ b/kernel/sched_stats.h
> > @@ -26,9 +26,8 @@ static int show_schedstat(struct seq_file *seq, void *v)
> >  
> >  		/* runqueue-specific stats */
> >  		seq_printf(seq,
> > -		    "cpu%d %u %u %u %u %u %u %u %u %u %llu %llu %lu",
> > -		    cpu, rq->yld_both_empty,
> > -		    rq->yld_act_empty, rq->yld_exp_empty, rq->yld_count,
> > +		    "cpu%d %u %u %u %u %u %u %llu %llu %lu",
> > +		    cpu, rq->yld_count,
> >  		    rq->sched_switch, rq->sched_count, rq->sched_goidle,
> >  		    rq->ttwu_count, rq->ttwu_local,
> >  		    rq->rq_cpu_time,
> 
> I think this bit is ABI, so you either have to bump the version number
> or emit 0s, iirc gregory touched some of that last -- or at least wrote
> userspace for it..

Hmm... you're right.  I should have though about that.  Anyway, what is the
the best approach here?

I know that changes in ABI shall not break anything, but just increasing the
version number will really solve the issue?  Will userspace care for this?
On the other hand, just writting 0s does not sound interesting either...

-- 
Luis Henriques
--
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/