On 1/3/2014 7:17 AM, Jeff Liu wrote:
On 01/03 2014 18:25 PM, Jeff Liu wrote:
On 01/02 2014 08:45, Dave Chinner wrote:
On Wed, Jan 01, 2014 at 10:38:36PM +0800, Jeff Liu wrote:
On 12/30 2013 23:20 PM, Mark Tinguely wrote:
On 12/24/13 06:48, Jeff Liu wrote:
From: Jie Liu<jeff.liu@xxxxxxxxxx>
I can easily to hit a hang up while running fsstress and shutting down
XFS on SSD via the tests below:
As a result, we should handle this situation in xlog_cil_committed().
Signed-off-by: Jie Liu<jeff.liu@xxxxxxxxxx>
fs/xfs/xfs_log_cil.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/xfs/xfs_log_cil.c b/fs/xfs/xfs_log_cil.c
index 5eb51fc..8c7e9c7 100644
@@ -406,6 +406,8 @@ xlog_cil_committed(
+ if (abort)
Hi Jeff, I hope you had a good break,
So you are saying the wakeup in the CIL push error path missing?
I agree with that. But I don't like adding a new wake up to
xlog_cil_committed(), which is after the log buffer is written.
Hi Mark, any particular reason why you don't like this? It would be
great if you could explain why you don't like something up front so
we don't have to guess at your reasons or wait for another round
My concern is consistency, with the patch there will be two paths that
could do the wake up.
Originally, the wakeup happened before the iclog write. With the patch,
if the cil push
sequence successfully wrote it's ticket, woke up the waiters, wrote back
the iclog, and
then had an error writing the iclog, it would wakeup the xc_commit_wait
a second time.
Not too drastic of a problem, because the zeroed commit_lsn will prevent
write of the next cil push. I just prefer to handle the error in the cil
push routine and avoid
a second form of wake up.