linux-kernel - Re: [PATCH] aio: aio_complete() will never be called in interrupt context

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: <x49tzfft448.fsf@segfault.boston.devel.redhat.com>
Date:	Fri, 27 Jun 2008 09:11:03 -0400
From:	Jeff Moyer <jmoyer@...hat.com>
To:	Nikanth Karthikesan <knikanth@...e.de>
Cc:	linux-aio@...ck.org, linux-kernel@...r.kernel.org,
	Benjamin LaHaise <bcrl@...ck.org>,
	Zach Brown <zach.brown@...cle.com>
Subject: Re: [PATCH] aio: aio_complete() will never be called in interrupt context

Nikanth Karthikesan <knikanth@...e.de> writes:

> aio_complete() is never called from interrupt context. It is called from user 
> context or worker threads. Remove disabling interrupts and for kmap_atomic use 
> KM_USER slots instead of KM_IRQ slots.

Actually, it can be called from softirq context.  See fs/directio.c.

Cheers,

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