linux-kernel - Re: XFS problem in 2.6.32

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]

Date:	Tue, 7 Jun 2011 15:05:56 -0700 (PDT)
From:	david@...g.hm
To:	Stefan Priebe - Profihost AG <s.priebe@...fihost.ag>
cc:	Theodore Tso <tytso@....EDU>, linux-kernel@...r.kernel.org
Subject: Re: XFS problem in 2.6.32

On Tue, 7 Jun 2011, Stefan Priebe - Profihost AG wrote:

>> whoever the maintainer of the -stable/-longterm tree is (be it an
>> individual or a team employeed by some comapny) then looks at the patch
>> and considers backporting it (if it's too hard, or to intrusive, they
>> may decide not to).
> So i have to contact Greg Kohan from SUSE directly?

if he's the maintainer of the longterm tree, then yes, you would contact 
him or the stable mailing list.

>> the idea of the lonterm kernels is that organizations need to maintain a
>> kernel for a long time due to commitments that they have made (Debian
>> doesn't want to change the kernel it ships in a stable version, RedHat
>> doesn't want to change the kernel version in a RHEL release, etc), and
>> so they publicly announce this so that anyone else wanting to use the
>> same kernel version can share in the work (and therefor everyone can
>> benifit from each other's work)
> That was what i thoght. So a bug like this should get fixed right? Otherwise 
> this makes no sense. Sadly Redhat has ported the fix back in his RHEL 6 
> 2.6.32 kernel but they haven't send the patch to stable / vanilla team.

it depends on how intrusive/disruptive the patch is.

David Lang
--
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/