public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Valentin Rothberg <valentinrothberg@gmail.com>,
	akpm@linux-foundation.org
Cc: Nishanth Menon <nm@ti.com>,
	linux-mips@linux-mips.org,
	Quentin Lambert <lambert.quentin@gmail.com>,
	Jiri Kosina <jkosina@suse.cz>, Tony Lindgren <tony@atomide.com>,
	Peter Ujfalusi <peter.ujfalusi@ti.com>,
	Sricharan R <r.sricharan@ti.com>,
	linux-mtd@lists.infradead.org, Ralf Baechle <ralf@linux-mips.org>,
	Huacai Chen <chenhc@lemote.com>, Christoph Hellwig <hch@lst.de>,
	Kukjin Kim <kgene.kim@samsung.com>,
	iss_storagedev@hp.com, Jonathan Corbet <corbet@lwn.net>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	Ewan Milne <emilne@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Dan Carpenter <dan.carpenter@oracle.com>,
	Afzal Mohammed <afzal@ti.com>, Arnd Bergmann <arnd@arndb.de>,
	Rajendra Nayak <rnayak@ti.com>, Eyal Perry <eyalpe@mellanox.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Paul Bolle <pebolle@tiscali.nl>, Keerthy <j-keerthy@ti.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Felipe Balbi <balbi@ti.com>, Zhou Wang <wangzhou1@hisilicon.com>,
	linux-usb@vger.kernel.org,
	Santosh Shilimkar <santosh.shilimkar@ti.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Hongliang Tao <taohl@lemote.com>,
	Brian Norris <computersforpeace@gmail.com>,
	David Woodhouse <dwmw2@infradead.org>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH] Remove deprecated IRQF_DISABLED flag entirely
Date: Thu, 05 Mar 2015 14:11:00 +0100	[thread overview]
Message-ID: <54F855E4.9030106@suse.de> (raw)
In-Reply-To: <1425560442-13367-1-git-send-email-valentinrothberg@gmail.com>

On 03/05/2015 01:59 PM, Valentin Rothberg wrote:
> The IRQF_DISABLED is a NOOP and has been scheduled for removal since
> Linux v2.6.36 by commit 6932bf37bed4 ("genirq: Remove IRQF_DISABLED from
> core code").
> 
> According to commit e58aa3d2d0cc ("genirq: Run irq handlers with
> interrupts disabled") running IRQ handlers with interrupts enabled can
> cause stack overflows when the interrupt line of the issuing device is
> still active.
> 
> This patch ends the grace period for IRQF_DISABLED (i.e., SA_INTERRUPT
> in older versions of Linux) and removes the definition and all remaining
> usages of this flag.
> 
> Signed-off-by: Valentin Rothberg <valentinrothberg@gmail.com>
> ---
> The bigger hunk in Documentation/scsi/ncr53c8xx.txt is removed entirely
> as IRQF_DISABLED is gone now; the usage in older kernel versions
> (including the old SA_INTERRUPT flag) should be discouraged.  The
> trouble of using IRQF_SHARED is a general problem and not specific to
> any driver.
> 
> I left the reference in Documentation/PCI/MSI-HOWTO.txt untouched since
> it has already been removed in linux-next by commit b0e1ee8e1405
> ("MSI-HOWTO.txt: remove reference on IRQF_DISABLED").
> 
> All remaining references are changelogs that I suggest to keep.

While you're at it: having '0x0' as a value for the irq flags looks
a bit silly, and makes you wonder what the parameter is for.

I would rather like to have

#define IRQF_NONE 0x0

and use it for these cases.
That way the scope of that parameter is clear.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		               zSeries & Storage
hare@suse.de			               +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)

  parent reply	other threads:[~2015-03-05 13:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-05 12:59 [PATCH] Remove deprecated IRQF_DISABLED flag entirely Valentin Rothberg
2015-03-05 13:08 ` Dan Carpenter
2015-03-05 13:33   ` Valentin Rothberg
2015-03-05 13:11 ` Hannes Reinecke [this message]
2015-03-05 13:41   ` Valentin Rothberg
2015-03-06 19:41   ` Dmitry Torokhov
2015-03-09  8:41     ` Valentin Rothberg
2015-03-05 14:23 ` [PATCH v2] " Valentin Rothberg
2015-03-06 18:31   ` Tony Lindgren
2015-03-06 18:46   ` Brian Norris
2015-03-09 16:52   ` Felipe Balbi
2015-03-09 17:24     ` Valentin Rothberg
2015-03-09 17:29       ` Felipe Balbi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54F855E4.9030106@suse.de \
    --to=hare@suse.de \
    --cc=afzal@ti.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=balbi@ti.com \
    --cc=chenhc@lemote.com \
    --cc=computersforpeace@gmail.com \
    --cc=corbet@lwn.net \
    --cc=dan.carpenter@oracle.com \
    --cc=dwmw2@infradead.org \
    --cc=emilne@redhat.com \
    --cc=eyalpe@mellanox.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=iss_storagedev@hp.com \
    --cc=j-keerthy@ti.com \
    --cc=jkosina@suse.cz \
    --cc=kgene.kim@samsung.com \
    --cc=lambert.quentin@gmail.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=pebolle@tiscali.nl \
    --cc=peter.ujfalusi@ti.com \
    --cc=peterz@infradead.org \
    --cc=r.sricharan@ti.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=ralf@linux-mips.org \
    --cc=rdunlap@infradead.org \
    --cc=rnayak@ti.com \
    --cc=santosh.shilimkar@ti.com \
    --cc=taohl@lemote.com \
    --cc=tglx@linutronix.de \
    --cc=tony@atomide.com \
    --cc=valentinrothberg@gmail.com \
    --cc=wangzhou1@hisilicon.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox