linux-kernel - Re: 2.6.28.2 kernel 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <49C5D217.2010201@xs4all.nl>
Date:	Sun, 22 Mar 2009 06:52:23 +0100
From:	Udo van den Heuvel <udovdh@...all.nl>
To:	Hugh Dickins <hugh@...itas.com>
CC:	linux-kernel@...r.kernel.org,
	Folkert van Heusden <folkert@...heusden.com>
Subject: Re: 2.6.28.2 kernel bug

Hugh Dickins wrote:
> This would become more interesting if you are able to reproduce it,

Just restarted the find command again, crashed after about 7 hours, this 
time with just one line in messages, about the bad page state for `find` 
again.

> or something like it - is that massive removal of files something
> you often do without a problem, or was this new?  What does your
> find/rm command line look like?  I'm wondering if we have a bug
> with exceptionally long arg lists.

I ran a find to get rid of ~2.5M files in 
~/.beagle/Indexes/Thunderbird/ToIndex which shouldn't have been there:
find ToIndex -type f -exec rm -f {} \;
This find runs pretty slowish.

The 2nd time I ran a sync severy 123 seconds to avoid big troubles in 
case of a crash.

Now I just made a list of all files and have a small shell script delete 
the files one by one.

I seldomly have these amounts of files to delete.
I never have this specific problem logged. (as far as I recall for this box)
It is typical that `find` triggers it and not cc1, Xorg etc.
--
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/