From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH] ipv6: avoid copy_from_user() via ipv6_renew_options_kern() Date: Sat, 23 Jun 2018 10:57:06 +0900 (KST) Message-ID: <20180623.105706.385733107379565893.davem@davemloft.net> References: <152970230022.7734.15824980755229329454.stgit@chester> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, selinux@tycho.nsa.gov, linux-security-module@vger.kernel.org To: pmoore@redhat.com Return-path: Received: from shards.monkeyblade.net ([23.128.96.9]:34536 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933977AbeFWB5J (ORCPT ); Fri, 22 Jun 2018 21:57:09 -0400 In-Reply-To: <152970230022.7734.15824980755229329454.stgit@chester> Sender: netdev-owner@vger.kernel.org List-ID: From: Paul Moore Date: Fri, 22 Jun 2018 17:18:20 -0400 > - const mm_segment_t old_fs = get_fs(); > - > - set_fs(KERNEL_DS); > - ret_val = ipv6_renew_options(sk, opt, newtype, > - (struct ipv6_opt_hdr __user *)newopt, > - newoptlen); > - set_fs(old_fs); So is it really the case that the traditional construct: set_fs(KERNEL_DS); ... copy_{from,to}_user(...); set_fs(old_fs); is no longer allowed? Setting fs to KERNEL_DS is supposed to make user copies work on kernel memory. Or at least it did for 20+ years :-)