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 X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 63C41C282C7 for ; Sat, 26 Jan 2019 17:49:10 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 3B99D2184B for ; Sat, 26 Jan 2019 17:49:10 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726264AbfAZRtI (ORCPT ); Sat, 26 Jan 2019 12:49:08 -0500 Received: from s3.sipsolutions.net ([144.76.43.62]:41708 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726089AbfAZRtI (ORCPT ); Sat, 26 Jan 2019 12:49:08 -0500 Received: by sipsolutions.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92-RC4) (envelope-from ) id 1gnS4o-0005Bg-S9; Sat, 26 Jan 2019 18:49:07 +0100 Message-ID: <5812aacf62c99fcf98da7d4fc7eaa0ef9cd6afa1.camel@sipsolutions.net> Subject: Re: [PATCH net 2/4] Revert "kill dev_ifsioc()" From: Johannes Berg To: Al Viro Cc: netdev@vger.kernel.org, Robert O'Callahan Date: Sat, 26 Jan 2019 18:49:05 +0100 In-Reply-To: <8e8423d668eb4e38809618c89afbdfa1a1e772af.camel@sipsolutions.net> References: <20190125214320.17685-1-johannes@sipsolutions.net> <20190125214320.17685-3-johannes@sipsolutions.net> <20190126172926.GG2217@ZenIV.linux.org.uk> <8e8423d668eb4e38809618c89afbdfa1a1e772af.camel@sipsolutions.net> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 (3.28.5-2.fc28) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Sat, 2019-01-26 at 18:45 +0100, Johannes Berg wrote: > > Yes and no. It *sometimes* (actually rarely, since we don't really have > dev_ioctls that much, afaict) hits this, but it could also just hit Actually, no, I'm wrong. We do mostly hit dev_ioctl(), since that's the common case for things like SIOCGIFNAME. However, e.g. for SIOCGIFADDR we do go into > static long sock_do_ioctl(struct net *net, struct socket *sock, > unsigned int cmd, unsigned long arg) > { > [...] > err = sock->ops->ioctl(sock, cmd, arg); > [...] > if (err != -ENOIOCTLCMD) > return err; This, and like I said, plumbing the whole compat stuff through to the sock->ops->ioctl() there doesn't seem like a great idea. johannes