linux-ext4 - Re: [patch 1/1] ext4-fix-dirty-extent-when-origin-leaf-extent-reac.patch

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: <20110927193523.GB3309@thunk.org>
Date:	Tue, 27 Sep 2011 15:35:23 -0400
From:	Ted Ts'o <tytso@....edu>
To:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Cc:	MaoXiaoyun <tinnycloud@...mail.com>, linux-ext4@...r.kernel.org,
	xen devel <xen-devel@...ts.xensource.com>, jack@...e.cz
Subject: Re: [patch 1/1]
 ext4-fix-dirty-extent-when-origin-leaf-extent-reac.patch

On Mon, Sep 26, 2011 at 10:28:08AM -0400, Konrad Rzeszutek Wilk wrote:
> >  
> >    Attached is the fix, verified in our env. 
> 
> So.. you are asking for this upstream git commit to be back-ported
> to 2.6.32, right?

I'm curious --- is there a good reason why Xen users are using an
upstream 2.6.32 kernel?  If they are using a distro kernel, fine, but
then the distro kernel should be providing the support.  But at this
point, 2.6.32 is so positively *ancient* that, I'm personally not
interesting in providing free, unpaid distro support for users who
aren't willing to either (a) pay $$$ and get a supported distro
kernel, or (b) use a much more modern kernel.  At this point, Guest
and Host Xen support is available in 3.0 kernels, so there's really no
excuse, right?

						- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html