From: Justin Banks <justinb@bakbone.com>
To: linux-kernel@vger.kernel.org
Subject: security module question
Date: Tue, 4 Aug 2009 16:06:32 -0600 [thread overview]
Message-ID: <20090804220632.GG26133@bleen> (raw)
Hello - I'm trying to implement a security module that will allow or
disallow writes on files by byte ranges. Is there a way to use
inode_permission() to do this, or is there an alternative route I should
take? It doesn't look like inode_permission() will give me the data I
need (offset + length of write).
Also, is there a security module that will examine data being written
for certain patterns or content?
Please CC: me on responses. I used to be subscribed, but the traffic was
just too much.
-justinb
--
Justin Banks
BakBone Software
justinb@bakbone.com
next reply other threads:[~2009-08-04 22:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 22:06 Justin Banks [this message]
2009-08-05 2:02 ` security module question James Morris
2009-08-06 18:38 ` Eric Paris
2009-08-06 18:45 ` Shaya Potter
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=20090804220632.GG26133@bleen \
--to=justinb@bakbone.com \
--cc=linux-kernel@vger.kernel.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