From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] gfs2: Fix extended attribute readahead optimization
Date: Thu, 18 Aug 2016 13:06:19 -0400 (EDT) [thread overview]
Message-ID: <1383699653.5806004.1471539979111.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1471535523-15060-1-git-send-email-agruenba@redhat.com>
----- Original Message -----
| Commit 39b0555f didn't check for a failing bio_add_page in
| gfs2_submit_bhs. This could cause I/O requests to get lost, and the
| affected buffer heads to stay locked forever. Fix that by submitting
| the current bio and allocating another one when bio_add_page fails. (It
| is guaranteed that we can at least add one page to a bio.)
|
| Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
| ---
| fs/gfs2/meta_io.c | 35 +++++++++++++++++++----------------
| 1 file changed, 19 insertions(+), 16 deletions(-)
Hi,
Thanks. This is now applied to the for-next branch of the linux-gfs2 tree:
https://git.kernel.org/cgit/linux/kernel/git/gfs2/linux-gfs2.git/commit/fs/gfs2?h=for-next&id=23e5671a79be00b2f1c895aa93ff40fb75a4647e
Regards,
Bob Peterson
Red Hat File Systems
next prev parent reply other threads:[~2016-08-18 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 15:52 [Cluster-devel] [PATCH] gfs2: Fix extended attribute readahead optimization Andreas Gruenbacher
2016-08-18 17:06 ` Bob Peterson [this message]
2016-08-18 17:18 ` Andreas Gruenbacher
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=1383699653.5806004.1471539979111.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.