From: Greg KH <gregkh@linuxfoundation.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
torvalds@linux-foundation.org, lwn@lwn.net,
Jiri Slaby <jslaby@suse.cz>
Subject: Re: Linux 4.19.98
Date: Thu, 23 Jan 2020 10:45:08 +0100 [thread overview]
Message-ID: <20200123094508.GA661791@kroah.com> (raw)
In-Reply-To: <157977223818.18920.13596879587159565742@skylake-alporthouse-com>
On Thu, Jan 23, 2020 at 09:37:18AM +0000, Chris Wilson wrote:
> Quoting Greg KH (2020-01-23 09:28:32)
> > On Thu, Jan 23, 2020 at 08:54:45AM +0000, Chris Wilson wrote:
> > > 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 <longman@redhat.com>
> > > 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 <longman@redhat.com>
> > > Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> > > Acked-by: Sai Praneeth Prakhya <sai.praneeth.prakhya@intel.com>
> > > Cc: Linus Torvalds <torvalds@linux-foundation.org>
> > > Cc: Peter Zijlstra <peterz@infradead.org>
> > > Cc: Thomas Gleixner <tglx@linutronix.de>
> > > Cc: linux-efi@vger.kernel.org
> > > Fixes: 9dbbedaa6171 ("efi: Make efi_rts_work accessible to efi page fault handler")
> > > Link: http://lkml.kernel.org/r/20181114175544.12860-2-ard.biesheuvel@linaro.org
> > > Signed-off-by: Ingo Molnar <mingo@kernel.org>
> > > Signed-off-by: Sasha Levin <sashal@kernel.org>
> > >
> > > was incorrectly applied to v4.19.41 and causes lockdep complaints for
> > > the onstack efi_rts_work being initialised by INIT_WORK().
> >
> > Incorrectly how? Fuzz off, or it shouldn't be applied at all? Should
> > this be reverted, or just fixed up, and if fixed up, do you have a patch
> > to fix it?
>
> Just reverted. It applies to 9dbbedaa6171 which moved the efi_rts_work
> off the stack, but is not in v4.19.y, so efi_rts_work is still a local
> and needs the INIT_WORK_ONSTACK annotation.
Ok, thanks, will go revert this and push out a new release with that
fix, thanks for letting me know.
greg k-h
next prev parent reply other threads:[~2020-01-23 9:45 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
2020-01-23 9:28 ` Greg KH
2020-01-23 9:37 ` Chris Wilson
2020-01-23 9:45 ` Greg KH [this message]
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:
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=20200123094508.GA661791@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=chris@chris-wilson.co.uk \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).