From: Simon Horman <horms@verge.net.au>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
lvs-devel@vger.kernel.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org,
Wensong Zhang <wensong@linux-vs.org>,
Julian Anastasov <ja@ssi.bg>,
Sasha Levin <levinsasha928@gmail.com>,
stable@vger.kernel.org
Subject: Re: [PATCH 2/2] netfilter: ipvs: use GFP_KERNEL allocation where possible
Date: Mon, 23 Apr 2012 23:29:36 +0900 [thread overview]
Message-ID: <20120423142935.GC19734@verge.net.au> (raw)
In-Reply-To: <20120423142327.GB32269@kroah.com>
On Mon, Apr 23, 2012 at 07:23:27AM -0700, Greg KH wrote:
> On Mon, Apr 23, 2012 at 09:17:08PM +0900, Simon Horman wrote:
> > From: Sasha Levin <levinsasha928@gmail.com>
> >
> > Use GFP_KERNEL instead of GFP_ATOMIC when registering an ipvs protocol.
> >
> > This is safe since it will always run from a process context.
> >
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Sasha Levin <levinsasha928@gmail.com>
> > Acked-by: Julian Anastasov <ja@ssi.bg>
> > Signed-off-by: Simon Horman <horms@verge.net.au>
> > ---
> > net/netfilter/ipvs/ip_vs_proto.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
>
> How does this patch meet the Documentation/stable_kernel_rules.txt
> requirements?
Sorry about that, I would like to withdraw this change from
consideration for stable.
next prev parent reply other threads:[~2012-04-23 14:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 12:17 [GIT PULL net] IPVS Simon Horman
2012-04-23 12:17 ` [PATCH 1/2] netfilter: ipvs: Verify that IP_VS protocol has been registered Simon Horman
2012-04-23 12:17 ` [PATCH 2/2] netfilter: ipvs: use GFP_KERNEL allocation where possible Simon Horman
2012-04-23 14:23 ` Greg KH
2012-04-23 14:29 ` Simon Horman [this message]
2012-04-23 12:44 ` [GIT PULL net] IPVS Simon Horman
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=20120423142935.GC19734@verge.net.au \
--to=horms@verge.net.au \
--cc=gregkh@linuxfoundation.org \
--cc=ja@ssi.bg \
--cc=levinsasha928@gmail.com \
--cc=lvs-devel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=stable@vger.kernel.org \
--cc=wensong@linux-vs.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).