linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: broonie@kernel.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	linux-next@vger.kernel.org, mhocko@suse.cz,
	mm-commits@vger.kernel.org, sfr@canb.auug.org.au
Subject: Re: mmotm 2021-05-10-21-46 uploaded (mm/*)
Date: Tue, 11 May 2021 15:22:36 -0700	[thread overview]
Message-ID: <ae5036c0-efb7-32c3-1bad-d399f2d80f77@infradead.org> (raw)
In-Reply-To: <20210511134705.ef543a2ff6022f1ad0154a30@linux-foundation.org>

[-- Attachment #1: Type: text/plain, Size: 1563 bytes --]

On 5/11/21 1:47 PM, Andrew Morton wrote:
> On Tue, 11 May 2021 12:39:00 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
> 
>> Lots of various mm/ build errors:
> 
> Huh, It Worked For Me (tm).   Can you please share the .config?
> 

configs (plural). All of them are randconfigs. All on x86_64.


mm/slab_common.c:754:8: error: array index in initializer exceeds array bounds
config-r9247

../include/linux/hugetlb.h:340:30: error: parameter 6 (‘mode’) has incomplete type
../include/linux/hugetlb.h:335:19: error: function declaration isn’t a prototype [-Werror=strict-prototypes]
config-r9251

../include/linux/kernel.h:53:43: error: dereferencing pointer to incomplete type ‘struct module’
../include/linux/build_bug.h:78:41: error: static assertion failed: "sizeof(typeof_member(struct module, build_id)) == 20"
config-r9253


../include/linux/compiler_types.h:328:38: error: call to ‘__compiletime_assert_253’ declared with attribute error: BUILD_BUG_ON failed: sizeof(struct page) > 80
config-r9254


The randconfig files are attached.

I have been wondering lately if I could just tell you/other people the
randconfig SEED that was used and then you/other people could just use
that SEED to reproduce the randconfig file(s).
Are rand() and srand() stable across GCC versions and h/w platforms?

config-r9247:KCONFIG_SEED=0x7ABE8042
config-r9251:KCONFIG_SEED=0x67B989AA
config-r9253:KCONFIG_SEED=0x7B3D63BE
config-r9254:KCONFIG_SEED=0x331557C5


Usage:
KCONFIG_SEED=0x331557C5 make [ARCH=x86_64] [O=builddir] randconfig

thanks.
-- 
~Randy


[-- Attachment #2: config-r9254.gz --]
[-- Type: application/gzip, Size: 46636 bytes --]

[-- Attachment #3: config-r9253.gz --]
[-- Type: application/gzip, Size: 25606 bytes --]

[-- Attachment #4: config-r9251.gz --]
[-- Type: application/gzip, Size: 35679 bytes --]

[-- Attachment #5: config-r9247.gz --]
[-- Type: application/gzip, Size: 45496 bytes --]

      reply	other threads:[~2021-05-11 22:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-11  4:47 mmotm 2021-05-10-21-46 uploaded akpm
2021-05-11 19:39 ` mmotm 2021-05-10-21-46 uploaded (mm/*) Randy Dunlap
2021-05-11 20:47   ` Andrew Morton
2021-05-11 22:22     ` Randy Dunlap [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=ae5036c0-efb7-32c3-1bad-d399f2d80f77@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mhocko@suse.cz \
    --cc=mm-commits@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --subject='Re: mmotm 2021-05-10-21-46 uploaded (mm/*)' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).