Re: Repercussions of overflow in get_next_ino()

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

Repercussions of overflow in get_next_ino()

Hello, get_next_ino would allocate a number between 0...2^32 - 1 to be used as an inode number. The implementation of this mechanism relies on an unsigned int which is 32 bits. On one server I'm observing that every couple of months grsec complains that the percpu variable last_ino overflows

Repercussions of overflow in get_next_ino()

Hello, get_next_ino would allocate a number between 0...2^32 - 1 to be used as an inode number. The implementation of this mechanism relies on an unsigned int which is 32 bits. On one server I'm observing that every couple of months grsec complains that the percpu variable last_ino overflows

Re: Repercussions of overflow in get_next_ino()

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