From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 9DEA6C433F5 for ; Sat, 14 May 2022 02:01:12 +0000 (UTC) Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.94.2) (envelope-from ) id 1nph5L-0006Da-IJ; Fri, 13 May 2022 22:00:47 -0400 Received: from mail-qv1-xf31.google.com ([2607:f8b0:4864:20::f31]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1nph5H-00060t-LK for Kernelnewbies@kernelnewbies.org; Fri, 13 May 2022 22:00:43 -0400 Received: by mail-qv1-xf31.google.com with SMTP id jt15so8181275qvb.8 for ; Fri, 13 May 2022 19:00:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vt-edu.20210112.gappssmtp.com; s=20210112; h=sender:from:to:cc:subject:in-reply-to:references:mime-version:date :message-id; bh=hfaEdjAmdlRlPJVu9ChvXeEaGuRgEblEAwy++yH38xQ=; b=OuFNDKN4zVkLsn9aBYZVONAlC/DsmjGR6HelgFfHppi+V5nonRXfxJJrueCkvuOBCW Rq6ew189UbhzUiLALtDdaoT1lhhr0O2rrThlX8KWPHQ6RZFRLsLE48XVbLXOo/sDCjeb WcQaDTvXWs1ThkgQAJpTqFqFKmpzSVXSqH/q/DsB2/xLT/b1aSzrL6+M7w797ijjgdOj 0mSzRnqHwUBP+BqAIq7hWiIRkTe9UJOnQdgUi1z/eBip+v9D68lMfZVmXPXPWPonhvvt O4RFBAilEQBgkvNIVy3ZI5hAsjomwwrQCFBO+Nyo4NDrFS9tA6ilfFdqCujAeBfxVJ+D /Yhg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:sender:from:to:cc:subject:in-reply-to:references :mime-version:date:message-id; bh=hfaEdjAmdlRlPJVu9ChvXeEaGuRgEblEAwy++yH38xQ=; b=pzumC9XhACCjwf51fdKKCtugoZCL48+MbEZ+CapL6hiUUtOSRnuNdMFmqyltLPRMNO peTIdSajj+Qpe9QJzPEPrn6KfCVSQUCFRzUao6yofYjjT/uQyYiVgnA3uZufG4hcG14u 7YEV9wUSP4TNKp8c0+U3tm9yamks3Qz5i2MwPXA3gL50tNs20398ioM+Ueogxz9wl3QV JjV5Ksyrl7qa9WpstTSCQ3ulnVXQldIabcSl1qzP80etabZx0FwRjN2itk+sSSDC6XdV WmScNAqBF2Q1MvuLIJpSorrvMTGeTnksdVZohGXV2ADKQLGPjF9I3PJOC4h51AQGhzpE 6ohg== X-Gm-Message-State: AOAM531wdZbLK8VFP+ze9KtKZetbMJ6MMJGoYMKeslv7ZNIiHj3cDZ3V GkDzraXP1pl0IOZm9JpHU9whdGq4XP4uFw== X-Google-Smtp-Source: ABdhPJx+B0092QmxsIc0aU24l7s8Y+msSk+bFJbsPvQT4lxTt0KR4HW6FsvB+iiX616R96WDmPLl8Q== X-Received: by 2002:a05:6214:260f:b0:45a:f683:befb with SMTP id gu15-20020a056214260f00b0045af683befbmr6614093qvb.35.1652493638150; Fri, 13 May 2022 19:00:38 -0700 (PDT) Received: from turing-police ([2601:5c0:c380:d60:f276:1cff:fe8f:1dec]) by smtp.gmail.com with ESMTPSA id z13-20020a37650d000000b0069fdbe43a5asm2306163qkb.41.2022.05.13.19.00.36 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 13 May 2022 19:00:37 -0700 (PDT) From: "Valdis Kl=?utf-8?Q?=c4=93?=tnieks" X-Google-Original-From: "Valdis Kl=?utf-8?Q?=c4=93?=tnieks" X-Mailer: exmh version 2.10.0-pre 07/05/2021 with nmh-1.7+dev To: Muhammad Ali Subject: Re: UAPI syscall exception interpretation In-reply-to: References: Mime-Version: 1.0 Date: Fri, 13 May 2022 22:00:36 -0400 Message-ID: <618473.1652493636@turing-police> Cc: "Kernelnewbies@kernelnewbies.org" X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kernelnewbies-bounces@kernelnewbies.org On Wed, 11 May 2022 21:19:42 -0000, Muhammad Ali said: > Does the Linux-syscall-note say that a.out can ALL be under any license of > your choice? > Or do you have to note that your binary is under License X and also includes > code which is under license GPL-2.0-WITH-Linux-syscall-note? Not a lawyer, but... :) For any program that's big and complex enough that you aren't embarrassed to distribute it, the kernel isn't going to be your problem, because down in the details, your code is probably not issuing syscall() itself, but is letting glibc or musl or whatever the cool kids are using this week do the syscall. So what you need to worry about is the license on glibc or whatever... and also the license on any *other* libraries that you use (you're not going to write your own JSON parser or other stuff like that, are you?). In particular, understand the difference between GPL and LGPL licenses. There's also a lot of other userspace licenses in play - as an example on my laptop, I have: [~] for i in `rpm -qa`; do rpm -qi $i | grep ^License; done | sort | uniq -c > /tmp/licenses [~] wc /tmp/licenses 304 2397 14912 /tmp/licenses [~] more /tmp/licenses 3 License : (ASL 2.0 or MIT) and (BSD and MIT) 1 License : (Artistic 2.0 or ASL 2.0) and MIT 1 License : (Copyright only) and (Artistic or GPL+) 1 License : (Copyright only) and (GPL+ or Artistic) 2 License : (FTL or GPLv2+) and BSD and MIT and Public Domain and zlib with acknowledgement 1 License : (GPL+ or Artistic) and (GPLv2+ or Artistic) and MIT 1 License : (GPL+ or Artistic) and Artistic 2.0 and UCD 3 License : (GPL+ or Artistic) and BSD 1 License : (GPL+ or Artistic) and BSD and HSRL and MIT and UCD and Public domain 1 License : (GPL+ or Artistic) and CC0 1 License : (GPL+ or Artistic) and CC0 and Public Domain 1 License : (GPL+ or Artistic) and FSFAP (and so on for another 300-ish lines.. And as Greg noted, if the answer actually matters, hire a lawyer who is experienced in intellectual property law. _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies