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]
Date:	Fri, 17 Jan 2014 10:29:35 -0700
From:	Stephen Warren <swarren@...dotorg.org>
To:	mingo@...nel.org, hpa@...or.com, linux-kernel@...r.kernel.org,
	peterz@...radead.org, tglx@...utronix.de, raistlin@...ux.it,
	juri.lelli@...il.com, linux-tip-commits@...r.kernel.org
Subject: Re: [tip:sched/core] sched: Add new scheduler syscalls to support
 an extended scheduling parameters ABI

On 01/13/2014 08:53 AM, tip-bot for Dario Faggioli wrote:
> Commit-ID:  d50dde5a10f305253cbc3855307f608f8a3c5f73
> Gitweb:     http://git.kernel.org/tip/d50dde5a10f305253cbc3855307f608f8a3c5f73
> Author:     Dario Faggioli <raistlin@...ux.it>
> AuthorDate: Thu, 7 Nov 2013 14:43:36 +0100
> Committer:  Ingo Molnar <mingo@...nel.org>
> CommitDate: Mon, 13 Jan 2014 13:41:04 +0100
> 
> sched: Add new scheduler syscalls to support an extended scheduling parameters ABI
> 
> Add the syscalls needed for supporting scheduling algorithms
> with extended scheduling parameters (e.g., SCHED_DEADLINE).

I'm seeing a regression in next-20140116 on my system, and "git bisect"
points at this patch. I noticed the fix patch "sched: Fix up scheduler
syscall LTP fails", but applying that doesn't solve the problem.

The symptoms are that when the system boots, I see the login prompt over
the serial port OK, but after I've entered my user/password, the login
process simply hangs. CTRL-C drops me back to the login prompt.

Do you have any hints how I should debug this?
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ