Messages in this thread | | | Subject | Re: linux-next: Tree for Oct 5 (warnings: a. trace; b. mm/migrate) | From | Randy Dunlap <> | Date | Wed, 6 Oct 2021 09:39:44 -0700 |
| |
On 10/6/21 7:56 AM, Steven Rostedt wrote: > 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.
OK, so a failed experiment. :(
The failing randconfig file is attached (for a. trace).
thanks. -- ~Randy [unhandled content-type:application/gzip] | |