All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Srinivasarao Pathipati <quic_c_spathi@quicinc.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH V1] rcu-tasks: Fix build error
Date: Tue, 21 Feb 2023 11:37:03 +0100	[thread overview]
Message-ID: <Y/Sez06gvJbAv7VE@kroah.com> (raw)
In-Reply-To: <72e8a2a5-8729-5551-563a-d8d7c143f527@quicinc.com>

On Tue, Feb 21, 2023 at 02:57:15PM +0530, Srinivasarao Pathipati wrote:
> 
> On 2/21/2023 12:24 AM, Greg KH wrote:
> > On Mon, Feb 20, 2023 at 11:43:59PM +0530, Srinivasarao Pathipati wrote:
> > > Making show_rcu_tasks_rude_gp_kthread() function as 'inline' to
> > > fix below compilation error.
> > > This is applicable to only 5.10 kernels as code got modified
> > > in latest kernels.
> > > 
> > >   In file included from kernel/rcu/update.c:579:0:
> > >   kernel/rcu/tasks.h:710:13: error: ‘show_rcu_tasks_rude_gp_kthread’ defined but not used [-Werror=unused-function]
> > >    static void show_rcu_tasks_rude_gp_kthread(void) {}
> > > 
> > > Signed-off-by: Srinivasarao Pathipati <quic_c_spathi@quicinc.com>
> > > ---
> > >   kernel/rcu/tasks.h | 2 +-
> > >   1 file changed, 1 insertion(+), 1 deletion(-)
> > > 
> > > diff --git a/kernel/rcu/tasks.h b/kernel/rcu/tasks.h
> > > index 8b51e6a..53ddb4e 100644
> > > --- a/kernel/rcu/tasks.h
> > > +++ b/kernel/rcu/tasks.h
> > > @@ -707,7 +707,7 @@ static void show_rcu_tasks_rude_gp_kthread(void)
> > >   #endif /* #ifndef CONFIG_TINY_RCU */
> > >   #else /* #ifdef CONFIG_TASKS_RUDE_RCU */
> > > -static void show_rcu_tasks_rude_gp_kthread(void) {}
> > > +static inline void show_rcu_tasks_rude_gp_kthread(void) {}
> > >   #endif /* #else #ifdef CONFIG_TASKS_RUDE_RCU */
> > >   ////////////////////////////////////////////////////////////////////////
> > > -- 
> > > 2.7.4
> > > 
> > What commit id caused this problem?
> 
> commit  (8344496e8b49c4122c1808d6cd3f8dc71bccb595 rcu-tasks: Conditionally
> compile show_rcu_tasks_gp_kthreads()) introduced this issue

So this has been around for a very very long time.

Why is this suddenly an issue now, almost 3 years later?  What changed
to cause this to become an issue?

And please put this information in the changelog text.

> This patch added conditional macros for definition of
> show_rcu_tasks_rude_gp_kthread()  but not for dummy definition.
> 
> > And why isn't it an issue in newer kernels, what commit id fixed it and
> > why can't we just take that instead?
> 
> Later code got modified with patch (27c0f1448389 rcutorture: Make
> grace-period kthread report match RCU flavor being tested)  , with this
> there won't be compilation issue.
> 
> This patch is part of below series, Not sure all these can be picked to this
> 5.10 stable branch so fixed issue by simply making function inline.
> 
> if you think it is better to pick this series, please merge to 5.10 branch.
> 
> https://lore.kernel.org/lkml/20201105233900.GA20676@paulmck-ThinkPad-P72/
> 
> [1/4] e1eb075ccf37 rcutorture: Make preemptible TRACE02 enable lockdep
> [2/4] 77dc174103fd rcu-tasks: Convert rcu_tasks_wait_gp() for-loop to
> while-loop
> [3/4] 27c0f1448389 rcutorture: Make grace-period kthread report match RCU
> flavor being tested
> [4/4] 75dc2da5ecd6 rcu-tasks: Make the units of ->init_fract be jiffies

I would need you to test and verify that these actually work properly
and do not cause any regressions and sign off on them before I could
take them.

thanks,

greg k-h

  reply	other threads:[~2023-02-21 10:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-20 18:13 [PATCH V1] rcu-tasks: Fix build error Srinivasarao Pathipati
2023-02-20 18:54 ` Greg KH
2023-02-21  9:27   ` Srinivasarao Pathipati
2023-02-21 10:37     ` Greg KH [this message]
2023-02-21 11:19       ` Srinivasarao Pathipati
2023-02-21 13:45         ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2023-02-21 12:03 Srinivasarao Pathipati
2023-02-21 13:44 ` Greg KH

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=Y/Sez06gvJbAv7VE@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=quic_c_spathi@quicinc.com \
    --cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.