)]}' { "log": [ { "commit": "edd5cd4a9424f22b0fa08bef5e299d41befd5622", "tree": "dba461b19b066c862a2c4e443b2deb9443bc78c5", "parents": [ "2f4d4da8f82c2598b8713f4a01f360f3751d90be" ], "author": { "name": "David Woodhouse", "email": "dwmw2@infradead.org", "time": "Wed Jun 27 14:10:09 2007 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Thu Jun 28 11:38:30 2007 -0700" }, "message": "Introduce fixed sys_sync_file_range2() syscall, implement on PowerPC and ARM\n\nNot all the world is an i386. Many architectures need 64-bit arguments to be\naligned in suitable pairs of registers, and the original\nsys_sync_file_range(int, loff_t, loff_t, int) was therefore wasting an\nargument register for padding after the first integer. Since we don\u0027t\nnormally have more than 6 arguments for system calls, that left no room for\nthe final argument on some architectures.\n\nFix this by introducing sys_sync_file_range2(int, int, loff_t, loff_t) which\nall fits nicely. In fact, ARM already had that, but called it\nsys_arm_sync_file_range. Move it to fs/sync.c and rename it, then implement\nthe needed compatibility routine. And stop the missing syscall check from\nbitching about the absence of sys_sync_file_range() if we\u0027ve implemented\nsys_sync_file_range2() instead.\n\nTested on PPC32 and with 32-bit and 64-bit userspace on PPC64.\n\nSigned-off-by: David Woodhouse \u003cdwmw2@infradead.org\u003e\nAcked-by: Russell King \u003crmk+kernel@arm.linux.org.uk\u003e\nCc: Arnd Bergmann \u003carnd@arndb.de\u003e\nCc: Paul Mackerras \u003cpaulus@samba.org\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "ef51c97623b94f51e439ac91d2736aab3d1b6594", "tree": "5c020421f1e5a6e28b5a9f341fec32479a8ffb3a", "parents": [ "524e6752912a891a396a9cf74c5d7d60fff5510a" ], "author": { "name": "Mark Fasheh", "email": "mark.fasheh@oracle.com", "time": "Tue May 08 00:27:10 2007 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Tue May 08 11:15:04 2007 -0700" }, "message": "Remove do_sync_file_range()\n\nRemove do_sync_file_range() and convert callers to just use\ndo_sync_mapping_range().\n\nSigned-off-by: Mark Fasheh \u003cmark.fasheh@oracle.com\u003e\nCc: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "5b04aa3a64f854244bc40a6f528176ed50b5c4f6", "tree": "2bdee522ce482f06a9f3adc8e66e4ff23be06860", "parents": [ "60b11392f1a09433740bda3048202213daa27736" ], "author": { "name": "Mark Fasheh", "email": "mark.fasheh@oracle.com", "time": "Thu Mar 01 11:01:55 2007 -0800" }, "committer": { "name": "Mark Fasheh", "email": "mark.fasheh@oracle.com", "time": "Thu Apr 26 15:02:26 2007 -0700" }, "message": "[PATCH] Turn do_sync_file_range() into do_sync_mapping_range()\n\ndo_sync_file_range() accepts a file * from which it takes an address_space to\nsync. Abstract out the bulk of the function into do_sync_mapping_range()\nwhich takes the address_space directly. This way callers who want to sync an\naddress_space directly can take advantage of the functionality provided.\n\ndo_sync_file_range() is preserved as a small wrapper around\ndo_sync_mapping_range().\n\nOcfs2 in particular would like to use this to initiate a sync of a specific\ninode range during truncate, where a file * may not be available.\n\nSigned-off-by: Mark Fasheh \u003cmark.fasheh@oracle.com\u003e\nCc: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\n" }, { "commit": "0f7fc9e4d03987fe29f6dd4aa67e4c56eb7ecb05", "tree": "51763269e44eb9bf4d0f8c529577489902850cf9", "parents": [ "b65d34fd465f19fbe2f32f2205a9a06ca7c2bdeb" ], "author": { "name": "Josef \"Jeff\" Sipek", "email": "jsipek@cs.sunysb.edu", "time": "Fri Dec 08 02:36:35 2006 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.osdl.org", "time": "Fri Dec 08 08:28:41 2006 -0800" }, "message": "[PATCH] VFS: change struct file to use struct path\n\nThis patch changes struct file to use struct path instead of having\nindependent pointers to struct dentry and struct vfsmount, and converts all\nusers of f_{dentry,vfsmnt} in fs/ to use f_path.{dentry,mnt}.\n\nAdditionally, it adds two #define\u0027s to make the transition easier for users of\nthe f_dentry and f_vfsmnt.\n\nSigned-off-by: Josef \"Jeff\" Sipek \u003cjsipek@cs.sunysb.edu\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "914e26379decf1fd984b22e51fd2e4209b7a7f1b", "tree": "4f20ee40e959699e344cdff0e117d309d238f6be", "parents": [ "f6a570333e554b48ad589e7137c77c57809eee81" ], "author": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Wed Oct 18 13:55:46 2006 -0400" }, "committer": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Mon Dec 04 02:00:24 2006 -0500" }, "message": "[PATCH] severing fs.h, radix-tree.h -\u003e sched.h\n\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\n" }, { "commit": "cf9a2ae8d49948f861b56e5333530e491a9da190", "tree": "21f0b0d781b3e60cc60464d39b6d95681201b37e", "parents": [ "4090959aee403817ff386415f9bc602c1a0882ef" ], "author": { "name": "David Howells", "email": "dhowells@redhat.com", "time": "Tue Aug 29 19:05:54 2006 +0100" }, "committer": { "name": "Jens Axboe", "email": "axboe@nelson.home.kernel.dk", "time": "Sat Sep 30 20:31:19 2006 +0200" }, "message": "[PATCH] BLOCK: Move functions out of buffer code [try #6]\n\nMove some functions out of the buffering code that aren\u0027t strictly buffering\nspecific. This is a precursor to being able to disable the block layer.\n\n (*) Moved some stuff out of fs/buffer.c:\n\n (*) The file sync and general sync stuff moved to fs/sync.c.\n\n (*) The superblock sync stuff moved to fs/super.c.\n\n (*) do_invalidatepage() moved to mm/truncate.c.\n\n (*) try_to_release_page() moved to mm/filemap.c.\n\n (*) Moved some related declarations between header files:\n\n (*) declarations for do_invalidatepage() and try_to_release_page() moved\n \t to linux/mm.h.\n\n (*) __set_page_dirty_buffers() moved to linux/buffer_head.h.\n\nSigned-Off-By: David Howells \u003cdhowells@redhat.com\u003e\nSigned-off-by: Jens Axboe \u003caxboe@kernel.dk\u003e\n" }, { "commit": "111ebb6e6f7bd7de6d722c5848e95621f43700d9", "tree": "bb00b13001db9be201e9b6d31468a79f4d1240bf", "parents": [ "4c91c3648c620003cb7b21b8858f36cd6132e168" ], "author": { "name": "OGAWA Hirofumi", "email": "hirofumi@mail.parknet.co.jp", "time": "Fri Jun 23 02:03:26 2006 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Fri Jun 23 07:42:49 2006 -0700" }, "message": "[PATCH] writeback: fix range handling\n\nWhen a writeback_control\u0027s `start\u0027 and `end\u0027 fields are used to\nindicate a one-byte-range starting at file offset zero, the required\nvalues of .start\u003d0,.end\u003d0 mean that the -\u003ewritepages() implementation\nhas no way of telling that it is being asked to perform a range\nrequest. Because we\u0027re currently overloading (start \u003d\u003d 0 \u0026\u0026 end \u003d\u003d 0)\nto mean \"this is not a write-a-range request\".\n\nTo make all this sane, the patch changes range of writeback_control.\n\nSo caller does: If it is calling -\u003ewritepages() to write pages, it\nsets range (range_start/end or range_cyclic) always.\n\nAnd if range_cyclic is true, -\u003ewritepages() thinks the range is\ncyclic, otherwise it just uses range_start and range_end.\n\nThis patch does,\n\n - Add LLONG_MAX, LLONG_MIN, ULLONG_MAX to include/linux/kernel.h\n -1 is usually ok for range_end (type is long long). But, if someone did,\n\n\t\trange_end +\u003d val;\t\trange_end is \"val - 1\"\n\t\tu64val \u003d range_end \u003e\u003e bits;\tu64val is \"~(0ULL)\"\n\n or something, they are wrong. So, this adds LLONG_MAX to avoid nasty\n things, and uses LLONG_MAX for range_end.\n\n - All callers of -\u003ewritepages() sets range_start/end or range_cyclic.\n\n - Fix updates of -\u003ewriteback_index. It seems already bit strange.\n If it starts at 0 and ended by check of nr_to_write, this last\n index may reduce chance to scan end of file. So, this updates\n -\u003ewriteback_index only if range_cyclic is true or whole-file is\n scanned.\n\nSigned-off-by: OGAWA Hirofumi \u003chirofumi@mail.parknet.co.jp\u003e\nCc: Nathan Scott \u003cnathans@sgi.com\u003e\nCc: Anton Altaparmakov \u003caia21@cantab.net\u003e\nCc: Steven French \u003csfrench@us.ibm.com\u003e\nCc: \"Vladimir V. Saveliev\" \u003cvs@namesys.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "5246d0503130fa58904c8beb987fcf93b96d8ab6", "tree": "c807f1bba6a1d5abf0b3a9f221bc3e49ca5810c8", "parents": [ "8833d328caf009f8da58337e17a2cf5d52993a7c" ], "author": { "name": "Andrew Morton", "email": "akpm@osdl.org", "time": "Mon Apr 10 22:53:57 2006 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Tue Apr 11 06:18:40 2006 -0700" }, "message": "[PATCH] sync_file_range(): use unsigned for flags\n\nUlrich suggested that the `flags\u0027 arg to sync_file_range() become unsigned.\n\nCc: Ulrich Drepper \u003cdrepper@redhat.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "f79e2abb9bd452d97295f34376dedbec9686b986", "tree": "56b9998caa11983556e842fb9a8143d86d765fa3", "parents": [ "d6dfd1310d3562698fd7c3c086f6c239f96394ac" ], "author": { "name": "Andrew Morton", "email": "akpm@osdl.org", "time": "Fri Mar 31 02:30:42 2006 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Fri Mar 31 12:18:54 2006 -0800" }, "message": "[PATCH] sys_sync_file_range()\n\nRemove the recently-added LINUX_FADV_ASYNC_WRITE and LINUX_FADV_WRITE_WAIT\nfadvise() additions, do it in a new sys_sync_file_range() syscall instead.\nReasons:\n\n- It\u0027s more flexible. Things which would require two or three syscalls with\n fadvise() can be done in a single syscall.\n\n- Using fadvise() in this manner is something not covered by POSIX.\n\nThe patch wires up the syscall for x86.\n\nThe sycall is implemented in the new fs/sync.c. The intention is that we can\nmove sys_fsync(), sys_fdatasync() and perhaps sys_sync() into there later.\n\nDocumentation for the syscall is in fs/sync.c.\n\nA test app (sync_file_range.c) is in\nhttp://www.zip.com.au/~akpm/linux/patches/stuff/ext3-tools.tar.gz.\n\nThe available-to-GPL-modules do_sync_file_range() is for knfsd: \"A COMMIT can\nsay NFS_DATA_SYNC or NFS_FILE_SYNC. I can skip the -\u003efsync call for\nNFS_DATA_SYNC which is hopefully the more common.\"\n\nNote: the `async\u0027 writeout mode SYNC_FILE_RANGE_WRITE will turn synchronous if\nthe queue is congested. This is trivial to fix: add a new flag bit, set\nwbc-\u003enonblocking. But I\u0027m not sure that we want to expose implementation\ndetails down to that level.\n\nNote: it\u0027s notable that we can sync an fd which wasn\u0027t opened for writing.\nSame with fsync() and fdatasync()).\n\nNote: the code takes some care to handle attempts to sync file contents\noutside the 16TB offset on 32-bit machines. It makes such attempts appear to\nsucceed, for best 32-bit/64-bit compatibility. Perhaps it should make such\nrequests fail...\n\nCc: Nick Piggin \u003cnickpiggin@yahoo.com.au\u003e\nCc: Michael Kerrisk \u003cmtk-manpages@gmx.net\u003e\nCc: Ulrich Drepper \u003cdrepper@redhat.com\u003e\nCc: Neil Brown \u003cneilb@cse.unsw.edu.au\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" } ] }