From: Andreas Gruenbacher <agruenba@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andreas Gruenbacher <agruenba@redhat.com>,
cluster-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: [GIT PULL] gfs2 fixes
Date: Tue, 24 May 2022 21:41:45 +0200 [thread overview]
Message-ID: <20220524194145.884805-1-agruenba@redhat.com> (raw)
Hi Linus,
please consider pulling the following gfs2 fixes for 5.19.
Thank you very much,
Andreas
The following changes since commit d928e8f3af38abc8d2d56d9329a8280f7af5f10e:
Merge tag 'gfs2-v5.18-rc4-fix3' of git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2 (2022-05-13 14:32:53 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git tags/gfs2-v5.18-rc6-fixes
for you to fetch changes up to c360abbb9db298d0548b31e1a86a48ebb157d7cd:
gfs2: Convert function bh_get to use iomap (2022-05-24 21:29:14 +0200)
----------------------------------------------------------------
gfs2 fixes
- Clean up the allocation of glocks that have an address space attached.
- Quota locking fix and quota iomap conversion.
- Fix the FITRIM error reporting.
- Some list iterator cleanups.
----------------------------------------------------------------
Andreas Gruenbacher (1):
gfs2: Explain some direct I/O oddities
Andrew Price (1):
gfs2: Return more useful errors from gfs2_rgrp_send_discards()
Bob Peterson (2):
gfs2: use i_lock spin_lock for inode qadata
gfs2: Convert function bh_get to use iomap
Jakob Koschel (1):
gfs2: replace 'found' with dedicated list iterator variable
Kees Cook (1):
gfs2: Use container_of() for gfs2_glock(aspace)
fs/gfs2/file.c | 4 ++++
fs/gfs2/glock.c | 35 ++++++++++++++++--------------
fs/gfs2/glock.h | 12 +++++++++--
fs/gfs2/main.c | 10 ++++-----
fs/gfs2/meta_io.h | 8 ++++---
fs/gfs2/quota.c | 62 ++++++++++++++++++++++++++++++++----------------------
fs/gfs2/recovery.c | 22 +++++++++----------
fs/gfs2/rgrp.c | 4 ++--
8 files changed, 91 insertions(+), 66 deletions(-)
next reply other threads:[~2022-05-24 19:41 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 19:41 Andreas Gruenbacher [this message]
2022-05-25 2:16 ` [GIT PULL] gfs2 fixes pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2023-11-07 14:21 Andreas Gruenbacher
2023-11-07 20:30 ` Linus Torvalds
2023-11-07 22:18 ` Andreas Grünbacher
2023-11-08 0:04 ` Linus Torvalds
2023-11-07 20:34 ` pr-tracker-bot
2023-09-18 14:34 Andreas Gruenbacher
2023-09-18 20:20 ` pr-tracker-bot
2023-09-05 16:12 Andreas Gruenbacher
2023-09-05 20:14 ` pr-tracker-bot
2023-08-08 12:53 Andreas Gruenbacher
2023-07-04 12:51 Andreas Gruenbacher
2023-07-04 18:59 ` pr-tracker-bot
2023-02-22 12:01 Andreas Gruenbacher
2023-02-22 22:27 ` pr-tracker-bot
2022-12-16 14:33 Andreas Gruenbacher
2022-12-17 14:28 ` pr-tracker-bot
2022-10-09 10:45 Andreas Gruenbacher
2022-10-11 3:43 ` pr-tracker-bot
2022-08-05 20:12 Andreas Gruenbacher
2022-08-06 22:08 ` pr-tracker-bot
2022-05-13 21:07 Andreas Gruenbacher
2022-05-13 21:35 ` Linus Torvalds
2022-05-13 21:38 ` pr-tracker-bot
2022-02-11 17:05 Andreas Gruenbacher
2022-02-11 19:47 ` Linus Torvalds
2022-02-11 21:40 ` Andreas Gruenbacher
2022-02-11 20:05 ` 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=20220524194145.884805-1-agruenba@redhat.com \
--to=agruenba@redhat.com \
--cc=cluster-devel@redhat.com \
--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 NNTP newsgroup(s).