linux-kernel - Re: konqueror deadlocks on 2.6.22

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: <20080122101014.GD5722@elte.hu>
Date:	Tue, 22 Jan 2008 11:10:15 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Oliver Pinter (Pintér Olivér) 
	<oliver.pntr@...il.com>
Cc:	Al Boldi <a1426z@...ab.com>, linux-kernel@...r.kernel.org,
	linux-fsdevel@...r.kernel.org
Subject: Re: konqueror deadlocks on 2.6.22

* Oliver Pinter (Pintér Olivér) <oliver.pntr@...il.com> wrote:

> and then please update to CFS-v24.1
> http://people.redhat.com/~mingo/cfs-scheduler/sched-cfs-v2.6.22.15-v24.1.patch

> > Yes with CFSv20.4, as in the log.
> >
> > It also hangs on 2.6.23.13

my feeling is that this is some sort of timing dependent race in 
konqueror/kde/qt that is exposed when a different scheduler is put in.

If it disappears with CFS-v24.1 it is probably just because the timings 
will change again. Would be nice to debug this on the konqueror side and 
analyze why it fails and how. You can probably tune the timings by 
enabling SCHED_DEBUG and tweaking /proc/sys/kernel/*sched* values - in 
particular sched_latency and the granularity settings. Setting wakeup 
granularity to 0 might be one of the things that could make a 
difference.

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