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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Sat, 2 Jan 2021 07:58:13 +0000
From:   "Song Bao Hua (Barry Song)" <>
To:     Dmitry Torokhov <>,
        Thomas Gleixner <>
CC:     "" <>,
        "" <>
Subject: RE: [PATCH] Input: ar1021 - use IRQ_NOAUTOEN flags to replace

> -----Original Message-----
> From: Dmitry Torokhov []
> Sent: Saturday, January 2, 2021 6:55 PM
> To: Song Bao Hua (Barry Song) <>
> Cc:;
> Subject: Re: [PATCH] Input: ar1021 - use IRQ_NOAUTOEN flags to replace
> disable_irq
> Hi Barry,

Hi Dmitry,
Thanks for your quick reply.

> On Sat, Jan 02, 2021 at 05:29:02PM +1300, Barry Song wrote:
> > disable_irq() after request_irq is unsafe as it gives a time gap which
> > irq can come before disable_irq(). IRQ_NOAUTOEN is the common way to
> > avoid enabling IRQ due to requesting IRQ.
> Actually it is OK for the ISR to fire before the input device is
> registered, input core allows that.

Yep. probably the only issue left is that the code looks silly.
It enables the interrupt in request_irq() automatically and
disables it immediately. So a better way would be avoiding enabling
the IRQ during request_irq().

> What I would like to see is to allow passing something like
> IRQF_DISABLED to request_irq() so that we would not need neither
> irq_set_status_flags() nor disable_irq().

IRQF_DISABLED has been deleted for many years since Linux kernel
doesn't support interrupts enter while an irq handler is running
any more. That flag used to work for forbidding all interrupts
while  kernel was running in one hardIRQ to avoid IRQ races for
kernel older than 2.6.32.

Maybe we can invent a new flag like IRQF_NOAUTOEN for request_irq()?
but right now all other drivers are using irq_set_status_flags
(IRQ_NOAUTOEN) since this request flag doesn't exist.

Do you think it is worth to add a new flag to replace many
irq_set_status_flags(irq, IRQ_NOAUTOEN);
in drivers/gpu, i2c, input, media, net, perf, tc, spi, tty,
usb, vfio?

and +Thomas to get his comments as well :-)

> Thanks.
> --
> Dmitry


Powered by blists - more mailing lists