| 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
| ||
|
Message-ID: <20080224161135.GA4918@shareable.org> Date: Sun, 24 Feb 2008 16:11:35 +0000 From: Jamie Lokier <jamie@...reable.org> To: Pavel Machek <pavel@....cz> Cc: David Woodhouse <dwmw2@...radead.org>, linux-mtd@...ts.infradead.org, kernel list <linux-kernel@...r.kernel.org> Subject: Re: jffs2: -ENOSPC when truncating file?! Pavel Machek wrote: > > You need to write a log entry indicating the new length of the file. > > There is no space for new log entries. > > > > There is a special case for removal -- 'rm gps.nmea' would work. Perhaps > > we should add a special case for truncation too, so that it can also use > > the extra pool of free space. > > Yes, that would be nice. I somehow assumed that truncate can't fail > for -ENOSPC ... I was trying to actually free some space on the > filesystem... Same here! When I got ENOSPC from truncate, trying to free some space, I was so surprised (and a bit disappointed) that I assumed removal could fail too. So now I'm pleasantly surprised to learn I can at least remove a file. It does seem odd that truncate to zero length can fail. It is guaranteed to free up one or more data nodes, so there should be enough space for the size change node, provided GC is invoked when necessary and the node sizes are compatible for this in corner cases. -- Jamie -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists