On Fri, Apr 17, 2020 at 11:05:30AM +0800, Rong Chen wrote:
On 4/17/20 11:03 AM, Paul E. McKenney wrote:
> On Fri, Apr 17, 2020 at 10:49:49AM +0800, kbuild test robot wrote:
> > FYI, we noticed a +83 bytes kernel size regression due to commit:
> >
> > commit: 97192c6c046907e58e6cdb958d0c3d7e5d7c289d (sched/core: Add function to
sample state of locked-down task)
> >
https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
dev.2020.04.13b
> >
> > Details as below (size data is obtained by `nm --size-sort vmlinux`):
> >
> > d9899f93: MAINTAINERS: Update maintainers for new Documentaion/litmus-tests/
> > 97192c6c: sched/core: Add function to sample state of locked-down task
> >
> > +-------------------------------------+----------+----------+-------+
> > | symbol | d9899f93 | 97192c6c | delta |
> > +-------------------------------------+----------+----------+-------+
> > | bzImage | 439232 | 439392 | 160 |
> > | nm.T.try_invoke_on_locked_down_task | 0 | 83 | 83 |
> > +-------------------------------------+----------+----------+-------+
> Given that this commit does nothing but update MAINTAINERS, I have to
> assume that this is a false positive. ;-)
>
> Thanx, Paul
> _______________________________________________
Hi Paul,
The first bad commit is "97192c6c: sched/core: Add function to sample state
of locked-down task",
the 'update MAINTAINERS' commit is the parent.
Ah, got it! This is expected behavior, given that I really did add
a function.
Thanx, Paul