[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8c956766-57ba-c6f7-405c-04a41ae926be@linux.intel.com>
Date: Thu, 25 Oct 2018 09:51:35 +0200
From: Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>
To: Christian König <easy2remember.chk@...glemail.com>,
"Zhou, David(ChunMing)" <David1.Zhou@....com>,
Julia Lawall <julia.lawall@...6.fr>
Cc: "kbuild-all@...org" <kbuild-all@...org>,
"intel-gfx@...ts.freedesktop.org" <intel-gfx@...ts.freedesktop.org>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
Gustavo Padovan <gustavo@...ovan.org>,
Sean Paul <sean@...rly.run>, David Airlie <airlied@...ux.ie>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] drm: fix call_kern.cocci warnings (fwd)
Op 25-10-18 om 08:53 schreef Christian König:
> Am 25.10.18 um 03:28 schrieb Zhou, David(ChunMing):
>> Reviewed-by: Chunming Zhou <david1.zhou@....com>
>
> NAK, GFP_ATOMIC should be avoided.
>
> The correct solution is to move the allocation out of the spinlock or drop the lock and reacquire.
Yeah +1. Especially in a case like this where it's obvious to prevent. :)
Powered by blists - more mailing lists