From: Sasha Levin <sashal@kernel.org>
To: Mike Snitzer <snitzer@redhat.com>
Cc: gregkh@linuxfoundation.org, vcaputo@pengaru.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] Revert "dm crypt: use WQ_HIGHPRI for the IO and crypt" failed to apply to 4.14-stable tree
Date: Tue, 26 Nov 2019 20:49:22 -0500 [thread overview]
Message-ID: <20191127014922.GK5861@sasha-vm> (raw)
In-Reply-To: <20191126170755.GB2718@redhat.com>
On Tue, Nov 26, 2019 at 12:07:55PM -0500, Mike Snitzer wrote:
>On Tue, Nov 26 2019 at 5:41am -0500,
>gregkh@linuxfoundation.org <gregkh@linuxfoundation.org> wrote:
>
>>
>> The patch below does not apply to the 4.14-stable tree.
>> If someone wants it applied there, or to any other stable or longterm
>> tree, then please email the backport, including the original git commit
>> id to <stable@vger.kernel.org>.
>>
>> thanks,
>>
>> greg k-h
>
>Same as 4.19 goes for 4.14, this worked for me:
>
>git cherry-pick ed0302e83098d
>git cherry-pick f612b2132db529feac4f965f28a1b9258ea7c22b
$ git cherry-pick ed0302e83098d
[queue-4.19 fa98ce88d51b9] dm crypt: make workqueue names device-specific
Author: Michał Mirosław <mirq-linux@rere.qmqm.pl>
Date: Tue Oct 9 22:13:43 2018 +0200
1 file changed, 10 insertions(+), 5 deletions(-)
$ git cherry-pick f612b2132db529feac4f965f28a1b9258ea7c22b
[queue-4.19 73eb292b80f32] Revert "dm crypt: use WQ_HIGHPRI for the IO and crypt workqueues"
Author: Mike Snitzer <snitzer@redhat.com>
Date: Wed Nov 20 17:27:39 2019 -0500
1 file changed, 3 insertions(+), 6 deletions(-)
$ make allmodconfig
scripts/kconfig/conf --allmodconfig Kconfig
#
# configuration written to .config
#
$ make drivers/md/dm-crypt.o
scripts/kconfig/conf --syncconfig Kconfig
CALL scripts/checksyscalls.sh
DESCEND objtool
CC [M] drivers/md/dm-crypt.o
drivers/md/dm-crypt.c: In function ‘crypt_ctr’:
drivers/md/dm-crypt.c:2674:24: error: implicit declaration of function ‘dm_table_device_name’; did you mean ‘dm_device_name’? [-Werror=implicit-function-declaration]
const char *devname = dm_table_device_name(ti->table);
^~~~~~~~~~~~~~~~~~~~
dm_device_name
drivers/md/dm-crypt.c:2674:24: warning: initialization of ‘const char *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion]
cc1: some warnings being treated as errors
make[1]: *** [scripts/Makefile.build:310: drivers/md/dm-crypt.o] Error 1
make: *** [Makefile:1678: drivers/md/dm-crypt.o] Error 2
--
Thanks,
Sasha
prev parent reply other threads:[~2019-11-27 1:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 10:41 FAILED: patch "[PATCH] Revert "dm crypt: use WQ_HIGHPRI for the IO and crypt" failed to apply to 4.14-stable tree gregkh
2019-11-26 17:07 ` Mike Snitzer
2019-11-27 1:49 ` 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=20191127014922.GK5861@sasha-vm \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=snitzer@redhat.com \
--cc=stable@vger.kernel.org \
--cc=vcaputo@pengaru.com \
/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