All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 5.15
Date: Sun, 31 Oct 2021 17:23:46 -0700	[thread overview]
Message-ID: <20211101002346.GA304515@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wjfbfQobW2jygMvgfJXKmzZNB=UTzBrFs2vTEzVpBXA4Q@mail.gmail.com>

On Sun, Oct 31, 2021 at 02:09:07PM -0700, Linus Torvalds wrote:
> It's been calm, and I have no excuse to add an extra rc, so here we
> are, with v5.15 pushed out, and the merge window starting tomorrow.
> 
> Which is going to be a bit inconvenient for me, since I also have some
> conference travel coming up. But it's only a couple of days and I'll
> have my laptop with me. Sometimes the release timing works out, and
> sometimes it doesn't..
> 
> Anyway, the last week of 5.15 was mainly networking and gpu fixes,
> with some random sprinkling of other things (a few btrfs reverts, some
> kvm updates, minor other fixes here and there - a few architecture
> fixes, couple of tracing, small driver fixes etc). Full shortlog
> appended.
> 
> This release may have started out with some -Werror pain, but it
> calmed down fairly quickly and on the whole 5.15 was fair small and
> calm. Let's hope for more of the same - without Werror issues this
> time - for the upcoming merge window.
> 

Here are my test results:

Build results:
	total: 154 pass: 153 fail: 1
Failed builds:
	m68k:allmodconfig
Qemu test results:
	total: 480 pass: 480 fail: 0

The build error is:

Building m68k:allmodconfig ... failed
--------------
Error log:
In file included from include/linux/string.h:20,
                 from include/linux/bitmap.h:10,
                 from include/linux/cpumask.h:12,
                 from include/linux/smp.h:13,
                 from include/linux/lockdep.h:14,
                 from include/linux/spinlock.h:63,
                 from include/linux/mmzone.h:8,
                 from include/linux/gfp.h:6,
                 from include/linux/slab.h:15,
                 from drivers/nvme/target/discovery.c:7:
In function 'memcpy_and_pad',
    inlined from 'nvmet_execute_disc_identify' at drivers/nvme/target/discovery.c:268:2:
arch/m68k/include/asm/string.h:72:25: error: '__builtin_memcpy' reading 8 bytes from a region of size 7

Another instance of the same problem:

In function 'memcpy_and_pad',
    inlined from 'nvmet_execute_identify_ctrl' at drivers/nvme/target/admin-cmd.c:372:2:
arch/m68k/include/asm/string.h:72:25: error: '__builtin_memcpy' reading 8 bytes from a region of size 7

This is seen with gcc 11.1 and 11.2. gcc 10.3 builds fine.
The code in question is

        memcpy_and_pad(id->fr, sizeof(id->fr),
                       UTS_RELEASE, strlen(UTS_RELEASE), ' ');

and UTS_RELEASE is "5.15.0". I have no idea what might be wrong with the code.
Does anyone have an idea ? Do I need to revert to gcc 10.3 for m68k ?

Thanks,
Guenter

  reply	other threads:[~2021-11-01  0:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-31 21:09 Linux 5.15 Linus Torvalds
2021-11-01  0:23 ` Guenter Roeck [this message]
2021-11-01  8:13   ` Geert Uytterhoeven
2021-11-02  1:17     ` Guenter Roeck
2021-11-02  1:44       ` Linus Torvalds
2021-11-02  3:19         ` Guenter Roeck
2021-11-01  4:49 ` Thorsten is tracking regression again and could need a little help (was: Re: Linux 5.15) Thorsten Leemhuis
2021-11-01 11:46   ` Idzibear
2021-11-01 11:56     ` Greg KH
2021-11-01 12:54     ` Thorsten Leemhuis
2021-11-01 12:33   ` Greg KH
2021-11-01 12:44     ` Thorsten Leemhuis
2021-11-01 13:03       ` Greg KH
2021-11-01 13:34         ` Thorsten Leemhuis
2021-11-01 15:27           ` Greg KH
2021-11-01 16:19             ` Thorsten Leemhuis
2021-11-01 15:07 ` Linux 5.15 Andy Shevchenko
2021-11-01 16:19   ` Lee Jones
2021-11-01 17:25 ` Sudip Mukherjee

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=20211101002346.GA304515@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.