DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:date:to:cc:subject:message-id:mime-version:content-type:content-disposition:user-agent:from;
        b=p3FU/i/kojT0CTzwjkUCr9o3taUdx7xXe6CMYFsvtlHQbhyxmZEkPQcO5b3yTydNIz09t1hjVidE7eNhwvFaygXZ8UgQCk+ujQ7lpP5atEQpcXFKhw05S8IpBcKWDUSPCpNw9hZkBotTXcLorcS6JfKJRBPx6xeal5eg9tZqG9s=
Date: Wed, 24 Oct 2007 13:00:43 +0200
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
Message-ID: <20071024110043.GA5297@Ahmed>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.11
From: "Ahmed S. Darwish" <darwish.07@gmail.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 973
Lines: 32

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/