From: Steven Rostedt <rostedt@goodmis.org>
To: Dave Hansen <dave.hansen@intel.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: linux-next: Tree for Oct 5 (warnings: a. trace; b. mm/migrate)
Date: Wed, 6 Oct 2021 10:56:21 -0400 [thread overview]
Message-ID: <20211006105621.7219404f@gandalf.local.home> (raw)
In-Reply-To: <2216e7c0-093b-3d90-ae1c-91902147fe05@intel.com>
On Wed, 6 Oct 2021 07:52:07 -0700
Dave Hansen <dave.hansen@intel.com> wrote:
> On 10/5/21 1:46 PM, Randy Dunlap wrote:
> > On 10/5/21 1:06 AM, Stephen Rothwell wrote:
> >> Hi all,
> >>
> >> Changes since 20211001:
> >
> > on x86_64:
> ...
> > b. randconfig: KCONFIG_SEED=0xFD1CE406
> >
> > ../mm/migrate.c:3216:22: error: 'migrate_on_reclaim_callback' defined
> > but not used [-Werror=unused-function]
> > static int __meminit migrate_on_reclaim_callback(struct notifier_block
> > *self,
> > ^~~~~~~~~~~~~~~~~~~~~~~~~~~
> > ../mm/migrate.c:3197:13: error: 'set_migration_target_nodes' defined but
> > not used [-Werror=unused-function]
> > static void set_migration_target_nodes(void)
> > ^~~~~~~~~~~~~~~~~~~~~~~~~~
> >
> >
> > (example usage to get the randconfig files:
> > KCONFIG_SEED=0xBFBEA13C make [ARCH=x86_64] randconfig
> > )
>
> Hi Randy,
>
> I'm having a heck of a time reproducing this one. Any chance you could
> share an exact sha1 for the tree where you're hitting this, and maybe
> even the actual .config (just in case the KCONFIG_SEED isn't working
> somehow).
>
> I've tried a few linux-next trees as well as the mmotm, mmots and
> mainline with the culprit patch applied. No luck reproducing this so far.
also, just sending the .config that broke would be much better than
supplying the seed you used to make it. I'm assuming if we don't use the
exact kernel image, with different configs available between versions, the
seed will produce different results.
Not to mention, I'll spend the time to look at a .config and less likely to
spend the time trying to figure out how to create that config.
-- Steve
next prev parent reply other threads:[~2021-10-06 14:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211005190628.1f26b13d@canb.auug.org.au>
2021-10-05 20:46 ` Randy Dunlap
2021-10-06 14:52 ` Dave Hansen
2021-10-06 14:56 ` Steven Rostedt [this message]
2021-10-06 16:39 ` Randy Dunlap
2021-10-06 18:16 ` Dave Hansen
2021-10-06 16:33 ` Randy Dunlap
2021-10-06 21:22 ` Steven Rostedt
2021-10-06 21:32 ` Randy Dunlap
2021-10-06 22:06 ` Steven Rostedt
2021-10-07 1:10 ` Steven Rostedt
2021-10-07 3:13 ` Randy Dunlap
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=20211006105621.7219404f@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox