netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Wang <wangyun@linux.vnet.ibm.com>
To: LKML <linux-kernel@vger.kernel.org>,
	linux-raid@vger.kernel.org, linux-mm@kvack.org,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	netfilter@vger.kernel.org, coreteam@netfilter.org,
	netfilter-devel@vger.kernel.org
Cc: neilb@suse.de, catalin.marinas@arm.com,
	David Miller <davem@davemloft.net>,
	kaber@trash.net, pablo@netfilter.org,
	"paulmck@linux.vnet.ibm.com" <paulmck@linux.vnet.ibm.com>
Subject: [PATCH 0/3] raid, kmemleak, netfilter: replace list_for_each_continue_rcu with new interface
Date: Fri, 17 Aug 2012 12:33:22 +0800	[thread overview]
Message-ID: <502DC992.4040304@linux.vnet.ibm.com> (raw)
In-Reply-To: <502CB91E.4050304@linux.vnet.ibm.com>

From: Michael Wang <wangyun@linux.vnet.ibm.com>

This patch set will replace the list_for_each_continue_rcu with the new
interface list_for_each_entry_continue_rcu, so we could remove the old
one later.

Changed:
	raid:		in "next_active_rdev"
	kmemleak:	in "kmemleak_seq_next"
	netfilter:	in "nf_iterate"	

Tested:
	raid:
		mdadm command with an internal bitmap.
	kmemleak:
		enable kmemleak and check the info it captured.
	netfilter:
		add rule to iptables and check result by ping.
		nfqnl_test which is a test utility of libnetfilter_queue.

	All testing are using printk to make sure the code we want test
	was invoked.

Signed-off-by: Michael Wang <wangyun@linux.vnet.ibm.com>
---
 drivers/md/bitmap.c  |    9 +++------
 mm/kmemleak.c        |    6 ++----
 net/netfilter/core.c |   11 +++++++----
 3 files changed, 12 insertions(+), 14 deletions(-)


--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

           reply	other threads:[~2012-08-17  4:33 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <502CB91E.4050304@linux.vnet.ibm.com>]

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=502DC992.4040304@linux.vnet.ibm.com \
    --to=wangyun@linux.vnet.ibm.com \
    --cc=catalin.marinas@arm.com \
    --cc=coreteam@netfilter.org \
    --cc=davem@davemloft.net \
    --cc=kaber@trash.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=netfilter@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=paulmck@linux.vnet.ibm.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).