linux-kernel - Re: [2.6.23-rt3] NMI watchdog trace of deadlock

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: <3f9a31f40710270312o5a4eb79exa67ed63b4f084f9e@mail.gmail.com>
Date:	Sat, 27 Oct 2007 15:42:32 +0530
From:	"Jaswinder Singh" <jaswinderlinux@...il.com>
To:	"Ingo Molnar" <mingo@...e.hu>
Cc:	"Nick Piggin" <nickpiggin@...oo.com.au>,
	"Mike Galbraith" <efault@....de>,
	"Steven Rostedt" <rostedt@...dmis.org>,
	LKML <linux-kernel@...r.kernel.org>,
	RT <linux-rt-users@...r.kernel.org>,
	"Thomas Gleixner" <tglx@...utronix.de>
Subject: Re: [2.6.23-rt3] NMI watchdog trace of deadlock

Hello Ingo,

On 10/27/07, Ingo Molnar <mingo@...e.hu> wrote:
>
> it's not atomic interrupt context but irq thread context - and -rt
> remaps kmap_atomic() to kmap() internally.
>
> the problem seems to be what Mike's patch works around: fiddling with
> irq flags in the ntfs code. That fiddling seems quite unnecessary at
> first sight.
>

Is this a nice idea to go inside device drivers and filesystem and
make changes in kernel source code to enable RT.

RT related change should be in header files, so that we don't need to
make changes for drivers or filesystem source files.

And when user will disable RT then these patches will again make problems.

We need to find some better alternative.

Thank you,

Jaswinder Singh.
-
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/