Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] zfs: update to 0.8.5.
Date: Wed, 07 Oct 2020 04:01:07 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25401@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 333 bytes --]

There is a new pull request by ahesford against master on the void-packages repository

https://github.com/ahesford/void-packages zfs
https://github.com/void-linux/void-packages/pull/25401

zfs: update to 0.8.5.
@Vaelatern @ericonr @zdykstra

A patch file from https://github.com/void-linux/void-packages/pull/25401.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-zfs-25401.patch --]
[-- Type: text/x-diff, Size: 5713 bytes --]

From e26104fcb5a458ead76cf4ade2bf837b32962a86 Mon Sep 17 00:00:00 2001
From: "Andrew J. Hesford" <ajh@sideband.org>
Date: Tue, 6 Oct 2020 22:00:00 -0400
Subject: [PATCH] zfs: update to 0.8.5.

---
 srcpkgs/zfs/patches/linux58.patch | 119 ------------------------------
 srcpkgs/zfs/template              |   8 +-
 2 files changed, 4 insertions(+), 123 deletions(-)
 delete mode 100644 srcpkgs/zfs/patches/linux58.patch

diff --git a/srcpkgs/zfs/patches/linux58.patch b/srcpkgs/zfs/patches/linux58.patch
deleted file mode 100644
index a05cd4f8dab..00000000000
--- a/srcpkgs/zfs/patches/linux58.patch
+++ /dev/null
@@ -1,119 +0,0 @@
-diff -ur a/config/kernel.m4 b/config/kernel.m4
---- a/config/kernel.m4	2020-05-05 12:56:29.709370875 -0400
-+++ b/config/kernel.m4	2020-08-12 10:38:58.842672016 -0400
-@@ -45,6 +45,7 @@
- 	ZFS_AC_KERNEL_SRC_SCHED
- 	ZFS_AC_KERNEL_SRC_USLEEP_RANGE
- 	ZFS_AC_KERNEL_SRC_KMEM_CACHE
-+	ZFS_AC_KERNEL_SRC_VMALLOC_PAGE_KERNEL
- 	ZFS_AC_KERNEL_SRC_WAIT
- 	ZFS_AC_KERNEL_SRC_INODE_TIMES
- 	ZFS_AC_KERNEL_SRC_INODE_LOCK
-@@ -163,6 +164,7 @@
- 	ZFS_AC_KERNEL_SCHED
- 	ZFS_AC_KERNEL_USLEEP_RANGE
- 	ZFS_AC_KERNEL_KMEM_CACHE
-+	ZFS_AC_KERNEL_VMALLOC_PAGE_KERNEL
- 	ZFS_AC_KERNEL_WAIT
- 	ZFS_AC_KERNEL_INODE_TIMES
- 	ZFS_AC_KERNEL_INODE_LOCK
-@@ -894,3 +896,28 @@
- 	    [test -f build/conftest/conftest.ko],
- 	    [$3], [$4], [$5])
- ])
-+
-+dnl #
-+dnl # 5.8 API,
-+dnl # __vmalloc PAGE_KERNEL removal
-+dnl #
-+AC_DEFUN([ZFS_AC_KERNEL_SRC_VMALLOC_PAGE_KERNEL], [
-+	ZFS_LINUX_TEST_SRC([__vmalloc], [
-+		#include <linux/mm.h>
-+		#include <linux/vmalloc.h>
-+	],[
-+		void *p __attribute__ ((unused));
-+
-+		p = __vmalloc(0, GFP_KERNEL, PAGE_KERNEL);
-+	])
-+])
-+
-+AC_DEFUN([ZFS_AC_KERNEL_VMALLOC_PAGE_KERNEL], [
-+	AC_MSG_CHECKING([whether __vmalloc(ptr, flags, pageflags) is available])
-+	ZFS_LINUX_TEST_RESULT([__vmalloc], [
-+		AC_MSG_RESULT(yes)
-+		AC_DEFINE(HAVE_VMALLOC_PAGE_KERNEL, 1, [__vmalloc page flags exists])
-+	],[
-+		AC_MSG_RESULT(no)
-+	])
-+])
-diff -ur a/include/spl/sys/kmem.h b/include/spl/sys/kmem.h
---- a/include/spl/sys/kmem.h	2020-05-05 12:56:29.717370676 -0400
-+++ b/include/spl/sys/kmem.h	2020-08-12 10:41:20.253453058 -0400
-@@ -170,6 +170,15 @@
- extern void spl_kmem_free(const void *ptr, size_t sz);
- 
- /*
-+ * 5.8 API change, pgprot_t argument removed.
-+ */
-+#ifdef HAVE_VMALLOC_PAGE_KERNEL
-+#define spl_vmalloc(size, flags) __vmalloc(size, flags, PAGE_KERNEL)
-+#else
-+#define spl_vmalloc(size, flags) __vmalloc(size, flags)
-+#endif
-+
-+/*
-  * The following functions are only available for internal use.
-  */
- extern void *spl_kmem_alloc_impl(size_t size, int flags, int node);
-diff -ur a/module/spl/spl-kmem-cache.c b/module/spl/spl-kmem-cache.c
---- a/module/spl/spl-kmem-cache.c	2020-05-05 12:57:28.442960922 -0400
-+++ b/module/spl/spl-kmem-cache.c	2020-08-12 10:38:58.843672014 -0400
-@@ -203,7 +203,7 @@
- 		ASSERT(ISP2(size));
- 		ptr = (void *)__get_free_pages(lflags, get_order(size));
- 	} else {
--		ptr = __vmalloc(size, lflags | __GFP_HIGHMEM, PAGE_KERNEL);
-+		ptr = spl_vmalloc(size, lflags | __GFP_HIGHMEM);
- 	}
- 
- 	/* Resulting allocated memory will be page aligned */
-@@ -1242,7 +1242,7 @@
- 	 * allocation.
- 	 *
- 	 * However, this can't be applied to KVM_VMEM due to a bug that
--	 * __vmalloc() doesn't honor gfp flags in page table allocation.
-+	 * spl_vmalloc() doesn't honor gfp flags in page table allocation.
- 	 */
- 	if (!(skc->skc_flags & KMC_VMEM)) {
- 		rc = __spl_cache_grow(skc, flags | KM_NOSLEEP);
-diff -ur a/module/spl/spl-kmem.c b/module/spl/spl-kmem.c
---- a/module/spl/spl-kmem.c	2020-05-05 12:57:28.442960922 -0400
-+++ b/module/spl/spl-kmem.c	2020-08-12 10:38:58.843672014 -0400
-@@ -172,7 +172,7 @@
- 		 * kmem_zalloc() callers.
- 		 *
- 		 * For vmem_alloc() and vmem_zalloc() callers it is permissible
--		 * to use __vmalloc().  However, in general use of __vmalloc()
-+		 * to use spl_vmalloc().  However, in general use of spl_vmalloc()
- 		 * is strongly discouraged because a global lock must be
- 		 * acquired.  Contention on this lock can significantly
- 		 * impact performance so frequently manipulating the virtual
-@@ -180,8 +180,7 @@
- 		 */
- 		if ((size > spl_kmem_alloc_max) || use_vmem) {
- 			if (flags & KM_VMEM) {
--				ptr = __vmalloc(size, lflags | __GFP_HIGHMEM,
--				    PAGE_KERNEL);
-+				ptr = spl_vmalloc(size, lflags | __GFP_HIGHMEM);
- 			} else {
- 				return (NULL);
- 			}
-@@ -194,7 +193,7 @@
- 
- 		/*
- 		 * For vmem_alloc() and vmem_zalloc() callers retry immediately
--		 * using __vmalloc() which is unlikely to fail.
-+		 * using spl_vmalloc() which is unlikely to fail.
- 		 */
- 		if ((flags & KM_VMEM) && (use_vmem == 0))  {
- 			use_vmem = 1;
diff --git a/srcpkgs/zfs/template b/srcpkgs/zfs/template
index cc50f79d8ac..0c8a5634e06 100644
--- a/srcpkgs/zfs/template
+++ b/srcpkgs/zfs/template
@@ -1,7 +1,7 @@
 # Template file for 'zfs'
 pkgname=zfs
-version=0.8.4
-revision=6
+version=0.8.5
+revision=1
 build_style=gnu-configure
 configure_args="--with-config=user --with-mounthelperdir=/usr/bin
  --with-udevdir=/usr/lib/udev --with-udevruledir=/usr/lib/udev/rules.d
@@ -14,7 +14,7 @@ maintainer="Toyam Cox <Vaelatern@voidlinux.org>"
 license="CDDL-1.0"
 homepage="https://zfsonlinux.org/"
 distfiles="https://github.com/zfsonlinux/zfs/releases/download/zfs-${version}/zfs-${version}.tar.gz"
-checksum=2b988f5777976f09d08083f6bebf6e67219c4c4c183c1f33033fb7e5e5eacafb
+checksum=dbb41d6b9c606a34ac93f4c19069fd6806ceeacb558f834f8a70755dadb7cd3d
 
 patch_args="-Np1"
 
@@ -74,7 +74,7 @@ zfs-devel_package() {
 		vmove usr/include
 		vmove "usr/lib/*.a"
 		vmove "usr/lib/*.so"
-		vmove usr/share/pkgconfig
+		vmove usr/lib/pkgconfig
 	}
 }
 

             reply	other threads:[~2020-10-07  2:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-07  2:01 ahesford [this message]
2020-10-07  3:31 ` zdykstra
2020-10-07 17:23 ` sgn
2020-10-07 17:23 ` sgn
2020-10-07 17:40 ` [PR PATCH] [Merged]: " Vaelatern

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25401@inbox.vuxu.org \
    --to=ahesford@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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).