lkml.org 
[lkml]   [2015]   [May]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Repercussions of overflow in get_next_ino()
Date
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

[unhandled content-type:application/x-bzip2]
\
 
 \ /
  Last update: 2015-05-07 19:21    [W:0.041 / U:0.068 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site