From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 89359 invoked by alias); 30 Jun 2016 07:52:16 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 89347 invoked by uid 89); 30 Jun 2016 07:52:15 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy= X-HELO: mail-oi0-f68.google.com Received: from mail-oi0-f68.google.com (HELO mail-oi0-f68.google.com) (209.85.218.68) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Thu, 30 Jun 2016 07:52:13 +0000 Received: by mail-oi0-f68.google.com with SMTP id w141so6159445oia.0 for ; Thu, 30 Jun 2016 00:52:13 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-transfer-encoding; bh=Pq4kVwkfd8tQ91Iojax4CZ+UlDiLr0ja9GR0WQAcDJ4=; b=PAVPdnzh1R52Ga0NgBRJ3Yn239CJOzq7pI3utBniTeKLLuuBvSHV/+JyBftFCvjsbT fBSRYZXoRH/PXva8CmdRfS398JDShdWb/71r4a2zdDB7W7N693q4Z9wBZ7syAl2Pn9Ez 1cOzKVzvJJ6fijWh9me+ir07951f821iDG4EfVwSvUXrPH0R3gsMduayU3yVP2N8hNI0 tPGgEw+BoK7rYonSm2mBBYBcB9MknPcIso0li/y9Zb0smM94nsA2NtwFYW+kaSwDxTev WX8x61OOGs0tb5ILoWVnYNYS4HIP2wiLvaJNaypZAGG6qTAh3ewt8jxErdcMSdHBS4ZX p3hw== X-Gm-Message-State: ALyK8tLuCi+o7atw7w+BZQCnPe3+DIXjtislYteUGWngfSDIPBIWBx6YYzb6TFCZpFhBeRZ2wUQk1+DdjKPD4w== X-Received: by 10.202.62.196 with SMTP id l187mr7860986oia.142.1467273131944; Thu, 30 Jun 2016 00:52:11 -0700 (PDT) MIME-Version: 1.0 Received: by 10.202.182.130 with HTTP; Thu, 30 Jun 2016 00:52:11 -0700 (PDT) In-Reply-To: <20160629174103.GW4685@vapier.lan> References: <1467105996-18063-1-git-send-email-yao.qi@linaro.org> <20160629174103.GW4685@vapier.lan> From: Yao Qi Date: Thu, 30 Jun 2016 07:52:00 -0000 Message-ID: Subject: Re: [PATCH] Set unknown_syscall differently on arm linux To: Yao Qi , "gdb-patches@sourceware.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2016-06/txt/msg00529.txt.bz2 On Wed, Jun 29, 2016 at 6:41 PM, Mike Frysinger wrote: > On 28 Jun 2016 10:26, Yao Qi wrote: >> Currently, we use 123456789 as unknown or illegal syscall number, and >> expect program return ENOSYS. Although 123456789 is an illegal syscall >> number on arm linux, kernel sends SIGILL rather than returns -ENOSYS. > > err, what ? calling random syscalls should not result in signals being > generated (ignoring obvious ones like __NR_kill). is the kernel broken ? > i think this needs more investigation & explanation. I checked kernel source arch/arm/kernel/traps.c:arm_syscall, and that is how I get the knowledge that kernel doesn't raise SIGIILL if sysno is within 0xf0001..0xf07ff. That is intentional, but I don't know why arm kernel beh= aves this way. --=20 Yao (=E9=BD=90=E5=B0=A7)