Messages in this thread Patch in this message | | | From | dan@pwienter ... | Subject | Re: [PATCH]: initialize parts of udf inode earlier in create | Date | Mon, 07 Aug 2006 00:14:20 -0700 |
| |
> I saw an oops down this path when trying to create a new file on a UDF > filesystem which was internally marked as readonly, but mounted rw: > > udf_create > udf_new_inode > new_inode > alloc_inode > udf_alloc_inode > udf_new_block > returns EIO due to readonlyness > iput (on error)
I ran into the same issue today, but when listing a directory with invalid/corrupt entries:
udf_lookup udf_iget get_new_inode_fast alloc_inode udf_alloc_inode __udf_read_inode fails for any reason iput (on error) ...
The following patch to udf_alloc_inode() should take care of both (and other similar) cases, but I've only tested it with udf_lookup().
Dan
--
Signed-off-by: Dan Bastone <dan@pwienterprises.com>
--- linux-2.6.17.7/fs/udf/super.c.orig +++ linux-2.6.17.7/fs/udf/super.c @@ -116,6 +116,13 @@ ei = (struct udf_inode_info *)kmem_cache_alloc(udf_inode_cachep, SLAB_KERNEL); if (!ei) return NULL; + + ei->i_unique = 0; + ei->i_lenExtents = 0; + ei->i_next_alloc_block = 0; + ei->i_next_alloc_goal = 0; + ei->i_strat4096 = 0; + return &ei->vfs_inode; }
--
diegogarcia@cluemail.com
-- http://www.fastmail.fm - Email service worth paying for. Try it for free
- 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/
| |