linux-kernel - Re: [PATCH 3/7] SLIM main patch

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20060824135803.GA32764@sergelap.austin.ibm.com>
Date:	Thu, 24 Aug 2006 08:58:03 -0500
From:	"Serge E. Hallyn" <serue@...ibm.com>
To:	Benjamin LaHaise <bcrl@...ck.org>
Cc:	"Serge E. Hallyn" <sergeh@...ibm.com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>, kjhall@...ibm.com,
	linux-kernel <linux-kernel@...r.kernel.org>,
	LSM ML <linux-security-module@...r.kernel.org>,
	David Safford <safford@...ibm.com>,
	Mimi Zohar <zohar@...ibm.com>
Subject: Re: [PATCH 3/7] SLIM main patch

Quoting Benjamin LaHaise (bcrl@...ck.org):
> On Thu, Aug 24, 2006 at 08:32:48AM -0500, Serge E. Hallyn wrote:
> > > You also have to deal with existing mmap() mappings and outstanding I/O.
> > 
> > That she does.
> 
> Outstanding I/O is not revoked.  Any in-progress I/O continues.

Yes, that should have read:

> > > You also have to deal with existing mmap() mappings
> > 
> > That she does.
> >
> > > and outstanding I/O.

Still not certain this is needed.  If you were able to write data to a
pipe, then even though data may be in the buffer, the other end
shouldn't be able to read it if it's own level were changed.

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