Re: [PATCH] stat.2: fixed inode printing in example program

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Konstantin Bukin <kbukin@xxxxxxxxx>
Subject: Re: [PATCH] stat.2: fixed inode printing in example program
From: "Dmitry V. Levin" <ldv@xxxxxxxxxxxx>
Date: Sun, 13 Sep 2020 20:38:01 +0300
Cc: mtk.manpages@xxxxxxxxx, linux-man@xxxxxxxxxxxxxxx
In-reply-to: <CAF98MAKpdwqowXT9VnO=bZ5CNYPp1Z1OWHg5qVrH7d-0yyui0w@mail.gmail.com>
References: <20200913150449.11188-1-kbukin@gmail.com> <20200913151642.GA14054@altlinux.org> <CAF98MAKpdwqowXT9VnO=bZ5CNYPp1Z1OWHg5qVrH7d-0yyui0w@mail.gmail.com>

On Sun, Sep 13, 2020 at 10:24:23AM -0700, Konstantin Bukin wrote:
> On x86 the size of ino_t does not appear to be larger than long.

It depends.  For example, with glibc on all architectures ino_t is 64-bit
when the code is compiled using -D_FILE_OFFSET_BITS=64.


-- 
ldv

Follow-Ups:
- Re: [PATCH] stat.2: fixed inode printing in example program
  - From: Konstantin Bukin
- Re: [PATCH] stat.2: fixed inode printing in example program
  - From: Alejandro Colomar

References:
- [PATCH] stat.2: fixed inode printing in example program
  - From: Konstantin Bukin
- Re: [PATCH] stat.2: fixed inode printing in example program
  - From: Dmitry V. Levin
- Re: [PATCH] stat.2: fixed inode printing in example program
  - From: Konstantin Bukin

[Index of Archives] [Kernel Documentation] [Netdev] [Linux Ethernet Bridging] [Linux Wireless] [Kernel Newbies] [Security] [Linux for Hams] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux RAID] [Linux Admin] [Samba]

Powered by Linux