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 369AAC433EF for ; Sun, 23 Jan 2022 11:05:31 +0000 (UTC) Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.94.2) (envelope-from ) id 1nBag8-0002zu-Mu; Sun, 23 Jan 2022 06:05:00 -0500 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1nBag5-0002zn-7e for kernelnewbies@kernelnewbies.org; Sun, 23 Jan 2022 06:04:58 -0500 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id B97533200973; Sun, 23 Jan 2022 06:04:52 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Sun, 23 Jan 2022 06:04:53 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h=cc :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm2; bh=nH9UtWrkdo3P2j9DwNpFTiC0YwkyvTIMPrbABB 6ClfM=; b=wgf/FpPekmnIN3iK0RYli+WJqlpOPHjj3bM8beMnekwXckDFFrNocQ KgMDcbDU/KF0GZwEiAgorkWq32f4DwpRaOpF6X8fghKAIbKrpXrdBc/cIZrzkM/C wXcYRFKIq7Ww7E2kian2hJ09tJJIlegeZ8Y+97hgomNMDmZ6/TmqBuMXZqjuhzO4 Fgyi5x9k8gY8umFDXg+icrV2e/xxP/3bYuMD+LrnodjFkKERxHik8kOFmhXkJNqa fzbuF6tVxu0lgaP8H6U6yKLqJOkownATFp9Nu9vX2OxOxKpN/09r1Iawqx37c24d /YA4PG2kEsqskwxpN9zWRNQim6+rjKrg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=nH9UtWrkdo3P2j9Dw NpFTiC0YwkyvTIMPrbABB6ClfM=; b=FP0V6w6acxDlIacQk5kSHcdxO18crOoVW HvDJ3fDa3fi2LWuPtCGIB9T6mq2isu5ZmVdOHhPboLr6Y/O3xSxZGS7svdXxiPnv TsjTYU+jTltvvqJqoNH7viBKTvm6sjXWn5lhPaPLLZMkZo4EUiZ24beHqkAlYrmi AbK59FxnPkQytvOdUz0BqwkKnT/wYEfBt4mbYWOYIex5yMxdZYdeetmPS8eHKjLQ 1E+9cxtnHCXwxXMIeX3kAySoK6rVMlnvkC0goR7rotCSzRSHm73ODb46l24N9In1 Xvj2Lpl4oxlnWCHlsuYAezd2jIbrrK/vXEsqwi3UKqDYAPHNBkROg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrvdeggddvgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepfffhvffukfhfgggtuggjsehttdertd dttddvnecuhfhrohhmpefirhgvghcumffjuceoghhrvghgsehkrhhorghhrdgtohhmqeen ucggtffrrghtthgvrhhnpeevueehjefgfffgiedvudekvdektdelleelgefhleejieeuge egveeuuddukedvteenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhl fhhrohhmpehgrhgvgheskhhrohgrhhdrtghomh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 23 Jan 2022 06:04:51 -0500 (EST) Date: Sun, 23 Jan 2022 12:04:48 +0100 From: Greg KH To: Paulo Miguel Almeida , kernelnewbies@kernelnewbies.org Subject: Re: ioctl number change / backwards compatibility doubt Message-ID: References: <20220117070125.GA17186@mail.google.com> <20220123075530.GB79751@mail.google.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20220123075530.GB79751@mail.google.com> 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 Sun, Jan 23, 2022 at 08:55:30PM +1300, Paulo Miguel Almeida wrote: > > > 1: Given the driver's history and ioctl number conflit, is the backwards > > > compatibility something to be kept or not to be taken into consideration > > > as ioctl numbering rules weren't followed? > > > > Try to find out who is using these ioctls. If you can change the > > userspace tool at the same time, all is fine. If not, then there can be > > problems. > > Apologies for the delay, I had emailed the original author and I was waiting > for his reply before I could answer this. It turns out I haven't gotten > an official answer from him yet. (I do understand that he might be busy) > > I googled a fair bit of time and I'm 99% confident that there isn't such > userspace/lib tool so I guess this will have done the hard way :( If there is no tool, why was the ioctl code written at all? Something had to call it. _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies