From: Andreas Gruenbacher <agruenba@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andreas Gruenbacher <agruenba@redhat.com>,
gfs2@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Revert "gfs2: Use GL_NOBLOCK flag for non-blocking lookups"
Date: Fri, 2 Feb 2024 17:28:27 +0100 [thread overview]
Message-ID: <20240202162830.1323578-1-agruenba@redhat.com> (raw)
Hello Linus,
please consider pulling the following tag to revert commit "gfs2: Use
GL_NOBLOCK flag for non-blocking lookups". It turns out that the commit has
several issues, and not all of them have a simple fix:
https://lore.kernel.org/gfs2/20240202050230.GA875515@ZenIV/T/
Thanks,
Andreas
The following changes since commit 41bccc98fb7931d63d03f326a746ac4d429c1dd3:
Linux 6.8-rc2 (2024-01-28 17:01:12 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git tags/gfs2-v6.8-rc2-revert
for you to fetch changes up to e9f1e6bb55bea4f8cb48f8f7443bbac99b60d285:
Revert "gfs2: Use GL_NOBLOCK flag for non-blocking lookups" (2024-02-02 17:21:44 +0100)
----------------------------------------------------------------
gfs2: revert this broken commit
----------------------------------------------------------------
Andreas Gruenbacher (1):
Revert "gfs2: Use GL_NOBLOCK flag for non-blocking lookups"
fs/gfs2/dentry.c | 23 +++++++++--------------
fs/gfs2/inode.c | 8 ++++----
2 files changed, 13 insertions(+), 18 deletions(-)
next reply other threads:[~2024-02-02 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 16:28 Andreas Gruenbacher [this message]
2024-02-02 23:37 ` [GIT PULL] Revert "gfs2: Use GL_NOBLOCK flag for non-blocking lookups" pr-tracker-bot
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=20240202162830.1323578-1-agruenba@redhat.com \
--to=agruenba@redhat.com \
--cc=gfs2@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 read-only IMAP folder(s) and NNTP newsgroup(s).