> if (pos + count > inode->i_sb->s_maxbytes) > { > count = inode->i_sb->s_maxbytes - count; > goto out; > } > > looks funny - goto out means that new (and rather meaningless) value of > count goes to hell. Shouldn't we remove that line and s/- count/- pos/ I already fixed that in my tree. We also send signals in a couple of spots we shouldnt tht I fixed Alan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- Re: ramfs problem... (unlink o... Stefan Traby
- Re: ramfs problem... (unlink o... Alexander Viro
- Re: ramfs problem... (unlink o... Stefan Traby
- Re: ramfs problem... (unlink o... Marc Lehmann
- Re: ramfs problem... (unlink o... Alexander Viro
- Re: ramfs problem... (unlink o... Alexander Viro
- Re: ramfs problem... (unlink o... Chris Mason
- Re: ramfs problem... (unlink o... Alexander Viro
- Re: ramfs problem... (unlink o... Chris Mason
- Re: ramfs problem... (unlink o... Alexander Viro
- Re: ramfs problem... (unlink o... Alan Cox
- Re: ramfs problem... (unlink o... Andreas Dilger
- Re: ramfs problem... (unlink o... Alexander Viro
- Re: ramfs problem... (unlink o... Andreas Dilger
- Re: ramfs problem... (unlink o... David Woodhouse
- Re: ramfs problem... (unlink of sparse file in "D&q... Alan Cox
- Re: ramfs problem... (unlink of sparse file in &quo... Eric W. Biederman
- Re: ramfs problem... (unlink of sparse file in ... Alan Cox
- Re: ramfs problem... (unlink of sparse file... Eric W. Biederman
- Re: ramfs problem... (unlink of sparse file in "D&q... Alan Cox
- Re: ramfs problem... (unlink of sparse file in "D&q... Alan Cox