linux-kernel - Re: linux-next: build failure after merge of the rcu tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Sat, 4 Apr 2020 20:10:34 -0700
From:   "Paul E. McKenney" <paulmck@...nel.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the rcu tree

On Sun, Apr 05, 2020 at 11:49:59AM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the rcu tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
> 
> kernel/trace/ftrace.c: In function 'ftrace_shutdown':
> kernel/trace/ftrace.c:2924:3: error: implicit declaration of function 'synchronize_rcu_tasks_rude'; did you mean 'synchronize_rcu_tasks'? [-Werror=implicit-function-declaration]
>  2924 |   synchronize_rcu_tasks_rude();
>       |   ^~~~~~~~~~~~~~~~~~~~~~~~~~
>       |   synchronize_rcu_tasks
> 
> Caused by commit
> 
>   59377f3e06b8 ("ftrace: Use synchronize_rcu_tasks_rude() instead of ftrace_sync()")
> 
> synchronize_rcu_tasks_rude() is only declared when
> CONFIG_TASKS_RCU_GENERIC is defined.
> 
> I have reverted that commit for today.
> 
> Just asking: are all the commits currently in the rcu tree actually
> intended for v5.7?

My bad!  I have moved rcu/next to where it need to be for the duration
of the merge window.  Please accept my apologies for the hassle.

							Thanx, Paul