)]}' { "log": [ { "commit": "6a6160a7b5c27b3c38651baef92a14fa7072b3c1", "tree": "a4a7640bd12611c445dfc013f69ce307674d1b13", "parents": [ "64fd1de3d821659ac0a3004fd5ee1de59e64af30" ], "author": { "name": "Heiko Carstens", "email": "heiko.carstens@de.ibm.com", "time": "Wed Jan 14 14:14:15 2009 +0100" }, "committer": { "name": "Heiko Carstens", "email": "heiko.carstens@de.ibm.com", "time": "Wed Jan 14 14:15:23 2009 +0100" }, "message": "[CVE-2009-0029] System call wrappers part 13\n\nSigned-off-by: Heiko Carstens \u003cheiko.carstens@de.ibm.com\u003e\n" }, { "commit": "4c728ef583b3d82266584da5cb068294c09df31e", "tree": "1252fa82b5a7cf60c0898c3da810228b4c34ebb3", "parents": [ "6110e3abbff8b785907d4db50240e63c1be726e3" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Mon Dec 22 21:11:15 2008 +0100" }, "committer": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Mon Jan 05 11:54:28 2009 -0500" }, "message": "add a vfs_fsync helper\n\nFsync currently has a fdatawrite/fdatawait pair around the method call,\nand a mutex_lock/unlock of the inode mutex. All callers of fsync have\nto duplicate this, but we have a few and most of them don\u0027t quite get\nit right. This patch adds a new vfs_fsync that takes care of this.\nIt\u0027s a little more complicated as usual as -\u003efsync might get a NULL file\npointer and just a dentry from nfsd, but otherwise gets afile and we\nwant to take the mapping and file operations from it when it is there.\n\nNotes on the fsync callers:\n\n - ecryptfs wasn\u0027t calling filemap_fdatawrite / filemap_fdatawait on the\n \tlower file\n - coda wasn\u0027t calling filemap_fdatawrite / filemap_fdatawait on the host\n\tfile, and returning 0 when -\u003efsync was missing\n - shm wasn\u0027t calling either filemap_fdatawrite / filemap_fdatawait nor\n taking i_mutex. Now given that shared memory doesn\u0027t have disk\n backing not doing anything in fsync seems fine and I left it out of\n the vfs_fsync conversion for now, but in that case we might just\n not pass it through to the lower file at all but just call the no-op\n simple_sync_file directly.\n\n[and now actually export vfs_fsync]\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\n" }, { "commit": "e8edc6e03a5c8562dc70a6d969f732bdb355a7e7", "tree": "fc86c863655128a7041dfe613d14393d761fa7b9", "parents": [ "ff1be9ad61e3e17ba83702d8ed0b534e5b8ee15c" ], "author": { "name": "Alexey Dobriyan", "email": "adobriyan@gmail.com", "time": "Mon May 21 01:22:52 2007 +0400" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Mon May 21 09:18:19 2007 -0700" }, "message": "Detach sched.h from mm.h\n\nFirst thing mm.h does is including sched.h solely for can_do_mlock() inline\nfunction which has \"current\" dereference inside. By dealing with can_do_mlock()\nmm.h can be detached from sched.h which is good. See below, why.\n\nThis patch\na) removes unconditional inclusion of sched.h from mm.h\nb) makes can_do_mlock() normal function in mm/mlock.c\nc) exports can_do_mlock() to not break compilation\nd) adds sched.h inclusions back to files that were getting it indirectly.\ne) adds less bloated headers to some files (asm/signal.h, jiffies.h) that were\n getting them indirectly\n\nNet result is:\na) mm.h users would get less code to open, read, preprocess, parse, ... if\n they don\u0027t need sched.h\nb) sched.h stops being dependency for significant number of files:\n on x86_64 allmodconfig touching sched.h results in recompile of 4083 files,\n after patch it\u0027s only 3744 (-8.3%).\n\nCross-compile tested on\n\n\tall arm defconfigs, all mips defconfigs, all powerpc defconfigs,\n\talpha alpha-up\n\tarm\n\ti386 i386-up i386-defconfig i386-allnoconfig\n\tia64 ia64-up\n\tm68k\n\tmips\n\tparisc parisc-up\n\tpowerpc powerpc-up\n\ts390 s390-up\n\tsparc sparc-up\n\tsparc64 sparc64-up\n\tum-x86_64\n\tx86_64 x86_64-up x86_64-defconfig x86_64-allnoconfig\n\nas well as my two usual configs.\n\nSigned-off-by: Alexey Dobriyan \u003cadobriyan@gmail.com\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "204ec841fbea3e5138168edbc3a76d46747cc987", "tree": "bc52089e8862b24d7f4153b56eaf7ecc3f1af9fe", "parents": [ "ee6a6457886a80415db209e87033b63f2b06558c" ], "author": { "name": "Peter Zijlstra", "email": "a.p.zijlstra@chello.nl", "time": "Mon Sep 25 23:31:01 2006 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Tue Sep 26 08:48:45 2006 -0700" }, "message": "[PATCH] mm: msync() cleanup\n\nWith the tracking of dirty pages properly done now, msync doesn\u0027t need to scan\nthe PTEs anymore to determine the dirty status.\n\nFrom: Hugh Dickins \u003chugh@veritas.com\u003e\n\nIn looking to do that, I made some other tidyups: can remove several\n#includes, and sys_msync loop termination not quite right.\n\nMost of those points are criticisms of the existing sys_msync, not of your\npatch. In particular, the loop termination errors were introduced in 2.6.17:\nI did notice this shortly before it came out, but decided I was more likely to\nget it wrong myself, and make matters worse if I tried to rush a last-minute\nfix in. And it\u0027s not terribly likely to go wrong, nor disastrous if it does\ngo wrong (may miss reporting an unmapped area; may also fsync file of a\nfollowing vma).\n\nSigned-off-by: Peter Zijlstra \u003ca.p.zijlstra@chello.nl\u003e\nSigned-off-by: Hugh Dickins \u003chugh@veritas.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "b31dc66a54ad986b6b73bdc49c8efc17cbad1833", "tree": "5591383c1cbffe11512da889c971f899333f1a44", "parents": [ "271f18f102c789f59644bb6c53a69da1df72b2f4" ], "author": { "name": "Jens Axboe", "email": "axboe@suse.de", "time": "Tue Jun 13 08:26:10 2006 +0200" }, "committer": { "name": "Jens Axboe", "email": "axboe@nelson.home.kernel.dk", "time": "Fri Jun 23 17:10:39 2006 +0200" }, "message": "[PATCH] Kill PF_SYNCWRITE flag\n\nA process flag to indicate whether we are doing sync io is incredibly\nugly. It also causes performance problems when one does a lot of async\nio and then proceeds to sync it. Part of the io will go out as async,\nand the other part as sync. This causes a disconnect between the\npreviously submitted io and the synced io. For io schedulers such as CFQ,\nthis will cause us lost merges and suboptimal behaviour in scheduling.\n\nRemove PF_SYNCWRITE completely from the fsync/msync paths, and let\nthe O_DIRECT path just directly indicate that the writes are sync\nby using WRITE_SYNC instead.\n\nSigned-off-by: Jens Axboe \u003caxboe@suse.de\u003e\n" }, { "commit": "16538c40776b8be6b0f23966e08fdc7b8fff823f", "tree": "77646f8bf17f0ef78ea9c50415ab639a734dc870", "parents": [ "de0dfcdf550e6339e9f373587da62cffb5b559f8" ], "author": { "name": "Amos Waterland", "email": "apw@us.ibm.com", "time": "Fri Mar 24 18:30:53 2006 +0100" }, "committer": { "name": "Adrian Bunk", "email": "bunk@stusta.de", "time": "Fri Mar 24 18:30:53 2006 +0100" }, "message": "The comment describing how MS_ASYNC works in msync.c is confusing\nbecause of a typo. This patch just changes \"my\" to \"by\", which I\nbelieve was the original intent.\n\nSigned-off-by: Adrian Bunk \u003cbunk@stusta.de\u003e\n" }, { "commit": "8f2e9f157a94f444dad974b088b853ac40785b02", "tree": "a8a3b2413ffb2a4a6f84762f052f0f6b4699ef9a", "parents": [ "18e79b40ed9c5223b88771f805c69f5993fc131b" ], "author": { "name": "Andrew Morton", "email": "akpm@osdl.org", "time": "Fri Mar 24 03:18:15 2006 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Fri Mar 24 07:33:27 2006 -0800" }, "message": "[PATCH] msync(): use do_fsync()\n\nNo need to duplicate all that code.\n\nCc: Hugh Dickins \u003chugh@veritas.com\u003e\nCc: Nick Piggin \u003cnickpiggin@yahoo.com.au\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "676758bdb7bfca8413a85203921746f446e237be", "tree": "23c731f429652e16f2cdba98cd503eaa059f929b", "parents": [ "707c21c848deeb0200ba3f07e4ba90e6dc419c2f" ], "author": { "name": "Andrew Morton", "email": "akpm@osdl.org", "time": "Fri Mar 24 03:18:14 2006 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Fri Mar 24 07:33:26 2006 -0800" }, "message": "[PATCH] msync: fix return value\n\nmsync() does a strange thing. Essentially:\n\n\tvma \u003d find_vma();\n\tfor ( ; ; ) {\n\t\tif (!vma)\n\t\t\treturn -ENOMEM;\n\t\t...\n\t\tvma \u003d vma-\u003evm_next;\n\t}\n\nso an msync() request which starts within or before a valid VMA and which ends\nwithin or beyond the final VMA will incorrectly return -ENOMEM.\n\nFix.\n\nCc: Hugh Dickins \u003chugh@veritas.com\u003e\nCc: Nick Piggin \u003cnickpiggin@yahoo.com.au\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "707c21c848deeb0200ba3f07e4ba90e6dc419c2f", "tree": "d8e8f32916ac1f04e45e42595ddd0ef771ddb1ad", "parents": [ "9c50823eebf7c256b92b4e0f02b5fb30e97788c2" ], "author": { "name": "Andrew Morton", "email": "akpm@osdl.org", "time": "Fri Mar 24 03:18:13 2006 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Fri Mar 24 07:33:26 2006 -0800" }, "message": "[PATCH] msync(MS_SYNC): don\u0027t hold mmap_sem while syncing\n\nIt seems bad to hold mmap_sem while performing synchronous disk I/O. Alter\nthe msync(MS_SYNC) code so that the lock is released while we sync the file.\n\nCc: Hugh Dickins \u003chugh@veritas.com\u003e\nCc: Nick Piggin \u003cnickpiggin@yahoo.com.au\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "9c50823eebf7c256b92b4e0f02b5fb30e97788c2", "tree": "241b754698c3501355d1061c828ab6d894dba617", "parents": [ "4741c9fd36b3bcadd37238321c469049da94a4b9" ], "author": { "name": "Andrew Morton", "email": "akpm@osdl.org", "time": "Fri Mar 24 03:18:12 2006 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Fri Mar 24 07:33:26 2006 -0800" }, "message": "[PATCH] msync(): perform dirty page levelling\n\nIt seems sensible to perform dirty page throttling in msync: as the application\ndirties pages we can kick off pdflush early, or even force the msync() caller\nto perform writeout, or even throttle the msync() caller.\n\nThe main effect of this is to start disk writeback earlier if we\u0027ve just\ndiscovered that a large amount of pagecache has been dirtied. (Otherwise it\nwouldn\u0027t happen for up to five seconds, next time pdflush wakes up).\n\nIt also will cause the page-dirtying process to get panalised for dirtying\nthose pages rather than whacking someone else with the problem.\n\nWe should do this for munmap() and possibly even exit(), too.\n\nWe drop the mmap_sem while performing the dirty page balancing. It doesn\u0027t\nseem right to hold mmap_sem for that long.\n\nNote that this patch only affects MS_ASYNC. MS_SYNC will be syncing all the\ndirty pages anyway.\n\nWe note that msync(MS_SYNC) does a full-file-sync inside mmap_sem, and always\nhas. We can fix that up...\n\nThe patch also tightens up the mmap_sem coverage in sys_msync(): no point in\ntaking it while we perform the incoming arg checking.\n\nCc: Hugh Dickins \u003chugh@veritas.com\u003e\nCc: Nick Piggin \u003cnickpiggin@yahoo.com.au\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "1b1dcc1b57a49136f118a0f16367256ff9994a69", "tree": "b0b36d4f41d28c9d6514fb309d33c1a084d6309b", "parents": [ "794ee1baee1c26be40410233e6c20bceb2b03c08" ], "author": { "name": "Jes Sorensen", "email": "jes@sgi.com", "time": "Mon Jan 09 15:59:24 2006 -0800" }, "committer": { "name": "Ingo Molnar", "email": "mingo@hera.kernel.org", "time": "Mon Jan 09 15:59:24 2006 -0800" }, "message": "[PATCH] mutex subsystem, semaphore to mutex: VFS, -\u003ei_sem\n\nThis patch converts the inode semaphore to a mutex. I have tested it on\nXFS and compiled as much as one can consider on an ia64. Anyway your\nluck with it might be different.\n\nModified-by: Ingo Molnar \u003cmingo@elte.hu\u003e\n\n(finished the conversion)\n\nSigned-off-by: Jes Sorensen \u003cjes@sgi.com\u003e\nSigned-off-by: Ingo Molnar \u003cmingo@elte.hu\u003e\n" }, { "commit": "6aab341e0a28aff100a09831c5300a2994b8b986", "tree": "1af3908275aa5e1b16e80efee554a9a7504c56d4", "parents": [ "458af5439fe7ae7d95ca14106844e61f0795166c" ], "author": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Mon Nov 28 14:34:23 2005 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Mon Nov 28 14:34:23 2005 -0800" }, "message": "mm: re-architect the VM_UNPAGED logic\n\nThis replaces the (in my opinion horrible) VM_UNMAPPED logic with very\nexplicit support for a \"remapped page range\" aka VM_PFNMAP. It allows a\nVM area to contain an arbitrary range of page table entries that the VM\nnever touches, and never considers to be normal pages.\n\nAny user of \"remap_pfn_range()\" automatically gets this new\nfunctionality, and doesn\u0027t even have to mark the pages reserved or\nindeed mark them any other way. It just works. As a side effect, doing\nmmap() on /dev/mem works for arbitrary ranges.\n\nSparc update from David in the next commit.\n\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "0b14c179a483e71ea41df2aa4a661760063115bd", "tree": "075fc303a3d2fd33f66c0af8f64064cff2b72b79", "parents": [ "664beed0190fae687ac51295694004902ddeb18e" ], "author": { "name": "Hugh Dickins", "email": "hugh@veritas.com", "time": "Mon Nov 21 21:32:15 2005 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Tue Nov 22 09:13:42 2005 -0800" }, "message": "[PATCH] unpaged: VM_UNPAGED\n\nAlthough we tend to associate VM_RESERVED with remap_pfn_range, quite a few\ndrivers set VM_RESERVED on areas which are then populated by nopage. The\nPageReserved removal in 2.6.15-rc1 changed VM_RESERVED not to free pages in\nzap_pte_range, without changing those drivers not to set it: so their pages\njust leak away.\n\nLet\u0027s not change miscellaneous drivers now: introduce VM_UNPAGED at the core,\nto flag the special areas where the ptes may have no struct page, or if they\nhave then it\u0027s not to be touched. Replace most instances of VM_RESERVED in\ncore mm by VM_UNPAGED. Force it on in remap_pfn_range, and the sparc and\nsparc64 io_remap_pfn_range.\n\nRevert addition of VM_RESERVED to powerpc vdso, it\u0027s not needed there. Is it\nneeded anywhere? It still governs the mm-\u003ereserved_vm statistic, and special\nvmas not to be merged, and areas not to be core dumped; but could probably be\neliminated later (the drivers are probably specifying it because in 2.4 it\nkept swapout off the vma, but in 2.6 we work from the LRU, which these pages\ndon\u0027t get on).\n\nUse the VM_SHM slot for VM_UNPAGED, and define VM_SHM to 0: it serves no\npurpose whatsoever, and should be removed from drivers when we clean up.\n\nSigned-off-by: Hugh Dickins \u003chugh@veritas.com\u003e\nAcked-by: William Irwin \u003cwli@holomorphy.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "705e87c0c3c38424f7f30556c85bc20e808d2f59", "tree": "7a237e6266f4801385e1226cc497b47e3a2458bd", "parents": [ "8f4e2101fd7df9031a754eedb82e2060b51f8c45" ], "author": { "name": "Hugh Dickins", "email": "hugh@veritas.com", "time": "Sat Oct 29 18:16:27 2005 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Sat Oct 29 21:40:40 2005 -0700" }, "message": "[PATCH] mm: pte_offset_map_lock loops\n\nConvert those common loops using page_table_lock on the outside and\npte_offset_map within to use just pte_offset_map_lock within instead.\n\nThese all hold mmap_sem (some exclusively, some not), so at no level can a\npage table be whipped away from beneath them. But whereas pte_alloc loops\ntested with the \"atomic\" pmd_present, these loops are testing with pmd_none,\nwhich on i386 PAE tests both lower and upper halves.\n\nThat\u0027s now unsafe, so add a cast into pmd_none to test only the vital lower\nhalf: we lose a little sensitivity to a corrupt middle directory, but not\nenough to worry about. It appears that i386 and UML were the only\narchitectures vulnerable in this way, and pgd and pud no problem.\n\nSigned-off-by: Hugh Dickins \u003chugh@veritas.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "b5810039a54e5babf428e9a1e89fc1940fabff11", "tree": "835836cb527ec9bd525f93eb7e016f3dfb8c8ae2", "parents": [ "f9c98d0287de42221c624482fd4f8d485c98ab22" ], "author": { "name": "Nick Piggin", "email": "nickpiggin@yahoo.com.au", "time": "Sat Oct 29 18:16:12 2005 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Sat Oct 29 21:40:39 2005 -0700" }, "message": "[PATCH] core remove PageReserved\n\nRemove PageReserved() calls from core code by tightening VM_RESERVED\nhandling in mm/ to cover PageReserved functionality.\n\nPageReserved special casing is removed from get_page and put_page.\n\nAll setting and clearing of PageReserved is retained, and it is now flagged\nin the page_alloc checks to help ensure we don\u0027t introduce any refcount\nbased freeing of Reserved pages.\n\nMAP_PRIVATE, PROT_WRITE of VM_RESERVED regions is tentatively being\ndeprecated. We never completely handled it correctly anyway, and is be\nreintroduced in future if required (Hugh has a proof of concept).\n\nOnce PageReserved() calls are removed from kernel/power/swsusp.c, and all\narch/ and driver code, the Set and Clear calls, and the PG_reserved bit can\nbe trivially removed.\n\nLast real user of PageReserved is swsusp, which uses PageReserved to\ndetermine whether a struct page points to valid memory or not. This still\nneeds to be addressed (a generic page_is_ram() should work).\n\nA last caveat: the ZERO_PAGE is now refcounted and managed with rmap (and\nthus mapcounted and count towards shared rss). These writes to the struct\npage could cause excessive cacheline bouncing on big systems. There are a\nnumber of ways this could be addressed if it is an issue.\n\nSigned-off-by: Nick Piggin \u003cnpiggin@suse.de\u003e\n\nRefcount bug fix for filemap_xip.c\n\nSigned-off-by: Carsten Otte \u003ccotte@de.ibm.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "0c942a4539c09adf09097315cc174aefd0eeedf7", "tree": "b9b7d5093ca0a130ef2221f8932fabcf4291f6a6", "parents": [ "e040f218bb49a6965a5b77edce05fe47a62dda39" ], "author": { "name": "Hugh Dickins", "email": "hugh@veritas.com", "time": "Sat Oct 29 18:15:53 2005 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Sat Oct 29 21:40:36 2005 -0700" }, "message": "[PATCH] mm: msync_pte_range progress\n\nUse latency breaking in msync_pte_range like that in copy_pte_range, instead\nof the ugly CONFIG_PREEMPT filemap_msync alternatives.\n\nSigned-off-by: Hugh Dickins \u003chugh@veritas.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "b57b98d147ef98758886a39efb94f3254542c39b", "tree": "1aab53a2bb1add92d55fbce963e371527c05d281", "parents": [ "662f3a0b94cc92bd708c27b80f8207cd7db93204" ], "author": { "name": "OGAWA Hirofumi", "email": "hirofumi@mail.parknet.co.jp", "time": "Sat Oct 29 18:15:50 2005 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Sat Oct 29 21:40:36 2005 -0700" }, "message": "[PATCH] mm/msync.c cleanup\n\nThis is not problem actually, but sync_page_range() is using for exported\nfunction to filesystems.\n\nThe msync_xxx is more readable at least to me.\n\nSigned-off-by: OGAWA Hirofumi \u003chirofumi@mail.parknet.co.jp\u003e\nAcked-by: Hugh Dickins \u003chugh@veritas.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "b4955ce3dd0818b56da532a16c9a4a3804a558ee", "tree": "6e01667181bfc495b56e39748783ad2235a4f56e", "parents": [ "c475a8ab625d567eacf5e30ec35d6d8704558062" ], "author": { "name": "Abhijit Karmarkar", "email": "abhijitk@veritas.com", "time": "Tue Jun 21 17:15:13 2005 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@ppc970.osdl.org", "time": "Tue Jun 21 18:46:21 2005 -0700" }, "message": "[PATCH] msync: check pte dirty earlier\n\nIt\u0027s common practice to msync a large address range regularly, in which\noften only a few ptes have actually been dirtied since the previous pass.\n\nsync_pte_range then goes much faster if it tests whether pte is dirty\nbefore locating and accessing each struct page cacheline; and it is hardly\nslowed by ptep_clear_flush_dirty repeating that test in the opposite case,\nwhen every pte actually is dirty.\n\nBut beware, s390\u0027s pte_dirty always says false, since its dirty bit is kept\nin the storage key, located via the struct page address. So skip this\noptimization in its case: use a pte_maybe_dirty macro which just says true\nif page_test_and_clear_dirty is implemented.\n\nSigned-off-by: Abhijit Karmarkar \u003cabhijitk@veritas.com\u003e\nSigned-off-by: Hugh Dickins \u003chugh@veritas.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2", "tree": "0bba044c4ce775e45a88a51686b5d9f90697ea9d", "parents": [], "author": { "name": "Linus Torvalds", "email": "torvalds@ppc970.osdl.org", "time": "Sat Apr 16 15:20:36 2005 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@ppc970.osdl.org", "time": "Sat Apr 16 15:20:36 2005 -0700" }, "message": "Linux-2.6.12-rc2\n\nInitial git repository build. I\u0027m not bothering with the full history,\neven though we have it. We can create a separate \"historical\" git\narchive of that later if we want to, and in the meantime it\u0027s about\n3.2GB when imported into git - space that would just make the early\ngit days unnecessarily complicated, when we don\u0027t have a lot of good\ninfrastructure for it.\n\nLet it rip!\n" } ] }