{"ref":"refs/heads/master","commits":[{"author":{"name":"Sage Weil","email":"6dd34506bbd5e58221bbb3e4732d97c91f02277b@newdream.net"},"message":"ceph: use new D_COMPLETE dentry flag\n\nWe used to use a flag on the directory inode to track whether the dcache\ncontents for a directory were a complete cached copy.  Switch to a dentry\nflag CEPH_D_COMPLETE that is safely updated by ->d_prune().\n\nSigned-off-by: Sage Weil <sage@newdream.net>","url":"https://api.github.com/repos/omasab/linux/commits/c6ffe10015f4e6fba8a915318b319c43aed1836f","sha":"c6ffe10015f4e6fba8a915318b319c43aed1836f"},{"author":{"name":"H Hartley Sweeten","email":"5fdf5119aa8419249433b0dc3d437dd85e1dca0d@visionengravers.com"},"message":"ceph/mds_client.c: quiet sparse noise\n\nQuiet the following sparse noise:\n\nwarning: symbol 'get_nonsnap_parent' was not declared. Should it be static?\nwarning: symbol 'done_closing_sessions' was not declared. Should it be static?\n\nLocal functions don't need external visability. Make them static.\n\nSigned-off-by: H Hartley Sweeten <hsweeten@visionengravers.com>\nCc: Sage Weil <sage@newdream.net>\nSigned-off-by: Sage Weil <sage@newdream.net>","url":"https://api.github.com/repos/omasab/linux/commits/7fd7d101ff50af55d6d69f4705facc00c324024e","sha":"7fd7d101ff50af55d6d69f4705facc00c324024e"},{"author":{"name":"H Hartley Sweeten","email":"5fdf5119aa8419249433b0dc3d437dd85e1dca0d@visionengravers.com"},"message":"ceph/super.c: quiet sparse noise\n\nQuiet the sparse noise:\n\nwarning: symbol 'create_fs_client' was not declared. Should it be static?\nwarning: symbol 'destroy_fs_client' was not declared. Should it be static?\n\nSigned-off-by: H Hartley Sweeten <hsweeten@visionengravers.com>\nCc: Sage Weil <sage@newdream.net>\nceph-devel@vger.kernel.org\nSigned-off-by: Sage Weil <sage@newdream.net>","url":"https://api.github.com/repos/omasab/linux/commits/0c6d4b4e22a513f8563a2e00c5ab08e9f8796272","sha":"0c6d4b4e22a513f8563a2e00c5ab08e9f8796272"},{"author":{"name":"Jonghwan Choi","email":"a1b1c34da4eddaa3495f0b6a971517234e873a08@gmail.com"},"message":"ARM: SAMSUNG: Fix compile error due to kfree\n\nFix following build error.\narch/arm/plat-samsung/dev-backlight.c: In function 'samsung_bl_set':\narch/arm/plat-samsung/dev-backlight.c:145: error: implicit declaration of function 'kfree'\n\nSigned-off-by: Jonghwan Choi <jhbird.choi@gmail.com>\nSigned-off-by: Kukjin Kim <kgene.kim@samsung.com>","url":"https://api.github.com/repos/omasab/linux/commits/8088041ee35604640760321621e3f058ea2c7061","sha":"8088041ee35604640760321621e3f058ea2c7061"},{"author":{"name":"Joonyoung Shim","email":"b2207686f8c5343cf0f505ae1d5720ecb0c3202a@samsung.com"},"message":"ARM: SAMSUNG: Add clk enable/disable of pwm\n\nPWM timers use pclk(\"timers\" clk) as parent clk. If this pclk is the\ndisabled state when PWM driver is probed, then it causes wrong read and\nwrite operation about registers of PWM.\n\nSigned-off-by: Joonyoung Shim <jy0922.shim@samsung.com>\nSigned-off-by: Kyungmin Park <kyungmin.park@samsung.com>\nSigned-off-by: Kukjin Kim <kgene.kim@samsung.com>","url":"https://api.github.com/repos/omasab/linux/commits/d8633c1da161de7e0b880d919d305a97c01372f4","sha":"d8633c1da161de7e0b880d919d305a97c01372f4"},{"author":{"name":"Marc Zyngier","email":"a16cc0c82647c52d401177f8e50567df5499e36c@arm.com"},"message":"ARM: EXYNOS4: convert MCT to percpu interrupt API\n\nMCT recently gained per cpu interrupts, and missed the fact that\nARM has moved to a genirq based implementation.\n\nThis patch converts the driver to the new API.\n\nBoot tested on Origen.\n\nCc: Kukjin Kim <kgene.kim@samsung.com>\nSigned-off-by: Marc Zyngier <marc.zyngier@arm.com>\nSigned-off-by: Kukjin Kim <kgene.kim@samsung.com>","url":"https://api.github.com/repos/omasab/linux/commits/e700e41d9abfbf9fee01e979a41b185695132c19","sha":"e700e41d9abfbf9fee01e979a41b185695132c19"},{"author":{"name":"Kukjin Kim","email":"3fc711f4e08bc570a586748633ff7c76d0e1e253@samsung.com"},"message":"ARM: EXYNOS: Add ARCH_EXYNOS and reorganize arch/arm/mach-exynos\n\nThe arch/arm/mach-exynos4 directory (CONFIG_ARCH_EXYNOS4) has\nmade for plaforms based on EXYNOS4 SoCs. But since upcoming\nSamsung's SoCs such as EXYNOS5 (ARM Cortex A15) can reuse most\ncodes in current mach-exynos4, one mach-exynos directory will\nbe used for them.\n\nThis patch changes to CONFIG_ARCH_EXYNOS (arch/arm/mach-exynos)\nbut keeps original CONFIG_ARCH_EXYNOS4 in mach-exynos/Kconfig to\navoid changing in driver side.\n\nCc: Arnd Bergmann <arnd@arndb.de>\nCc: Russell King <rmk+kernel@arm.linux.org.uk>\nSigned-off-by: Kukjin Kim <kgene.kim@samsung.com>","url":"https://api.github.com/repos/omasab/linux/commits/830145796a5c8f1ca3f87ea619063c1d99a57df5","sha":"830145796a5c8f1ca3f87ea619063c1d99a57df5"},{"author":{"name":"Chris Mason","email":"a169954b4cb1a46cee25f659d3bddfebe02b5fba@oracle.com"},"message":"Btrfs: don't wait as long for more batches during SSD log commit\n\nWhen we're doing log commits, we try to wait for more writers to come in\nand make the commit bigger.  This helps improve performance on rotating\ndisks, but on SSDs it adds latencies.\n\nSigned-off-by: Chris Mason <chris.mason@oracle.com>","url":"https://api.github.com/repos/omasab/linux/commits/cd354ad613a393424f85333ceed6b15e07fb94ae","sha":"cd354ad613a393424f85333ceed6b15e07fb94ae"},{"author":{"name":"Chris Mason","email":"a169954b4cb1a46cee25f659d3bddfebe02b5fba@oracle.com"},"message":"Btrfs: make sure btrfs_remove_free_space doesn't leak EAGAIN\n\nbtrfs_remove_free_space needs to make sure to set ret back to a\nvalid return value after setting it to EAGAIN, otherwise we return\nit to the callers.\n\nSigned-off-by: Chris Mason <chris.mason@oracle.com>","url":"https://api.github.com/repos/omasab/linux/commits/1eae31e918972bbeefc119d23c1d67674f49a301","sha":"1eae31e918972bbeefc119d23c1d67674f49a301"},{"author":{"name":"Chris Mason","email":"a169954b4cb1a46cee25f659d3bddfebe02b5fba@oracle.com"},"message":"Btrfs: fix extent pinning bugs in the tree log\n\nThe tree log had two important bugs that could cause corruptions after a\ncrash.  Sometimes we were allowing tree log blocks to be reused after\nthe tree log was committed but before the transaction commit was done.\n\nThis allowed a future metadata write to overwrite the tree log data.  It\nis fixed by adding a new variant of freeing reserved extents that always\npins them.  Credit goes to Stefan Behrens and Arne Jansen for many many\nhours spent tracking this bug down.\n\nDuring tree log replay, we do a pass through the tree log and pin all\nthe extents we find.  This makes sure the replay code won't go in and\nuse any of those blocks for new allocations during replay.  The problem\nis the free space cache isn't honoring these pinned extents.  So the\nallocator can end up handing them out, leading to all kinds of problems\nduring replay.\n\nThe fix here is to force any free space cache to load while we pin the\nextents, and then to make sure we remove the pinned extents from the\nfree space rbtree.\n\nSigned-off-by: Chris Mason <chris.mason@oracle.com>\nReported-by: Stefan Behrens <sbehrens@giantdisaster.de>","url":"https://api.github.com/repos/omasab/linux/commits/e688b7252f784c2479d559f9f70ca8354752c5e7","sha":"e688b7252f784c2479d559f9f70ca8354752c5e7"},{"author":{"name":"Chris Mason","email":"a169954b4cb1a46cee25f659d3bddfebe02b5fba@oracle.com"},"message":"Btrfs: make sure to flush queued bios if write_cache_pages waits\n\nwrite_cache_pages tries to build up a large bio to stuff down the pipe.\nBut if it needs to wait for a page lock, it needs to make sure and send\ndown any pending writes so we don't deadlock with anyone who has the\npage lock and is waiting for writeback of things inside the bio.\n\nDave Sterba triggered this as a deadlock between the autodefrag code and\nthe extent write_cache_pages\n\nSigned-off-by: Chris Mason <chris.mason@oracle.com>","url":"https://api.github.com/repos/omasab/linux/commits/01d658f2ca3c85c1ffb20b306e30d16197000ce7","sha":"01d658f2ca3c85c1ffb20b306e30d16197000ce7"},{"author":{"name":"Josef Bacik","email":"78b342861d821967b29f951b7366f5a0267e0c38@redhat.com"},"message":"Btrfs: release metadata from global reserve if we have to fallback for unlink\n\nI fixed a problem where we weren't reserving space for an orphan item when we\nhad to fallback to using the global reserve for an unlink, but I introduced\nanother problem.  I was migrating the bytes from the transaction reserve to the\nglobal reserve and then releasing from the global reserve in\nbtrfs_end_transaction().  The problem with this is that a migrate will jack up\nthe size for the destination, but leave the size alone for the source, with the\nidea that you can do a release normally on the source and it all washes out, and\nthen you can do a release again on the destination and it works out right.  My\nway was skipping the release on the trans_block_rsv which still had the jacked\nup size from our original reservation.  So instead release manually from the\nglobal reserve if this transaction was using it, and then set the\ntrans->block_rsv back to the trans_block_rsv so that btrfs_end_transaction\ncleans everything up properly.  With this patch xfstest 83 doesn't emit warnings\nabout leaking space.  Thanks,\n\nSigned-off-by: Josef Bacik <josef@redhat.com>\nSigned-off-by: Chris Mason <chris.mason@oracle.com>","url":"https://api.github.com/repos/omasab/linux/commits/5a77d76c243be18d854aa1b14d697525f60e169a","sha":"5a77d76c243be18d854aa1b14d697525f60e169a"},{"author":{"name":"Josef Bacik","email":"78b342861d821967b29f951b7366f5a0267e0c38@redhat.com"},"message":"Btrfs: use the global reserve when truncating the free space cache inode\n\nWe no longer use the orphan block rsv for holding the reservation for truncating\nthe inode, so instead use the global block rsv and check to make sure it has\nenough space for us to truncate the space.  Thanks,\n\nSigned-off-by: Josef Bacik <josef@redhat.com>\nSigned-off-by: Chris Mason <chris.mason@oracle.com>","url":"https://api.github.com/repos/omasab/linux/commits/c8174313a8102e874aaa321e2fc4c7c460a87151","sha":"c8174313a8102e874aaa321e2fc4c7c460a87151"},{"author":{"name":"David Sterba","email":"a2ce9d316ca04d17b520237d2846a218b8284e52@suse.cz"},"message":"btrfs: separate superblock items out of fs_info\n\nfs_info has now ~9kb, more than fits into one page. This will cause\nmount failure when memory is too fragmented. Top space consumers are\nsuper block structures super_copy and super_for_commit, ~2.8kb each.\nAllocate them dynamically. fs_info will be ~3.5kb. (measured on x86_64)\n\nAdd a wrapper for freeing fs_info and all of it's dynamically allocated\nmembers.\n\nSigned-off-by: David Sterba <dsterba@suse.cz>","url":"https://api.github.com/repos/omasab/linux/commits/6c41761fc6efe1503103a1afe03a6635c0b5d4ec","sha":"6c41761fc6efe1503103a1afe03a6635c0b5d4ec"},{"author":{"name":"Chris Mason","email":"a169954b4cb1a46cee25f659d3bddfebe02b5fba@oracle.com"},"message":"Btrfs: add a log of past tree roots\n\nThis takes some of the free space in the btrfs super block\nto record information about most of the roots in the last four\ncommits.\n\nIt also adds a -o recovery to use the root history log when\nwe're not able to read the tree of tree roots, the extent\ntree root, the device tree root or the csum root.\n\nSigned-off-by: Chris Mason <chris.mason@oracle.com>","url":"https://api.github.com/repos/omasab/linux/commits/af31f5e5b84b5bf2bcec464153a5130b170b2770","sha":"af31f5e5b84b5bf2bcec464153a5130b170b2770"},{"author":{"name":"Josef Bacik","email":"78b342861d821967b29f951b7366f5a0267e0c38@redhat.com"},"message":"Btrfs: make a delayed_block_rsv for the delayed item insertion\n\nI've been hitting warnings in use_block_rsv when running the delayed insertion\nstuff.  It's because we will readjust global block rsv based on what is in use,\nwhich means we could end up discarding reservations that are for the delayed\ninsertion stuff.  So instead create a seperate block rsv for the delayed\ninsertion stuff.  This will also make it easier to debug problems with the\ndelayed insertion reservations since we will know that only the delayed\ninsertion code touches this block_rsv.  Thanks,\n\nSigned-off-by: Josef Bacik <josef@redhat.com>\nSigned-off-by: Chris Mason <chris.mason@oracle.com>","url":"https://api.github.com/repos/omasab/linux/commits/6d668dda0caec537fbf28c4d91e6d18181af3cff","sha":"6d668dda0caec537fbf28c4d91e6d18181af3cff"},{"author":{"name":"Josef Bacik","email":"78b342861d821967b29f951b7366f5a0267e0c38@redhat.com"},"message":"Btrfs: be smarter about committing the transaction in reserve_metadata_bytes\n\nBecause of the overcommit stuff I had to make it so that we committed the\ntransaction all the time in reserve_metadata_bytes in case we had overcommitted\nbecause of delayed items.  This was because previously we had no way of knowing\nhow much space was reserved for delayed items.  Now that we have the\ndelayed_block_rsv we can check it to see if committing the transaction would get\nus anywhere.  This patch breaks out the committing logic into a helper function\nthat will check to see if committing the transaction would free enough space for\nus to get anything done.  With this patch xfstests 83 goes from taking 445\nseconds to taking 28 seconds on my box.  Thanks,\n\nSigned-off-by: Josef Bacik <josef@redhat.com>\nSigned-off-by: Chris Mason <chris.mason@oracle.com>","url":"https://api.github.com/repos/omasab/linux/commits/663350ac38c67ca388acea6e876dc6d668c232b0","sha":"663350ac38c67ca388acea6e876dc6d668c232b0"},{"author":{"name":"Chris Mason","email":"a169954b4cb1a46cee25f659d3bddfebe02b5fba@oracle.com"},"message":"Btrfs: ClearPageError during writepage and clean_tree_block\n\nFailure testing was tripping up over stale PageError bits in\nmetadata pages.  If we have an io error on a block, and later on\nend up reusing it, nobody ever clears PageError on those pages.\n\nDuring commit, we'll find PageError and think we had trouble writing\nthe block, which will lead to aborts and other problems.\n\nThis changes clean_tree_block and the btrfs writepage code to\nclear the PageError bit.  In both cases we're either completely\ndone with the page or the page has good stuff and the error bit\nis no longer valid.\n\nSigned-off-by: Chris Mason <chris.mason@oracle.com>","url":"https://api.github.com/repos/omasab/linux/commits/bf0da8c183a15656eee63c54f334c3794320872a","sha":"bf0da8c183a15656eee63c54f334c3794320872a"},{"author":{"name":"Josef Bacik","email":"78b342861d821967b29f951b7366f5a0267e0c38@redhat.com"},"message":"Btrfs: fix delayed insertion reservation\n\nWe all keep getting those stupid warnings from use_block_rsv when running\nstress.sh, and it's because the delayed insertion stuff is being stupid.  It's\nnot the delayed insertion stuffs fault, it's all just stupid.  When marking an\ninode dirty for oh say updating the time on it, we just do a\nbtrfs_join_transaction, which doesn't reserve any space.  This is stupid because\nwe're going to have to have space reserve to make this change, but we do it\nbecause it's fast because chances are we're going to call it over and over again\nand it doesn't matter.  Well thanks to the delayed insertion stuff this is\nmostly the case, so we do actually need to make this reservation.  So if\ntrans->bytes_reserved is 0 then try to do a normal reservation.  If not return\nENOSPC which will make the btrfs_dirty_inode start a proper transaction which\nwill let it do the whole ENOSPC dance and reserve enough space for the delayed\ninsertion to steal the reservation from the transaction.\n\nThe other stupid thing we do is not reserve space for the inode when writing to\nthe thing.  Usually this is ok since we have to update the time so we'd have\nalready done all this work before we get to the endio stuff, so it doesn't\nmatter.  But this is stupid because we could write the data after the\ntransaction commits where we changed the mtime of the inode so we have to cow\nall the way down to the inode anyway.  This used to be masked by the delalloc\nreservation stuff, but because we delay the update it doesn't get masked in this\ncase.  So again the delayed insertion stuff bites us in the ass.  So if our\ntrans->block_rsv is delalloc, just steal the reservation from the delalloc\nreserve.  Hopefully this won't bite us in the ass, but I've said that before.\n\nWith this patch stress.sh no longer spits out those stupid warnings (famous last\nwords).  Thanks,\n\nSigned-off-by: Josef Bacik <josef@redhat.com>\nSigned-off-by: Chris Mason <chris.mason@oracle.com>","url":"https://api.github.com/repos/omasab/linux/commits/c06a0e120a4e381a1c291c1fce3c6155c5791cae","sha":"c06a0e120a4e381a1c291c1fce3c6155c5791cae"},{"author":{"name":"Chris Mason","email":"a169954b4cb1a46cee25f659d3bddfebe02b5fba@oracle.com"},"message":"Merge branch 'for-chris' of git://github.com/sensille/linux into integration\n\nConflicts:\n\tfs/btrfs/ctree.h\n\nSigned-off-by: Chris Mason <chris.mason@oracle.com>","url":"https://api.github.com/repos/omasab/linux/commits/531f4b1ae5e0fc8c9b3f03838218e5ea178f80d3","sha":"531f4b1ae5e0fc8c9b3f03838218e5ea178f80d3"}],"head":"b32fc0a0629bf5894b35f33554c118aacfd0d1e2","size":59,"push_id":48950483}