From: "David S. Miller" <davem@redhat.com>
To: jmorris@intercode.com.au
Cc: kuznet@ms2.inr.ac.ru, netdev@oss.sgi.com,
linux-security-module@wirex.com
Subject: Re: [PATCH] LSM networking: tcp hooks for 2.5.42 (7/7)
Date: Tue, 15 Oct 2002 10:41:46 -0700 (PDT) [thread overview]
Message-ID: <20021015.104146.112719962.davem@redhat.com> (raw)
In-Reply-To: <Mutt.LNX.4.44.0210160030350.27676-100000@blackbird.intercode.com.au>
I totally reject all of these LSM networking patches.
The more I read of them the more I hate them.
You have to hide this stuff away so that:
1) I don't read it when I read the normal networking code
2) It doesn't get built into my tree because there is no way
we're going to add all of these nop function calls all over
the stack in the most critical of places
prev parent reply other threads:[~2002-10-15 17:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 14:41 [PATCH] LSM networking: tcp hooks for 2.5.42 (7/7) James Morris
2002-10-15 17:41 ` David S. Miller [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=20021015.104146.112719962.davem@redhat.com \
--to=davem@redhat.com \
--cc=jmorris@intercode.com.au \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-security-module@wirex.com \
--cc=netdev@oss.sgi.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).