archive mirror
 help / color / mirror / Atom feed
From: Chris Wilson <>
To: Andrew Morton <>,
	Greg KH <>,,,
Cc:, Jiri Slaby <>
Subject: Re: Linux 4.19.98
Date: Thu, 23 Jan 2020 08:54:45 +0000	[thread overview]
Message-ID: <157976968555.18920.13404367012873725550@skylake-alporthouse-com> (raw)
In-Reply-To: <>

Quoting Greg KH (2020-01-23 08:46:32)
> I'm announcing the release of the 4.19.98 kernel.

commit 3e6b472f474accf757e107919f8ee42e7315ac0d
Author: Waiman Long <>
Date:   Wed Nov 14 09:55:40 2018 -0800

    efi: Fix debugobjects warning on 'efi_rts_work'

    [ Upstream commit ef1491e791308317bb9851a0ad380c4a68b58d54 ]

    The following commit:

      9dbbedaa6171 ("efi: Make efi_rts_work accessible to efi page fault handler")

    converted 'efi_rts_work' from an auto variable to a global variable.
    However, when submitting the work, INIT_WORK_ONSTACK() was still used,
    causing the following complaint from debugobjects:

      ODEBUG: object 00000000ed27b500 is NOT on stack 00000000c7d38760, but annotated.

    Change the macro to just INIT_WORK() to eliminate the warning.

    Signed-off-by: Waiman Long <>
    Signed-off-by: Ard Biesheuvel <>
    Acked-by: Sai Praneeth Prakhya <>
    Cc: Linus Torvalds <>
    Cc: Peter Zijlstra <>
    Cc: Thomas Gleixner <>
    Fixes: 9dbbedaa6171 ("efi: Make efi_rts_work accessible to efi page fault handler")
    Signed-off-by: Ingo Molnar <>
    Signed-off-by: Sasha Levin <>

was incorrectly applied to v4.19.41 and causes lockdep complaints for
the onstack efi_rts_work being initialised by INIT_WORK().

  parent reply	other threads:[~2020-01-23  8:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-23  8:46 Linux 4.19.98 Greg KH
2020-01-23  8:46 ` Greg KH
2020-01-23  8:54 ` Chris Wilson [this message]
2020-01-23  9:28   ` Greg KH
2020-01-23  9:37     ` Chris Wilson
2020-01-23  9:45       ` Greg KH
2020-01-23  9:46         ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=157976968555.18920.13404367012873725550@skylake-alporthouse-com \ \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).