From: Waiman Long <longman@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Dave Chinner <dchinner@redhat.com>
Subject: Re: [PATCH 2/2] xfs: Use wake_q for waking up log space waiters
Date: Sun, 26 Aug 2018 17:02:44 -0400 [thread overview]
Message-ID: <36d1f3f5-9a4a-2511-4dce-c3ae30022d4a@redhat.com> (raw)
In-Reply-To: <bbdaf330-ce6b-bc53-eb97-93b34359bd3d@redhat.com>
On 08/24/2018 05:54 PM, Waiman Long wrote:
> On 08/23/2018 08:30 PM, Dave Chinner wrote:
>>
>> That's racy. You can't drop the spin lock between
>> xlog_grant_head_wake() and xlog_grant_head_wait(), because
>> free_bytes is only valid while while the spinlock is held. Same for
>> the "wake_all" variable you added. i..e. while waking up the
>> waiters, we could have run out of space again and had more tasks
>> queued, or had the AIL tail move and now have space available.
>> Either way, we can do the wrong thing because we dropped the lock
>> and free_bytes and wake_all are now stale and potentially incorrect.
>>
>>> @@ -1068,6 +1088,7 @@
>>> {
>>> struct xlog *log = mp->m_log;
>>> int free_bytes;
>>> + DEFINE_WAKE_Q(wakeq);
>>>
>>> if (XLOG_FORCED_SHUTDOWN(log))
>>> return;
>>> @@ -1077,8 +1098,11 @@
>>>
>>> spin_lock(&log->l_write_head.lock);
>>> free_bytes = xlog_space_left(log, &log->l_write_head.grant);
>>> - xlog_grant_head_wake(log, &log->l_write_head, &free_bytes);
>>> + xlog_grant_head_wake(log, &log->l_write_head, &free_bytes,
>>> + &wakeq);
>>> spin_unlock(&log->l_write_head.lock);
>>> + wake_up_q(&wakeq);
>>> + wake_q_init(&wakeq);
>> That's another landmine. Just define the wakeq in the context where
>> it is used rather than use a function wide variable that requires
>> reinitialisation.
>>
>>> }
>>>
>>> if (!list_empty_careful(&log->l_reserve_head.waiters)) {
>>> @@ -1086,8 +1110,10 @@
>>>
>>> spin_lock(&log->l_reserve_head.lock);
>>> free_bytes = xlog_space_left(log, &log->l_reserve_head.grant);
>>> - xlog_grant_head_wake(log, &log->l_reserve_head, &free_bytes);
>>> + xlog_grant_head_wake(log, &log->l_reserve_head, &free_bytes,
>>> + &wakeq);
>>> spin_unlock(&log->l_reserve_head.lock);
>>> + wake_up_q(&wakeq);
>>> }
>>> }
>> Ok, what about xlog_grant_head_wake_all()? You didn't convert that
>> to use wake queues, and so that won't remove tickets for the grant
>> head waiter list, and so those tasks will never get out of the new
>> inner loop you added to xlog_grant_head_wait(). That means
>> filesystem shutdowns will just hang the filesystem and leave it
>> unmountable. Did you run this through fstests?
>>
>> Cheers,
>>
>> Dave
> OK, I need more time to think about some of the questions that you
> raise. Thanks for reviewing the patch.
>
> Cheers,
> Longman
Thanks for your detailed review of the patch. I now have a better
understanding of what should and shouldn't be done. I have sent out a
more conservative v2 patchset which, hopefully, can address the concerns
that you raised.
Cheers,
Longman
prev parent reply other threads:[~2018-08-27 0:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 16:26 [PATCH 0/2] xfs: Use wake_q for waking up log space waiters Waiman Long
2018-08-23 16:26 ` [PATCH 1/2] sched/core: Export wake_q functions to kernel modules Waiman Long
2018-08-23 16:26 ` [PATCH 2/2] xfs: Use wake_q for waking up log space waiters Waiman Long
2018-08-24 0:30 ` Dave Chinner
2018-08-24 21:54 ` Waiman Long
2018-08-26 21:02 ` Waiman Long [this message]
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=36d1f3f5-9a4a-2511-4dce-c3ae30022d4a@redhat.com \
--to=longman@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=dchinner@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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).