Subject: [ANNOUNCE] v5.9-rc8-rt12

Dear RT folks!

I'm pleased to announce the v5.9-rc8-rt12 patch set.

Changes since v5.9-rc8-rt11:

- The kernel test robot reported a few warnings due to the printk code
and a compile error in the powerpc architecture.

Known issues
- It has been pointed out that due to changes to the printk code the
internal buffer representation changed. This is only an issue if tools
like `crash' are used to extract the printk buffer from a kernel memory
image.

The delta patch against v5.9-rc8-rt11 is appended below and can be found here:

https://cdn.kernel.org/pub/linux/kernel/projects/rt/5.9/incr/patch-5.9-rc8-rt11-rt12.patch.xz

You can get this release via the git tree at:

git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git v5.9-rc8-rt12

The RT patch against v5.9-rc8 can be found here:

https://cdn.kernel.org/pub/linux/kernel/projects/rt/5.9/older/patch-5.9-rc8-rt12.patch.xz

The split quilt queue is available at:

https://cdn.kernel.org/pub/linux/kernel/projects/rt/5.9/older/patches-5.9-rc8-rt12.tar.xz

Sebastian

diff --git a/arch/powerpc/kexec/crash.c b/arch/powerpc/kexec/crash.c
index c9a889880214e..d488311efab1f 100644
--- a/arch/powerpc/kexec/crash.c
+++ b/arch/powerpc/kexec/crash.c
@@ -311,9 +311,6 @@ void default_machine_crash_shutdown(struct pt_regs *regs)
unsigned int i;
int (*old_handler)(struct pt_regs *regs);

- /* Avoid hardlocking with irresponsive CPU holding logbuf_lock */
- printk_nmi_enter();
-
/*
* This function is only called after the system
* has panicked or is otherwise in a critical state.
diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
index 8b74ff17b2eef..ee7008c436ca1 100644
--- a/kernel/printk/printk.c
+++ b/kernel/printk/printk.c
@@ -1981,12 +1981,6 @@ asmlinkage int vprintk(const char *fmt, va_list args)
}
EXPORT_SYMBOL(vprintk);

-int vprintk_default(const char *fmt, va_list args)
-{
- return vprintk_emit(0, LOGLEVEL_DEFAULT, NULL, 0, fmt, args);
-}
-EXPORT_SYMBOL_GPL(vprintk_default);
-
/**
* printk - print a kernel message
* @fmt: format string
@@ -2784,7 +2778,7 @@ static int __init init_printk_kthread(void)
}
late_initcall(init_printk_kthread);

-static int vprintk_deferred(const char *fmt, va_list args)
+__printf(1, 0) static int vprintk_deferred(const char *fmt, va_list args)
{
return vprintk_emit(0, LOGLEVEL_DEFAULT, NULL, 0, fmt, args);
}
diff --git a/localversion-rt b/localversion-rt
index 05c35cb580779..6e44e540b927b 100644
--- a/localversion-rt
+++ b/localversion-rt
@@ -1 +1 @@
--rt11
+-rt12


2020-10-06 14:48:07

by Daniel Wagner

[permalink] [raw]
Subject: Re: [ANNOUNCE] v5.9-rc8-rt12

Hi Sebastian,

On 06.10.20 10:58, Sebastian Andrzej Siewior wrote:
> Dear RT folks!
>
> I'm pleased to announce the v5.9-rc8-rt12 patch set.

Just as heads up. I just tried to build for arm64 but PREEMPT_RT
is not available anymore. Looks like ARCH_SUPPORTS_RT is only
available for !KVM.

Thanks,
Daniel

Subject: Re: [ANNOUNCE] v5.9-rc8-rt12

On 2020-10-06 16:37:21 [+0200], Daniel Wagner wrote:
> Hi Sebastian,
Hi Daniel,

> On 06.10.20 10:58, Sebastian Andrzej Siewior wrote:
> > Dear RT folks!
> >
> > I'm pleased to announce the v5.9-rc8-rt12 patch set.
>
> Just as heads up. I just tried to build for arm64 but PREEMPT_RT
> is not available anymore. Looks like ARCH_SUPPORTS_RT is only
> available for !KVM.

It has been announced in v5.9-rc2-rt1
https://lore.kernel.org/linux-rt-users/[email protected]/

and you replied to that mail. That mail contains information why and
what needs to be done to remove that restriction.

> Thanks,
> Daniel

Sebastian

2020-10-06 16:38:09

by Daniel Wagner

[permalink] [raw]
Subject: Re: [ANNOUNCE] v5.9-rc8-rt12

Hi Sebastian,

On 06.10.20 18:13, Sebastian Andrzej Siewior wrote:
>> Just as heads up. I just tried to build for arm64 but PREEMPT_RT
>> is not available anymore. Looks like ARCH_SUPPORTS_RT is only
>> available for !KVM.
>
> It has been announced in v5.9-rc2-rt1
> https://lore.kernel.org/linux-rt-users/[email protected]/
>
> and you replied to that mail. That mail contains information why and
> what needs to be done to remove that restriction.

D'oh, you have clearly a better memory than me. I forgot about it
completely. Sorry for the noise.

Thanks,
Daniel