From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx2.suse.de ([195.135.220.15]:42287 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752168AbcCKMnr (ORCPT ); Fri, 11 Mar 2016 07:43:47 -0500 Subject: Re: [PATCH 02/18] mm: make vm_mmap killable References: <1456752417-9626-1-git-send-email-mhocko@kernel.org> <1456752417-9626-3-git-send-email-mhocko@kernel.org> <56E29702.5030100@suse.cz> <20160311121235.GI27701@dhcp22.suse.cz> From: Vlastimil Babka Message-ID: <56E2BD7D.10701@suse.cz> Date: Fri, 11 Mar 2016 13:43:41 +0100 MIME-Version: 1.0 In-Reply-To: <20160311121235.GI27701@dhcp22.suse.cz> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-arch-owner@vger.kernel.org List-ID: To: Michal Hocko Cc: LKML , Andrew Morton , linux-mm@kvack.org, Alex Deucher , Alex Thorlton , Andrea Arcangeli , Andy Lutomirski , Benjamin LaHaise , =?UTF-8?Q?Christian_K=c3=b6nig?= , Daniel Vetter , Dave Hansen , David Airlie , Davidlohr Bueso , David Rientjes , "H . Peter Anvin" , Hugh Dickins , Ingo Molnar , Johannes Weiner , "Kirill A . Shutemov" , Konstantin Khlebnikov , linux-arch@vger.kernel.org, Mel Gorman , Oleg Nesterov , Peter Zijlstra , Petr Cermak , Thomas Gleixner , Al Viro Message-ID: <20160311124341.pQhh_wXiiF2LpMW71S5YzraOWSXpHt7z6HxdSxJ94z4@z> On 03/11/2016 01:12 PM, Michal Hocko wrote: > On Fri 11-03-16 10:59:30, Vlastimil Babka wrote: >> On 02/29/2016 02:26 PM, Michal Hocko wrote: >> >From: Michal Hocko >> > >> >All the callers of vm_mmap seem to check for the failure already >> >and bail out in one way or another on the error which means that >> >> Hmm I'm not that sure about this one: >> 17 1071 fs/binfmt_elf.c <> >> >> Assigns result of vm_mmap() to "error" variable which is never checked. > > Yes it is not checked but not used either. If the current got killed > then it wouldn't return to the userspace so my understanding is that not > checking this value is not a problem. At least that is my understanding. Hmm, that's true. So, Acked-by: Vlastimil Babka >> Shouldn't __must_check trigger here? > > well, __must_check is a misleading name. It doesn't actually enforce the > value is checked. It just has to be used and an assignment is > sufficient. I was discussing this without our gcc guy and he promissed > to look and try to come up with a different attribute which would > actually work like __must_check. OK!