linux-kernel - Re: scheduling while atomic & hang.

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: <CA+55aFz+Bo+MGMmUsuxb2uHRNBUvKEdQqR7nZTTQdHOtgnVkDw@mail.gmail.com>
Date:	Thu, 4 Jul 2013 10:22:09 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Dave Jones <davej@...hat.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Anvin <hpa@...or.com>
Subject: Re: scheduling while atomic & hang.

On Thu, Jul 4, 2013 at 12:49 AM, Dave Jones <davej@...hat.com> wrote:
>
> top of tree was 0b0585c3e192967cb2ef0ac0816eb8a8c8d99840 I think.
> (That's what it is on my local box that I pull all my test trees from,
> and I don't think it changed after I started that run, but I'll
> double check on Friday)

Ok. So that has all the scheduler changes, and all the x86 changes
(and all the cgroup workqueue changes too - but without any call chain
at all, I'm disinclined to blame those yet).

> I don't use the auto config, because I end up filling up /boot
> unless I go through and clean them out by hand every time I install
> a new one (which I do probably a dozen or so times a day).
> Is there some easy way to prune old builds I'm missing ?

I'm sure it could be done automatically some way, but yeah, I just do
it by hand. I often *compile* dozens of kernels a day, but I seldom
install more than one or two even during the merge window..

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