cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] gfs2: Fix loop in gfs2_rbm_find (2)
Date: Wed, 30 Jan 2019 15:39:36 -0500 (EST)	[thread overview]
Message-ID: <631177443.68537540.1548880776738.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20190129003511.953A720870@mail.kernel.org>

----- Original Message -----
> Hi,
> 
> [This is an automated email]
> 
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: 2d29f6b96d8f gfs2: Fix loop in gfs2_rbm_find.
> 
> The bot has tested the following trees: v4.20.5, v4.19.18, v4.14.96,
> v4.9.153, v4.4.172, v3.18.133.
> 
> v4.20.5: Build OK!
> v4.19.18: Failed to apply! Possible dependencies:
>     281b4952d185 ("gfs2: Rename bitmap.bi_{len => bytes}")
>     e54c78a27fcd ("gfs2: Use fs_* functions instead of pr_* function where we
>     can")
> 
> v4.14.96: Failed to apply! Possible dependencies:
>     281b4952d185 ("gfs2: Rename bitmap.bi_{len => bytes}")
>     dc8fbb03dcd6 ("GFS2: gfs2_free_extlen can return an extent that is too
>     long")
>     e54c78a27fcd ("gfs2: Use fs_* functions instead of pr_* function where we
>     can")
> 
> v4.9.153: Failed to apply! Possible dependencies:
>     0d1c7ae9d849 ("GFS2: Prevent BUG from occurring when normal Withdraws
>     occur")
>     281b4952d185 ("gfs2: Rename bitmap.bi_{len => bytes}")
>     9862ca056e65 ("GFS2: Switch tr_touched to flag in transaction")
>     dc8fbb03dcd6 ("GFS2: gfs2_free_extlen can return an extent that is too
>     long")
>     e54c78a27fcd ("gfs2: Use fs_* functions instead of pr_* function where we
>     can")
>     ed17545d01e4 ("GFS2: Allow glocks to be unlocked after withdraw")
> 
> v4.4.172: Failed to apply! Possible dependencies:
>     0d1c7ae9d849 ("GFS2: Prevent BUG from occurring when normal Withdraws
>     occur")
>     281b4952d185 ("gfs2: Rename bitmap.bi_{len => bytes}")
>     3e11e5304150 ("GFS2: ignore unlock failures after withdraw")
>     471f3db2786b ("gfs2: change gfs2 readdir cookie")
>     9862ca056e65 ("GFS2: Switch tr_touched to flag in transaction")
>     dc8fbb03dcd6 ("GFS2: gfs2_free_extlen can return an extent that is too
>     long")
>     e54c78a27fcd ("gfs2: Use fs_* functions instead of pr_* function where we
>     can")
>     ed17545d01e4 ("GFS2: Allow glocks to be unlocked after withdraw")
> 
> v3.18.133: Failed to apply! Possible dependencies:
>     0d1c7ae9d849 ("GFS2: Prevent BUG from occurring when normal Withdraws
>     occur")
>     281b4952d185 ("gfs2: Rename bitmap.bi_{len => bytes}")
>     2e60d7683c8d ("GFS2: update freeze code to use freeze/thaw_super on all
>     nodes")
>     3cdcf63ed2d1 ("GFS2: use kvfree() instead of open-coding it")
>     3e11e5304150 ("GFS2: ignore unlock failures after withdraw")
>     471f3db2786b ("gfs2: change gfs2 readdir cookie")
>     9862ca056e65 ("GFS2: Switch tr_touched to flag in transaction")
>     a3e3213676d8 ("gfs2: fix shadow warning in gfs2_rbm_find()")
>     dc8fbb03dcd6 ("GFS2: gfs2_free_extlen can return an extent that is too
>     long")
>     e54c78a27fcd ("gfs2: Use fs_* functions instead of pr_* function where we
>     can")
>     ed17545d01e4 ("GFS2: Allow glocks to be unlocked after withdraw")
> 
> 
> How should we proceed with this patch?
> 
> --
> Thanks,
> Sasha

Hi Sasha,

We have found problems with the "gfs2: Fix loop in gfs2_rbm_find (2)" patch,
so for now we would like to revert the patch it's trying to fix, which is
"gfs2: Fix loop in gfs2_rbm_find" (the original).

Andreas Gruenbacher just sent a revert request for the broken patch to Linus,
so we should just delete "gfs2: Fix loop in gfs2_rbm_find (2)" until we can
get a proper replacement and test it thoroughly.

Regards,

Bob Peterson



  reply	other threads:[~2019-01-30 20:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-24 15:57 [Cluster-devel] [PATCH] gfs2: Fix loop in gfs2_rbm_find (2) Andreas Gruenbacher
2019-01-24 17:43 ` Bob Peterson
2019-01-24 18:32   ` Bob Peterson
2019-01-29  0:35 ` Sasha Levin
2019-01-30 20:39   ` Bob Peterson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-01-31 14:42 Andreas Gruenbacher
2019-02-02 14:38 ` Sasha Levin

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=631177443.68537540.1548880776738.JavaMail.zimbra@redhat.com \
    --to=rpeterso@redhat.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;
as well as URLs for NNTP newsgroup(s).