From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH v3 03/14] GFS2: Protect log tail calculations with inside locks
Date: Fri, 30 Oct 2015 11:14:02 +0000 [thread overview]
Message-ID: <563350FA.10300@redhat.com> (raw)
In-Reply-To: <1445542222-30672-4-git-send-email-rpeterso@redhat.com>
Hi,
sd_log_tail should be protected by sdp->sd_log_flush_lock, so is that
not happening for some reason?
Steve.
On 22/10/15 20:30, Bob Peterson wrote:
> This patch moves the variables "old_tail" and "wrap" in function
> gfs2_ail2_empty_one inside the protective spin_lock so they can't
> be moved by another process. If the calculations aren't protected,
> the log's tail may not be properly pulled, which eventually makes
> it seem like there isn't enough room in the journal for more
> transactions. This results in a hang where GFS2 repeatedly does
> log flushes without making any progress.
>
> Signed-off-by: Bob Peterson <rpeterso@redhat.com>
> ---
> fs/gfs2/log.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/fs/gfs2/log.c b/fs/gfs2/log.c
> index 536e7a6..18959de 100644
> --- a/fs/gfs2/log.c
> +++ b/fs/gfs2/log.c
> @@ -277,11 +277,12 @@ static void gfs2_ail2_empty_one(struct gfs2_sbd *sdp, struct gfs2_trans *tr)
> static void ail2_empty(struct gfs2_sbd *sdp, unsigned int new_tail)
> {
> struct gfs2_trans *tr, *safe;
> - unsigned int old_tail = sdp->sd_log_tail;
> - int wrap = (new_tail < old_tail);
> - int a, b, rm;
> + unsigned int old_tail;
> + int wrap, a, b, rm;
>
> spin_lock(&sdp->sd_ail_lock);
> + old_tail = sdp->sd_log_tail;
> + wrap = (new_tail < old_tail);
>
> list_for_each_entry_safe(tr, safe, &sdp->sd_ail2_list, tr_list) {
> a = (old_tail <= tr->tr_first);
next prev parent reply other threads:[~2015-10-30 11:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 19:30 [Cluster-devel] [GFS2 PATCH v3 00/14] Fourteen patches related to file unlink->delete->new Bob Peterson
2015-10-22 19:30 ` [Cluster-devel] [GFS2 PATCH v3 01/14] GFS2: Update master statfs buffer with sd_statfs_spin locked Bob Peterson
2015-10-30 10:49 ` Steven Whitehouse
2015-10-22 19:30 ` [Cluster-devel] [GFS2 PATCH v3 02/14] GFS2: Allow fail_gunlock3 to set the free_vfs_inode bit Bob Peterson
2015-10-30 11:07 ` Steven Whitehouse
2015-10-22 19:30 ` [Cluster-devel] [GFS2 PATCH v3 03/14] GFS2: Protect log tail calculations with inside locks Bob Peterson
2015-10-30 11:14 ` Steven Whitehouse [this message]
2015-10-22 19:30 ` [Cluster-devel] [GFS2 PATCH v3 04/14] GFS2: Wait for iopen glock dequeues Bob Peterson
2015-10-30 11:14 ` Steven Whitehouse
2015-10-22 19:30 ` [Cluster-devel] [GFS2 PATCH v3 05/14] GFS2: Reintroduce a timeout in function gfs2_gl_hash_clear Bob Peterson
2015-10-30 11:18 ` Steven Whitehouse
2015-10-22 19:30 ` [Cluster-devel] [GFS2 PATCH v3 06/14] GFS2: Prevent gl_delete work for re-used inodes Bob Peterson
2015-10-30 11:23 ` Steven Whitehouse
2015-10-22 19:30 ` [Cluster-devel] [GFS2 PATCH v3 07/14] GFS2: Truncate address space mapping when deleting an inode Bob Peterson
2015-10-30 11:27 ` Steven Whitehouse
2015-10-22 19:30 ` [Cluster-devel] [GFS2 PATCH v3 08/14] GFS2: Don't filter out I_FREEING inodes anymore Bob Peterson
2015-10-30 11:32 ` Steven Whitehouse
2015-12-10 16:29 ` Bob Peterson
2015-10-22 19:30 ` [Cluster-devel] [GFS2 PATCH v3 09/14] GFS2: generalize gfs2_check_blk_type Bob Peterson
2015-10-22 19:30 ` [Cluster-devel] [GFS2 PATCH v3 10/14] GFS2: Change from tr_touched to tr_bufs Bob Peterson
2015-10-30 11:47 ` Steven Whitehouse
2015-10-22 19:30 ` [Cluster-devel] [GFS2 PATCH v3 11/14] GFS2: Add new function gfs2_inode_lookup_for_del Bob Peterson
2015-10-22 19:30 ` [Cluster-devel] [GFS2 PATCH v3 12/14] gfs2: Remove unused param non_block from gfs2_inode_lookup Bob Peterson
2015-10-22 19:30 ` [Cluster-devel] [GFS2 PATCH v3 13/14] GFS2: Hold onto iopen glock longer when dinode creation fails Bob Peterson
2015-10-22 19:30 ` [Cluster-devel] [GFS2 PATCH v3 14/14] GFS2: Rework gfs2_evict_inode to prevent collisions with openers Bob Peterson
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=563350FA.10300@redhat.com \
--to=swhiteho@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).