From: "Ahmed S. Darwish" <darwish.07@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: casey@schaufler-ca.com, viro@zeniv.linux.org.uk
Subject: Rule parsing from a virtual FS write() syscall
Date: Wed, 24 Oct 2007 13:00:43 +0200 [thread overview]
Message-ID: <20071024110043.GA5297@Ahmed> (raw)
Hi all,
In SMACK, some rules are written to a virtual fs file named
"cipso".
Rule format is
label level[/cat[,cat]]
Under high I/O load we don't recieve the whole rule in one shot.
This means that sometimes the write() operation begins from the
middle of the rule. Under some conditions, the first rule _letter_
was only recieved while others were recieved in remaining write()
calls.
Current SMACK versions don't assume fragmented input like above
cases. This means that sometimes bogus rules that does not
represent users' intent got created.
What is the best way to parse a rule in such hard coditions?
Regards,
--
Ahmed S. Darwish
HomePage: http://darwish.07.googlepages.com
Blog: http://darwish-07.blogspot.com
reply other threads:[~2007-10-24 11:01 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=20071024110043.GA5297@Ahmed \
--to=darwish.07@gmail.com \
--cc=casey@schaufler-ca.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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