lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 23 May 2017 10:41:16 +0200 From: Richard Weinberger <richard@....at> To: Christoph Hellwig <hch@...radead.org> Cc: linux-mtd@...ts.infradead.org, david@...ma-star.at, dedekind1@...il.com, adrian.hunter@...el.com, linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org, adilger.kernel@...ger.ca, akpm@...ux-foundation.org, linux-ext4@...r.kernel.org, bfields@...hat.com, marcus.folkesson@...il.com, hyc.lee@...il.com, rockdotlee@...il.com, leon.pollak@...il.com Subject: Re: [PATCH 5/6] ubifs: Implement export_operations Christoph, Am 23.05.2017 um 10:39 schrieb Christoph Hellwig: >> +static struct inode *ubifs_nfs_get_inode(struct super_block *sb, uint64_t ino, >> + uint32_t generation) >> +{ >> + return ubifs_iget(sb, ino); >> +} > > You need to maintain and check an inode generation counter for this > to be safe. UBIFS has no inode generations, inodes simply can't wrap around. We "handle" it like JFF2 does, we assumes that the NAND is long dead before we reach the maximum inode number. Thanks, //richard
Powered by blists - more mailing lists