All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jeff Layton <jlayton@redhat.com>
Subject: linux-next: manual merge of the nfsd tree with Linus' tree
Date: Wed, 3 Apr 2013 11:01:08 +1100	[thread overview]
Message-ID: <20130403110108.e669ebda4b5a88550d96a485@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]

Hi,

Today's linux-next merge of the nfsd tree got a conflict in
fs/nfsd/nfscache.c between commit a517b608fa3d ("nfsd: only unhash DRC
entries that are in the hashtable") from Linus' tree and commit
559aa350587e ("nfsd: track memory utilization in the DRC") from the nfsd
tree.

I fixed it up (see below) and can carry the fix as necessary (no action
is required).

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

diff --cc fs/nfsd/nfscache.c
index ca05f6d,3af1767..0000000
--- a/fs/nfsd/nfscache.c
+++ b/fs/nfsd/nfscache.c
@@@ -100,12 -130,14 +130,15 @@@ nfsd_reply_cache_alloc(void
  static void
  nfsd_reply_cache_free_locked(struct svc_cacherep *rp)
  {
- 	if (rp->c_type == RC_REPLBUFF)
+ 	if (rp->c_type == RC_REPLBUFF && rp->c_replvec.iov_base) {
+ 		drc_mem_usage -= rp->c_replvec.iov_len;
  		kfree(rp->c_replvec.iov_base);
+ 	}
 -	hlist_del(&rp->c_hash);
 +	if (!hlist_unhashed(&rp->c_hash))
 +		hlist_del(&rp->c_hash);
  	list_del(&rp->c_lru);
  	--num_drc_entries;
+ 	drc_mem_usage -= sizeof(*rp);
  	kmem_cache_free(drc_slab, rp);
  }
  

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

             reply	other threads:[~2013-04-03  0:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-03  0:01 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-07-30  1:23 linux-next: manual merge of the nfsd tree with Linus' tree Stephen Rothwell
2015-07-30  1:35 ` Trond Myklebust
2015-07-30  2:12   ` J. Bruce Fields
2014-01-29  1:42 Stephen Rothwell
2013-03-01  0:49 Stephen Rothwell
2011-01-06  0:47 Stephen Rothwell

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=20130403110108.e669ebda4b5a88550d96a485@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=bfields@fieldses.org \
    --cc=jlayton@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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 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.