linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Linux 6.0-rc1
@ 2022-08-14 23:41 Linus Torvalds
  2022-08-15  1:23 ` Kirill A. Shutemov
                   ` (3 more replies)
  0 siblings, 4 replies; 8+ messages in thread
From: Linus Torvalds @ 2022-08-14 23:41 UTC (permalink / raw)
  To: Linux Kernel Mailing List

So here we are, two weeks later, and the merge window has closed.

People are chasing down one active bug, and I'm sure there are others
hiding that just need more people to do testing, but that's kind of
the point of rc1: all the big changes have been merged, and now we
need to calm it down and chase down any problems.

Despite the major number change, there's nothing fundamentally
different about this release - I've long eschewed the notion that
major numbers are meaningful, and the only reason for a "hierarchical"
numbering system is to make the numbers easier to remember and
distinguish. Which is why when the minor number gets to around 20 I
prefer to just increment the major number instead and reset to
something smaller.

"Nothing fundamentally different about this release" obviously doesn't
mean there aren't lots of changes, though. There's about 13.5k
non-merge commits in here (and 800+ merges), so 6.0 looks to be
another fairly sizable release.

I actually was hoping that we'd get some of the first rust
infrastructure, and the multi-gen LRU VM, but neither of them happened
this time around. There's always more releases. But there's a lot of
continued development pretty much all over the place, with the
"shortlog" being much too long to post and thus - as always for rc1
notices - below only contains my "merge log". You can definitely get a
kind of high-level overview by just scanning that, but obviously it's
worth once again pointing out that the people mentioned in the merge
log are just the maintainers I pull from, and there's more than 1700
developers involved when you start looking at the full details in the
git tree.

And, once again, this is one of those releases where you should not
look at the diffstat too closely, because more than half of it is yet
another AMD GPU register dump. And the Habanalabs Gaudi2 people want
to play in that space too, but they don't reach quite the same lofty
results that the AMD GPU people  have become so famous for. I'm sure
it's just a matter of time.

The CPU people also show up in the JSON files that describe the perf
events, but they look absolutely tiny compared to the 'asic_reg'
auto-generated GPU and AI hardware definitions.

So just avert your eyes from those parts if you decide that you
actually want to look at the diffs themselves. Once you do that, the
stats look pretty normal, with roughly 60% driver updates (all over,
but gpu, networking and sound are the big updates - again, that's
pretty much par for the course). The rest is a mix of arch updates,
filesystems, tooling, and just random changes all over.

In all its glory (so all those AMD GPU hardware definitions etc included), it's

 13099 files changed, 1280295 insertions(+), 341210 deletions(-)

just because I was curious and looked.

Oh, and after I had already decided to call this kernel 6.0, a few
Chinese developers piped up and pointed out that "5.20" is a more
wholesome version of the Western "4.20" internet-famous number. So if
you want to call this "Linux 5.20", go right ahead. Because the kernel
version  numbers really are entirely made up and have no intrinsic
meaning.

But whatever you call it, please help test this, so that we can get it
all in shape for the final release (hopefully early October).

                 Linus

---

Al Viro (9):
    vfs namei updates
    vfs lseek updates
    vfs dcache updates
    vfs iov_iter updates
    copy_to_iter_mc fix
    9p iov_iter fix
    more iov_iter updates
    /proc/mounts fix
    vfs lseek fix

Alex Williamson (2):
    VFIO updates
    another VFIO update

Alexander Gordeev (1):
    s390 updates

Alexandre Belloni (1):
    RTC updates

Andreas Gruenbacher (1):
    gfs2 updates

Andrew Morton (3):
    MM updates
    misc updates
    remaining MM updates

Ard Biesheuvel (2):
    EFI updates
    efivars sysfs interface removal

Arnaldo Carvalho de Melo (2):
    perf tools updates
    more perf tool updates

Arnd Bergmann (8):
    ARM SoC updates
    ARM SoC drivers
    ARM DT updates
    ARM SoC defconfig updates
    ARM new SoC support
    ARM boardfile deprecation
    more ARM SoC updates
    asm-generic updates

Bartosz Golaszewski (1):
    gpio updates

Bjorn Andersson (4):
    hwspinlock updates
    rpmsg updates
    remoteproc updates
    rpmsg fixes

Bjorn Helgaas (1):
    pci updates

Borislav Petkov (11):
    RAS update
    x86 vmware cleanup
    x86 cleanup
    x86 mm updates
    x86 fpu update
    x86 cpu updates
    misc x86 updates
    x86 core updates
    x86 build updates
    x86 kdump updates
    x86 eIBRS fixes

Casey Schaufler (1):
    msack updates

Christian Brauner (3):
    fs idmapping updates
    acl updates
    setgid updates

Christoph Hellwig (1):
    dma-mapping updates

Chuck Lever (1):
    nfsd updates

Damien Le Moal (2):
    zonefs update
    ATA updates

Dan Williams (1):
    cxl updates

Darrick Wong (4):
    iomap updates
    xfs updates
    more iomap updates
    more xfs updates

Dave Airlie (2):
    drm updates
    drm fixes

Dave Hansen (1):
    x86 SGX updates

David Howells (2):
    AFS fixes
    fscache updates

David Sterba (2):
    btrfs updates
    affs fix

David Teigland (1):
    dlm updates

Dmitry Torokhov (1):
    input updates

Dominique Martinet (1):
    9p updates

Eric Biggers (1):
    fsverity update

Gao Xiang (1):
    erofs updates

Geert Uytterhoeven (1):
    m68k updates

Greg KH (6):
    char / misc driver updates
    driver core / kernfs updates
    USB / Thunderbolt updates
    staging driver updates
    SPDX updates
    tty / serial driver updates

Greg Ungerer (1):
    m68knommu fixes

Guenter Roeck (2):
    hwmon updates
    hwmon fixes

Guo Ren (1):
    csky updates

Gustavo Silva (1):
    uapi flexible array update

Hans de Goede (1):
    x86 platform driver updates

Hans-Christian Noren Egtvedt (1):
    AVR32 updates

Helge Deller (2):
    parisc updates
    fbdev updates

Herbert Xu (1):
    crypto updates

Huacai Chen (1):
    LoongArch updates

Ilya Dryomov (1):
    ceph updates

Ingo Molnar (8):
    scheduler updates
    locking updates
    perf events updates
    perf fixes
    scheduler fixes
    x86 fixes
    x86 fix
    timer fixes

Jaegeuk Kim (1):
    f2fs updates

Jakub Kicinski (1):
    networking fixes

James Bottomley (2):
    SCSI updates
    more SCSI updates

Jan Kara (2):
    ext2 and reiserfs updates
    fsnotify updates

Jarkko Sakkinen (1):
    tpm updates

Jason Donenfeld (1):
    random number generator updates

Jason Gunthorpe (1):
    rdma updates

Jassi Brar (1):
    mailbox updates

Jeff Layton (1):
    file locking updates

Jens Axboe (7):
    io_uring updates
    io_uring buffered writes support
    io_uring zerocopy support
    block updates
    block driver updates
    io_uring fixes
    block fixes

Jiri Kosina (1):
    HID updates

Joerg Roedel (1):
    iommu updates

John Johansen (1):
    AppArmor updates

Jon Mason (1):
    NTB updates

Jonathan Corbet (1):
    documentation updates

Juergen Gross (2):
    xen updates
    more xen updates

Julia Lawall (1):
    coccinelle semantic patch updates

Kees Cook (4):
    pstore updates
    seccomp update
    execve updates
    hardening updates

Lee Jones (2):
    MFD updates
    backlight updates

Len Brown (1):
    turbostat updates

Linus Walleij (1):
    pin control updates

Luis Chamberlain (2):
    module updates
    sysctl updates

Mark Brown (3):
    regmap updates
    regulator updates
    spi updates

Masahiro Yamada (1):
    Kbuild updates

Matthew Wilcox (2):
    XArray/IDR updates
    folio updates

Mauro Carvalho Chehab (1):
    media updates

Max Filippov (1):
    xtensa updates

Micah Morton (1):
    SafeSetID updates

Michael Ellerman (2):
    powerpc updates
    powerpc fixes

Michael Tsirkin (1):
    virtio updates

Michal Simek (1):
    microblaze updates

Mike Rapoport (1):
    memblock updates

Mike Snitzer (3):
    device mapper updates
    more device mapper updates
    device mapper fixes

Miklos Szeredi (2):
    overlayfs update
    fuse updates

Mimi Zohar (1):
    integrity updates

Namjae Jeon (1):
    exfat updates

Palmer Dabbelt (2):
    RISC-V updates
    more RISC-V updates

Paolo Abeni (1):
    networking changes

Paolo Bonzini (2):
    kvm updates
    more kvm updates

Paul McKenney (2):
    RCU updates
    nolibc updates

Paul Moore (3):
    selinux updates
    audit updates
    LSM update

Pavel Machek (1):
    LED updates

Petr Mladek (2):
    printk updates
    livepatching update

Rafael Wysocki (6):
    ACPI updates
    power management updates
    thermal control updates
    more thermal control updates
    more power management updates
    more ACPI updates

Richard Weinberger (2):
    UML updates
    MTD updates

Rob Herring (2):
    devicetree updates
    devicetree fixes

Russell King (1):
    ARM updates

Sebastian Reichel (1):
    power supply and reset updates

Shuah Khan (2):
    KUnit updates
    Kselftest updates

Stafford Horne (1):
    OpenRISC updates

Stephen Boyd (1):
    clk updates

Steve French (3):
    cifs updates
    ksmbd updates
    more cifs updates

Steven Rostedt (2):
    real time analysis tool (rtla) updates
    tracing updates

Takashi Iwai (2):
    sound updates
    sound fixes

Ted Ts'o (1):
    ext4 updates

Tejun Heo (1):
    cgroup updates

Thierry Reding (1):
    pwm updates

Thomas Bogendoerfer (1):
    MIPS updates

Thomas Gleixner (2):
    timer updates
    irq updates

Trond Myklebust (1):
    NFS client updates

Tzung-Bi Shih (1):
    chrome platform updates

Ulf Hansson (1):
    MMC updates

Vinod Koul (1):
    dmaengine updates

Vlastimil Babka (1):
    slab updates

Wei Liu (1):
    hyperv updates

Will Deacon (1):
    arm64 updates

Wim Van Sebroeck (1):
    watchdog updates

Wolfram Sang (2):
    i2c updates
    more i2c updates

Yury Norov (1):
    bitmap updates

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Linux 6.0-rc1
  2022-08-14 23:41 Linux 6.0-rc1 Linus Torvalds
@ 2022-08-15  1:23 ` Kirill A. Shutemov
  2022-08-15  2:27   ` Steven Rostedt
  2022-08-15  2:50 ` linux-next: stats (Was: Linux 6.0-rc1) Stephen Rothwell
                   ` (2 subsequent siblings)
  3 siblings, 1 reply; 8+ messages in thread
From: Kirill A. Shutemov @ 2022-08-15  1:23 UTC (permalink / raw)
  To: Linus Torvalds, Song Liu, Daniel Borkmann, Steven Rostedt
  Cc: Linux Kernel Mailing List

53cd885bc5c3 ("ftrace: Allow IPMODIFY and DIRECT ops on the same
function") breaks build for me (CONFIG_MODULE=n):

  CC      kernel/trace/ftrace.o
kernel/trace/ftrace.c:3149:1: error: ‘ops_references_rec’ defined but not used [-Werror=unused-function]
 3149 | ops_references_rec(struct ftrace_ops *ops, struct dyn_ftrace *rec)
      | ^~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors

The fix I used locally:

diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c
index bc921a3f7ea8..90fa3ceeaeeb 100644
--- a/kernel/trace/ftrace.c
+++ b/kernel/trace/ftrace.c
@@ -3138,19 +3138,6 @@ ops_references_ip(struct ftrace_ops *ops, unsigned long ip)
 	return true;
 }

-/*
- * Check if the current ops references the record.
- *
- * If the ops traces all functions, then it was already accounted for.
- * If the ops does not trace the current record function, skip it.
- * If the ops ignores the function via notrace filter, skip it.
- */
-static bool
-ops_references_rec(struct ftrace_ops *ops, struct dyn_ftrace *rec)
-{
-	return ops_references_ip(ops, rec->ip);
-}
-
 static int ftrace_update_code(struct module *mod, struct ftrace_page *new_pgs)
 {
 	bool init_nop = ftrace_need_init_nop();
@@ -6818,6 +6805,19 @@ static int ftrace_get_trampoline_kallsym(unsigned int symnum,

 static LIST_HEAD(ftrace_mod_maps);

+/*
+ * Check if the current ops references the record.
+ *
+ * If the ops traces all functions, then it was already accounted for.
+ * If the ops does not trace the current record function, skip it.
+ * If the ops ignores the function via notrace filter, skip it.
+ */
+static bool
+ops_references_rec(struct ftrace_ops *ops, struct dyn_ftrace *rec)
+{
+	return ops_references_ip(ops, rec->ip);
+}
+
 static int referenced_filters(struct dyn_ftrace *rec)
 {
 	struct ftrace_ops *ops;
-- 
  Kiryl Shutsemau / Kirill A. Shutemov

^ permalink raw reply related	[flat|nested] 8+ messages in thread

* Re: Linux 6.0-rc1
  2022-08-15  1:23 ` Kirill A. Shutemov
@ 2022-08-15  2:27   ` Steven Rostedt
  0 siblings, 0 replies; 8+ messages in thread
From: Steven Rostedt @ 2022-08-15  2:27 UTC (permalink / raw)
  To: Kirill A. Shutemov
  Cc: Linus Torvalds, Song Liu, Daniel Borkmann, Linux Kernel Mailing List

On Mon, 15 Aug 2022 04:23:00 +0300
"Kirill A. Shutemov" <kirill@shutemov.name> wrote:

> 53cd885bc5c3 ("ftrace: Allow IPMODIFY and DIRECT ops on the same
> function") breaks build for me (CONFIG_MODULE=n):
> 
>   CC      kernel/trace/ftrace.o
> kernel/trace/ftrace.c:3149:1: error: ‘ops_references_rec’ defined but not used [-Werror=unused-function]
>  3149 | ops_references_rec(struct ftrace_ops *ops, struct dyn_ftrace *rec)
>       | ^~~~~~~~~~~~~~~~~~
> cc1: all warnings being treated as errors
> 
> The fix I used locally:
> 

This was submitted back here:

   https://lore.kernel.org/all/20220801084745.1187987-1-wangjingjin1@huawei.com/

But the broken change went through the BPF tree, so I can't fix it.

-- Steve

> diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c
> index bc921a3f7ea8..90fa3ceeaeeb 100644
> --- a/kernel/trace/ftrace.c
> +++ b/kernel/trace/ftrace.c
> @@ -3138,19 +3138,6 @@ ops_references_ip(struct ftrace_ops *ops, unsigned long ip)
>  	return true;
>  }
> 
> -/*
> - * Check if the current ops references the record.
> - *
> - * If the ops traces all functions, then it was already accounted for.
> - * If the ops does not trace the current record function, skip it.
> - * If the ops ignores the function via notrace filter, skip it.
> - */
> -static bool
> -ops_references_rec(struct ftrace_ops *ops, struct dyn_ftrace *rec)
> -{
> -	return ops_references_ip(ops, rec->ip);
> -}
> -
>  static int ftrace_update_code(struct module *mod, struct ftrace_page *new_pgs)
>  {
>  	bool init_nop = ftrace_need_init_nop();
> @@ -6818,6 +6805,19 @@ static int ftrace_get_trampoline_kallsym(unsigned int symnum,
> 
>  static LIST_HEAD(ftrace_mod_maps);
> 
> +/*
> + * Check if the current ops references the record.
> + *
> + * If the ops traces all functions, then it was already accounted for.
> + * If the ops does not trace the current record function, skip it.
> + * If the ops ignores the function via notrace filter, skip it.
> + */
> +static bool
> +ops_references_rec(struct ftrace_ops *ops, struct dyn_ftrace *rec)
> +{
> +	return ops_references_ip(ops, rec->ip);
> +}
> +
>  static int referenced_filters(struct dyn_ftrace *rec)
>  {
>  	struct ftrace_ops *ops;


^ permalink raw reply	[flat|nested] 8+ messages in thread

* linux-next: stats (Was: Linux 6.0-rc1)
  2022-08-14 23:41 Linux 6.0-rc1 Linus Torvalds
  2022-08-15  1:23 ` Kirill A. Shutemov
@ 2022-08-15  2:50 ` Stephen Rothwell
  2022-08-17 14:41   ` Geert Uytterhoeven
  2022-08-15 18:04 ` Build regressions/improvements in v6.0-rc1 Geert Uytterhoeven
  2022-08-15 23:48 ` Linux 6.0-rc1 Guenter Roeck
  3 siblings, 1 reply; 8+ messages in thread
From: Stephen Rothwell @ 2022-08-15  2:50 UTC (permalink / raw)
  To: Linus Torvalds; +Cc: Linux Kernel Mailing List, Linux Next Mailing List

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

Hi all,

As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)

(No merge commits counted, next-20220802 was the first linux-next after
the merge window opened.)

Commits in v6.0-rc1 (relative to v5.19):           13543
Commits in next-20220802:                          13109
Commits with the same SHA1:                        12468
Commits with the same patch_id:                      309 (1)
Commits with the same subject line:                   12 (1)

(1) not counting those in the lines above.

So commits in -rc1 that were in next-20220802:     12789 94%

Some breakdown of the list of extra commits (relative to next-20220802)
in -rc1:

Top ten first word of commit summary:

     95 perf
     33 dt-bindings
     30 tools
     25 net
     24 kvm
     23 virtio_ring
     19 riscv
     19 cxl
     19 ceph
     18 bpf

Top ten authors:

     43 xuanzhuo@linux.alibaba.com
     25 irogers@google.com
     17 krzysztof.kozlowski@linaro.org
     15 conor.dooley@microchip.com
     14 leo.yan@linaro.org
     13 xiubli@redhat.com
     13 dan.j.williams@intel.com
     11 zhengjun.xing@linux.intel.com
     11 namhyung@kernel.org
     10 snitzer@kernel.org

Top ten commiters:

    107 acme@redhat.com
     78 mst@redhat.com
     58 kuba@kernel.org
     43 palmer@rivosinc.com
     26 pbonzini@redhat.com
     24 idryomov@gmail.com
     20 dan.j.williams@intel.com
     18 ast@kernel.org
     17 tiwai@suse.de
     17 len.brown@intel.com

There are also 320 commits in next-20220802 that didn't make it into
v6.0-rc1.

Top ten first word of commit summary:

     29 tools
     27 thermal
     22 arm
     20 mm
     20 fs
     15 arm64
     14 soc
     13 dt-bindings
     10 rust
      9 btrfs

Top ten authors:

     29 paulmck@kernel.org
     19 ojeda@kernel.org
     18 zokeefe@google.com
     11 marex@denx.de
     10 daniel.lezcano@linexp.org
      8 windhl@126.com
      8 wedsonaf@google.com
      7 iangelak@fb.com
      7 daniel.lezcano@linaro.org
      7 broonie@kernel.org

Top ten commiters:

     43 daniel.lezcano@linaro.org
     32 ojeda@kernel.org
     32 akpm@linux-foundation.org
     29 paulmck@kernel.org
     18 almaz.alexandrovich@paragon-software.com
     13 geert+renesas@glider.be
     12 alexandre.torgue@foss.st.com
     11 broonie@kernel.org
      9 srinivas.kandagatla@linaro.org
      8 treding@nvidia.com

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Build regressions/improvements in v6.0-rc1
  2022-08-14 23:41 Linux 6.0-rc1 Linus Torvalds
  2022-08-15  1:23 ` Kirill A. Shutemov
  2022-08-15  2:50 ` linux-next: stats (Was: Linux 6.0-rc1) Stephen Rothwell
@ 2022-08-15 18:04 ` Geert Uytterhoeven
  2022-08-15 18:10   ` Geert Uytterhoeven
  2022-08-15 23:48 ` Linux 6.0-rc1 Guenter Roeck
  3 siblings, 1 reply; 8+ messages in thread
From: Geert Uytterhoeven @ 2022-08-15 18:04 UTC (permalink / raw)
  To: linux-kernel

Below is the list of build error/warning regressions/improvements in
v6.0-rc1[1] compared to v5.19[2].

Summarized:
  - build errors: +26/-15
  - build warnings: +8/-28

Happy fixing! ;-)

Thanks to the linux-next team for providing the build service.

[1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/568035b01cfb107af8d2e4bd2fb9aea22cf5b868/ (all 135 configs)
[2] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/3d7cb6b04c3f3115719235cc6866b10326de34cd/ (all 135 configs)


*** ERRORS ***

26 error regressions:
  + /kisskb/src/arch/parisc/kernel/vdso32/restart_syscall.S: Error: .cfi_endproc without corresponding .cfi_startproc:  => 32
  + /kisskb/src/arch/parisc/kernel/vdso32/restart_syscall.S: Error: bad or irreducible absolute expression:  => 16
  + /kisskb/src/arch/parisc/kernel/vdso32/restart_syscall.S: Error: junk at end of line, first unrecognized character is `:':  => 16
  + /kisskb/src/arch/parisc/kernel/vdso32/restart_syscall.S: Error: no such instruction: `be 0x100(%sr2,%r0)':  => 29
  + /kisskb/src/arch/parisc/kernel/vdso32/restart_syscall.S: Error: no such instruction: `ldi 0,%r20':  => 30
  + /kisskb/src/arch/parisc/kernel/vdso32/restart_syscall.S: Error: no such instruction: `ldw 0(%sp),%r31':  => 26
  + /kisskb/src/arch/parisc/kernel/vdso32/sigtramp.S: Error: no such instruction: `ble 0x100(%sr2,%r0)':  => 51, 46
  + /kisskb/src/arch/parisc/kernel/vdso32/sigtramp.S: Error: no such instruction: `ldi 0,%r25':  => 44
  + /kisskb/src/arch/parisc/kernel/vdso32/sigtramp.S: Error: no such instruction: `ldi 1,%r25':  => 49
  + /kisskb/src/arch/parisc/kernel/vdso32/sigtramp.S: Error: no such instruction: `ldi 173,%r20':  => 50, 45
  + /kisskb/src/arch/parisc/kernel/vdso32/sigtramp.S: Error: unknown pseudo-op: `.callinfo':  => 40
  + /kisskb/src/arch/parisc/kernel/vdso32/sigtramp.S: Error: unknown pseudo-op: `.entry':  => 41
  + /kisskb/src/arch/parisc/kernel/vdso32/sigtramp.S: Error: unknown pseudo-op: `.exit':  => 54
  + /kisskb/src/arch/parisc/kernel/vdso32/sigtramp.S: Error: unknown pseudo-op: `.proc':  => 39
  + /kisskb/src/arch/parisc/kernel/vdso32/sigtramp.S: Error: unknown pseudo-op: `.procend':  => 55
  + /kisskb/src/arch/parisc/kernel/vdso32/sigtramp.S: Error: unknown pseudo-op: `.stringz':  => 76
  + /kisskb/src/arch/sh/include/asm/io.h: error: cast to pointer from integer of different size [-Werror=int-to-pointer-cast]:  => 239:34
  + /kisskb/src/drivers/gpu/drm/amd/amdgpu/../display/dc/dml/dcn30/display_mode_vba_30.c: error: the frame size of 2096 bytes is larger than 2048 bytes [-Werror=frame-larger-than=]:  => 6806:1
  + /kisskb/src/drivers/gpu/drm/amd/amdgpu/../display/dc/dml/dcn32/display_mode_vba_32.c: error: the frame size of 2160 bytes is larger than 2048 bytes [-Werror=frame-larger-than=]:  => 3778:1
  + /kisskb/src/include/linux/bitfield.h: error: call to '__field_overflow' declared with attribute error: value doesn't fit into mask:  => 151:3
  + /kisskb/src/include/linux/compiler_types.h: error: call to '__compiletime_assert_603' declared with attribute error: FIELD_GET: mask is not constant:  => 354:38
  + /kisskb/src/include/linux/random.h: error: 'latent_entropy' undeclared (first use in this function):  => 25:39
  + /kisskb/src/include/linux/random.h: error: 'latent_entropy' undeclared (first use in this function); did you mean 'add_latent_entropy'?:  => 25:46
  + {standard input}: Error: displacement to undefined symbol .L377 overflows 12-bit field:  => 2286
  + {standard input}: Error: displacement to undefined symbol .L378 overflows 8-bit field :  => 2302
  + {standard input}: Error: displacement to undefined symbol .L382 overflows 8-bit field :  => 2213

15 error improvements:
  - /kisskb/src/arch/um/include/asm/processor-generic.h: error: called object is not a function or function pointer: 103:18 => 
  - /kisskb/src/crypto/blake2b_generic.c: error: the frame size of 2288 bytes is larger than 2048 bytes [-Werror=frame-larger-than=]: 109:1 => 
  - /kisskb/src/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_topology.c: error: control reaches end of non-void function [-Werror=return-type]: 1614:1 => 
  - /kisskb/src/drivers/gpu/drm/r128/r128_cce.c: error: case label does not reduce to an integer constant: 417:2, 418:2 => 
  - /kisskb/src/drivers/infiniband/hw/qib/qib_wc_x86_64.c: error: 'X86_VENDOR_AMD' undeclared (first use in this function): 149:37 => 
  - /kisskb/src/drivers/infiniband/hw/qib/qib_wc_x86_64.c: error: 'struct cpuinfo_um' has no member named 'x86_vendor': 149:22 => 
  - /kisskb/src/drivers/infiniband/hw/qib/qib_wc_x86_64.c: error: control reaches end of non-void function [-Werror=return-type]: 150:1 => 
  - /kisskb/src/drivers/infiniband/sw/rdmavt/qp.c: error: 'struct cpuinfo_um' has no member named 'x86_cache_size': 88:22 => 
  - /kisskb/src/drivers/infiniband/sw/rdmavt/qp.c: error: control reaches end of non-void function [-Werror=return-type]: 89:1 => 
  - /kisskb/src/drivers/infiniband/sw/rdmavt/qp.c: error: implicit declaration of function '__copy_user_nocache' [-Werror=implicit-function-declaration]: 100:2 => 
  - {standard input}: Error: displacement to undefined symbol .L271 overflows 12-bit field: 1625 => 
  - {standard input}: Error: displacement to undefined symbol .L271 overflows 8-bit field : 1634 => 
  - {standard input}: Error: displacement to undefined symbol .L318 overflows 8-bit field : 1711, 1681, 1665, 1693 => 
  - {standard input}: Error: pcrel too far: 1667, 1609, 1698, 1660, 1629, 1670, 1684, 1702, 1635, 1632, 1705, 1657, 1656, 1644, 1695, 1673, 1676, 1686, 1649, 1655, 1700, 1618, 1685, 1672 => 2249, 2206, 2231, 2261, 2293, 2248, 2215, 2262, 2247, 2232, 2216, 2217, 2209, 2204, 2274, 2221, 2229, 2259
  - {standard input}: Error: unknown opcode: 1713 => 


*** WARNINGS ***

8 warning regressions:
  + /kisskb/src/fs/ext4/readpage.c: warning: the frame size of 1132 bytes is larger than 1024 bytes [-Wframe-larger-than=]:  => 407:1
  + /kisskb/src/fs/mpage.c: warning: the frame size of 1092 bytes is larger than 1024 bytes [-Wframe-larger-than=]:  => 308:1
  + /kisskb/src/fs/mpage.c: warning: the frame size of 1144 bytes is larger than 1024 bytes [-Wframe-larger-than=]:  => 634:1
  + modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o: section mismatch in reference: qed_mfw_ext_maps (section: .data) -> qed_mfw_legacy_bb_100g (section: .init.rodata):  => N/A
  + modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o: section mismatch in reference: qed_mfw_legacy_maps (section: .data) -> qed_mfw_legacy_bb_100g (section: .init.rodata):  => N/A
  + modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qede/qede.o: section mismatch in reference: qede_forced_speed_maps (section: .data) -> qede_forced_speed_100000 (section: .init.rodata):  => N/A
  + modpost: WARNING: modpost: vmlinux.o: section mismatch in reference: __trace_event_discard_commit (section: .text.unlikely) -> initcall_level_names (section: .init.data):  => N/A
  + {standard input}: Warning: overflow in branch to .L3; converted into longer instruction sequence:  => 2308

28 warning improvements:
  - /kisskb/src/fs/ext4/readpage.c: warning: the frame size of 1136 bytes is larger than 1024 bytes [-Wframe-larger-than=]: 407:1 => 
  - /kisskb/src/fs/mpage.c: warning: the frame size of 1088 bytes is larger than 1024 bytes [-Wframe-larger-than=]: 303:1 => 
  - /kisskb/src/fs/mpage.c: warning: the frame size of 1148 bytes is larger than 1024 bytes [-Wframe-larger-than=]: 638:1 => 
  - arch/m68k/configs/multi_defconfig: warning: symbol value 'm' invalid for ZPOOL: 61 => 
  - arch/m68k/configs/sun3_defconfig: warning: symbol value 'm' invalid for ZPOOL: 37 => 
  - modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o(.data+0x14410): Section mismatch in reference from the variable qed_mfw_legacy_maps to the variable .init.rodata:qed_mfw_legacy_bb_100g: N/A => 
  - modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o(.data+0x14428): Section mismatch in reference from the variable qed_mfw_legacy_maps to the variable .init.rodata:qed_mfw_legacy_bb_100g: N/A => 
  - modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o(.data+0x14440): Section mismatch in reference from the variable qed_mfw_legacy_maps to the variable .init.rodata:qed_mfw_legacy_bb_100g: N/A => 
  - modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o(.data+0x14458): Section mismatch in reference from the variable qed_mfw_legacy_maps to the variable .init.rodata:qed_mfw_legacy_bb_100g: N/A => 
  - modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o(.data+0x14470): Section mismatch in reference from the variable qed_mfw_legacy_maps to the variable .init.rodata:qed_mfw_legacy_bb_100g: N/A => 
  - modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o(.data+0x14488): Section mismatch in reference from the variable qed_mfw_legacy_maps to the variable .init.rodata:qed_mfw_legacy_bb_100g: N/A => 
  - modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o(.data+0x144a0): Section mismatch in reference from the variable qed_mfw_legacy_maps to the variable .init.rodata:qed_mfw_legacy_bb_100g: N/A => 
  - modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o(.data+0x144f0): Section mismatch in reference from the variable qed_mfw_ext_maps to the variable .init.rodata:qed_mfw_legacy_bb_100g: N/A => 
  - modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o(.data+0x14508): Section mismatch in reference from the variable qed_mfw_ext_maps to the variable .init.rodata:qed_mfw_legacy_bb_100g: N/A => 
  - modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o(.data+0x14520): Section mismatch in reference from the variable qed_mfw_ext_maps to the variable .init.rodata:qed_mfw_legacy_bb_100g: N/A => 
  - modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o(.data+0x14538): Section mismatch in reference from the variable qed_mfw_ext_maps to the variable .init.rodata:qed_mfw_legacy_bb_100g: N/A => 
  - modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o(.data+0x14550): Section mismatch in reference from the variable qed_mfw_ext_maps to the variable .init.rodata:qed_mfw_legacy_bb_100g: N/A => 
  - modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o(.data+0x14568): Section mismatch in reference from the variable qed_mfw_ext_maps to the variable .init.rodata:qed_mfw_legacy_bb_100g: N/A => 
  - modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o(.data+0x14580): Section mismatch in reference from the variable qed_mfw_ext_maps to the variable .init.rodata:qed_mfw_legacy_bb_100g: N/A => 
  - modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o(.data+0x14598): Section mismatch in reference from the variable qed_mfw_ext_maps to the variable .init.rodata:qed_mfw_legacy_bb_100g: N/A => 
  - modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qede/qede.o(.data+0x47b0): Section mismatch in reference from the variable qede_forced_speed_maps to the variable .init.rodata:qede_forced_speed_100000: N/A => 
  - modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qede/qede.o(.data+0x47c8): Section mismatch in reference from the variable qede_forced_speed_maps to the variable .init.rodata:qede_forced_speed_100000: N/A => 
  - modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qede/qede.o(.data+0x47e0): Section mismatch in reference from the variable qede_forced_speed_maps to the variable .init.rodata:qede_forced_speed_100000: N/A => 
  - modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qede/qede.o(.data+0x47f8): Section mismatch in reference from the variable qede_forced_speed_maps to the variable .init.rodata:qede_forced_speed_100000: N/A => 
  - modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qede/qede.o(.data+0x4810): Section mismatch in reference from the variable qede_forced_speed_maps to the variable .init.rodata:qede_forced_speed_100000: N/A => 
  - modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qede/qede.o(.data+0x4828): Section mismatch in reference from the variable qede_forced_speed_maps to the variable .init.rodata:qede_forced_speed_100000: N/A => 
  - modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qede/qede.o(.data+0x4840): Section mismatch in reference from the variable qede_forced_speed_maps to the variable .init.rodata:qede_forced_speed_100000: N/A => 
  - modpost: WARNING: modpost: vmlinux.o(.text.unlikely+0x52bc): Section mismatch in reference from the function __trace_event_discard_commit() to the variable .init.data:initcall_level_names: N/A => 

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Build regressions/improvements in v6.0-rc1
  2022-08-15 18:04 ` Build regressions/improvements in v6.0-rc1 Geert Uytterhoeven
@ 2022-08-15 18:10   ` Geert Uytterhoeven
  0 siblings, 0 replies; 8+ messages in thread
From: Geert Uytterhoeven @ 2022-08-15 18:10 UTC (permalink / raw)
  To: linux-kernel
  Cc: linux-parisc, linux-staging, amd-gfx, dri-devel, linux-wireless,
	netdev, kvmarm, linux-arm-kernel, Jason A. Donenfeld,
	linuxppc-dev, linux-sh

On Mon, 15 Aug 2022, Geert Uytterhoeven wrote:
> Below is the list of build error/warning regressions/improvements in
> v6.0-rc1[1] compared to v5.19[2].
>
> Summarized:
>  - build errors: +26/-15

   + /kisskb/src/arch/parisc/kernel/vdso32/restart_syscall.S: Error: .cfi_endproc without corresponding .cfi_startproc:  => 32
   + /kisskb/src/arch/parisc/kernel/vdso32/restart_syscall.S: Error: bad or irreducible absolute expression:  => 16
   + /kisskb/src/arch/parisc/kernel/vdso32/restart_syscall.S: Error: junk at end of line, first unrecognized character is `:':  => 16
   + /kisskb/src/arch/parisc/kernel/vdso32/restart_syscall.S: Error: no such instruction: `be 0x100(%sr2,%r0)':  => 29
   + /kisskb/src/arch/parisc/kernel/vdso32/restart_syscall.S: Error: no such instruction: `ldi 0,%r20':  => 30
   + /kisskb/src/arch/parisc/kernel/vdso32/restart_syscall.S: Error: no such instruction: `ldw 0(%sp),%r31':  => 26
   + /kisskb/src/arch/parisc/kernel/vdso32/sigtramp.S: Error: no such instruction: `ble 0x100(%sr2,%r0)':  => 51, 46
   + /kisskb/src/arch/parisc/kernel/vdso32/sigtramp.S: Error: no such instruction: `ldi 0,%r25':  => 44
   + /kisskb/src/arch/parisc/kernel/vdso32/sigtramp.S: Error: no such instruction: `ldi 1,%r25':  => 49
   + /kisskb/src/arch/parisc/kernel/vdso32/sigtramp.S: Error: no such instruction: `ldi 173,%r20':  => 50, 45
   + /kisskb/src/arch/parisc/kernel/vdso32/sigtramp.S: Error: unknown pseudo-op: `.callinfo':  => 40
   + /kisskb/src/arch/parisc/kernel/vdso32/sigtramp.S: Error: unknown pseudo-op: `.entry':  => 41
   + /kisskb/src/arch/parisc/kernel/vdso32/sigtramp.S: Error: unknown pseudo-op: `.exit':  => 54
   + /kisskb/src/arch/parisc/kernel/vdso32/sigtramp.S: Error: unknown pseudo-op: `.proc':  => 39
   + /kisskb/src/arch/parisc/kernel/vdso32/sigtramp.S: Error: unknown pseudo-op: `.procend':  => 55
   + /kisskb/src/arch/parisc/kernel/vdso32/sigtramp.S: Error: unknown pseudo-op: `.stringz':  => 76

parisc64-gcc11/generic-64bit_defconfig
parisc-gcc11/generic-32bit_defconfig
parisc-gcc11/parisc-{allmod,allno,def}config

   + /kisskb/src/arch/sh/include/asm/io.h: error: cast to pointer from integer of different size [-Werror=int-to-pointer-cast]:  => 239:34

sh4-gcc11/sh-allmodconfig (drivers/staging/octeon/ethernet-mem.c)

   + /kisskb/src/drivers/gpu/drm/amd/amdgpu/../display/dc/dml/dcn30/display_mode_vba_30.c: error: the frame size of 2096 bytes is larger than 2048 bytes [-Werror=frame-larger-than=]:  => 6806:1
   + /kisskb/src/drivers/gpu/drm/amd/amdgpu/../display/dc/dml/dcn32/display_mode_vba_32.c: error: the frame size of 2160 bytes is larger than 2048 bytes [-Werror=frame-larger-than=]:  => 3778:1

x86_64-gcc8/x86-allmodconfig

   + /kisskb/src/include/linux/bitfield.h: error: call to '__field_overflow' declared with attribute error: value doesn't fit into mask:  => 151:3

mipsel-gcc5/mips-allmodconfig (net/mac80211/tx.c)

   + /kisskb/src/include/linux/compiler_types.h: error: call to '__compiletime_assert_603' declared with attribute error: FIELD_GET: mask is not constant:  => 354:38

arm64-gcc5/arm64-allmodconfig (arch/arm64/kvm/arm.c)

   + /kisskb/src/include/linux/random.h: error: 'latent_entropy' undeclared (first use in this function):  => 25:39

powerpc-gcc5/powerpc-all{mod,yes}config
powerpc-gcc5/ppc32_allmodconfig
powerpc-gcc5/ppc64_book3e_allmodconfig
powerpc-gcc5/ppc64le_allmodconfig

   + /kisskb/src/include/linux/random.h: error: 'latent_entropy' undeclared (first use in this function); did you mean 'add_latent_entropy'?:  => 25:46

powerpc-gcc11/powerpc-all{mod,yes}config
powerpc-gcc11/ppc64_book3e_allmodconfig

   + {standard input}: Error: displacement to undefined symbol .L377 overflows 12-bit field:  => 2286
   + {standard input}: Error: displacement to undefined symbol .L378 overflows 8-bit field :  => 2302
   + {standard input}: Error: displacement to undefined symbol .L382 overflows 8-bit field :  => 2213

sh4-gcc11/sh-allmodconfig (seen before, root cause is internal compiler error)

> [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/568035b01cfb107af8d2e4bd2fb9aea22cf5b868/ (all 135 configs)
> [2] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/3d7cb6b04c3f3115719235cc6866b10326de34cd/ (all 135 configs)

Gr{oetje,eeting}s,

 						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
 							    -- Linus Torvalds

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Linux 6.0-rc1
  2022-08-14 23:41 Linux 6.0-rc1 Linus Torvalds
                   ` (2 preceding siblings ...)
  2022-08-15 18:04 ` Build regressions/improvements in v6.0-rc1 Geert Uytterhoeven
@ 2022-08-15 23:48 ` Guenter Roeck
  3 siblings, 0 replies; 8+ messages in thread
From: Guenter Roeck @ 2022-08-15 23:48 UTC (permalink / raw)
  To: Linus Torvalds; +Cc: Linux Kernel Mailing List

On Sun, Aug 14, 2022 at 04:41:33PM -0700, Linus Torvalds wrote:
> So here we are, two weeks later, and the merge window has closed.
> 
[ ... ]
> 
> But whatever you call it, please help test this, so that we can get it
> all in shape for the final release (hopefully early October).
> 

Build results:
	total: 149 pass: 147 fail: 2
Failed builds:
	powerpc:allmodconfig
	powerpc:ppc32_allmodconfig
Qemu test results:
	total: 483 pass: 458 fail: 25
Failed tests:
	<various arm>

Details below.

Guenter

---
Build:

powerpc:allmodconfig
powerpc:ppc32_allmodconfig

include/linux/random.h: In function 'add_latent_entropy':
include/linux/random.h:25:46: error: 'latent_entropy' undeclared

Caused by commit 36d4b36b6959 ("lib/nodemask: inline next_node_in() and
node_random()"). Fix is at:

https://www.spinics.net/lists/kernel/msg4468633.html

===========
qemu tests:

Crashes:

Various crashes in pl011_probe() due to commit f2d3b9a46e0e ("ARM: 9220/1:
amba: Remove deferred device addition"). The suggested fix is at
https://lore.kernel.org/lkml/20220811190747.797081-1-isaacmanjarres@google.com/T/
and mostly works but exposes or introduces another crash. The suggested fix for
that crash introduces yet another crash. See
https://lore.kernel.org/lkml/20220811195234.GA4018948@roeck-us.net/T/#m2192446c13d46612a00c4d499da7896d692db75c
for details.

Note: I just saw v2 of the proposed fix. I'll need to retest. 

--------

Warnings:

Seen in various ppc boot tests:

BUG: sleeping function called from invalid context at kernel/locking/mutex.c:580
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 1, name: swapper
preempt_count: 1, expected: 0
RCU nest depth: 0, expected: 0
1 lock held by swapper/1:
 #0: c157efb0 (hose_spinlock){+.+.}-{2:2}, at: pcibios_alloc_controller+0x64/0x220
Preemption disabled at:
[<00000000>] 0x0
CPU: 0 PID: 1 Comm: swapper Not tainted 5.19.0-yocto-standard+ #1
Call Trace:
[d101dc90] [c073b264] dump_stack_lvl+0x50/0x8c (unreliable)
[d101dcb0] [c0093b70] __might_resched+0x258/0x2a8
[d101dcd0] [c0d3e634] __mutex_lock+0x6c/0x6ec
[d101dd50] [c0a84174] of_alias_get_id+0x50/0xf4
[d101dd80] [c002ec78] pcibios_alloc_controller+0x1b8/0x220
[d101ddd0] [c140c9dc] pmac_pci_init+0x198/0x784
[d101de50] [c140852c] discover_phbs+0x30/0x4c
[d101de60] [c0007fd4] do_one_initcall+0x94/0x344
[d101ded0] [c1403b40] kernel_init_freeable+0x1a8/0x22c
[d101df10] [c00086e0] kernel_init+0x34/0x160
[d101df30] [c001b334] ret_from_kernel_thread+0x5c/0x64

=============================
[ BUG: Invalid wait context ]
5.19.0-yocto-standard+ #1 Tainted: G        W
-----------------------------
swapper/1 is trying to lock:
c16a9dd8 (of_mutex){+.+.}-{3:3}, at: of_alias_get_id+0x50/0xf4
other info that might help us debug this:
context-{4:4}
1 lock held by swapper/1:
 #0: c157efb0 (hose_spinlock){+.+.}-{2:2}, at: pcibios_alloc_controller+0x64/0x220
stack backtrace:
CPU: 0 PID: 1 Comm: swapper Tainted: G        W          5.19.0-yocto-standard+ #1
Call Trace:
[d101dbc0] [c073b264] dump_stack_lvl+0x50/0x8c (unreliable)
[d101dbe0] [c00bb8e8] __lock_acquire+0x8c4/0x2278
[d101dc60] [c00ba4b8] lock_acquire+0x148/0x3b4
[d101dcd0] [c0d3e688] __mutex_lock+0xc0/0x6ec
[d101dd50] [c0a84174] of_alias_get_id+0x50/0xf4
[d101dd80] [c002ec78] pcibios_alloc_controller+0x1b8/0x220
[d101ddd0] [c140c9dc] pmac_pci_init+0x198/0x784
[d101de50] [c140852c] discover_phbs+0x30/0x4c
[d101de60] [c0007fd4] do_one_initcall+0x94/0x344
[d101ded0] [c1403b40] kernel_init_freeable+0x1a8/0x22c
[d101df10] [c00086e0] kernel_init+0x34/0x160
[d101df30] [c001b334] ret_from_kernel_thread+0x5c/0x64

Bisect points to commit 0fe1e96fef0a ("powerpc/pci: Prefer PCI domain
assignment via DT 'linux,pci-domain' and alias").

Fix is at:

https://lore.kernel.org/all/20220815065550.1303620-1-mpe@ellerman.id.au/

---
riscv32/riscv64:

[   15.272080] DEBUG_LOCKS_WARN_ON(!lockdep_hardirqs_enabled())
[   15.272421] WARNING: CPU: 0 PID: 140 at kernel/locking/lockdep.c:5510 check_flags+0xe2/0x1c2
[   15.272813] Modules linked in:
[   15.273132] CPU: 0 PID: 140 Comm: S01syslogd Tainted: G                 N 5.19.0-14184-g69dac8e431af #1
[   15.273428] Hardware name: riscv-virtio,qemu (DT)
[   15.273701] epc : check_flags+0xe2/0x1c2
[   15.273893]  ra : check_flags+0xe2/0x1c2
[   15.274040] epc : ffffffff80a8ea50 ra : ffffffff80a8ea50 sp : ff200000107cbcb0
[   15.274228]  gp : ffffffff819fec50 tp : ff6000000494d640 t0 : ffffffff81833628
[   15.274416]  t1 : 0000000000000001 t2 : 2d2d2d2d2d2d2d2d s0 : ff200000107cbcd0
[   15.274608]  s1 : ffffffff81a00130 a0 : 0000000000000030 a1 : ffffffff818925e8
[   15.274801]  a2 : 0000000000000010 a3 : fffffffffffffffe a4 : 0000000000000000
[   15.274997]  a5 : 0000000000000000 a6 : ffffffff80066d80 a7 : 0000000000000038
[   15.275179]  s2 : ffffffff81a024e0 s3 : ffffffff818935b0 s4 : ff200000107cbe28
[   15.275365]  s5 : ffffffff80e27708 s6 : 0000000200000022 s7 : ffffffffffffffff
[   15.275558]  s8 : ffffffff8249da18 s9 : 0000000000001000 s10: 0000000000000001
[   15.275745]  s11: 0000000000000001 t3 : ffffffff824740af t4 : ffffffff824740af
[   15.275926]  t5 : ffffffff824740b0 t6 : ff200000107cbaa8
[   15.276079] status: 0000000200000100 badaddr: 0000000000000000 cause: 0000000000000003
[   15.276355] [<ffffffff80a8eba8>] lock_is_held_type+0x78/0x14a
[   15.276565] [<ffffffff8003d648>] __might_resched+0x26/0x232
[   15.276717] [<ffffffff8003d892>] __might_sleep+0x3e/0x66
[   15.276861] [<ffffffff8002262c>] get_signal+0xa6/0x8f6
[   15.277007] [<ffffffff800051da>] do_notify_resume+0x68/0x418
[   15.277160] [<ffffffff80003af4>] ret_from_exception+0x0/0x10
[   15.277365] irq event stamp: 2974
[   15.277474] hardirqs last  enabled at (2973): [<ffffffff80a9761c>] _raw_spin_unlock_irqrestore+0x54/0x62
[   15.277705] hardirqs last disabled at (2974): [<ffffffff8000812c>] __trace_hardirqs_off+0xc/0x14
[   15.277933] softirqs last  enabled at (1650): [<ffffffff80a98092>] __do_softirq+0x3e2/0x51c
[   15.278168] softirqs last disabled at (1633): [<ffffffff80016fc8>] __irq_exit_rcu+0xb4/0xdc
[   15.278399] ---[ end trace 0000000000000000 ]---
[   15.278699] possible reason: unannotated irqs-on.
[   15.278838] irq event stamp: 2974
[   15.278929] hardirqs last  enabled at (2973): [<ffffffff80a9761c>] _raw_spin_unlock_irqrestore+0x54/0x62
[   15.279141] hardirqs last disabled at (2974): [<ffffffff8000812c>] __trace_hardirqs_off+0xc/0x14
[   15.279339] softirqs last  enabled at (1650): [<ffffffff80a98092>] __do_softirq+0x3e2/0x51c
[   15.279534] softirqs last disabled at (1633): [<ffffffff80016fc8>] __irq_exit_rcu+0xb4/0xdc

Caused or exposed by commit ba6cfef057e1 ("riscv: enable Docker requirements
in defconfig").

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: linux-next: stats (Was: Linux 6.0-rc1)
  2022-08-15  2:50 ` linux-next: stats (Was: Linux 6.0-rc1) Stephen Rothwell
@ 2022-08-17 14:41   ` Geert Uytterhoeven
  0 siblings, 0 replies; 8+ messages in thread
From: Geert Uytterhoeven @ 2022-08-17 14:41 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Linus Torvalds, Linux Kernel Mailing List, Linux Next Mailing List

Hi Stephen,

On Mon, Aug 15, 2022 at 4:55 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> There are also 320 commits in next-20220802 that didn't make it into
> v6.0-rc1.

> Top ten commiters:

>      13 geert+renesas@glider.be

How did that happen? Turns out these are false positives.

Whenever I update any of the renesas-*-for-vX.Y branches, I merge
them into renesas-next, which is pulled into linux-next.
When a commit in a renesas-*-for-vX.Y branch turns out to be bad,
and the branch hasn't been pulled by soc yet, I just fix that by
rebasing the renesas-*-for-vX.Y branch, and resolving any conflicts
during the next merge into renesas-next.
So the bad commits are gone from the renesas-*-for-vX.Y branches,
and thus will never go upstream, but technically, they are still part
of linux-next.  Hence  they show up in the statistics you do not
want to be part of...

Perhaps I should just recreate renesas-next every time any of the
renesas-*-for-vX.Y branches needs to be rebased? I already recreate
renesas-next after each rc1 release.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2022-08-17 14:42 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-08-14 23:41 Linux 6.0-rc1 Linus Torvalds
2022-08-15  1:23 ` Kirill A. Shutemov
2022-08-15  2:27   ` Steven Rostedt
2022-08-15  2:50 ` linux-next: stats (Was: Linux 6.0-rc1) Stephen Rothwell
2022-08-17 14:41   ` Geert Uytterhoeven
2022-08-15 18:04 ` Build regressions/improvements in v6.0-rc1 Geert Uytterhoeven
2022-08-15 18:10   ` Geert Uytterhoeven
2022-08-15 23:48 ` Linux 6.0-rc1 Guenter Roeck

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).