linux-kernel - Re: [PATCH] change lock model in aio_put

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] [day] [month] [year] [list]

Date:	Thu, 7 Jun 2012 23:30:55 +0300
From:	mihailov ivan <mihailov.iaa@...il.com>
To:	Jeff Moyer <jmoyer@...hat.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] change lock model in aio_put_req

>> From side - never changed, only we will can execute this call in
>> interrupt context.  I understood what is works as designed but don't
>> understood why we can't imporve this call, it's 'fairly convention in
>> the kernel'?
>
> Changing this is simply not an improvement, it's just a change with no
> benefit.  There's really no point.
>
okay, got it.

> Now, are you going to tell me that you want to call this function from
> interrupt context in some third party driver?  What's the real
> motivation for this patch?
You are right, I'm supporting drivers which are calling this function
from interrupt context.
And I'm trying to find proper way to fix it.
It is clear that this patch is pointless in general case and
I'll try to avoid using this call from interrupt context.
Thanks for your help and patience.
--
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/