From: Venkat Yekkirala <vyekkirala@trustedcs.com>
To: netdev@vger.kernel.org, selinux@tycho.nsa.gov
Cc: jmorris@namei.org, sds@tycho.nsa.gov, tjaeger@cse.psu.edu
Subject: [PATCH 00/10] MLSXFRM-v02: Repost patchset with updates
Date: Tue, 18 Jul 2006 12:24:02 -0500 [thread overview]
Message-ID: <44BD1932.90605@trustedcs.com> (raw)
The following are the changes included in this patch set (relative to 2.6.18-rc1-mm2)
as compared to the previous posting:
- Correct use of BUG_ON (per James' and Stephen's comments)
- security_sid_mls_copy: check context with policydb_context_isvalid (Stephen)
- sk_getsecid: do away with extracting isec (Stephen)
- Do away with extracting isec in rcv_skb and postroute_last hooks (Stephen)
- Drop useless printk invocations (Stephen)
- Better description of the xfrm_decode_session hook in security.h
- Nicer function naming; security_sk_classify_flow, security_skb_classify_flow (David)
NOTE: Also added a new LSM hook req_classify_flow (reluctantly since I wasn't able to
just copy the secid from the request_sock to the flow in include/linux/security.h itself
due to "incomplete datatype" compilation errors related to the inaccessibility of the
request_sock definition in security.h in a clean way; would welcome suggestions in this regard).
reply other threads:[~2006-07-18 17:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=44BD1932.90605@trustedcs.com \
--to=vyekkirala@trustedcs.com \
--cc=jmorris@namei.org \
--cc=netdev@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=tjaeger@cse.psu.edu \
/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).