[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] selinux_sb_copy_data requires a whole page?

To: Eric Paris <eparis@xxxxxxxxxxxxxx>
Subject: Re: [PATCH] selinux_sb_copy_data requires a whole page?
From: Stephen Smalley <sds@xxxxxxxxxxxxxx>
Date: Fri, 24 Jun 2005 07:56:33 -0400
Cc: James Morris <jmorris@xxxxxxxxxx>, selinux@xxxxxxxxxxxxx
In-reply-to: <1119558154.10817.45.camel@xxxxxxxxxxxxxxxxxxxxx>
Organization: National Security Agency
References: <Xine.LNX.4.44.0506231548050.14587-100000@xxxxxxxxxxxxxxxxxxxxxxxx> <1119558154.10817.45.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: owner-selinux@xxxxxxxxxxxxx

On Thu, 2005-06-23 at 16:22 -0400, Eric Paris wrote:
> This would still (maybe) leave sec info in the buffer after the null
> whereas previously it would have been nulled out.  Do we care?

I don't think so.  fs code should stop on the NUL byte; if it doesn't,
that is a bug in the fs code.

-- 
Stephen Smalley
National Security Agency


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with
the words "unsubscribe selinux" without quotes as the message.

References:
- Re: [PATCH] selinux_sb_copy_data requires a whole page?
  - From: James Morris
- Re: [PATCH] selinux_sb_copy_data requires a whole page?
  - From: Eric Paris

Prev by Date: Re: [PATCH] disallow * and ~ in rules
Next by Date: RE: file contexts and modularity
Previous by thread: Re: [PATCH] selinux_sb_copy_data requires a whole page?
Next by thread: mdadm policy
Index(es):
- Date
- Thread

This mailing list archive is a service of Copilot Consulting.