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: <alpine.LFD.2.00.1009082056210.2477@localhost6.localdomain6>
Date:	Wed, 8 Sep 2010 21:34:21 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	James Bottomley <James.Bottomley@...senPartnership.com>
cc:	LKML <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>,
	Peter Zijlstra <peterz@...radead.org>,
	Christoph Hellwig <hch@...radead.org>,
	linux-alpha@...r.kernel.org, linux-cris-kernel@...s.com,
	Haavard Skinnemoen <hskinnemoen@...el.com>,
	Tony Luck <tony.luck@...el.com>, linux-ia64@...r.kernel.org,
	Yoshinori Sato <ysato@...rs.sourceforge.jp>,
	Hirokazu Takata <takata@...ux-m32r.org>,
	Greg Ungerer <gerg@...inux.org>, Jeff Dike <jdike@...toit.com>,
	linux-parisc@...r.kernel.org, Chris Zankel <chris@...kel.net>,
	linux-arch@...r.kernel.org
Subject: Re: [RFC trollpatch 1/1] genirq: Remove the fits all and nothing
 __do_IRQ() code

On Wed, 8 Sep 2010, James Bottomley wrote:
> On Wed, 2010-09-08 at 18:14 +0000, Thomas Gleixner wrote:
> > plain text document attachment (genirq-troll-patch.patch)
> > __do_IRQ() has been deprecated after a two years migration phase in
> > commit 0e57aa1. Since then another 18 month have gone by.
> > 
> > So here's the status three and a half years after the flow based
> > infrastructure was merged:
> > 
> >  The following architectures are fully converted to the new flow
> >  handler code:
> > 
> >   arm, avr32, blackfin, frv, microblaze, mips, mn10300, powerpc, score, sh,
> >   sparc 64bit, tile, x86, xtensa
> > 
> >   (avr32 and xtensa should set CONFIG_GENERIC_HARDIRQS_NO__DO_IRQ
> >   though)
> > 
> >  The following architectures are not using the generic interrupt
> >  infrastructure at all and are therefor unaffected:
> > 
> >   s390, m68k, sparc 32bit
> > 
> >  The following architectures are still using __do_IRQ():
> > 
> >   alpha, cris, ia64, h8300, m32r, m68knommu, parisc, um
> > 
> > So now the question arises what to do with __do_IRQ().
> > 
> > Removing it would be the right thing, but that'll break 8 archs, so
> > it's probably not considered a good idea, though for most of them the
> > conversion should be reasonably trivial.
> > 
> > I'm happy to move that code into kernel/irq/cruft.c forever if there
> > is no way to get the remaining users converted in the forseeable
> > future. It looks like they can cope with the annoying build warning
> > nicely.
> 
> Well, if you're going to deprecate something that 8 architectures rely
> on, it would be nice to tell people ... or even just linux-arch ... most

It's been told people. The deprecation patch was on LKMl (I don't
remember whether I sent it to linux-arch), but there were a bunch of
related patches to clean out the old irq related cruft which were sent
to linux-arch and also hit the parisc tree. There is an entry in
feature-removal-schedule.txt for 18 month now.

> of us do read that.  I've actually never noticed the warning the commit
> activated in any of my parisc compiles for some reason.

CONFIG_ENABLE_WARN_DEPRECATED=y perhaps ?

I'm really tired of your whining when you did not get a personalized
taylored to your needs info.

14 architectures got converted and some maintainers sent out mail to
their users 18 month ago right after the deprecation patch was sent
(www.linux-mips.org/archives/linux-mips/2009-03/msg00068.html), there
were reviews of new architecture code on linux-arch where this was
pointed out, so don't tell me that there was not enough information
about this.

> > Either that or moving everything what breaks into staging/arch/* and
> > hand it over to GregKH :)
> > 
> > Thoughts ?
> 
> We could move x86 into staging while it tries out the replacement ...

The replacement of what? 

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