{"push_id":1282793240,"size":372,"distinct_size":372,"ref":"refs/heads/master","head":"c6935931c1894ff857616ff8549b61236a19148f","before":"3eab887a55424fc2c27553b7bfe32330df83f7b8","commits":[{"sha":"9b622e2bbcf049c82e2550d35fb54ac205965f50","author":{"name":"Tomasz Majchrzak","email":"f80fe5a1d8d7f16e6da1365bbfd9fd12cb6c0dd4@intel.com"},"message":"raid10: increment write counter after bio is split\n\nmd pending write counter must be incremented after bio is split,\notherwise it gets decremented too many times in end bio callback and\nbecomes negative.\n\nSigned-off-by: Tomasz Majchrzak <tomasz.majchrzak@intel.com>\nReviewed-by: Artur Paszkiewicz <artur.paszkiewicz@intel.com>\nSigned-off-by: Shaohua Li <shli@fb.com>","distinct":true,"url":"https://api.github.com/repos/minipli/linux-grsec/commits/9b622e2bbcf049c82e2550d35fb54ac205965f50"},{"sha":"3980bd3b406addb327d858aebd19e229ea340b9a","author":{"name":"Theodore Ts'o","email":"27d72d8f7672ec04389c6b6ff53fcc4e9145bb77@mit.edu"},"message":"ext4: reserve xattr index for the Hurd\n\nThe Hurd is using inode fields which restricts it from using more\nadvanced ext4 file system features, due to design choices made over a\ndecade ago.  By giving the Hurd an extended attribute index field we\nallow it to move the translator and author fields out of the core\ninode fields, and hopefully we can get rid of ugly hacks such as\nEXT4_OS_HURD and EXT4_MOUNT2_HURD_COMPAT somday.\n\nFor more information please see:\n      https://summerofcode.withgoogle.com/projects/#5869799859027968\n\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>","distinct":true,"url":"https://api.github.com/repos/minipli/linux-grsec/commits/3980bd3b406addb327d858aebd19e229ea340b9a"},{"sha":"829fa70dddadf9dd041d62b82cd7cea63943899d","author":{"name":"Theodore Ts'o","email":"27d72d8f7672ec04389c6b6ff53fcc4e9145bb77@mit.edu"},"message":"ext4: validate that metadata blocks do not overlap superblock\n\nA number of fuzzing failures seem to be caused by allocation bitmaps\nor other metadata blocks being pointed at the superblock.\n\nThis can cause kernel BUG or WARNings once the superblock is\noverwritten, so validate the group descriptor blocks to make sure this\ndoesn't happen.\n\nCc: stable@vger.kernel.org\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>","distinct":true,"url":"https://api.github.com/repos/minipli/linux-grsec/commits/829fa70dddadf9dd041d62b82cd7cea63943899d"},{"sha":"ff00d3b4e5e4395c825e8ec628f25932d812f31a","author":{"name":"ZhengYuan Liu","email":"a04d831dd99aa331b1af1ea9996e406f4dcdd593@kylinos.cn"},"message":"raid5: fix incorrectly counter of conf->empty_inactive_list_nr\n\nThe counter conf->empty_inactive_list_nr is only used for determine if the\nraid5 is congested which is deal with in function raid5_congested().\nIt was increased in get_free_stripe() when conf->inactive_list got to be\nempty and decreased in release_inactive_stripe_list() when splice\ntemp_inactive_list to conf->inactive_list. However, this may have a\nproblem when raid5_get_active_stripe or stripe_add_to_batch_list was called,\nbecause these two functions may call list_del_init(&sh->lru) to delete sh from\n\"conf->inactive_list + hash\" which may cause \"conf->inactive_list + hash\" to\nbe empty when atomic_inc_not_zero(&sh->count) got false. So a check should be\ndone at these two point and increase empty_inactive_list_nr accordingly.\nOtherwise the counter may get to be negative number which would influence\nasync readahead from VFS.\n\nSigned-off-by: ZhengYuan Liu <liuzhengyuan@kylinos.cn>\nSigned-off-by: Shaohua Li <shli@fb.com>","distinct":true,"url":"https://api.github.com/repos/minipli/linux-grsec/commits/ff00d3b4e5e4395c825e8ec628f25932d812f31a"},{"sha":"d9dd26b20cff88b45d861ec786d86b1c9bd2ee60","author":{"name":"Shaohua Li","email":"78841d68de820ce65a8f2019d48ffc5e6c8a1f78@fb.com"},"message":"MD: hold mddev lock to change bitmap location\n\nChanging the location changes a lot of things. Holding the lock to avoid race.\nThis makes the .quiesce called with mddev lock hold too.\n\nAcked-by: NeilBrown <neilb@suse.com>\nSigned-off-by: Shaohua Li <shli@fb.com>","distinct":true,"url":"https://api.github.com/repos/minipli/linux-grsec/commits/d9dd26b20cff88b45d861ec786d86b1c9bd2ee60"},{"sha":"11367799f3d12a5074c4a3c0fa4ea8da2a21a2a4","author":{"name":"Alexey Obitotskiy","email":"cff95c52f954a6ff6cf33e78e045a1742b0e373c@intel.com"},"message":"md: Prevent IO hold during accessing to faulty raid5 array\n\nAfter array enters in faulty state (e.g. number of failed drives\nbecomes more then accepted for raid5 level) it sets error flags\n(one of this flags is MD_CHANGE_PENDING). For internal metadata\narrays MD_CHANGE_PENDING cleared into md_update_sb, but not for\nexternal metadata arrays. MD_CHANGE_PENDING flag set prevents to\nfinish all new or non-finished IOs to array and hold them in\npending state. In some cases this can leads to deadlock situation.\n\nFor example, we have faulty array (2 of 4 drives failed) and\nudev handle array state changes and blkid started (or other\nuserspace application that used array to read/write) but unable\nto finish reads due to IO hold. At the same time we unable to get\nexclusive access to array (to stop array in our case) because\nanother external application still use this array.\n\nFix makes possible to return IO with errors immediately.\nSo external application can finish working with array and\ngive exclusive access to other applications to perform\nrequired management actions with array.\n\nSigned-off-by: Alexey Obitotskiy <aleksey.obitotskiy@intel.com>\nSigned-off-by: Shaohua Li <shli@fb.com>","distinct":true,"url":"https://api.github.com/repos/minipli/linux-grsec/commits/11367799f3d12a5074c4a3c0fa4ea8da2a21a2a4"},{"sha":"626d2f07de89bf6be3d7301524d0ab3375b81b9c","author":{"name":"Yoshihiro Shimoda","email":"806084c42fbad0778b005fdc6faa04d57cfdf777@renesas.com"},"message":"dmaengine: usb-dmac: check CHCR.DE bit in usb_dmac_isr_channel()\n\nThe USB-DMAC's interruption happens even if the CHCR.DE is not set to 1\nbecause CHCR.NULLE is set to 1. So, this driver should call\nusb_dmac_isr_transfer_end() if the DE bit is set to 1 only. Otherwise,\nthe desc is possible to be NULL in the usb_dmac_isr_transfer_end().\n\nFixes: 0c1c8ff32fa2 (\"dmaengine: usb-dmac: Add Renesas USB DMA Controller (USB-DMAC) driver)\nCc: <stable@vger.kernel.org> # v4.1+\nSigned-off-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>\nSigned-off-by: Vinod Koul <vinod.koul@intel.com>","distinct":true,"url":"https://api.github.com/repos/minipli/linux-grsec/commits/626d2f07de89bf6be3d7301524d0ab3375b81b9c"},{"sha":"0956254a2d5b9e2141385514553aeef694dfe3b5","author":{"name":"Miklos Szeredi","email":"c27ee2952768e22f4d3ab9aec0e78ac5f4ddea98@redhat.com"},"message":"ovl: don't copy up opaqueness\n\nWhen a copy up of a directory occurs which has the opaque xattr set, the\nxattr remains in the upper directory. The immediate behavior with overlayfs\nis that the upper directory is not treated as opaque, however after a\nremount the opaque flag is used and upper directory is treated as opaque.\nThis causes files created in the lower layer to be hidden when using\nmultiple lower directories.\n\nFix by not copying up the opaque flag.\n\nTo reproduce:\n\n ----8<---------8<---------8<---------8<---------8<---------8<----\nmkdir -p l/d/s u v w mnt\nmount -t overlay overlay -olowerdir=l,upperdir=u,workdir=w mnt\nrm -rf mnt/d/\nmkdir -p mnt/d/n\numount mnt\nmount -t overlay overlay -olowerdir=u:l,upperdir=v,workdir=w mnt\ntouch mnt/d/foo\numount mnt\nmount -t overlay overlay -olowerdir=u:l,upperdir=v,workdir=w mnt\nls mnt/d\n ----8<---------8<---------8<---------8<---------8<---------8<----\n \noutput should be:  \"foo  n\"\n\nReported-by: Derek McGowan <dmcg@drizz.net>\nLink: https://bugzilla.kernel.org/show_bug.cgi?id=151291\nSigned-off-by: Miklos Szeredi <mszeredi@redhat.com>\nCc: <stable@vger.kernel.org>","distinct":true,"url":"https://api.github.com/repos/minipli/linux-grsec/commits/0956254a2d5b9e2141385514553aeef694dfe3b5"},{"sha":"06f4e94898918bcad00cdd4d349313a439d6911e","author":{"name":"Zefan Li","email":"5b5e21a558f468d565c29de4a38a97f6bf4eca64@huawei.com"},"message":"cpuset: make sure new tasks conform to the current config of the cpuset\n\nA new task inherits cpus_allowed and mems_allowed masks from its parent,\nbut if someone changes cpuset's config by writing to cpuset.cpus/cpuset.mems\nbefore this new task is inserted into the cgroup's task list, the new task\nwon't be updated accordingly.\n\nSigned-off-by: Zefan Li <lizefan@huawei.com>\nSigned-off-by: Tejun Heo <tj@kernel.org>\nCc: stable@vger.kernel.org","distinct":true,"url":"https://api.github.com/repos/minipli/linux-grsec/commits/06f4e94898918bcad00cdd4d349313a439d6911e"},{"sha":"ed0ab110235c659fdb3f73d27907b1b45b89cf30","author":{"name":"Chen-Yu Tsai","email":"d935d34b7d281e4f50030b838a1bf5c8f10bdb43@csie.org"},"message":"clk: sunxi-ng: Fix inverted test condition in ccu_helper_wait_for_lock\n\nThe condition passed to read*_poll_timeout() is the break condition,\ni.e. wait for this condition to happen and return success.\n\nThe original code assumed the opposite, resulting in a warning when\nthe PLL clock rate was changed but never lost it's lock as far as\nthe readout indicated. This was verified by checking the read out\nregister value.\n\nFixes: 1d80c14248d6 (\"clk: sunxi-ng: Add common infrastructure\")\nSigned-off-by: Chen-Yu Tsai <wens@csie.org>\nAcked-by: Maxime Ripard <maxime.ripard@free-electrons.com>\nSigned-off-by: Stephen Boyd <sboyd@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/minipli/linux-grsec/commits/ed0ab110235c659fdb3f73d27907b1b45b89cf30"},{"sha":"d0141191a20289f8955c1e03dad08e42e6f71ca9","author":{"name":"Jan Kara","email":"7bb7087018cc5fef3c041f6f038f586664845dbf@suse.cz"},"message":"ext4: fix xattr shifting when expanding inodes\n\nThe code in ext4_expand_extra_isize_ea() treated new_extra_isize\nargument sometimes as the desired target i_extra_isize and sometimes as\nthe amount by which we need to grow current i_extra_isize. These happen\nto coincide when i_extra_isize is 0 which used to be the common case and\nso nobody noticed this until recently when we added i_projid to the\ninode and so i_extra_isize now needs to grow from 28 to 32 bytes.\n\nThe result of these bugs was that we sometimes unnecessarily decided to\nmove xattrs out of inode even if there was enough space and we often\nended up corrupting in-inode xattrs because arguments to\next4_xattr_shift_entries() were just wrong. This could demonstrate\nitself as BUG_ON in ext4_xattr_shift_entries() triggering.\n\nFix the problem by introducing new isize_diff variable and use it where\nappropriate.\n\nCC: stable@vger.kernel.org   # 4.4.x\nReported-by: Dave Chinner <david@fromorbit.com>\nSigned-off-by: Jan Kara <jack@suse.cz>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>","distinct":true,"url":"https://api.github.com/repos/minipli/linux-grsec/commits/d0141191a20289f8955c1e03dad08e42e6f71ca9"},{"sha":"418c12d08dc64a45107c467ec1ba29b5e69b0715","author":{"name":"Jan Kara","email":"7bb7087018cc5fef3c041f6f038f586664845dbf@suse.cz"},"message":"ext4: fix xattr shifting when expanding inodes part 2\n\nWhen multiple xattrs need to be moved out of inode, we did not properly\nrecompute total size of xattr headers in the inode and the new header\nposition. Thus when moving the second and further xattr we asked\next4_xattr_shift_entries() to move too much and from the wrong place,\nresulting in possible xattr value corruption or general memory\ncorruption.\n\nCC: stable@vger.kernel.org  # 4.4.x\nSigned-off-by: Jan Kara <jack@suse.cz>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>","distinct":true,"url":"https://api.github.com/repos/minipli/linux-grsec/commits/418c12d08dc64a45107c467ec1ba29b5e69b0715"},{"sha":"443a8c41cd49de66a3fda45b32b9860ea0292b84","author":{"name":"Jan Kara","email":"7bb7087018cc5fef3c041f6f038f586664845dbf@suse.cz"},"message":"ext4: properly align shifted xattrs when expanding inodes\n\nWe did not count with the padding of xattr value when computing desired\nshift of xattrs in the inode when expanding i_extra_isize. As a result\nwe could create unaligned start of inline xattrs. Account for alignment\nproperly.\n\nCC: stable@vger.kernel.org  # 4.4.x-\nSigned-off-by: Jan Kara <jack@suse.cz>","distinct":true,"url":"https://api.github.com/repos/minipli/linux-grsec/commits/443a8c41cd49de66a3fda45b32b9860ea0292b84"},{"sha":"2e81a4eeedcaa66e35f58b81e0755b87057ce392","author":{"name":"Jan Kara","email":"7bb7087018cc5fef3c041f6f038f586664845dbf@suse.cz"},"message":"ext4: avoid deadlock when expanding inode size\n\nWhen we need to move xattrs into external xattr block, we call\next4_xattr_block_set() from ext4_expand_extra_isize_ea(). That may end\nup calling ext4_mark_inode_dirty() again which will recurse back into\nthe inode expansion code leading to deadlocks.\n\nProtect from recursion using EXT4_STATE_NO_EXPAND inode flag and move\nits management into ext4_expand_extra_isize_ea() since its manipulation\nis safe there (due to xattr_sem) from possible races with\next4_xattr_set_handle() which plays with it as well.\n\nCC: stable@vger.kernel.org   # 4.4.x\nSigned-off-by: Jan Kara <jack@suse.cz>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>","distinct":true,"url":"https://api.github.com/repos/minipli/linux-grsec/commits/2e81a4eeedcaa66e35f58b81e0755b87057ce392"},{"sha":"9b4b3f6a062b22550e62523efe5213776cdd426b","author":{"name":"Christoph Hellwig","email":"ed9f47d6dfaca04b245b5f2816a0d3e9462a0b83@lst.de"},"message":"ahci: disable correct irq for dummy ports\n\nirq already contains the interrupt number for the port, don't add the\nport index to it.\n\nSigned-off-by: Christoph Hellwig <hch@lst.de>\nSigned-off-by: Tejun Heo <tj@kernel.org>\nFixes: d684a90d38e2 (\"ahci: per-port msix support\")\nCc: stable@vger.kernel.org v4.5+","distinct":true,"url":"https://api.github.com/repos/minipli/linux-grsec/commits/9b4b3f6a062b22550e62523efe5213776cdd426b"},{"sha":"a3f457d9636b3f5ae4fc6502cb0c95f60f5e342b","author":{"name":"Chris Zhong","email":"80bf4e3e261bfadb203857f1acaa041b4428d22e@rock-chips.com"},"message":"clk: rockchip: fix rk3399 aclk_vio gate bit\n\nFix incorrect rk3399 aclk_vio gating bit, it should be 0, not 10.\n\nFixes: 115510053e5e (\"clk: rockchip: add clock controller for the RK3399\")\nSigned-off-by: Chris Zhong <zyw@rock-chips.com>\nReviewed-by: Xing Zheng <zhengxing@rock-chips.com>\nReviewed-by: Guenter Roeck <groeck@chromium.org>\nSigned-off-by: Heiko Stuebner <heiko@sntech.de>","distinct":true,"url":"https://api.github.com/repos/minipli/linux-grsec/commits/a3f457d9636b3f5ae4fc6502cb0c95f60f5e342b"},{"sha":"e0cb1b84163720ec67ff0e54397fd3f57ad4a4dd","author":{"name":"Yoshihiro Shimoda","email":"806084c42fbad0778b005fdc6faa04d57cfdf777@renesas.com"},"message":"clk: renesas: r8a7795: Fix SD clocks\n\nAccording to the datasheet, SDn clocks are from the SDSRC clock. And\nthe SDSRC has a 1/2 divider. So, we should have \".sdsrc\" as an internal\ncore clock. Otherwise, since the sdhi driver will calculate clock for\na sd card using the wrong parent clock rate, and then performance will\nbe not good.\n\nFixes: 90c073e53909da85 (\"clk: shmobile: r8a7795: Add SD divider support\")\nSigned-off-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>\nAcked-by: Dirk Behme <dirk.behme@de.bosch.com>\nTested-by: Wolfram Sang <wsa+renesas@sang-engineering.com>\nSigned-off-by: Geert Uytterhoeven <geert+renesas@glider.be>\nCc: stable@vger.kernel.org\nSigned-off-by: Stephen Boyd <sboyd@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/minipli/linux-grsec/commits/e0cb1b84163720ec67ff0e54397fd3f57ad4a4dd"},{"sha":"20c389e656a89e2302017bf3f499cb5a31a2a7ba","author":{"name":"Xing Zheng","email":"2bdfef9cb1295ebcc2755d42cb44bb943abaa9f5@rock-chips.com"},"message":"clk: rockchip: fix incorrect aclk_emmc source gate bits on rk3399\n\nDues to incorrect diagram, we need to fix incorrect bits for\n(c/g)pll_aclk_emmc_src:\ncpll_aclk_emmc_src --> G6[13]\ngpll_aclk_emmc_src --> G6[12]\n\nFixes: 115510053e5e (\"clk: rockchip: add clock controller for the RK3399\")\nSigned-off-by: Xing Zheng <zhengxing@rock-chips.com>\nReviewed-by: Shawn Lin <shawn.lin@rock-chips.com>\nSigned-off-by: Heiko Stuebner <heiko@sntech.de>","distinct":true,"url":"https://api.github.com/repos/minipli/linux-grsec/commits/20c389e656a89e2302017bf3f499cb5a31a2a7ba"},{"sha":"b33ecca87df99fa6fff8a1d455de96f436934dcf","author":{"name":"Hans de Goede","email":"a4b43a7169288183ae7c1f5a0140023a97961f48@redhat.com"},"message":"phy-sun4i-usb: Add support for peripheral-only mode\n\nUse the new of_usb_get_dr_mode_by_phy() function to get the dr_mode\nfrom the musb controller node instead of assuming that having an id_det\ngpio means otg mode, and not having one means host mode.\n\nImplement peripheral-only mode by adding a sun4i_usb_phy0_get_id_det\nhelper which looks at the dr_mode, always registering our extcon and\nalways monitoring vbus.\n\nIf dr_mode is not specified in the dts, do not register phy0 as we then\ndo not know how to treat it. This is actually a good thing as this means\nwe will not be registering phy0 on devices where the otg controller is\nnot enabled in the devicetree.\n\nSigned-off-by: Hans de Goede <hdegoede@redhat.com>\nAcked-by: Kishon Vijay Abraham I <kishon@ti.com>\nSigned-off-by: Kishon Vijay Abraham I <kishon@ti.com>","distinct":true,"url":"https://api.github.com/repos/minipli/linux-grsec/commits/b33ecca87df99fa6fff8a1d455de96f436934dcf"},{"sha":"1766e7b3763a0707c2fda9689a7866dceed07b7a","author":{"name":"David Lechner","email":"d8099b0f90e53c29d29eb12a7a3caa5af4f12681@lechnology.com"},"message":"mfd: da8xx-cfgchip: New header file for CFGCHIP registers\n\nCreate a new header file for TI DA8XX SoC CFGCHIPx registers.\nThis will be used by a number of planned drivers including a new USB\nPHY driver and common clock framework drivers.\n\nThe same defines *will* be removed from the platform_data header,\nonce all the users start using the new syscon device header.\n\nThis also fixes the following compiler error caused due to\na dependent patch not merged.\ndrivers/phy/phy-da8xx-usb.c:19:37:\nfatal error: linux/mfd/da8xx-cfgchip.h: No such file or directory\n #include <linux/mfd/da8xx-cfgchip.h>\n\nSigned-off-by: David Lechner <david@lechnology.com>\nAcked-by: Lee Jones <lee.jones@linaro.org>\nReported-by: Arnd Bergmann <arnd@arndb.de>\nSigned-off-by: Kishon Vijay Abraham I <kishon@ti.com>","distinct":true,"url":"https://api.github.com/repos/minipli/linux-grsec/commits/1766e7b3763a0707c2fda9689a7866dceed07b7a"}]}
{"actor":{"display_login":"minipli"}}