linux-kernel - Re: [PATCH 18/46] kernel: Mark functions as static in sched/fair.c

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 for Android: free password hash cracker in your pocket

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

Date:	Thu, 27 Feb 2014 20:24:35 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Josh Triplett <josh@...htriplett.org>
Cc:	Rashika Kheria <rashika.kheria@...il.com>,
	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...hat.com>
Subject: Re: [PATCH 18/46] kernel: Mark functions as static in sched/fair.c

On Thu, Feb 27, 2014 at 08:03:22AM -0800, Josh Triplett wrote:
> On Thu, Feb 27, 2014 at 12:58:05PM +0100, Peter Zijlstra wrote:
> > On Thu, Feb 27, 2014 at 05:20:19PM +0530, Rashika Kheria wrote:
> > > @@ -5266,7 +5266,7 @@ static unsigned long default_scale_smt_power(struct sched_domain *sd, int cpu)
> > >  	return smt_gain;
> > >  }
> > >  
> > > -unsigned long __weak arch_scale_smt_power(struct sched_domain *sd, int cpu)
> > > +static unsigned long arch_scale_smt_power(struct sched_domain *sd, int cpu)
> > >  {
> > >  	return default_scale_smt_power(sd, cpu);
> > >  }
> > 
> > Fuck no; please think before sending.
> > 
> > I'm going to ignore all patches from you henceforth.
> 
> Did you perhaps check, and notice that there are *zero* uses of this
> function in the kernel?  Nothing overrides this weak symbol; it is no
> longer needed.  You removed the one and only user in your commit:

I know that; but you don't get to remove interfaces under the guise of a
static checker and without mention of such in the changelog.

You should bloody well know better.
--
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/