{"push_id":1015557820,"size":27,"distinct_size":27,"ref":"refs/heads/for-testing","head":"e94029f4a3f8a7cf474572daaa93fa6a34d89104","before":"0376238eb6d2903d2758efc77d8bc4b5b0d96643","commits":[{"sha":"07580f44a1c4bb40e82466d0985f243149ccc58b","author":{"email":"965b4f244a439078f6539b0689879a65682668dc@gmail.com","name":"Nick Reuter"},"message":"configs: make savedefconfig for shamu\n\nChange-Id: I66ab4fbd7c20e7210486c6a245218bf12b426538","distinct":true,"url":"https://api.github.com/repos/elginsk8r/android_kernel_moto_shamu/commits/07580f44a1c4bb40e82466d0985f243149ccc58b"},{"sha":"5d0b8a09380c609d5693b1dd03d1fd85830fc905","author":{"email":"4596b3305151c7ee743192a95d394341e3d3b644@suse.de","name":"Takashi Iwai"},"message":"UPSTREAM: ALSA: timer: Harden slave timer list handling\n\n(cherry pick from commit b5a663aa426f4884c71cd8580adae73f33570f0d)\n\nA slave timer instance might be still accessible in a racy way while\noperating the master instance as it lacks of locking.  Since the\nmaster operation is mostly protected with timer->lock, we should cope\nwith it while changing the slave instance, too.  Also, some linked\nlists (active_list and ack_list) of slave instances aren't unlinked\nimmediately at stopping or closing, and this may lead to unexpected\naccesses.\n\nThis patch tries to address these issues.  It adds spin lock of\ntimer->lock (either from master or slave, which is equivalent) in a\nfew places.  For avoiding a deadlock, we ensure that the global\nslave_active_lock is always locked at first before each timer lock.\n\nAlso, ack and active_list of slave instances are properly unlinked at\nsnd_timer_stop() and snd_timer_close().\n\nLast but not least, remove the superfluous call of _snd_timer_stop()\nat removing slave links.  This is a noop, and calling it may confuse\nreaders wrt locking.  Further cleanup will follow in a later patch.\n\nActually we've got reports of use-after-free by syzkaller fuzzer, and\nthis hopefully fixes these issues.\n\nReported-by: Dmitry Vyukov <dvyukov@google.com>\nCc: <stable@vger.kernel.org>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nBug: 26636060","distinct":true,"url":"https://api.github.com/repos/elginsk8r/android_kernel_moto_shamu/commits/5d0b8a09380c609d5693b1dd03d1fd85830fc905"},{"sha":"f59266389895e342745e7ef1672b4aaedd437a1b","author":{"email":"c745fa7b96fe79db6d669643d5feb03ff0641332@gmail.com","name":"Jiang Liu"},"message":"mm: use totalram_pages instead of num_physpages at runtime\n\nThe global variable num_physpages is scheduled to be removed, so use\ntotalram_pages instead of num_physpages at runtime.\n\nChange-Id: I4dc536af143784161cc2272da34c6c69b74d027a\nSigned-off-by: Jiang Liu <jiang.liu@huawei.com>\nCc: Miklos Szeredi <miklos@szeredi.hu>\nCc: \"David S. Miller\" <davem@davemloft.net>\nCc: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>\nCc: James Morris <jmorris@namei.org>\nCc: Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>\nCc: Patrick McHardy <kaber@trash.net>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git\nGit-commit: 0ed5fd138539940a493dc69359cb2f49de70ad89\nSigned-off-by: Lime Yang <limey@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/elginsk8r/android_kernel_moto_shamu/commits/f59266389895e342745e7ef1672b4aaedd437a1b"},{"sha":"a903ab1d9ec08bd41a2208988763d50190c1810f","author":{"email":"84cd5483a2f9acd1c37251cba7c2908448f221b8@suse.cz","name":"Miklos Szeredi"},"message":"fuse: handle large user and group ID\n\ncommit 233a01fa9c4c7c41238537e8db8434667ff28a2f upstream.\n\nIf the number in \"user_id=N\" or \"group_id=N\" mount options was larger than\nINT_MAX then fuse returned EINVAL.\n\nFix this to handle all valid uid/gid values.\n\nSigned-off-by: Miklos Szeredi <mszeredi@suse.cz>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/elginsk8r/android_kernel_moto_shamu/commits/a903ab1d9ec08bd41a2208988763d50190c1810f"},{"sha":"feac669ffda37d2e1ed3f4b4763d2afb88936625","author":{"email":"d9be9ca3f1b2d450305e034a370ae798faff7dfb@codeaurora.org","name":"Vignesh Radhakrishnan"},"message":"fs: fuse: lock the new non-CMA page before replace_page_cache_page()\n\nWhile swapping a page in FUSE filesystem from a CMA to non-CMA page,\nwe call replace_page_cache_page() to swap and this function expects\nold and new page to be locked. Else we will hit a VM_BUG_ON in\nreplace_page_cache_page().\n\nHence, lock the page before calling replace_page_cache_page() to\nsatisfy its requirement and prevent hitting VM_BUG_ON condition.\n\nCRs-Fixed: 751088\nChange-Id: I1dbb90dbaa9f056f211754bad15ae76c9d7171a5\nSigned-off-by: Vignesh Radhakrishnan <vigneshr@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/elginsk8r/android_kernel_moto_shamu/commits/feac669ffda37d2e1ed3f4b4763d2afb88936625"},{"sha":"ad135b9f7e6ad16e8cf2d06084e3869ae490fac2","author":{"email":"c8cfd11518263806e885f2c6a2b61e35d49e4229@parallels.com","name":"Maxim Patlasov"},"message":"mm/page-writeback.c: add strictlimit feature\n\nThe feature prevents mistrusted filesystems (ie: FUSE mounts created by\nunprivileged users) to grow a large number of dirty pages before\nthrottling.  For such filesystems balance_dirty_pages always check bdi\ncounters against bdi limits.  I.e.  even if global \"nr_dirty\" is under\n\"freerun\", it's not allowed to skip bdi checks.  The only use case for now\nis fuse: it sets bdi max_ratio to 1% by default and system administrators\nare supposed to expect that this limit won't be exceeded.\n\nThe feature is on if a BDI is marked by BDI_CAP_STRICTLIMIT flag.  A\nfilesystem may set the flag when it initializes its BDI.\n\nThe problematic scenario comes from the fact that nobody pays attention to\nthe NR_WRITEBACK_TEMP counter (i.e.  number of pages under fuse\nwriteback).  The implementation of fuse writeback releases original page\n(by calling end_page_writeback) almost immediately.  A fuse request queued\nfor real processing bears a copy of original page.  Hence, if userspace\nfuse daemon doesn't finalize write requests in timely manner, an\naggressive mmap writer can pollute virtually all memory by those temporary\nfuse page copies.  They are carefully accounted in NR_WRITEBACK_TEMP, but\nnobody cares.\n\nTo make further explanations shorter, let me use \"NR_WRITEBACK_TEMP\nproblem\" as a shortcut for \"a possibility of uncontrolled grow of amount\nof RAM consumed by temporary pages allocated by kernel fuse to process\nwriteback\".\n\nThe problem was very easy to reproduce.  There is a trivial example\nfilesystem implementation in fuse userspace distribution: fusexmp_fh.c.  I\nadded \"sleep(1);\" to the write methods, then recompiled and mounted it.\nThen created a huge file on the mount point and run a simple program which\nmmap-ed the file to a memory region, then wrote a data to the region.  An\nhour later I observed almost all RAM consumed by fuse writeback.  Since\nthen some unrelated changes in kernel fuse made it more difficult to\nreproduce, but it is still possible now.\n\nPutting this theoretical happens-in-the-lab thing aside, there is another\nthing that really hurts real world (FUSE) users.  This is write-through\npage cache policy FUSE currently uses.  I.e.  handling write(2), kernel\nfuse populates page cache and flushes user data to the server\nsynchronously.  This is excessively suboptimal.  Pavel Emelyanov's patches\n(\"writeback cache policy\") solve the problem, but they also make resolving\nNR_WRITEBACK_TEMP problem absolutely necessary.  Otherwise, simply copying\na huge file to a fuse mount would result in memory starvation.  Miklos,\nthe maintainer of FUSE, believes strictlimit feature the way to go.\n\nAnd eventually putting FUSE topics aside, there is one more use-case for\nstrictlimit feature.  Using a slow USB stick (mass storage) in a machine\nwith huge amount of RAM installed is a well-known pain.  Let's make simple\ncomputations.  Assuming 64GB of RAM installed, existing implementation of\nbalance_dirty_pages will start throttling only after 9.6GB of RAM becomes\ndirty (freerun == 15% of total RAM).  So, the command \"cp 9GB_file\n/media/my-usb-storage/\" may return in a few seconds, but subsequent\n\"umount /media/my-usb-storage/\" will take more than two hours if effective\nthroughput of the storage is, to say, 1MB/sec.\n\nAfter inclusion of strictlimit feature, it will be trivial to add a knob\n(e.g.  /sys/devices/virtual/bdi/x:y/strictlimit) to enable it on demand.\nManually or via udev rule.  May be I'm wrong, but it seems to be quite a\nnatural desire to limit the amount of dirty memory for some devices we are\nnot fully trust (in the sense of sustainable throughput).\n\n[akpm@linux-foundation.org: fix warning in page-writeback.c]\nSigned-off-by: Maxim Patlasov <MPatlasov@parallels.com>\nCc: Jan Kara <jack@suse.cz>\nCc: Miklos Szeredi <miklos@szeredi.hu>\nCc: Wu Fengguang <fengguang.wu@intel.com>\nCc: Pavel Emelyanov <xemul@parallels.com>\nCc: James Bottomley <James.Bottomley@HansenPartnership.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nGit-commit: 5a53748568f79641eaf40e41081a2f4987f005c2\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git\nChange-Id: I2def00e492ab04b4938d11e35dfc87656b2acf20\nSigned-off-by: Tarun Gupta <tarung@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/elginsk8r/android_kernel_moto_shamu/commits/ad135b9f7e6ad16e8cf2d06084e3869ae490fac2"},{"sha":"830c7d89c6f6cbbffa8829f43901ac517fafc74a","author":{"email":"c9a32589e048e044184536f7ac71ef92fe82df3e@openvz.org","name":"Pavel Emelyanov"},"message":"fuse: Linking file to inode helper\n\nWhen writeback is ON every writeable file should be in per-inode write list,\nnot only mmap-ed ones. Thus introduce a helper for this linkage.\n\nChange-Id: I9c4df97354b8f7c14de1106ccad24a3fb78319c4\nSigned-off-by: Maxim Patlasov <MPatlasov@parallels.com>\nSigned-off-by: Pavel Emelyanov <xemul@openvz.org>\nSigned-off-by: Miklos Szeredi <mszeredi@suse.cz>\nGit-commit:  650b22b941fa03590c4a3671e79ec2c96ea59e9a\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git\nSigned-off-by: Nikhilesh Reddy <reddyn@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/elginsk8r/android_kernel_moto_shamu/commits/830c7d89c6f6cbbffa8829f43901ac517fafc74a"},{"sha":"583762e62105e46967a99e82035200ae4900f297","author":{"email":"c9a32589e048e044184536f7ac71ef92fe82df3e@openvz.org","name":"Pavel Emelyanov"},"message":"fuse: Connection bit for enabling writeback\n\nOff (0) by default. Will be used in the next patches and will be turned\non at the very end.\n\nChange-Id: Icac47d3a3230fcc961dee94dd3c0c1830c79ac1a\nSigned-off-by: Maxim Patlasov <MPatlasov@parallels.com>\nSigned-off-by: Pavel Emelyanov <xemul@openvz.org>\nSigned-off-by: Miklos Szeredi <mszeredi@suse.cz>\nGit-commit:  d5cd66c58edf10a7ee786659994595fd43995aab\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git\nSigned-off-by: Nikhilesh Reddy <reddyn@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/elginsk8r/android_kernel_moto_shamu/commits/583762e62105e46967a99e82035200ae4900f297"},{"sha":"63e41b3df639c1222fa43c5abbd2f06b4f98e2d5","author":{"email":"95bad5edde439938e03d40e1830b47de3f52a0ea@gmail.com","name":"Rajat Jain"},"message":"fuse: fix \"uninitialized variable\" warning\n\nFix the following warning:\n\nIn file included from include/linux/fs.h:16:0,\n                 from fs/fuse/fuse_i.h:13,\n                 from fs/fuse/file.c:9:\nfs/fuse/file.c: In function 'fuse_file_poll':\ninclude/linux/rbtree.h:82:28: warning: 'parent' may be used\nuninitialized in this function [-Wmaybe-uninitialized]\nfs/fuse/file.c:2592:27: note: 'parent' was declared here\n\nChange-Id: I7edbfc0ef4574056c7442cb132636edf21fb5150\nSigned-off-by: Rajat Jain <rajatxjain@gmail.com>\nSigned-off-by: Miklos Szeredi <mszeredi@suse.cz>\nGit-commit:  f3846266f593595632a07242fcbc6c24bc2ade68\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git\nSigned-off-by: Nikhilesh Reddy <reddyn@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/elginsk8r/android_kernel_moto_shamu/commits/63e41b3df639c1222fa43c5abbd2f06b4f98e2d5"},{"sha":"17cac9178ebf8fb4efd8023555e3afff999678a0","author":{"email":"9b2b8b7e846e294db4fe93bddaa35ab6d2b5b49c@fb.com","name":"Andrew Gallagher"},"message":"fuse: don't invalidate attrs when not using atime\n\nVarious read operations (e.g. readlink, readdir) invalidate the cached\nattrs for atime changes.  This patch adds a new function\n'fuse_invalidate_atime', which checks for a read-only super block and\navoids the attr invalidation in that case.\n\nChange-Id: I482c57b1a0a82fee7e7a5b930df3fc6683497fda\nSigned-off-by: Andrew Gallagher <andrewjcg@fb.com>\nSigned-off-by: Miklos Szeredi <mszeredi@suse.cz>\nGit-commit:  451418fc928b5ec1ee96a9afac807b6312811a2a\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git\nSigned-off-by: Nikhilesh Reddy <reddyn@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/elginsk8r/android_kernel_moto_shamu/commits/17cac9178ebf8fb4efd8023555e3afff999678a0"},{"sha":"0f0a4390d1b5d147cf50a686b155c8d7de0a0e53","author":{"email":"c9a32589e048e044184536f7ac71ef92fe82df3e@openvz.org","name":"Pavel Emelyanov"},"message":"fuse: Prepare to handle short reads\n\nA helper which gets called when read reports less bytes than was requested.\nSee patch \"trust kernel i_size only\" for details.\n\nChange-Id: Ie62ca83066d7a91cb1fa4920f8ef822542711f1c\nSigned-off-by: Maxim Patlasov <MPatlasov@parallels.com>\nSigned-off-by: Pavel Emelyanov <xemul@openvz.org>\nSigned-off-by: Miklos Szeredi <mszeredi@suse.cz>\nGit-commit:  a92adc824ed5feaa2d4f7029f21170f574987aee\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git\nSigned-off-by: Nikhilesh Reddy <reddyn@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/elginsk8r/android_kernel_moto_shamu/commits/0f0a4390d1b5d147cf50a686b155c8d7de0a0e53"},{"sha":"c8a7182531c393d1487a28700a4fe412df691682","author":{"email":"c9a32589e048e044184536f7ac71ef92fe82df3e@openvz.org","name":"Pavel Emelyanov"},"message":"fuse: Trust kernel i_size only\n\nMake fuse think that when writeback is on the inode's i_size is always\nup-to-date and not update it with the value received from the userspace.\nThis is done because the page cache code may update i_size without letting\nthe FS know.\n\nThis assumption implies fixing the previously introduced short-read helper --\nwhen a short read occurs the 'hole' is filled with zeroes.\n\nfuse_file_fallocate() is also fixed because now we should keep i_size up to\ndate, so it must be updated if FUSE_FALLOCATE request succeeded.\n\nChange-Id: I79691ed5c5da732e7f5a4683433a24b30abce303\nSigned-off-by: Maxim V. Patlasov <MPatlasov@parallels.com>\nSigned-off-by: Miklos Szeredi <mszeredi@suse.cz>\nGit-commit:  8373200b124d03de7fa2e99be56de8642e604e9e\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git\nSigned-off-by: Nikhilesh Reddy <reddyn@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/elginsk8r/android_kernel_moto_shamu/commits/c8a7182531c393d1487a28700a4fe412df691682"},{"sha":"2100a1bae5de453c5bfc2c849fbe9e5aa905f78e","author":{"email":"a03f90017ab580fcc9558a98cd061c91599c42fd@parallels.com","name":"Maxim Patlasov"},"message":"fuse: Trust kernel i_mtime only\n\nLet the kernel maintain i_mtime locally:\n - clear S_NOCMTIME\n - implement i_op->update_time()\n - flush mtime on fsync and last close\n - update i_mtime explicitly on truncate and fallocate\n\nFuse inode flag FUSE_I_MTIME_DIRTY serves as indication that local i_mtime\nshould be flushed to the server eventually.\n\nChange-Id: I0db9f6faba551c88a618c4fddfff9b68338324cd\nSigned-off-by: Maxim Patlasov <MPatlasov@parallels.com>\nSigned-off-by: Miklos Szeredi <mszeredi@suse.cz>\nGit-commit:  b0aa760652179072119582375f8dc896ed5b5dfd\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git\nSigned-off-by: Nikhilesh Reddy <reddyn@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/elginsk8r/android_kernel_moto_shamu/commits/2100a1bae5de453c5bfc2c849fbe9e5aa905f78e"},{"sha":"56b00e65c5030023f9965bfdd4def280334fe416","author":{"email":"c9a32589e048e044184536f7ac71ef92fe82df3e@openvz.org","name":"Pavel Emelyanov"},"message":"fuse: Flush files on wb close\n\nAny write request requires a file handle to report to the userspace. Thus\nwhen we close a file (and free the fuse_file with this info) we have to\nflush all the outstanding dirty pages.\n\nfilemap_write_and_wait() is enough because every page under fuse writeback\nis accounted in ff->count. This delays actual close until all fuse wb is\ncompleted.\n\nIn case of \"write cache\" turned off, the flush is ensured by fuse_vma_close().\n\nChange-Id: I3f8793f46a0fc2263b2e42b5f367048452e6dcce\nSigned-off-by: Maxim Patlasov <MPatlasov@parallels.com>\nSigned-off-by: Miklos Szeredi <mszeredi@suse.cz>\nGit-commit:  e7cc133c370f541fa16723ad7df24de375c26fce\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git\nSigned-off-by: Nikhilesh Reddy <reddyn@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/elginsk8r/android_kernel_moto_shamu/commits/56b00e65c5030023f9965bfdd4def280334fe416"},{"sha":"31e39d2c6bd4c66ccded101892959d477886405f","author":{"email":"a03f90017ab580fcc9558a98cd061c91599c42fd@parallels.com","name":"Maxim Patlasov"},"message":"fuse: restructure fuse_readpage()\n\nMove the code filling and sending read request to a separate function. Future\npatches will use it for .write_begin -- partial modification of a page\nrequires reading the page from the storage very similarly to what fuse_readpage\ndoes.\n\nChange-Id: Ie02bdfd5dd7570f454d6d7cd9142b9be3e3198f1\nSigned-off-by: Maxim Patlasov <MPatlasov@parallels.com>\nSigned-off-by: Miklos Szeredi <mszeredi@suse.cz>\nGit-commit:  482fce55d2809d639fd0d2e6249c89dedc20eeae\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git\nSigned-off-by: Nikhilesh Reddy <reddyn@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/elginsk8r/android_kernel_moto_shamu/commits/31e39d2c6bd4c66ccded101892959d477886405f"},{"sha":"68404f23fbf3ffb2a9ea1d9ee1ac41352f690e83","author":{"email":"c9a32589e048e044184536f7ac71ef92fe82df3e@openvz.org","name":"Pavel Emelyanov"},"message":"fuse: Fix O_DIRECT operations vs cached writeback misorder\n\nThe problem is:\n\n1. write cached data to a file\n2. read directly from the same file (via another fd)\n\nThe 2nd operation may read stale data, i.e. the one that was in a file\nbefore the 1st op. Problem is in how fuse manages writeback.\n\nWhen direct op occurs the core kernel code calls filemap_write_and_wait\nto flush all the cached ops in flight. But fuse acks the writeback right\nafter the ->writepages callback exits w/o waiting for the real write to\nhappen. Thus the subsequent direct op proceeds while the real writeback\nis still in flight. This is a problem for backends that reorder operation.\n\nFix this by making the fuse direct IO callback explicitly wait on the\nin-flight writeback to finish.\n\nChange-Id: I9749cf91aaba4e2a74646edcb886d7245173d987\nSigned-off-by: Maxim Patlasov <MPatlasov@parallels.com>\nSigned-off-by: Miklos Szeredi <mszeredi@suse.cz>\nGit-commit:  ea8cd33390fafc1eca06a26e6a9c7bf1d386526f\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git\nSigned-off-by: Nikhilesh Reddy <reddyn@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/elginsk8r/android_kernel_moto_shamu/commits/68404f23fbf3ffb2a9ea1d9ee1ac41352f690e83"},{"sha":"064bd5467c0645e18cabf05a6f78c7c81627b0cb","author":{"email":"c9a32589e048e044184536f7ac71ef92fe82df3e@openvz.org","name":"Pavel Emelyanov"},"message":"fuse: Turn writeback cache on\n\nIntroduce a bit kernel and userspace exchange between each-other on\nthe init stage and turn writeback on if the userspace want this and\nmount option 'allow_wbcache' is present (controlled by fusermount).\n\nAlso add each writable file into per-inode write list and call the\ngeneric_file_aio_write to make use of the Linux page cache engine.\n\nChange-Id: Id5eea741c4e09e50122384e9e8b775cae74f132e\nSigned-off-by: Maxim Patlasov <MPatlasov@parallels.com>\nSigned-off-by: Miklos Szeredi <mszeredi@suse.cz>\nGit-commit:  4d99ff8f12eb20c6cde292f185cb1c8c334ba0ed\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git\nSigned-off-by: Nikhilesh Reddy <reddyn@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/elginsk8r/android_kernel_moto_shamu/commits/064bd5467c0645e18cabf05a6f78c7c81627b0cb"},{"sha":"1c8fb8035f109fdab3d5a0a98b62e5afa4a14647","author":{"email":"c9a32589e048e044184536f7ac71ef92fe82df3e@openvz.org","name":"Pavel Emelyanov"},"message":"fuse: Implement write_begin/write_end callbacks\n\nThe .write_begin and .write_end are requiered to use generic routines\n(generic_file_aio_write --> ... --> generic_perform_write) for buffered\nwrites.\n\nChange-Id: I37480cf01898a6692eb410e1998a0a80e906dcc5\nSigned-off-by: Maxim Patlasov <MPatlasov@parallels.com>\nSigned-off-by: Miklos Szeredi <mszeredi@suse.cz>\nGit-commit:  6b12c1b37e5556af073c1ebfa04c1f9df3a2beaf\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git\nSigned-off-by: Nikhilesh Reddy <reddyn@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/elginsk8r/android_kernel_moto_shamu/commits/1c8fb8035f109fdab3d5a0a98b62e5afa4a14647"},{"sha":"c83a33399d53912fef6f7ca5380e381419c25459","author":{"email":"a03f90017ab580fcc9558a98cd061c91599c42fd@parallels.com","name":"Maxim Patlasov"},"message":"fuse: fuse_flush() should wait on writeback\n\nThe aim of .flush fop is to hint file-system that flushing its state or caches\nor any other important data to reliable storage would be desirable now.\nfuse_flush() passes this hint by sending FUSE_FLUSH request to userspace.\nHowever, dirty pages and pages under writeback may be not visible to userspace\nyet if we won't ensure it explicitly.\n\nChange-Id: I98af8c91a417ceee645a8c2b8b877b302c38b303\nSigned-off-by: Maxim Patlasov <MPatlasov@parallels.com>\nSigned-off-by: Miklos Szeredi <mszeredi@suse.cz>\nGit-commit:  fe38d7df230b022e72014ef7aa799a4f2acfecf3\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git\nSigned-off-by: Nikhilesh Reddy <reddyn@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/elginsk8r/android_kernel_moto_shamu/commits/c83a33399d53912fef6f7ca5380e381419c25459"},{"sha":"3a900216c0091e3adbd9420eaa3a2b71b3e0c7a4","author":{"email":"84cd5483a2f9acd1c37251cba7c2908448f221b8@suse.cz","name":"Miklos Szeredi"},"message":"fuse: set stolen page uptodate\n\ncommit aa991b3b267e24f578bac7b09cc57579b660304b upstream.\n\nRegular pipe buffers' ->steal method (generic_pipe_buf_steal()) doesn't set\nPG_uptodate.\n\nDon't warn on this condition, just set the uptodate flag.\n\nSigned-off-by: Miklos Szeredi <mszeredi@suse.cz>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/elginsk8r/android_kernel_moto_shamu/commits/3a900216c0091e3adbd9420eaa3a2b71b3e0c7a4"}]}