From mboxrd@z Thu Jan 1 00:00:00 1970 From: Al Viro Subject: Re: [RFC PATCH] vfs: Use 12:20 bit major:minor in stat everywhere Date: Wed, 4 Mar 2015 01:22:12 +0000 Message-ID: <20150304012211.GV29656@ZenIV.linux.org.uk> References: <1425429420-13142-1-git-send-email-dehrenberg@chromium.org> <20150304005347.GU29656@ZenIV.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, Gwendal Grignou , Ezequiel Garcia To: Daniel Ehrenberg Return-path: Received: from zeniv.linux.org.uk ([195.92.253.2]:58358 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756358AbbCDBWR (ORCPT ); Tue, 3 Mar 2015 20:22:17 -0500 Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Tue, Mar 03, 2015 at 05:10:22PM -0800, Daniel Ehrenberg wrote: > > What's to guarantee that your ABI change won't break any of those? > > I guess it's impossible to guarantee, but if there is an error, it'll > be that an -EOVERFLOW error is suppressed and the high bits of the > major:minor pair are shaved off by the userspace program. I would > suspect that this would just make debugging harder, rather than > actually break an automated program which counts on getting EOVERFLOW > from a huge block device, but no way to know. The block device has to > actually exist for this to happen, and all we're talking about is stat > failing. So it's replacing an an error code with erroneous way to get > data about a device node (erroneous just because userspace ignores > some of the bits with the answer). All it takes is more than 16 SCSI disks, AFAICS, and use of open-coded MINOR() somewhere in old userland code...