linux-kernel - Re: inotify fixes in stable

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: <20080310215755.7e920738@mjolnir.drzeus.cx>
Date:	Mon, 10 Mar 2008 21:57:55 +0100
From:	Pierre Ossman <drzeus-list@...eus.cx>
To:	Greg KH <greg@...ah.com>
Cc:	LKML <linux-kernel@...r.kernel.org>, Nick Piggin <npiggin@...e.de>
Subject: Re: inotify fixes in stable

On Mon, 10 Mar 2008 13:31:16 -0700
Greg KH <greg@...ah.com> wrote:

> On Mon, Mar 10, 2008 at 08:36:58PM +0100, Pierre Ossman wrote:
> > 
> > The system is an OpenSuse 10.3 system, so 2.6.22.y would be the
> > interesting one. I'll see if I can get a custom kernel in there (I've
> > been unable to reproduce the problem outside a production
> > environment).
> 
> 2.6.22.y is no longer being released by me, so it isn't interesting to
> me at all :)
> 

Oh? You made a release just 13 days ago, so I figured you were still giving it some love.

> What about 2.6.24?  Is this still an issue there?

Judging from the kernel bugzilla, it would seem so.

But in my specific case, the guy on site was going to try an updated kernel from Suse's build system. I'll probably now the results tomorrow or the day after that.

Rgds
-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  PulseAudio, core developer          http://pulseaudio.org
  rdesktop, core developer          http://www.rdesktop.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/