From: Lukas Wunner <lukas@wunner.de>
To: Elimar Riesebieter <riesebie@lxtec.de>
Cc: Michael Hierweck <michael.hierweck@hostsharing.net>,
Lars Ellenberg <lars.ellenberg@linbit.com>,
Philipp Reisner <philipp.reisner@linbit.com>,
drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] [PATCH drbd-9.0] compat: __vmalloc() pgprot argument was removed in v5.8
Date: Mon, 12 Oct 2020 02:54:10 +0200 [thread overview]
Message-ID: <20201012005410.GA28362@wunner.de> (raw)
In-Reply-To: <20201011193048.rfe5qvuba2ovrwed@toy.home.lxtec.de>
On Sun, Oct 11, 2020 at 09:30:48PM +0200, Elimar Riesebieter wrote:
> * Lukas Wunner <lukas@wunner.de> [2020-10-11 20:51 +0200]:
> > The patch worked for me with v5.3.
>
> Did you build with brdb master? I used tag 9.0.25-1.
The patch is meant to be applied to the drbd-9.0 branch where all
development seems to happen. It also applies cleanly to the
drbd-9.0.25-1 tag.
I'm afraid I cannot reproduce the issue you're seeing with your
DKMS package on v4.19. Using tag drbd-9.0.25-1 and v4.19.95,
the call to __vmalloc() is correctly patched in drbd_bitmap.c
but the build fails for a different reason (conflicting types
for blkdev_issue_zeroout()). Doesn't look like 4.19 is well
supported.
If you're unsuccessful debugging the build failure on your own,
maybe you can upload your drbd build directory somewhere so I
can take a look.
Thanks,
Lukas
next prev parent reply other threads:[~2020-10-12 15:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-11 16:07 [Drbd-dev] [PATCH drbd-9.0] compat: __vmalloc() pgprot argument was removed in v5.8 Lukas Wunner
2020-10-11 18:39 ` Elimar Riesebieter
2020-10-11 18:47 ` Elimar Riesebieter
2020-10-11 18:55 ` Lukas Wunner
2020-10-11 18:51 ` Lukas Wunner
2020-10-11 19:20 ` Elimar Riesebieter
2020-10-11 19:30 ` Elimar Riesebieter
2020-10-12 0:54 ` Lukas Wunner [this message]
2020-10-12 11:14 ` Elimar Riesebieter
2020-10-23 7:23 ` Lukas Wunner
2020-10-12 10:57 ` Elimar Riesebieter
2020-10-20 14:06 ` Christoph Böhmwalder
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=20201012005410.GA28362@wunner.de \
--to=lukas@wunner.de \
--cc=drbd-dev@lists.linbit.com \
--cc=lars.ellenberg@linbit.com \
--cc=michael.hierweck@hostsharing.net \
--cc=philipp.reisner@linbit.com \
--cc=riesebie@lxtec.de \
/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.