public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Lachlan McIlroy <lachlan@sgi.com>
To: David Chinner <dgc@sgi.com>
Cc: xfs-dev@sgi.com, xfs@oss.sgi.com
Subject: Re: Review: Reduce in-core superblock lock contention near ENOSPC
Date: Fri, 01 Dec 2006 20:12:17 +0000	[thread overview]
Message-ID: <45708CA1.5090100@sgi.com> (raw)
In-Reply-To: <20061201004112.GW37654165@melbourne.sgi.com>

David Chinner wrote:
> On Fri, Dec 01, 2006 at 09:38:11AM +1100, David Chinner wrote:
> 
>>On Thu, Nov 30, 2006 at 06:03:40PM +0000, Lachlan McIlroy wrote:
>>
>>
>>>These changes wouldn't apply cleanly to tot (3 hunks failed in
>>>xfs_mount.c) but I couldn't see why.
>>
>>Whitespace issue? Try setting:
>>
>>$ export QUILT_PATCH_OPTS="--ignore-whitespace"
>>
>>I'll apply the patch to a separate tree and see if I hit the same
>>problem....
> 
> 
> I see the problem - the next patch I am going to send out for
> review which is earlier in my series....
> 
> The growfs fix changes the delta parameter to xfs_icsb_modify_counters()
> from int to int64_t, and that is why the hunks don't apply.
> 
> The attached patch should apply (with a 6 line offset to most hunks).
> 

That's even worse - now it loses track of which file it's patching.

[lachlan@linux (2.6.x-xfs)2.6.x-xfs]$ patch -p1 -l -i ENOSPC.patch.eml
patching file fs/xfs/xfs_mount.c
Hunk #2 succeeded at 543 (offset 5 lines).
Hunk #3 succeeded at 1485 (offset 6 lines).
Hunk #4 succeeded at 1523 (offset 6 lines).
Hunk #5 succeeded at 1736 (offset 6 lines).
Hunk #6 succeeded at 1758 (offset 6 lines).
Hunk #7 succeeded at 1794 (offset 6 lines).
Hunk #8 succeeded at 1901 (offset 6 lines).
Hunk #9 succeeded at 2021 (offset 6 lines).
Hunk #10 succeeded at 2060 (offset 6 lines).
Hunk #11 FAILED at 2087.
1 out of 11 hunks FAILED -- saving rejects to file fs/xfs/xfs_mount.c.rej
missing header for unified diff at line 256 of patch
can't find file to patch at input line 256
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|               break;
|
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
3 out of 3 hunks ignored
patching file fs/xfs/xfs_mount.h

It seems to have a problem with line 256 of the patch:

@@ -2081,7 +2121,7 @@ again:          <---- line 256
  		lcounter = icsbp->icsb_ifree;
  		lcounter += delta;
  		if (unlikely(lcounter < 0))
-			goto slow_path;
+			goto balance_counter;
  		icsbp->icsb_ifree = lcounter;
  		break;

I can't see what's wrong.  Don't sweat over it - it's not that important
now that the review is done.  I'll leave it to you to merge it with tot.

Lachlan

  reply	other threads:[~2006-12-01 20:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-23  4:41 Review: Reduce in-core superblock lock contention near ENOSPC David Chinner
2006-11-30 18:03 ` Lachlan McIlroy
2006-11-30 22:38   ` David Chinner
2006-12-01  0:41     ` David Chinner
2006-12-01 20:12       ` Lachlan McIlroy [this message]
2006-12-01 19:22     ` Lachlan McIlroy
2006-12-03 23:49       ` David Chinner
2006-12-05 11:46         ` Klaus Strebel
2006-12-05 21:55           ` David Chinner
2006-12-06  8:43             ` Lachlan McIlroy
2006-12-08  5:16               ` David Chinner

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=45708CA1.5090100@sgi.com \
    --to=lachlan@sgi.com \
    --cc=dgc@sgi.com \
    --cc=xfs-dev@sgi.com \
    --cc=xfs@oss.sgi.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