From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from gardel.0pointer.net (gardel.0pointer.net [85.214.157.71]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id A335F128805; Tue, 16 Apr 2024 14:18:19 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=85.214.157.71 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1713277102; cv=none; b=FNN1V8w8XeKZQwKx8zy0qZq7WQwX25O6wG7MyyeTFt18+yiBWhmSIG4LPcbKekleSdlmezcgBua7o98GdxrZPMda1RSripbL4sP1tHCK+CWqTo7ZqPWjPUbrhFoOevwDaauBnRfMS82PPdWiNfrR9/ydz9+cYy1/2n6v9/Olsk0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1713277102; c=relaxed/simple; bh=cD37T59aEkLC1V37YKhVxgH6MPLClBUqzyZJEc80Wso=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=V+g3ui6X6nXm4htNdE6BV7V55HSdmmbtP6dwwlTPGIBHW2ysqEMMXwloxZqZSJz+aFEOUa5xkQKKi4uk+EemraQpyW2yL/x6mG746P3K0Bo33HyJldmEljpLzfrMkJ9sCQ7kXaAeZHVo4eS4qizxLYaPv0oVOhOH3WHVV3cmuSY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=0pointer.de; spf=pass smtp.mailfrom=0pointer.de; arc=none smtp.client-ip=85.214.157.71 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=0pointer.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=0pointer.de Received: from gardel-login.0pointer.net (gardel-mail [IPv6:2a01:238:43ed:c300:10c3:bcf3:3266:da74]) by gardel.0pointer.net (Postfix) with ESMTP id 66AE3E803C0; Tue, 16 Apr 2024 16:18:15 +0200 (CEST) Received: by gardel-login.0pointer.net (Postfix, from userid 1000) id 1B2A81602F7; Tue, 16 Apr 2024 16:18:15 +0200 (CEST) Date: Tue, 16 Apr 2024 16:18:14 +0200 From: Lennart Poettering To: Jens Axboe Cc: Christoph Hellwig , Keith Busch , Linux regressions mailing list , linux-block@vger.kernel.org, LKML Subject: Re: API break, sysfs "capability" file Message-ID: References: <54e3c969-3ee8-40d8-91d9-9b9402001d27@leemhuis.info> <20240409141531.GB21514@lst.de> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: On Di, 09.04.24 09:17, Jens Axboe (axboe@kernel.dk) wrote: > On 4/9/24 8:15 AM, Christoph Hellwig wrote: > > On Tue, Apr 09, 2024 at 10:19:09AM +0200, Lennart Poettering wrote: > >> All I am looking for is a very simple test that returns me a boolean: > >> is there kernel-level partition scanning enabled on this device or > >> not. > > > > And we can add a trivial sysfs attribute for that. > > And I think we should. I don't know what was being smoked adding a sysfs > interface that exposed internal flag values - and honestly what was > being smoked to rely on that, but I think it's fair to say that the > majority of the fuckup here is on the kernel side. Yeah, it's a shitty interface, the kernel is rich in that. But it was excessively well documented, better in fact than almost all other kernel interfaces: → https://www.kernel.org/doc/html/v5.16/block/capability.html ← If you document something on so much detail in the API docs, how do you expect this *not* to be relied on by userspace. Lennart