linux-kernel - Re: Very slow header cache in mutt if the maildir is on ext3

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: <20081217123204.GO10590@mit.edu>
Date:	Wed, 17 Dec 2008 07:32:04 -0500
From:	Theodore Tso <tytso@....edu>
To:	linux-kernel@...r.kernel.org
Subject: Re: Very slow header cache in mutt if the maildir is on ext3

On Wed, Dec 17, 2008 at 10:10:03AM +0100, Tino Keitel wrote:
> On Tue, Dec 16, 2008 at 22:25:17 -0500, Theodore Tso wrote:
> 
> > I *thought* mutt had a patch which sorted the files returned by
> > readdir() by inode number, and then opened the files sorted by inode
> > number order; maybe it was a distro-specific patch that was never
> > pushed back to mainline, though.  In any case, sorting list of
> 
> It is in mutt upstream, and enabled by default, but only if
> maildir_header_cache_verify is set. If not, the inode list is kept
> unsorted. maildir_header_cache_verify is enabled by default, but I
> disabled it in my muttrc.

I just checked mutt 1.5.17 in Ubunty Hardy, and it sorts the inodes
even if maildir_header_cache_verify is unset.  (It sorts it earlier if
that option is set, but a little later in the function, if it wasn't
sorted earlier, it sorts it then.)  Check for calls to maildir_sort()
that use md_cmp_inode(); in my version of mutt, there are two such
calls in mh.c:maildir_delayed_parsing().

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