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=-5.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,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 77AEFC35240 for ; Sun, 26 Jan 2020 08:55:39 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 457222083E for ; Sun, 26 Jan 2020 08:55:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1580028939; bh=n2nIzaSKhRLa1kWmgJ3uBhJ4DhQVJLVuCuYtEtMl7ik=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=zRr+tV/SUA48E0bIN1co6g0I3pGP3lAeT+gvdYQKg5VhoSJPwDfsnPcxPsgjmpLdW RqfrOqhdcHzrVSKc1q7i78kxalM8K83N9QExKrWfhqLhZW8aoTf6634YRcIOoViQ3W rdwvDPckC9CjMknOsTxm3LbRBR8ks658r8SdUkig= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729163AbgAZIzi (ORCPT ); Sun, 26 Jan 2020 03:55:38 -0500 Received: from mail.kernel.org ([198.145.29.99]:39018 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726443AbgAZIzi (ORCPT ); Sun, 26 Jan 2020 03:55:38 -0500 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 102E32071A; Sun, 26 Jan 2020 08:55:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1580028937; bh=n2nIzaSKhRLa1kWmgJ3uBhJ4DhQVJLVuCuYtEtMl7ik=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=zrTfA3F4bkp7cB9QtVrBzAFPiesqw1fwFv7dkwpGgQSIMyD8XRU6JhMpbeZ13PZig pwJvqvC+3U8/IKhEdZK9Nbx6MfciCWkyrUiy6AE04uYitUOoVrMxDxLYk2Jgiov6iy 87eMDtaAqLn1gmhdttbmT/KOcuu8DXhQ2NR6J4wk= Date: Sun, 26 Jan 2020 09:55:35 +0100 From: Greg Kroah-Hartman To: Dmitry Vyukov Cc: Christian Brauner , Hridya Valsaraju , Arve =?iso-8859-1?B?SGr4bm5lduVn?= , Todd Kjos , Martijn Coenen , Joel Fernandes , "open list:ANDROID DRIVERS" , LKML , syzkaller Subject: Re: binderfs interferes with syzkaller? Message-ID: <20200126085535.GA3533171@kroah.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Jan 25, 2020 at 06:49:49PM +0100, Dmitry Vyukov wrote: > Hi binder maintainers, > > It seems that something has happened and now syzbot has 0 coverage in > drivers/android/binder.c: > https://storage.googleapis.com/syzkaller/cover/ci-upstream-kasan-gce-root.html > It covered at least something there before as it found some bugs in binder code. > I _suspect_ it may be related to introduction binderfs, but it's > purely based on the fact that binderfs changed lots of things there. > And I see it claims to be backward compatible. It is backwards compatible if you mount binderfs, right? > syzkaller strategy to reach binder devices is to use > CONFIG_ANDROID_BINDER_DEVICES to create a bunch of binderN devices (to > give each test process a private one): > https://github.com/google/syzkaller/blob/master/dashboard/config/upstream-kasan.config#L5671 > > Then it knows how to open these /dev/binderN devices: > https://github.com/google/syzkaller/blob/master/sys/linux/dev_binder.txt#L22 > and do stuff with them. > > Did these devices disappear or something? Try mounting binderfs and then you should be able to see them all. thanks, greg k-h