linux-kernel - Re: [GIT] Fix SELinux memory leak regression for 2.6.27

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] [day] [month] [year] [list]

Date:	Thu, 4 Sep 2008 08:53:50 +1000 (EST)
From:	James Morris <jmorris@...ei.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
cc:	linux-kernel@...r.kernel.org, Eric Paris <eparis@...hat.com>,
	Stephen Smalley <sds@...ho.nsa.gov>
Subject: Re: [GIT] Fix SELinux memory leak regression for 2.6.27

On Wed, 3 Sep 2008, Linus Torvalds wrote:

> 
> 
> On Wed, 3 Sep 2008, James Morris wrote:
> > On Wed, 3 Sep 2008, James Morris wrote:
> > 
> > > This is causing recent Fedora systems to die a slow and painful death.  
> > > Please pull.
> > 
> > Further review has raised an issue with this patch, an updated version 
> > should be available soon.
> 
> Ahh, that also explains why the branch isn't there any more. Thanks,

A more correct version of the patch is now up, please pull:

The following changes since commit ec0c15afb41fd9ad45b53468b60db50170e22346:
  Linus Torvalds (1):
        Split up PIT part of TSC calibration from native_calibrate_tsc

are available in the git repository at:

  
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/security-testing-2.6 for-linus

Eric Paris (1):
      SELinux: memory leak in security_context_to_sid_core

 security/selinux/ss/services.c |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)





-- 
James Morris
<jmorris@...ei.org>
--
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/