linux-ext4 - Re: Ext4 Kernel Crash

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

Message-ID: <20120226121802.GA8600@dinofilaria.home>
Date:	Sun, 26 Feb 2012 14:18:02 +0200
From:	Nanakos Chrysostomos <nanakos@...ed-net.gr>
To:	tytso@....edu
Cc:	linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org
Subject:  Re: Ext4 Kernel Crash

Hi Ted,
I tried a newer kernel and for the moment there are no problems.
I am testing our systems this weekend and the new week. I will
let you know the results.

Kind regards,
     Chris


On Mon, Jan 30, 2012 at 12:26:59PM -0500, Ted Ts'o wrote:
> On Sun, Jan 29, 2012 at 07:50:57PM +0200, Nanakos Chrysostomos wrote:
> > Dear Linux Kernel Developers,
> > I am writing to report a kernel or ext4 bug.
>
> Hi Nanakos,
>
> My apologies for not responding to the message that you sent to me
> personally three days ago, but I was on vacation in Hawaii; the best
> place to send queries about ext4 file systems is to use the
> linux-ext4@...r.kernel.org mailing list.
>
> One thing that I would immediately suggest is to see whether you can
> reproduce this bug using a modern kernel.  You are currently using a
> RHEL6-derived kernel (2.6.32-220.4.1.el6.x86_64).  The ext4 file
> system in such a kernel is quite different from what is in upstream,
> and there were a large number of bugs that have been fixed in ext4
> since 2.6.32.  Many of these fixes were backported into the RHEL6
> kernel, but I'm not an expert on which fixes have been backported into
> RHEL6 and which haven't.  (Especially since Red Hat doesn't release
> broken-out patches for their RHEL kernels....)
>
> My understanding is that Gluster doesn't require any kernel-side
> patches, so it should be OK to run Gluster on a v3.2 kernel.
> Alternatively, if you are a paid customer of RHEL6, I'd suggest
> sending a support request to Red Hat.
>
> Best regards,
>
>                                       - Ted
> --
> 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/
--
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