linux-kernel - Re: Which kernel options should be enabled to find the root cause of this bug?

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]

Message-ID: <4B0C087E.6050701@sandeen.net>
Date:	Tue, 24 Nov 2009 10:23:26 -0600
From:	Eric Sandeen <sandeen@...deen.net>
To:	Justin Piszcz <jpiszcz@...idpixels.com>
CC:	linux-raid@...r.kernel.org, Alan Piszcz <ap@...arrain.com>,
	linux-kernel@...r.kernel.org, xfs@....sgi.com
Subject: Re: Which kernel options should be enabled to find the root cause
 of this bug?

Justin Piszcz wrote:
> 
> On Tue, 24 Nov 2009, Eric Sandeen wrote:

...

>> Do you get the same behavior if you don't add the log options at mount time?
> I have not tried disabling the log options, although they have been in effect
> for a long time, (the logsbufs and bufsize and recently) the nobarrier
> support.  Could there be an issue using -o nobarrier on a raid1+xfs?

nobarrier should not cause problems.

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