Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp3058858yba; Sat, 18 May 2019 08:29:41 -0700 (PDT) X-Google-Smtp-Source: APXvYqz9aIue2p2xGEP0KMS14Vgz6Mt0ifh9DiaMP6VXou+abYTiHbrU3E+7zVpw+cXVqr1KJ5Gj X-Received: by 2002:aa7:9615:: with SMTP id q21mr49545909pfg.253.1558193381190; Sat, 18 May 2019 08:29:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558193381; cv=none; d=google.com; s=arc-20160816; b=mAx8eTCFuv5Te6XXyiXf5k+nq1qXSEYeP4esSA0eJVwt1NkU5IKU0Qj7tHPu5Kwznw afbLXveQ4Q1CbD9RLsgjtuWR4sJqy1K7ttkmFf7GbqaGpnjca0chCn6y99ICfI5Wnmbl gaRtIttsm7SDpaCYxgkXChdXwq56Uk9VHc8mcBFFXS3gD1IMkyhHm6jZ+IIPvsCQ0hP1 aPQVx1Qps9EB0R6zRp774KTWQ/YiSh5YN9PkizQNqVdlcFGCOoYq6l4K5YDGAv5Ez7ot mqNXOuUR7OSbODC037zgXDx7MVFlEj9Qlthi6/DlvCFa0gIRBxG1jjRW92fGyNzdITaP g2pg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:in-reply-to :subject:cc:to:from:date; bh=ZAd6WHm00H7FkDazVqLwW4fKLKsCxDCNSzxIsMPRy30=; b=LB4bFxhdrssFZXrP0ySy4BmR6DZ2OCWqM7m61K4h3KShFCjaCs6onuP+9SE/ncovVK 8Zb8tBIs/v8ZtfD4lICaSVuwW4I4NbfkgcyGfPu+t3kf/bHF3GcRFi5vKUh4Gji6X2Wn jwOh5P2wH7M4Z6MP0fns15VWPju1L7iveyX0LFm16RjHdlXsq8C4+6bQohLHTi2v6MSy U3sQu/RW6pYLWjHonua0eBddBfrDUFTen8jxCpVxaY+3mkkdM25RAFdRfEB33cxnQe9X XejaCSpWXZaWap9h75+2MfJAWLrWPUbkgqJANlstJUo1nt3Jt782m6sZ7utGK7lZ51vW HsnQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 92si11980020plf.299.2019.05.18.08.29.26; Sat, 18 May 2019 08:29:41 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729802AbfERPUs (ORCPT + 99 others); Sat, 18 May 2019 11:20:48 -0400 Received: from netrider.rowland.org ([192.131.102.5]:38683 "HELO netrider.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1728516AbfERPUs (ORCPT ); Sat, 18 May 2019 11:20:48 -0400 Received: (qmail 8577 invoked by uid 500); 18 May 2019 11:20:47 -0400 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 18 May 2019 11:20:47 -0400 Date: Sat, 18 May 2019 11:20:47 -0400 (EDT) From: Alan Stern X-X-Sender: stern@netrider.rowland.org To: "Eric W. Biederman" cc: linux-usb@vger.kernel.org, Greg Kroah-Hartman , Oliver Neukum , Subject: Re: [CFT][PATCH] signal/usb: Replace kill_pid_info_as_cred with kill_pid_usb_asyncio In-Reply-To: <87y334v8x1.fsf@xmission.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 17 May 2019, Eric W. Biederman wrote: > Wow I got a little distracted but now I am back to this. > > Using your test program I was able to test the basics of this. > > I found one bug in my patch where I was missing a memset. So I have > corrected that, and reorganized the patch a little bit. > > I have not figured out how to trigger a usb disconnect so I have not > tested that. Heh. Assuming the device file you tell the test program to use corresponds to an actual USB device, you can trigger a disconnect by literally unplugging the USB cable. (Add a 10-second delay to the program to give yourself enough time.) > The big thing I have not been able to test is running a 64bit big-endian > kernel with a 32bit user space. My modified version of your test > program should report "Bad" without my patch, and should report "Good" > with it. > > Is there any chance you can test that configuration? I could not figure > out how to get a 64bit big-endian system running in qemu, and I don't > have the necessary hardware so I was not able to test that at all. As > that is the actual bug I am still hoping someone can test it. Unfortunately, I don't have any big-endian systems either. Alan Stern