mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rich Felker <dalias@libc.org>
To: Rob Landley <rob@landley.net>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	linux-sh@vger.kernel.org,
	Michael Karcher <kernel@mkarcher.dialup.fu-berlin.de>,
	linux-kernel@vger.kernel.org,
	Yoshinori Sato <ysato@users.sourceforge.jp>
Subject: Re: [PATCH] sh: fix syscall tracing
Date: Thu, 10 Sep 2020 09:37:51 -0400	[thread overview]
Message-ID: <20200910133751.GE3265@brightrain.aerifal.cx> (raw)
In-Reply-To: <c0685f0b-e997-39e9-8ae9-ee22c8e74a01@landley.net>

On Thu, Sep 10, 2020 at 06:02:05AM -0500, Rob Landley wrote:
> On 9/10/20 4:55 AM, John Paul Adrian Glaubitz wrote:
> > Hi Rich!
> > 
> > On 9/7/20 7:44 PM, Rich Felker wrote:
> >>> Can we still get this merged as a hotfix for 5.9?
> >>
> >> Yes, fixes for regressions in the same release cycle are in-scope (the
> >> whole point of having -rc's). I have at least one other fix that needs
> >> to go in too and was just giving it a little time to make sure
> >> everything's ok now and that there are no more.
> > 
> > Let me know if there is anything else left for testing.
> 
> Could you also merge the fix the build break, ala:
> 
> > The vmlinux image is a current vanilla Linux kernel using an initramfs filesystem:
> > 
> >   make ARCH=sh CROSS_COMPILE=sh2eb-linux-muslfdpic- j2_defconfig vmlinux
> > 
> > And trying to do that in current git dies with:
> > 
> >   CC      init/version.o
> > In file included from ./include/linux/spinlock.h:318,
> >                  from ./arch/sh/include/asm/smp.h:11,
> >                  from ./include/linux/smp.h:82,
> >                  from ./include/linux/lockdep.h:14,
> >                  from ./include/linux/rcupdate.h:29,
> >                  from ./include/linux/rculist.h:11,
> >                  from ./include/linux/pid.h:5,
> >                  from ./include/linux/sched.h:14,
> >                  from ./include/linux/utsname.h:6,
> >                  from init/version.c:14:
> > ./include/linux/spinlock_api_smp.h: In function '__raw_spin_trylock':
> > ./include/linux/spinlock_api_smp.h:90:3: error: implicit declaration of function
> > 'spin_acquire'; did you mean 'xchg_acquire'? [-Werror=implicit-function-declaration]
> >    90 |   spin_acquire(&lock->dep_map, 0, 1, _RET_IP_);
> >       |   ^~~~~~~~~~~~
> >       |   xchg_acquire
> > ./include/linux/spinlock_api_smp.h:90:21: error: 'raw_spinlock_t' {aka 'struct
> > raw_spinlock'} has no member named 'dep_map'
> >    90 |   spin_acquire(&lock->dep_map, 0, 1, _RET_IP_);
> >       |                     ^~
> > 
> > And so on and so forth for pages. I bisected it to:
> > 
> > commit 0cd39f4600ed4de859383018eb10f0f724900e1b
> > Author: Peter Zijlstra <peterz@infradead.org>
> > Date:   Thu Aug 6 14:35:11 2020 +0200
> > 
> >     locking/seqlock, headers: Untangle the spaghetti monster
> 
> Which I reported to Rich on the 2nd and he had me test a one line patch fixing
> it (adding an extra #include) on the 3rd, but I just did a fresh pull and the
> j2_defconfig build still broke a week later.

Yes, that's presently the other regression fix I have queued for the
second pull request.

Rich

  reply	other threads:[~2020-09-10 14:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-03  5:48 Rich Felker
2020-09-03  8:13 ` John Paul Adrian Glaubitz
2020-09-03 10:14 ` John Paul Adrian Glaubitz
2020-09-03 16:16   ` Rich Felker
2020-09-07  9:52     ` John Paul Adrian Glaubitz
2020-09-07 17:44       ` Rich Felker
2020-09-10  9:55         ` John Paul Adrian Glaubitz
2020-09-10 11:02           ` Rob Landley
2020-09-10 13:37             ` Rich Felker [this message]
2020-09-15 10:35               ` John Paul Adrian Glaubitz
2020-09-16  0:28                 ` Rich Felker
2020-09-18 19:29                   ` Rich Felker

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=20200910133751.GE3265@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=kernel@mkarcher.dialup.fu-berlin.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=rob@landley.net \
    --cc=ysato@users.sourceforge.jp \
    /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

all inboxes | Powered by JetHome®