linux-kernel - Re: Oops with PREEMPT-RT on 2.6.25.4

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: <4831F364.8020702@freescale.com>
Date:	Mon, 19 May 2008 16:38:44 -0500
From:	Scott Wood <scottwood@...escale.com>
To:	Rune Torgersen <runet@...ovsys.com>
CC:	linuxppc-dev@...abs.org, linux-kernel@...r.kernel.org,
	linux-ide@...r.kernel.org
Subject: Re: Oops with PREEMPT-RT on 2.6.25.4

Rune Torgersen wrote:
> Scott Wood wrote:
>> Almost certainly the latter.  Is the disk interrupt shared with any
>> other interrupts, that are marked IRQF_NODELAY?  The -rt
>> patch doesn't seem to handle mixing the two well.
> 
> Disk is on a muxed PCI interrupt. None of the other interrupts on the
> mux is fireing at the time.

Regardless of whether they're firing, any request_irq with IRQF_NODELAY 
will turn off threading for all handlers.

> Is is possible that the demuxer is not set up right? It is based loosely
> on pq2-pci-pic.c

Try calling irq_set_chip_and_handler() with handle_level_irq, rather 
than irq_set_chip().  The -rt patch doesn't seem to have threadified the 
  __do_IRQ() path.

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