From: David Miller <davem@davemloft.net>
To: pmoore@redhat.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] netlabel: correctly list all the static label mappings
Date: Thu, 07 Mar 2013 16:21:19 -0500 (EST) [thread overview]
Message-ID: <20130307.162119.846409617201380362.davem@davemloft.net> (raw)
In-Reply-To: <20130306214524.4965.59796.stgit@localhost>
From: Paul Moore <pmoore@redhat.com>
Date: Wed, 06 Mar 2013 16:45:24 -0500
> When we have a large number of static label mappings that spill across
> the netlink message boundary we fail to properly save our state in the
> netlink_callback struct which causes us to repeat the same listings.
> This patch fixes this problem by saving the state correctly between
> calls to the NetLabel static label netlink "dumpit" routines.
>
> Signed-off-by: Paul Moore <pmoore@redhat.com>
Applied and queued up for -stable, thanks.
> Cc: stable@vger.kernel.org
Please just ask me to queue up networking fixes for stable, rather
than CC:'ing it to stable.
Thanks.
next prev parent reply other threads:[~2013-03-07 21:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 21:45 [PATCH] netlabel: correctly list all the static label mappings Paul Moore
2013-03-07 21:21 ` David Miller [this message]
2013-03-07 21:26 ` Paul Moore
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=20130307.162119.846409617201380362.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=pmoore@redhat.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).