All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. R. Okajima" <hooanon05g@gmail.com>
To: Nikolay Borisov <n.borisov.lkml@gmail.com>
Cc: viro@zeniv.linux.org.uk, "linux-kernel"@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, spender@grsecurity.net
Subject: Re: Repercussions of overflow in get_next_ino()
Date: Fri, 08 May 2015 01:33:41 +0900	[thread overview]
Message-ID: <30519.1431016421@jrobl> (raw)
In-Reply-To: <554B5AE1.4060901@gmail.com>

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

Hello,

Nikolay Borisov:
> My question is what are the repercussions of get_next_ino overflowing 
> and at some point having possibly multiple inodes on my system with the 
> same i_ino id? And why is it safe to have the inode id's overflow and 
> wrap around?

I am afraid some applications won't work correctly.
As far as I know, ls(1) and find(1) don't show the file whose inum is
zero.

See also
	Subject: [PATCH v2] vfs: get_next_ino(), never inum=0
	Date: 2014-05-28 14:06:32
	http://marc.info/?l=linux-fsdevel&m=140128600801771&w=2
and their thread.

For tmpfs, I have another patch. Just FYI, here attached.


J. R. Okajima


[-- Attachment #2: a.patch.bz2 --]
[-- Type: application/x-bzip2, Size: 2522 bytes --]

      reply	other threads:[~2015-05-07 16:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-07 12:30 Repercussions of overflow in get_next_ino() Nikolay Borisov
2015-05-07 16:33 ` J. R. Okajima [this message]

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=30519.1431016421@jrobl \
    --to=hooanon05g@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=n.borisov.lkml@gmail.com \
    --cc=spender@grsecurity.net \
    --cc=viro@zeniv.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.