From nobody Tue Jan 18 04:52:32 2022 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 8BB5B19573E9 for ; Tue, 18 Jan 2022 04:52:50 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-oi1-f182.google.com (mail-oi1-f182.google.com [209.85.167.182]) (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 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4JdGc15ltMz4tDB for ; Tue, 18 Jan 2022 04:52:49 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-oi1-f182.google.com with SMTP id t9so26711069oie.12 for ; Mon, 17 Jan 2022 20:52:49 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=wnUCBHEd7cl4YSukP46NyQU64Wzc8l+yNxbB78fPt8s=; b=lbqhOJ6lnOK23M7sunE+RFBgc3SP+l71jTTryatl8Y/5ECq3JEYIis3jpsPj8Z4wm8 IaHhGM+afTKtNroUsAmyzhsz003bokioIqOP7EP5ZucYANwwsCkh/wyUP2AH/KJX4Z/9 8lDyTMQzD2PGHgO8M4yko+FEFCEYlRiisf62IK0S0J8rVGFn09yo/au3zGy6y+rX2Ysq NrVlaLm0H1rpoTcd13ZrXPLTDWwFdfc0a2mhXtcKH9yER0psA4HoE2jWo5+NaPnwZ03h SYrl57ri95qyTGGkGaVxxOOlSfIg5QhjC6f2fm0MJKvOVgcsw+pkuT6PTZcXA9URsc24 D5BQ== X-Gm-Message-State: AOAM530XKxuot3g1CJvQO4Z7IsGzZ/o0Yl4mjCegmPY8/RY+zB0MW+B3 AjW4UMrcGunm1zPjBCwJGSHICoFtVNybYdC64KIke7P6ZHs= X-Google-Smtp-Source: ABdhPJw+plY8pKGCpVIkBt8m4IoGmphO/uHKuKcJJRS5xp7d0UyMWk1UNZiaXhQy1On6Ae5fCRpeakfPLixm03AkmPE= X-Received: by 2002:a05:6808:254:: with SMTP id m20mr25267239oie.55.1642481563183; Mon, 17 Jan 2022 20:52:43 -0800 (PST) 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: Mon, 17 Jan 2022 21:52:32 -0700 Message-ID: Subject: fspacectl meets DIOCGDELETEE To: FreeBSD CURRENT Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4JdGc15ltMz4tDB 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.182 as permitted sender) smtp.mailfrom=asomers@gmail.com X-Spamd-Result: default: False [3.00 / 15.00]; RCVD_TLS_ALL(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FREEFALL_USER(0.00)[asomers]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; ARC_NA(0.00)[]; NEURAL_SPAM_MEDIUM(1.00)[1.000]; RCPT_COUNT_ONE(0.00)[1]; DMARC_NA(0.00)[freebsd.org]; TO_DN_ALL(0.00)[]; NEURAL_SPAM_LONG(1.00)[1.000]; RCVD_IN_DNSWL_NONE(0.00)[209.85.167.182:from]; NEURAL_SPAM_SHORT(1.00)[1.000]; MLMMJ_DEST(0.00)[freebsd-current]; FORGED_SENDER(0.30)[asomers@freebsd.org,asomers@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.167.182:from]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_TWO(0.00)[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]; TO_DOM_EQ_FROM_DOM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N fspacectl(2) does for regular files the same thing that DIOCGDELETE does for GEOM devices. The only differences are that DIOCGDELETE requires the operation to be block-aligned, and if interrupted DIOCGDELETE doesn't give feedback about partial progress. Can we connect the two? That would allow a user to free space with a single API for both files and devices. It would require: * Adding a d_fspacectl_t member to struct cdevsw * Implementing d_fspacectl_t for g_dev_cdevsw by using DIOCGDELETE * Implementing .fo_fspacectl for devfs * Optionally implementing d_fspacectl on other device types, like zvols. -Alan