From: Sasha Levin <sashal@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "François Valenduc" <francoisvalenduc@gmail.com>, stable@vger.kernel.org
Subject: Re: Commit 8c37f7c23c02f6ac020ffdc746026c2363b23a5a causes warnings
Date: Sat, 4 May 2019 15:29:35 -0400 [thread overview]
Message-ID: <20190504192935.GA1747@sasha-vm> (raw)
In-Reply-To: <20190504071930.GB12815@kroah.com>
On Sat, May 04, 2019 at 09:19:30AM +0200, Greg KH wrote:
>On Sat, May 04, 2019 at 08:57:28AM +0200, François Valenduc wrote:
>> Le 4/05/19 à 08:41, Greg KH a écrit :
>> > On Fri, May 03, 2019 at 10:17:39PM +0200, François Valenduc wrote:
>> >> Commit 8c37f7c23c02f6ac020ffdc746026c2363b23a5a ( workqueue: Try to
>> >> catch flush_work() without INIT_WORK().) causes the following warning
>> >> when mounting encrypted filesystems:
[...]
>> > Great, it did what it was trying to do :)
>> >
>> > Do you have this problem on 5.0.y or Linus's current tree?
>> >
>> > thanks,
>> >
>> > greg k-h
>>
>>
>> It only occurs with the 4.19.y branch. On 5.0.11 and 5.1-rc7, I don't
>> have the problem.
>
>Thanks for letting us know, I'll dig through the tree on Monday to see
>if I can find the needed fix that happened between 4.19 and 5.0 for
>this.
Looks like it was fixed upstream with 2e3c18d0ada ("block: pass no-op
callback to INIT_WORK()."). It also looks like we're missing a few of
these kind of fixes in our various branches. I can queue them up when
the current -rc branches are released.
--
Thanks,
Sasha
prev parent reply other threads:[~2019-05-04 19:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 20:17 Commit 8c37f7c23c02f6ac020ffdc746026c2363b23a5a causes warnings François Valenduc
2019-05-04 6:41 ` Greg KH
2019-05-04 6:57 ` François Valenduc
2019-05-04 7:19 ` Greg KH
2019-05-04 19:29 ` Sasha Levin [this message]
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=20190504192935.GA1747@sasha-vm \
--to=sashal@kernel.org \
--cc=francoisvalenduc@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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.