I encountered a minor build failure in fs/cramfs, which I was able to
fix with the following patch. I'm not sure if it's exactly the right
fix - does the original author really mean to have zeroes for those
values? Anyway, please consider applying to 2.5.66 if it's okay.
Jeremy Brown
--- linux-2.5.66/fs/cramfs/inode.c.orig 2003-03-24 16:01:07.000000000 -0800
+++ linux-2.5.66/fs/cramfs/inode.c 2003-03-24 16:09:18.000000000 -0800
@@ -43,6 +43,7 @@
static struct inode *get_cramfs_inode(struct super_block *sb, struct cramfs_inode * cramfs_inode)
{
struct inode * inode = new_inode(sb);
+ struct timespec zerotime = {0, 0};
if (inode) {
inode->i_mode = cramfs_inode->mode;
@@ -51,7 +52,7 @@
inode->i_blocks = (cramfs_inode->size - 1) / 512 + 1;
inode->i_blksize = PAGE_CACHE_SIZE;
inode->i_gid = cramfs_inode->gid;
- inode->i_mtime = inode->i_atime = inode->i_ctime = 0;
+ inode->i_mtime = inode->i_atime = inode->i_ctime = zerotime;
inode->i_ino = CRAMINO(cramfs_inode);
/* inode->i_nlink is left 1 - arguably wrong for directories,
but it's the best we can do without reading the directory
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Mar 31 2003 - 22:00:18 EST