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:	Mon, 17 Aug 2009 23:52:28 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>
Subject: Re: [GIT pull] irq fixes for 2.6.31

Linus,

On Mon, 17 Aug 2009, Linus Torvalds wrote:
> On Mon, 17 Aug 2009, Thomas Gleixner wrote:
> > 
> > Please pull the latest irq-fixes-for-linus git tree from:
> > 
> >    git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git irq-fixes-for-linus
> > 
> > Thanks,
> > 
> > 	tglx
> > 
> > ------------------>
> > Thomas Gleixner (1):
> >       genirq: Do not wakeup irq thread from __setup_irq() and set action->irq
> > 
> > 
> >  kernel/irq/manage.c |    3 +--
> >  1 files changed, 1 insertions(+), 2 deletions(-)
> 
> This is not what I get when I pull. Instead I get the "genirq: Prevent 
> race between free_irq() and handle_IRQ_event()" commit that I thought we 
> agreed wasn't correct.

I have no idea what went wrong this time. I force pushed the branch
and pulled it back on a test machine to compile and test boot. The
test machine still has the correct sha1 for that branch while
master.kernel.org did not. I probably pushed out some other branch
between the point where I sent the pull request and the time you
pulled, but I can not find any hint in my bash history which would
explain why it wreckaged the irq-fixes-for-linus branch.

Just double checked that it is pushed out to git://.... as well.

Thanks,

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