Re: [PATCH] reiserfs: reiserfs_file_write will lose error code when a 0-length write occurs w/ O_SYNC

2006-03-03 Thread Hans Reiser
Andrew Morton wrote: Boy, lots of reiserfs things happening lately. We presently have: reiserfs-do-not-check-if-unsigned-0.patch [ merged today ] reiserfs-fix-transaction-overflowing.patch reiserfs-handle-trans_id-overflow.patch

Re: [PATCH] reiserfs: reiserfs_file_write will lose error code when a 0-length write occurs w/ O_SYNC

2006-03-03 Thread Clemens Eisserer
I suggest that they sit in -mm or an rc for ~2 weeks before they go in. If 2.6.16 is coming out before then, then let it ship without them. All of these things are pretty obscure/rare, so not unsettling the code matters more than getting them in. I know this sounds quite a bit stupid but

[PATCH] reiserfs: reiserfs_file_write will lose error code when a 0-length write occurs w/ O_SYNC

2006-03-02 Thread Jeff Mahoney
When an error occurs in reiserfs_file_write before any data is written, and O_SYNC is set, the return code of generic_osync_write will overwrite the error code, losing it. This patch ensures that generic_osync_inode() doesn't run under an error condition, losing the error. This duplicates

Re: [PATCH] reiserfs: reiserfs_file_write will lose error code when a 0-length write occurs w/ O_SYNC

2006-03-02 Thread Andrew Morton
Boy, lots of reiserfs things happening lately. We presently have: reiserfs-do-not-check-if-unsigned-0.patch [ merged today ] reiserfs-fix-transaction-overflowing.patch reiserfs-handle-trans_id-overflow.patch