linux-kernel - Re: [PATCH] Give kjournald a IOPRIO_CLASS

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20081002134659.GC25164@mit.edu>
Date:	Thu, 2 Oct 2008 09:46:59 -0400
From:	Theodore Tso <tytso@....edu>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Jens Axboe <jens.axboe@...cle.com>,
	linux-kernel@...r.kernel.org, Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [PATCH] Give kjournald a IOPRIO_CLASS_RT io priority

On Thu, Oct 02, 2008 at 06:16:29AM -0700, Arjan van de Ven wrote:
> On Thu, 2 Oct 2008 08:04:44 -0400
> Theodore Tso <tytso@....edu> wrote:
> 
> > 
> > > But sometimes that doesn't work (including the place where I
> > > knowingly broke it).  If we can find and fix the offending piece of
> > > jbd logic (a big if) then all is peachy.
> > 
> > Do we have workloads that can easily demonstrate this problem?  If so,
> > we can add some tracing code which will allow us to see which theory
> > is correct, and what is actually happening.
> 
> I can very easily reproduce it; my mail client (claws) stalls due to
> this several seconds at least once every 5 to 10 minutes...
> (usually when I'm typing an email.. grumble)

Are you running with noatime or relatime?

One quick thing to try that might show what is going on is to run
debugfs on the device where your mail directory is located, while
claws is running, and then use the debugfs command "logdump -a" to
dump out the contents of the journal.  You can then use ncheck and
icheck to take the FS block numbers from logdump and translate them to
inode numbers, and then from inode numbers to pathnames.  That might
give us some insight as to what is going on.

I can whip up a patch which adds some markers which we could use to
find out more information about what is happening.

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