public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: alx.manpages@gmail.com, mario.blaettermann@gmail.com,
	linux-man@vger.kernel.org
Subject: Re: Issue in man page getdents.2
Date: Wed, 1 Nov 2023 16:28:12 +0100	[thread overview]
Message-ID: <ZUJujd_4993OjKiO@debian> (raw)
In-Reply-To: <ZUJaYgHOEqVzhGhP@meinfjell.helgefjelltest.de>

[-- Attachment #1: Type: text/plain, Size: 987 bytes --]

Hi Helge,

On Wed, Nov 01, 2023 at 02:02:10PM +0000, Helge Kreutzmann wrote:
> Without further ado, the following was found:
> 
> Issue:    Zero padding byte →  null padding byte?
> 
> msgid ""
> "struct linux_dirent {\n"
> "    unsigned long  d_ino;     /* Inode number */\n"
> "    unsigned long  d_off;     /* Offset to next I<linux_dirent> */\n"
> "    unsigned short d_reclen;  /* Length of this I<linux_dirent> */\n"
> "    char           d_name[];  /* Filename (null-terminated) */\n"
> "                      /* length is actually (d_reclen - 2 -\n"
> "                         offsetof(struct linux_dirent, d_name)) */\n"
> "    /*\n"
> "    char           pad;       // Zero padding byte\n"

Both seem good to me.  Why not zero?

Cheers,
Alex

> "    char           d_type;    // File type (only since Linux\n"
> "                              // 2.6.4); offset is (d_reclen - 1)\n"
> "    */\n"
> "}\n"

-- 
<https://www.alejandro-colomar.es/>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-11-01 15:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-01 14:02 Issue in man page getdents.2 Helge Kreutzmann
2023-11-01 15:28 ` Alejandro Colomar [this message]
2023-11-01 15:40   ` Helge Kreutzmann
2023-11-11 19:45     ` Alejandro Colomar
  -- strict thread matches above, loose matches on Subject: below --
2024-11-17 10:46 Helge Kreutzmann
2024-11-17 15:24 ` Alejandro Colomar
2025-08-24 14:48 Helge Kreutzmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZUJujd_4993OjKiO@debian \
    --to=alx@kernel.org \
    --cc=alx.manpages@gmail.com \
    --cc=debian@helgefjell.de \
    --cc=linux-man@vger.kernel.org \
    --cc=mario.blaettermann@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox