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

Date:	Thu, 09 Jun 2011 09:22:02 +0200
From:	Stefan Priebe - Profihost AG <s.priebe@...fihost.ag>
To:	Dave Chinner <david@...morbit.com>
CC:	Steven Rostedt <rostedt@...dmis.org>, Theodore Tso <tytso@....EDU>,
	david@...g.hm, linux-kernel@...r.kernel.org
Subject: Re: XFS problem in 2.6.32

> If you want someone to blame, then point the fingers at me, not
> RedHat or RedHat's processes - RedHat is not involved in the
> processes and decisions as to what fixes
> get backported into the community stable trees. How that is done
> is mainly dictated by available resources, which are generally
> scarce. We push bug fixes into the lastest kernel release, and if
> known to be needed for stable series they get pushed back via the
> stable queues.
I'm really sorry that my post goes that way. It was never my intention 
to blame anybody for anything.

I just didn't know the things work and was just wondering that Redhat 
had a fix which wasn't pushed back to vanilla 2.6.32. But i also didn't 
know that the xfs codebase is totally different due to other backports.

I'm sorry.

Stefan
--
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/