From: Mark Brown <broonie@kernel.org>
To: Christian Brauner <brauner@kernel.org>
Cc: Andreas Gruenbacher <agruenba@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Mateusz Guzik <mjguzik@gmail.com>
Subject: linux-next: manual merge of the vfs-brauner tree with the gfs2 tree
Date: Thu, 13 Aug 2026 13:13:36 +0100 [thread overview]
Message-ID: <an208OpVMNEI2Zfo@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 2018 bytes --]
Hi all,
Today's linux-next merge of the vfs-brauner tree got a conflict in:
fs/gfs2/lock_dlm.c
between commit:
657e5af4fe0b9 ("gfs2: harden gfs2_glock_hold")
from the gfs2 tree and commit:
91e27ed8a387c ("lockref: tidy up dead count handling")
from the vfs-brauner tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
diff --combined fs/gfs2/lock_dlm.c
index babce07b84f19,cc901fb97da0c..0000000000000
--- a/fs/gfs2/lock_dlm.c
+++ b/fs/gfs2/lock_dlm.c
@@@ -126,7 -126,7 +126,7 @@@ static void gdlm_ast(void *arg
clear_bit(GLF_BLOCKING, &gl->gl_flags);
/* If the glock is dead, we only react to a dlm_unlock() reply. */
- if (__lockref_is_dead(&gl->gl_lockref) &&
+ if (lockref_is_dead(&gl->gl_lockref) &&
gl->gl_lksb.sb_status != -DLM_EUNLOCK)
return;
@@@ -182,6 -182,9 +182,6 @@@ static void gdlm_bast(void *arg, int mo
{
struct gfs2_glock *gl = arg;
- if (lockref_is_dead(&gl->gl_lockref))
- return;
-
switch (mode) {
case DLM_LOCK_EX:
gfs2_glock_cb(gl, LM_ST_UNLOCKED);
@@@ -326,7 -329,7 +326,7 @@@ static void gdlm_put_lock(struct gfs2_g
uint32_t flags = 0;
int error;
- BUG_ON(!__lockref_is_dead(&gl->gl_lockref));
+ BUG_ON(!lockref_is_dead(&gl->gl_lockref));
if (test_bit(GLF_INITIAL, &gl->gl_flags)) {
gfs2_glock_free(gl);
@@@ -344,7 -347,7 +344,7 @@@
* DLM_LOCK_PW mode, the lock value block (LVB) would be lost.
*/
- if (test_bit(SDF_SKIP_DLM_UNLOCK, &sdp->sd_flags) &&
+ if (test_bit(SDF_KILL, &sdp->sd_flags) &&
(!gl->gl_lksb.sb_lvbptr || gl->gl_state != LM_ST_EXCLUSIVE)) {
gfs2_glock_free_later(gl);
return;
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-08-13 12:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 12:13 Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-29 12:30 linux-next: manual merge of the vfs-brauner tree with the gfs2 tree Mark Brown
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=an208OpVMNEI2Zfo@sirena.org.uk \
--to=broonie@kernel.org \
--cc=agruenba@redhat.com \
--cc=brauner@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mjguzik@gmail.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