From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andreas Gruenbacher <agruenba@redhat.com>
Date: Tue, 19 Jan 2021 18:36:32 +0100
Subject: [Cluster-devel] [GFS2 PATCH] gfs2: make recovery workqueue
 operate on a gfs2 mount point, not journal
In-Reply-To: <1287886465.45164472.1611071084974.JavaMail.zimbra@redhat.com>
References: <2125295377.38904313.1608669538740.JavaMail.zimbra@redhat.com>
	<51252ca2-fa56-acb8-24cf-fb2e992f76de@redhat.com>
	<561946972.42407585.1609776564024.JavaMail.zimbra@redhat.com>
	<CAHc6FU7T5RzFhPWF_YbZY9a7+goVTPKrOybh46e12xe6zhL99Q@mail.gmail.com>
	<1287886465.45164472.1611071084974.JavaMail.zimbra@redhat.com>
Message-ID: <CAHc6FU6sNa5CA1Q9deyuVhBA7RohHhb59m6PZ3-EMFueW6W6kg@mail.gmail.com>
List-Id: <cluster-devel.redhat.com>
To: cluster-devel.redhat.com
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

On Tue, Jan 19, 2021 at 4:44 PM Bob Peterson <rpeterso@redhat.com> wrote:
> Sure, the recovery workers' bio allocations and submitting may be serialized,
> but that's where it ends. The recovery workers don't prevent races with each
> other when using the variable common to all of them: sdp->sd_log_bio.
> This is the case when there are, for example, 5 journals with 5 different
> recovery workers, all trying to use the same sdp->sd_log_bio at the same time.

Well, sdp->sd_log_bio obviously needs to be moved to a per-journal context.

Thanks,
Andreas