linux-ext4 - Re: Overwriting w/ discard-capable drive causes soft-lockup in ext4 journal code, 2.6.28.8

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: <49BFE572.9020302@redhat.com>
Date:	Tue, 17 Mar 2009 13:01:22 -0500
From:	Eric Sandeen <sandeen@...hat.com>
To:	Chris Worley <worleys@...il.com>
CC:	linux-ext4@...r.kernel.org
Subject: Re: Overwriting w/ discard-capable drive causes soft-lockup in ext4
 	journal code, 2.6.28.8

Chris Worley wrote:
> The issue I'm seeing is caused by running this repeatedly on an ext4
> fs (2.6.28.8 kernel) w/ discards enabled (a ram-based MTD device
> contains the fs):
> 
> while `true`
> do  i=0
>      while [ $i -lt 100 ]
>      do dd of=foo"$i" if=/dev/zero bs=1024k oflag=direct &
>           let i=$i+1
>      done
>      wait
> done
> 
> (Note: the loop is intended to fill-up the fs w/ 100 dd threads...
> successive re-runs of the loop will rewrite the same files from
> scratch.)
> 
> ... It causes "soft-lockup" issues on successive iterations,
> immediately as the DD's are launched, as previous foo files get their
> blocks discarded.

I need to find a machine w/ more memory to test on :)  but with a device
of half that size, on 2.6.29-rc7 machine w/ 2 cpus and 2G ram, I'm not
seeing it...

Any chance you can try a 2.6.29-rcX kernel just to double-check?

Thanks,
-Eric
--
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