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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 8 Jun 2011 09:30:37 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Theodore Tso <tytso@....EDU>
Cc:	Stefan Priebe - Profihost AG <s.priebe@...fihost.ag>,
	david@...g.hm, linux-kernel@...r.kernel.org
Subject: Re: XFS problem in 2.6.32

On Tue, Jun 07, 2011 at 11:28:59PM -0400, Theodore Tso wrote:

Ted, you need a new MUA, as it reads horribly in mutt.

> 
> Not all distributions will participate in the maintenance stable tree.  Red Hat for example is probably worried about people  (specifically, Oracle) taking their kernel expertise "for free" and bidding it against them.  So it doesn't surprise me that they aren't submitting patches to the stable tree.  After all, they would like you to purchase a support contract if you want to get high quality, supported kernel.   Why should they give that work away for free?  After all, their salaried developers have to get paid somehow.  Others will contribute work in the hopes that other people will also contribute fixes back, but of course nothing forces Red Hat to do this.
> 

As a Red Hat employee, I must speak against this. I have *never* been
told to keep something from stable. In fact, I've always been encouraged
to push to stable. But it is usually the individual engineer's
responsibility to get a patch into stable. If something was missed, it
was more the fault of that individual engineer that made the fix than
Red Hat.

Ask Greg, I'm constantly sending stable patches to him.

-- Steve

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