From: Andrew Morton <akpm@linux-foundation.org>
To: kbuild-all@lists.01.org
Subject: Re: [lkp] [+4218 bytes kernel size regression] [i386-tinyconfig] [865e23483f] linux-next
Date: Wed, 22 Jul 2020 19:43:39 -0700 [thread overview]
Message-ID: <20200722194339.a8092cdadeb60e3d0bf4202f@linux-foundation.org> (raw)
In-Reply-To: <20200722141129.GA292505@cmpxchg.org>
[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]
On Wed, 22 Jul 2020 10:11:29 -0400 Johannes Weiner <hannes@cmpxchg.org> wrote:
> On Wed, Jul 22, 2020 at 03:48:32PM +0800, kernel test robot wrote:
> >
> > FYI, we noticed a +4218 bytes kernel size regression due to commit:
> >
> > commit: 865e23483ff94043ca26eba00422fe2b245d3dfc (linux-next)
> > https://github.com/hnaz/linux-mm master
> >
> > Details as below (size data is obtained by `nm --size-sort vmlinux`):
> >
> > d517b0be: ipc/shm.c: Remove the superfluous break
> > 865e2348: linux-next
>
> This commit in this tree is a snapshot of the entire linux-next patch
> stack. Bisecting and flagging that particular commit to this
> particular CC list is probably not useful.
>
> Andrew would know best, but to analyze/bisect the MM tree for
> regressions, it'd probably be best to only do the individual commits
> between the `origin' (the Linus base) and `linux-next' commits.
>
The same regression should be present in Stephen's linux-next tree, so
bisect that?
prev parent reply other threads:[~2020-07-23 2:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 7:48 [lkp] [+4218 bytes kernel size regression] [i386-tinyconfig] [865e23483f] linux-next kernel test robot
2020-07-22 14:11 ` Johannes Weiner
2020-07-23 2:43 ` Andrew Morton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200722194339.a8092cdadeb60e3d0bf4202f@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=kbuild-all@lists.01.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.