From nobody Wed Aug 25 21:19:12 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 5E7B7178E929 for ; Wed, 25 Aug 2021 21:19:30 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-oi1-f175.google.com (mail-oi1-f175.google.com [209.85.167.175]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4GvzPs3c9Jz4dgn for ; Wed, 25 Aug 2021 21:19:29 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-oi1-f175.google.com with SMTP id c79so1258325oib.11 for ; Wed, 25 Aug 2021 14:19:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Cew+JNlcECTAMDr9Mt2tvYlDKWri1VA29iCdhWAdZDo=; b=LlZe1ybJk+PDSRO47YPEibX+q0Ced5J5OkKbHitPxWqFSogUN0CtK9esc8WcJIjNSF CV12I14mHMrApUey2Ss253nfbbm0ZnWaYxj93Rs+3c+WsunURtCu8mn1+lSm+nVtjfow YTFjw/oqF8gTsinT9bYPDGL/lyowbuM7izgBDTwGI36X/b6ugjZOZ0OBBgQAY+qO6Ouq Pel09VlV3wE/kSHiJ4uU9/q7UV6W2gEQK47vQA5sbAlPkW7kEJh8r/Ji3HGZ4vpKVfQU WKpJmHO3ePwyz5mrug6R/XDLRei82bM4K5yJ7p7CrYa3rqAnCMwCU1ouu6Ypph4dm8bU nNMA== X-Gm-Message-State: AOAM531upaMFySo688P2AEqQV26ODFqElXiv6/sPjprK5oQUJgNMy2t+ iU8NMC9x0Theo46n8xmfX0QWSTkbZy5fp2u7FtDYvJ9T X-Google-Smtp-Source: ABdhPJyzIRLG14EPPhZznzu2mVcobFwLvQPCnnhpKEXEbxOAVVoRCcMcrL86eLplGo1XgyLp3ol8HTr6HhyDgtTZER8= X-Received: by 2002:a54:4e94:: with SMTP id c20mr43534oiy.57.1629926362944; Wed, 25 Aug 2021 14:19:22 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 From: Alan Somers Date: Wed, 25 Aug 2021 15:19:12 -0600 Message-ID: Subject: ses ioctl API/ABI stability To: FreeBSD CURRENT Content-Type: multipart/alternative; boundary="000000000000df9a4705ca68cda8" X-Rspamd-Queue-Id: 4GvzPs3c9Jz4dgn X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of asomers@gmail.com designates 209.85.167.175 as permitted sender) smtp.mailfrom=asomers@gmail.com X-Spamd-Result: default: False [-0.84 / 15.00]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FREEFALL_USER(0.00)[asomers]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; NEURAL_SPAM_MEDIUM(1.00)[1.000]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000]; TO_DN_ALL(0.00)[]; NEURAL_HAM_SHORT(-0.84)[-0.842]; RCVD_TLS_ALL(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[209.85.167.175:from]; FORGED_SENDER(0.30)[asomers@freebsd.org,asomers@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.167.175:from]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[asomers@freebsd.org,asomers@gmail.com]; FREEMAIL_ENVFROM(0.00)[gmail.com]; TO_DOM_EQ_FROM_DOM(0.00)[] X-ThisMailContainsUnwantedMimeParts: Y --000000000000df9a4705ca68cda8 Content-Type: text/plain; charset="UTF-8" We usually try to maintain backwards compatibility forever. But is that necessary for the ses(4) ioctls? There are several problems with them as currently defined. They lack type safety, lack automatic copyin/copyout handling, and one of them can overrun a user buffer. I would like to fix them, but adding backwards-compatibility versions would almost negate the benefit. Or, can we consider this to be an internal API, changeable at will, as long as sesutil's CLI remains the same? -Alan --000000000000df9a4705ca68cda8--