From: Chris Wright <chrisw@sous-sol.org>
To: James Morris <jmorris@namei.org>
Cc: "David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, Stephen Smalley <sds@tycho.nsa.gov>,
Eric Paris <eparis@redhat.com>, Patrick McHardy <kaber@trash.net>,
Chris Wright <chrisw@sous-sol.org>
Subject: Re: [PATCH][SECURITY] secmark: nul-terminate secdata
Date: Wed, 2 Aug 2006 11:28:01 -0700 [thread overview]
Message-ID: <20060802182801.GS2654@sequoia.sous-sol.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0607281649440.20690@d.namei>
* James Morris (jmorris@namei.org) wrote:
> cc'd Chris Wright, as this patch seems like a candidate for the stable
> tree.
Would be, but I thought secmark went in post 2.6.17. And I expect Dave
will push this well before 2.6.18.
thanks,
-chris
prev parent reply other threads:[~2006-08-02 18:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 21:00 [PATCH][SECURITY] secmark: nul-terminate secdata James Morris
2006-07-29 1:19 ` Patrick McHardy
2006-07-31 3:47 ` David Miller
2006-08-02 18:28 ` Chris Wright [this message]
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=20060802182801.GS2654@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=davem@davemloft.net \
--cc=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
/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).