Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752749AbYLTEhj (ORCPT ); Fri, 19 Dec 2008 23:37:39 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751662AbYLTEhb (ORCPT ); Fri, 19 Dec 2008 23:37:31 -0500 Received: from yx-out-2324.google.com ([74.125.44.30]:14017 "EHLO yx-out-2324.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751394AbYLTEhb (ORCPT ); Fri, 19 Dec 2008 23:37:31 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=LcD25RCzs5d57yXOMvTCUQaumfUgLW0fr1gAxhds4qMzcqr+7OCpXjxyei3ShT7F6e q589jKTSBpkgmhW+rKqwOUJctoNXl/EvayS6IlEEyMcUGKy9AvXPAgSEV9phkUfsgnH8 nJukA1ng8kh/x5NNXkQZ1Q1rfToVGZZCrUF/s= Message-ID: Date: Fri, 19 Dec 2008 20:37:29 -0800 From: "Ulrich Drepper" To: "Linux Kernel Mailing List" Subject: st_mode bits MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 625 Lines: 12 What is the future of the bits beyond bit 15 in st_mode? Currently only 16 bits are used. There are old struct stat formats which have only 16 bit st_mode fields. Is this the limiting factor? I ask because I want to use one bit in glibc. If the future of the kernel calls for more than 16 bits in st_mode, can we agree on a bit (perhaps bit 31) to be reserved for userlevel? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/