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=-2.5 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no 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 2E5A9C06513 for ; Thu, 4 Jul 2019 12:40:11 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id E6CB121850 for ; Thu, 4 Jul 2019 12:40:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1562244011; bh=Dg6E6spylfkSYzp+dH8xuoGlslv5RTNRs4e7ma6/gxM=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=Xb2YpaZLvvfNsuXsC4kmFrnzIXq0Y0HBp1ipiqfMUqBLdm+M6E0LvVCXfcvqLFayj V8pGymve5ugzunZXoxQKXHM0MnGGO2TLagWPL1waWjQy3+OmwUHHoH5QflVk9/kwWW lCh4jSk4Q+95q87CvGRko/9dpi9YhBYoGQDpN/lE= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727682AbfGDMkK (ORCPT ); Thu, 4 Jul 2019 08:40:10 -0400 Received: from mail.kernel.org ([198.145.29.99]:48754 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727602AbfGDMkK (ORCPT ); Thu, 4 Jul 2019 08:40:10 -0400 Received: from localhost (unknown [89.205.128.15]) (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 8648B2082E; Thu, 4 Jul 2019 12:40:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1562244009; bh=Dg6E6spylfkSYzp+dH8xuoGlslv5RTNRs4e7ma6/gxM=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=kHWoi76spS7D37Em1G1Ol+M/BRzeEKM7UHA3Qx+3I87kXPq9Do7fwcyFYUX1Tl6ic foyeb46xwkST0KD0RxCU587FOWHx5EigV3hKMUGpqkopLOyno+LAueEo3Q7WvfSUPu qUakIsWHxbOS3VZgyHlDNMP6ott3OWjahW0V4aWk= Date: Thu, 4 Jul 2019 14:40:05 +0200 From: Greg Kroah-Hartman To: Stephen Rothwell Cc: Linux Next Mailing List , Linux Kernel Mailing List Subject: Re: linux-next: Tree for Jul 4 Message-ID: <20190704124005.GA6733@kroah.com> References: <20190704220945.27728dd9@canb.auug.org.au> <20190704222450.021c9d71@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190704222450.021c9d71@canb.auug.org.au> User-Agent: Mutt/1.12.1 (2019-06-15) Sender: linux-next-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org On Thu, Jul 04, 2019 at 10:24:50PM +1000, Stephen Rothwell wrote: > Hi all, > > This release produces a whole lot (over 200) of this message in my qemu > boot tests: > > [ 1.698497] debugfs: File 'sched' already present! > > Introduced by commit > > 43e23b6c0b01 ("debugfs: log errors when something goes wrong") > > from the driver-core tree. I assume that the error(?) was already > happening, but it is now being reported. Ugh. Looks like it's one of the block scheduler, and it seems to be creating that directory in the root of debugfs, not in a subdir like it is trying to do so. Odd, let me look into it some more. Oh, and I guess we might want to move this down to a 'dev_dbg' message, although this is showing that there is a problem here, so it did succeed :) thanks, greg k-h