From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 9441B3C942B for ; Mon, 27 Apr 2026 13:29:43 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=170.10.129.124 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777296586; cv=none; b=PowpuvmGt9h0UP+ML5eqyW+uDbboBnYF4SlgSY9xSDKRUTphyxTAr+zCMiSes7sy8jNb4dpeSBtEZPsSXLu4zhW+T9z3r8UfYF90jG7IqmJKKiR2E9q7ttbdJScBPqos3qivnrAfGFb/X71ewgE7VDy9GGps6+R38BR1kgWik2Q= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777296586; c=relaxed/simple; bh=72Vj0K0ahYjiIGlZw+3HO4C99x6D7GIrI8KmI+R3XqY=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=Bd8K0JwcLyyQx+4qVE24ei9MbbSoF11ksNvJEF6BbuLai1Cc0HeOEDuZngmKYzD6BSArPEmDVFqEyBygjNeNgqz3EmaKgktEfbhTLxIcFZH6u1+TqRA19aJ62GAgRnFTn8RKnuw3kZHTYNGuK8NIy7waJabcADKi9SztUKH9JCs= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b=LsxWE69h; arc=none smtp.client-ip=170.10.129.124 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="LsxWE69h" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1777296582; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=IiAO0uEG/jiG1zpDR09OVtbsVYFleUsY0hDNg9xxJe8=; b=LsxWE69hg60OUPg5/sClAh9jdwEYLh+BG09uNrrIT/AQ7u9Qk4OXroNtkww0b8mBmbVhQX FGrtHWuODl2R573pKJivqWLQTqJQnHDwGeOniQCOLFI633ovyIt7dMnLkW2mUpqbsZKSGv 2Zr42QxCcRRZU7fm6zVGk/qaqfZsjXU= Received: from mx-prod-mc-08.mail-002.prod.us-west-2.aws.redhat.com (ec2-35-165-154-97.us-west-2.compute.amazonaws.com [35.165.154.97]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-479-jkM-qN4wNLOUE0SH86uuDQ-1; Mon, 27 Apr 2026 09:29:37 -0400 X-MC-Unique: jkM-qN4wNLOUE0SH86uuDQ-1 X-Mimecast-MFC-AGG-ID: jkM-qN4wNLOUE0SH86uuDQ_1777296575 Received: from mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.17]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-08.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 1FB4718001D6; Mon, 27 Apr 2026 13:29:35 +0000 (UTC) Received: from fweimer-oldenburg.csb.redhat.com (unknown [10.44.48.4]) by mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 10E0B195608E; Mon, 27 Apr 2026 13:29:32 +0000 (UTC) From: Florian Weimer To: Alejandro Colomar Cc: Dorjoy Chowdhury , linux-man@vger.kernel.org, brauner@kernel.org, jlayton@kernel.org, libc-alpha@sourceware.org, linux-api@vger.kernel.org Subject: Re: [PATCH v2 1/2] man/man3/errno.3: Document EFTYPE error code In-Reply-To: (Alejandro Colomar's message of "Mon, 27 Apr 2026 15:13:07 +0200") References: <20260426111707.36541-1-dorjoychy111@gmail.com> <20260426111707.36541-2-dorjoychy111@gmail.com> Date: Mon, 27 Apr 2026 15:29:30 +0200 Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Precedence: bulk X-Mailing-List: linux-api@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Scanned-By: MIMEDefang 3.0 on 10.30.177.17 * Alejandro Colomar: > Hi Florian, > > On 2026-04-27T12:34:30+0200, Florian Weimer wrote: >> * Alejandro Colomar: >>=20 >> > [CC +=3D libc-alpha] >> > >> > Hi Dorjoy, >> > >> > On 2026-04-26T17:14:25+0600, Dorjoy Chowdhury wrote: >> >> Signed-off-by: Dorjoy Chowdhury >> > >> > Thanks! >> > >> > Reviewed-by: Alejandro Colomar >> > >> > I will wait until glibc adds this error code to their before >> > applying the patch. This means either you should write and send a pat= ch >> > to glibc (if so, please CC me), or you should ask them to add it >> > themselves (if you're not comfortable writing glibc code). >>=20 >> I'm not sure where this is coming from. > > Here's a link to the thread: > > >> POSIX says EFTYPE was rejected >> in favor of ENOTTY. > > Could you please share a link to that? > > Anyway, I guess ENOTTY would be inappropriate in this case. Although > maybe a better error code could be devised; I don't know. This is why > I wanted glibc involved in this discussion before this arrives to a > Linux release. Thanks for the quick feedback! It's in the Rationale for System Interfaces: =E2=80=9C [EFTYPE] This error code was proposed in earlier proposals as "Inappropriate operation for file type", meaning that the operation requested is not appropriate for the file specified in the function call. This code was proposed, although the same idea was covered by [ENOTTY], because the connotations of the name would be misleading. It was pointed out that the fcntl() function uses the error code [EINVAL] for this notion, and hence all instances of [EFTYPE] were changed to this code. =E2=80=9D I replied on linux-fsdevel, too. (It would be nice to submit patches introducing new error codes to linux-api with a subject mentioning the error code.) Thanks, Florian