linux-kernel - Re: [PATCH V2 linux-next] staging: media: atomisp: kmap() can't fail

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]

Message-ID: <1493247761.10302.129.camel@linux.intel.com>
Date:   Thu, 27 Apr 2017 00:02:41 +0100
From:   Alan Cox <alan@...ux.intel.com>
To:     Fabian Frederick <fabf@...net.be>,
        Mauro Carvalho Chehab <mchehab@...nel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     Jan Kara <jack@...e.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V2 linux-next] staging: media: atomisp: kmap() can't fail

On Wed, 2017-04-26 at 20:44 +0200, Fabian Frederick wrote:
> There's no need to check kmap() return value because it won't fail.
> If it's highmem mapping, it will receive virtual address
> or a new one; if it's lowmem, all kernel pages are already being
> mapped.
> 
> (Thanks to Jan Kara for explanations)
> 

Thanks - queued.

Alan