Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754627AbbLCVWx (ORCPT ); Thu, 3 Dec 2015 16:22:53 -0500 Received: from mail-lf0-f45.google.com ([209.85.215.45]:33922 "EHLO mail-lf0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754579AbbLCVWw (ORCPT ); Thu, 3 Dec 2015 16:22:52 -0500 MIME-Version: 1.0 In-Reply-To: <2473673.tSymyNlg3h@wuerfel> References: <1448370862-19120-1-git-send-email-lee.jones@linaro.org> <2600153.9u9Z7N2IT1@wuerfel> <20151203172830.GB26902@x1> <2473673.tSymyNlg3h@wuerfel> Date: Thu, 3 Dec 2015 13:22:50 -0800 Message-ID: Subject: Re: [RESEND v4 2/6] remoteproc: debugfs: Add ability to boot remote processor using debugfs From: Bjorn Andersson To: Arnd Bergmann Cc: "linux-arm-kernel@lists.infradead.org" , Lee Jones , Ohad Ben-Cohen , "devicetree@vger.kernel.org" , Florian Fainelli , kernel@stlinux.com, Nathan Lynch , "linux-kernel@vger.kernel.org" , ludovic.barre@st.com, Maxime Coquelin Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 957 Lines: 26 On Thu, Dec 3, 2015 at 1:12 PM, Arnd Bergmann wrote: > On Thursday 03 December 2015 17:28:30 Lee Jones wrote: >> > >> > Ah, interesting. I haven't tried myself, and just tried to read the >> > code. Maybe glibc already catches zero-length writes before it gets >> > into the kernel, or I just missed the part of the syscall that checks >> > for this. >> >> Glibc is responsible indeed: >> >> http://osxr.org/glibc/source/io/write.c > > Ok, so an attacker can force the stack overflow by calling > syscall(__NR_write, fd, p, 0) if that has any potential value, > but normal users won't hit this case. > It seems glibc might be the only libc implementation with this protection. Regards, Bjorn -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/