search for: ext3_write_inod

Hi, When trying to run a particular program, I reproducibly get a few dozen kernel messages of the form: attempt to access beyond end of device 03:06: rw=0, want=536995844, limit=11680168 attempt to access beyond end of device 03:06: rw=0, want=1342296068, limit=11680168

Hi, there appears to be a bug w.r.t. chown and quotas in ext3. In particular, if you "chown" a file on a filesystem with userquotas enabled, the quota charge in not transfered. ditto "chgrp" and group quotas. This happens because i_op->setattr has been redefined for files, and ext3_setattr doesn't do the DQUOT_TRANSFER like it should. I have fixed it by adding a

...removal of a number of changes in the core kernel which were required for to support the journalling of data. This has caused some duplication of core code within ext3, but it's not too bad. - A number of cleanups and resyncs with latest ext2. (Thanks, Al). - Reorganised and optimised ext3_write_inode() and the handling of files which were opened O_SYNC. - Move quota operations outside lock_super() - fixes last known source of quota deadlocks in -ac kernels. - Deleted large chunks of debug/development support code. - Improved handling of corner-case errors. - Improved robustness in out-...