linux-kernel - Re: [3.13.2] list passed to list_sort() too long for efficiency.

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-next>] [day] [month] [year] [list]

Message-ID: <4850975.2GAlrTXDHt@localhost.localdomain>
Date:	Wed, 12 Feb 2014 18:59:07 +0100
From:	Paweł Sikora <pawel.sikora@...k.net>
To:	Joe Perches <joe@...ches.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [3.13.2] list passed to list_sort() too long for efficiency.

On Wednesday 12 of February 2014 09:46:26 Joe Perches wrote:
> On Wed, 2014-02-12 at 18:16 +0100, Paweł Sikora wrote:
> > [16855.582522] list passed to list_sort() too long for efficiency
> > 
> > could someone put some light on the last line?
> 
> Did you look at the list_sort function in lib/list_sort.c?
> 
> (granted the dmesg is harder to find that it should be
>  because the format is split)
> 
> It just means it's slower than it could otherwise be

thanks,
so without a stacktrace in dmesg we can't isolate a root of cause :/

-- 
gpg key fingerprint = 60B4 9886 AD53 EB3E 88BB 1EB5 C52E D01B 683B 9411
--
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/