public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: Re: [pve-devel] [PATCH zfsonlinux/stable-6] cherry-pick fix for assertion from 2.0.6-staging
Date: Thu, 9 Sep 2021 09:02:52 +0200	[thread overview]
Message-ID: <bfbf8dbf-d154-a70a-eff3-a57f0ac9437d@proxmox.com> (raw)
In-Reply-To: <20210908142254.4000779-1-s.ivanov@proxmox.com>

On 08.09.21 16:22, Stoiko Ivanov wrote:
> The panic described in the issues closed by this commit were observed
> by some users.
> 
> Since the revert is already included in upstreams master and 2.1
> branches, and the proposed port to the 2.0 branches is already
> accepted the limit for regression should be small.
> 
> Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
> ---
> Tested by building pve-kernel-5.4 with zfs including this patch and
> booting it on 2 VMs of mine with replication enabled.
> 
>  ...onsolidate-arc_buf-allocation-checks.patch | 181 ++++++++++++++++++
>  debian/patches/series                         |   1 +
>  2 files changed, 182 insertions(+)
>  create mode 100644 debian/patches/0010-Revert-Consolidate-arc_buf-allocation-checks.patch
> 

as told off-list, I did the thankfully trivial cherry-pick at that time yesterday already
and also triggered a kernel build including an update to latest stable tag, so I rather
pushed that out.





      reply	other threads:[~2021-09-09  7:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-08 14:22 Stoiko Ivanov
2021-09-09  7:02 ` Thomas Lamprecht [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=bfbf8dbf-d154-a70a-eff3-a57f0ac9437d@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=s.ivanov@proxmox.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal