public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
	patches@kernelci.org, lkft-triage@lists.linaro.org,
	pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
	srw@sladewatkins.net, rwarsow@gmx.de
Subject: Re: [PATCH 6.0 000/314] 6.0.10-rc1 review
Date: Fri, 25 Nov 2022 08:45:07 +0100	[thread overview]
Message-ID: <Y4Byg4lq6jOWcY8D@kroah.com> (raw)
In-Reply-To: <Y39SmCRcY7EUhkhA@debian>

On Thu, Nov 24, 2022 at 11:16:40AM +0000, Sudip Mukherjee wrote:
> Hi Greg,
> 
> On Wed, Nov 23, 2022 at 09:47:25AM +0100, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.0.10 release.
> > There are 314 patches in this series, all will be posted as a response
> > to this one.  If anyone has any issues with these being applied, please
> > let me know.
> > 
> > Responses should be made by Fri, 25 Nov 2022 08:45:20 +0000.
> > Anything received after that time might be too late.
> 
> Build test (gcc version 12.2.1 20221016):
> mips: 52 configs -> 1 failure
> arm: 100 configs -> 2 failures
> arm64: 3 configs -> no failure
> x86_64: 4 configs -> no failure
> alpha allmodconfig -> no failure
> csky allmodconfig -> no failure
> powerpc allmodconfig -> 1 failure
> riscv allmodconfig -> no failure
> s390 allmodconfig -> no failure
> xtensa allmodconfig -> no failure
> 
> Note:
> 1. As reported by others arm mips and powerpc allmodconfig fails with:
> drivers/rtc/rtc-cmos.c:1299:13: error: 'rtc_wake_setup' defined but not used [-Werror=unused-function]
>  1299 | static void rtc_wake_setup(struct device *dev)
>       |             ^~~~~~~~~~~~~~
> 

Should now be fixed, thanks.


> 
> 2. arm imxrt_defconfig fails with:
> 
> In file included from ./include/linux/bpf-cgroup.h:5,
>                  from security/device_cgroup.c:8:
> ./include/linux/bpf.h:2310:20: error: static declaration of 'bpf_prog_inc_misses_counter' follows non-static declaration
>  2310 | static inline void bpf_prog_inc_misses_counter(struct bpf_prog *prog)
>       |                    ^~~~~~~~~~~~~~~~~~~~~~~~~~~
> ./include/linux/bpf.h:1970:14: note: previous declaration of 'bpf_prog_inc_misses_counter' with type 'void(struct bpf_prog *)'
>  1970 | void notrace bpf_prog_inc_misses_counter(struct bpf_prog *prog);
>       |              ^~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
> Caused by a1ba348f5325 ("bpf: Prevent bpf program recursion for raw tracepoint probes").

Oh, nice catch!  I messed up the backport of this commit, and put the
prototype in the wrong place in the .h file.  Let me push out a -rc2
with this moved a bit to see if that solves the problem.

Interesting that your build tests were the only one that caught this.

thanks,

greg k-h

  reply	other threads:[~2022-11-25  7:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-23  8:47 [PATCH 6.0 000/314] 6.0.10-rc1 review Greg Kroah-Hartman
2022-11-23 15:27 ` Jon Hunter
2022-11-23 17:03 ` Guenter Roeck
2022-11-25  7:35   ` Greg Kroah-Hartman
2022-11-23 22:31 ` Ron Economos
2022-11-24  2:39 ` Guenter Roeck
2022-11-24  8:18 ` Naresh Kamboju
2022-11-24  8:48 ` Bagas Sanjaya
2022-11-24 11:16 ` Sudip Mukherjee
2022-11-25  7:45   ` Greg Kroah-Hartman [this message]
2022-11-25  0:29 ` Justin Forbes
  -- strict thread matches above, loose matches on Subject: below --
2022-11-24  4:59 Ronald Warsow

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=Y4Byg4lq6jOWcY8D@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=f.fainelli@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@denx.de \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=srw@sladewatkins.net \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox