{"push_id":2787092794,"size":25,"distinct_size":25,"ref":"refs/heads/land-m-oss","head":"3fea8f5ad9a4d0c9cb7a545f4d62e5838675897c","before":"1b64ca94ed6790263f5b8093d67e6f77b686251b","commits":[{"sha":"db9e37a1c5f21cec095da9ed53a2c0cbeeb24ee6","author":{"name":"Al Viro","email":"de609eb4d5d70b1d38ec6642adbfc33a2781f63c@zeniv.linux.org.uk"},"message":"[PATCH] arm: fix handling of F_OFD_... in oabi_fcntl64()\n\n[ Upstream commit 76cc404bfdc0d419c720de4daaf2584542734f42 ]\n\nCc: stable@vger.kernel.org # 3.15+\nReviewed-by: Jeff Layton <jeff.layton@primarydata.com>\nSigned-off-by: Al Viro <viro@zeniv.linux.org.uk>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/NusantaraDev/Xiaomi_Kernel_land/commits/db9e37a1c5f21cec095da9ed53a2c0cbeeb24ee6"},{"sha":"ade4ba0d843dff6c430d00a88e55e373762de825","author":{"name":"Theodore Ts'o","email":"4ed386e0495d3e109932df055831d9ec2f824927@mit.edu"},"message":"ext4: validate that metadata blocks do not overlap superblock\n\n[ Upstream commit 829fa70dddadf9dd041d62b82cd7cea63943899d ]\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>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/NusantaraDev/Xiaomi_Kernel_land/commits/ade4ba0d843dff6c430d00a88e55e373762de825"},{"sha":"5edbe377024b8f702463e1cf6bb32048e9bce8d8","author":{"name":"Miklos Szeredi","email":"84cd5483a2f9acd1c37251cba7c2908448f221b8@redhat.com"},"message":"ovl: don't copy up opaqueness\n\n[ Upstream commit 0956254a2d5b9e2141385514553aeef694dfe3b5 ]\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>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/NusantaraDev/Xiaomi_Kernel_land/commits/5edbe377024b8f702463e1cf6bb32048e9bce8d8"},{"sha":"87fe0cd807d1974f852be46f19771813bc355991","author":{"name":"Zefan Li","email":"a8167b9d27aca9c6624754deb52c4c6420eded04@huawei.com"},"message":"cpuset: make sure new tasks conform to the current config of the cpuset\n\n[ Upstream commit 06f4e94898918bcad00cdd4d349313a439d6911e ]\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\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/NusantaraDev/Xiaomi_Kernel_land/commits/87fe0cd807d1974f852be46f19771813bc355991"},{"sha":"a1147c771a69625aaea70924cd7128ba35a2a74c","author":{"name":"Alexey Khoroshilov","email":"a9985f635ca4eb5d7c64df6d16c76aa9811509c5@ispras.ru"},"message":"USB: serial: mos7720: fix non-atomic allocation in write path\n\n[ Upstream commit 5a5a1d614287a647b36dff3f40c2b0ceabbc83ec ]\n\nThere is an allocation with GFP_KERNEL flag in mos7720_write(),\nwhile it may be called from interrupt context.\n\nFollow-up for commit 191252837626 (\"USB: kobil_sct: fix non-atomic\nallocation in write path\")\n\nFound by Linux Driver Verification project (linuxtesting.org).\n\nSigned-off-by: Alexey Khoroshilov <khoroshilov@ispras.ru>\nCc: stable <stable@vger.kernel.org>\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/NusantaraDev/Xiaomi_Kernel_land/commits/a1147c771a69625aaea70924cd7128ba35a2a74c"},{"sha":"178bc9085d938641a1d02dba2a3b0b4f8ecf79e9","author":{"name":"Alexey Khoroshilov","email":"a9985f635ca4eb5d7c64df6d16c76aa9811509c5@ispras.ru"},"message":"USB: serial: mos7840: fix non-atomic allocation in write path\n\n[ Upstream commit 3b7c7e52efda0d4640060de747768360ba70a7c0 ]\n\nThere is an allocation with GFP_KERNEL flag in mos7840_write(),\nwhile it may be called from interrupt context.\n\nFollow-up for commit 191252837626 (\"USB: kobil_sct: fix non-atomic\nallocation in write path\")\n\nFound by Linux Driver Verification project (linuxtesting.org).\n\nSigned-off-by: Alexey Khoroshilov <khoroshilov@ispras.ru>\nCc: stable <stable@vger.kernel.org>\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/NusantaraDev/Xiaomi_Kernel_land/commits/178bc9085d938641a1d02dba2a3b0b4f8ecf79e9"},{"sha":"d8107af012415fd200de7786da8f4ebbab6cf834","author":{"name":"Ian Abbott","email":"9e6ba6483b6a3e14d61f7c987e72ecb5b46122d6@mev.co.uk"},"message":"staging: comedi: daqboard2000: bug fix board type matching code\n\n[ Upstream commit 80e162ee9b31d77d851b10f8c5299132be1e120f ]\n\n`daqboard2000_find_boardinfo()` is supposed to check if the\nDaqBoard/2000 series model is supported, based on the PCI subvendor and\nsubdevice ID.  The current code is wrong as it is comparing the PCI\ndevice's subdevice ID to an expected, fixed value for the subvendor ID.\nIt should be comparing the PCI device's subvendor ID to this fixed\nvalue.  Correct it.\n\nFixes: 7e8401b23e7f (\"staging: comedi: daqboard2000: add back\nsubsystem_device check\")\nSigned-off-by: Ian Abbott <abbotti@mev.co.uk>\nCc: <stable@vger.kernel.org> # 3.7+\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/NusantaraDev/Xiaomi_Kernel_land/commits/d8107af012415fd200de7786da8f4ebbab6cf834"},{"sha":"985f3f2373e5f14936d866a823939766321b94e4","author":{"name":"Ian Abbott","email":"9e6ba6483b6a3e14d61f7c987e72ecb5b46122d6@mev.co.uk"},"message":"staging: comedi: ni_mio_common: fix wrong insn_write handler\n\n[ Upstream commit 5ca05345c56cb979e1a25ab6146437002f95cac8 ]\n\nFor counter subdevices, the `s->insn_write` handler is being set to the\nwrong function, `ni_tio_insn_read()`.  It should be\n`ni_tio_insn_write()`.\n\nSigned-off-by: Ian Abbott <abbotti@mev.co.uk>\nReported-by: Éric Piel <piel@delmic.com>\nFixes: 10f74377eec3 (\"staging: comedi: ni_tio: make ni_tio_winsn() a\n  proper comedi (*insn_write)\"\nCc: <stable@vger.kernel.org> # 3.17+\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/NusantaraDev/Xiaomi_Kernel_land/commits/985f3f2373e5f14936d866a823939766321b94e4"},{"sha":"6ef28f2f902ae5921048d7c4e6913ca4e38a1f3c","author":{"name":"Ian Abbott","email":"9e6ba6483b6a3e14d61f7c987e72ecb5b46122d6@mev.co.uk"},"message":"staging: comedi: ni_mio_common: fix AO inttrig backwards compatibility\n\n[ Upstream commit f0f4b0cc3a8cffd983f5940d46cd0227f3f5710a ]\n\nCommit ebb657babfa9 (\"staging: comedi: ni_mio_common: clarify the\ncmd->start_arg validation and use\") introduced a backwards compatibility\nissue in the use of asynchronous commands on the AO subdevice when\n`start_src` is `TRIG_EXT`.  Valid values for `start_src` are `TRIG_INT`\n(for internal, software trigger), and `TRIG_EXT` (for external trigger).\nWhen set to `TRIG_EXT`.  In both cases, the driver relies on an\ninternal, software trigger to set things up (allowing the user\napplication to write sufficient samples to the data buffer before the\ntrigger), so it acts as a software \"pre-trigger\" in the `TRIG_EXT` case.\nThe software trigger is handled by `ni_ao_inttrig()`.\n\nPrior to the above change, when `start_src` was `TRIG_INT`, `start_arg`\nwas required to be 0, and `ni_ao_inttrig()` checked that the software\ntrigger number was also 0.  After the above change, when `start_src` was\n`TRIG_INT`, any value was allowed for `start_arg`, and `ni_ao_inttrig()`\nchecked that the software trigger number matched this `start_arg` value.\nThe backwards compatibility issue is that the internal trigger number\nnow has to match `start_arg` when `start_src` is `TRIG_EXT` when it\npreviously had to be 0.\n\nFix the backwards compatibility issue in `ni_ao_inttrig()` by always\nallowing software trigger number 0 when `start_src` is something other\nthan `TRIG_INT`.\n\nThanks to Spencer Olson for reporting the issue.\n\nSigned-off-by: Ian Abbott <abbotti@mev.co.uk>\nReported-by: Spencer Olson <olsonse@umich.edu>\nFixes: ebb657babfa9 (\"staging: comedi: ni_mio_common: clarify the cmd->start_arg validation and use\")\nCc: stable <stable@vger.kernel.org>\nReviewed-by: H Hartley Sweeten <hsweeten@visionengravers.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/NusantaraDev/Xiaomi_Kernel_land/commits/6ef28f2f902ae5921048d7c4e6913ca4e38a1f3c"},{"sha":"93c7ae51294639d51ef0f6fbc722daae0544f873","author":{"name":"Linus Walleij","email":"9cd9d802d23c0ed5e224beabf4ae4a5c478746ef@linaro.org"},"message":"iio: accel: kxsd9: Fix raw read return\n\n[ Upstream commit 7ac61a062f3147dc23e3f12b9dfe7c4dd35f9cb8 ]\n\nAny readings from the raw interface of the KXSD9 driver will\nreturn an empty string, because it does not return\nIIO_VAL_INT but rather some random value from the accelerometer\nto the caller.\n\nCc: stable@vger.kernel.org\nSigned-off-by: Linus Walleij <linus.walleij@linaro.org>\nSigned-off-by: Jonathan Cameron <jic23@kernel.org>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/NusantaraDev/Xiaomi_Kernel_land/commits/93c7ae51294639d51ef0f6fbc722daae0544f873"},{"sha":"e066faf1b61036126cbc3163fa370d4247e880dc","author":{"name":"Alan Stern","email":"75ea6bb7bfc1186f92d26164de5f9268c9a45b59@rowland.harvard.edu"},"message":"USB: avoid left shift by -1\n\n[ Upstream commit 53e5f36fbd2453ad69a3369a1db62dc06c30a4aa ]\n\nUBSAN complains about a left shift by -1 in proc_do_submiturb().  This\ncan occur when an URB is submitted for a bulk or control endpoint on\na high-speed device, since the code doesn't bother to check the\nendpoint type; normally only interrupt or isochronous endpoints have\na nonzero bInterval value.\n\nAside from the fact that the operation is illegal, it shouldn't matter\nbecause the result isn't used.  Still, in theory it could cause a\nhardware exception or other problem, so we should work around it.\nThis patch avoids doing the left shift unless the shift amount is >= 0.\n\nThe same piece of code has another problem.  When checking the device\nspeed (the exponential encoding for interrupt endpoints is used only\nby high-speed or faster devices), we need to look for speed >=\nUSB_SPEED_SUPER as well as speed == USB_SPEED HIGH.  The patch adds\nthis check.\n\nSigned-off-by: Alan Stern <stern@rowland.harvard.edu>\nReported-by: Vittorio Zecca <zeccav@gmail.com>\nTested-by: Vittorio Zecca <zeccav@gmail.com>\nSuggested-by: Bjørn Mork <bjorn@mork.no>\nCC: <stable@vger.kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/NusantaraDev/Xiaomi_Kernel_land/commits/e066faf1b61036126cbc3163fa370d4247e880dc"},{"sha":"a6eba2f73bf3e402829724d7bfb736c609467d0f","author":{"name":"Aleksandr Makarov","email":"60ce939170ef8a56d0675ce41e9a474a371f765e@gmail.com"},"message":"USB: serial: option: add WeTelecom WM-D200\n\n[ Upstream commit 6695593e4a7659db49ac6eca98c164f7b5589f72 ]\n\nAdd support for WeTelecom WM-D200.\n\nT:  Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  4 Spd=12  MxCh= 0\nD:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1\nP:  Vendor=22de ProdID=6801 Rev=00.00\nS:  Manufacturer=WeTelecom Incorporated\nS:  Product=WeTelecom Mobile Products\nC:  #Ifs= 4 Cfg#= 1 Atr=80 MxPwr=500mA\nI:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)\nI:  If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)\nI:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)\nI:  If#= 3 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage\n\nSigned-off-by: Aleksandr Makarov <aleksandr.o.makarov@gmail.com>\nCc: stable <stable@vger.kernel.org>\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/NusantaraDev/Xiaomi_Kernel_land/commits/a6eba2f73bf3e402829724d7bfb736c609467d0f"},{"sha":"b735daae7a6afccbdd2338f11d818dfaac2e9fef","author":{"name":"Aleksandr Makarov","email":"60ce939170ef8a56d0675ce41e9a474a371f765e@gmail.com"},"message":"USB: serial: option: add WeTelecom 0x6802 and 0x6803 products\n\n[ Upstream commit 40d9c32525cba79130612650b1abc47c0c0f19a8 ]\n\nThese product IDs are listed in Windows driver.\n0x6803 corresponds to WeTelecom WM-D300.\n0x6802 name is unknown.\n\nSigned-off-by: Aleksandr Makarov <aleksandr.o.makarov@gmail.com>\nCc: stable <stable@vger.kernel.org>\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/NusantaraDev/Xiaomi_Kernel_land/commits/b735daae7a6afccbdd2338f11d818dfaac2e9fef"},{"sha":"4ff77f223a63b18745c4a202970682f138d056cc","author":{"name":"Dave Chinner","email":"4d9e23a041ac966f5316a7481300d4ae12e806fe@redhat.com"},"message":"xfs: fix superblock inprogress check\n\n[ Upstream commit f3d7ebdeb2c297bd26272384e955033493ca291c ]\n\nFrom inspection, the superblock sb_inprogress check is done in the\nverifier and triggered only for the primary superblock via a\n\"bp->b_bn == XFS_SB_DADDR\" check.\n\nUnfortunately, the primary superblock is an uncached buffer, and\nhence it is configured by xfs_buf_read_uncached() with:\n\n\tbp->b_bn = XFS_BUF_DADDR_NULL;  /* always null for uncached buffers */\n\nAnd so this check never triggers. Fix it.\n\ncc: <stable@vger.kernel.org>\nSigned-off-by: Dave Chinner <dchinner@redhat.com>\nReviewed-by: Brian Foster <bfoster@redhat.com>\nReviewed-by: Christoph Hellwig <hch@lst.de>\nSigned-off-by: Dave Chinner <david@fromorbit.com>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/NusantaraDev/Xiaomi_Kernel_land/commits/4ff77f223a63b18745c4a202970682f138d056cc"},{"sha":"13312f0f2c1f9135934c3f68a80a261717c1503e","author":{"name":"Trond Myklebust","email":"cc958843532c615cbd4920e868f78c7985331a5a@primarydata.com"},"message":"NFSv4.x: Fix a refcount leak in nfs_callback_up_net\n\n[ Upstream commit 98b0f80c2396224bbbed81792b526e6c72ba9efa ]\n\nOn error, the callers expect us to return without bumping\nnn->cb_users[].\n\nSigned-off-by: Trond Myklebust <trond.myklebust@primarydata.com>\nCc: stable@vger.kernel.org # v3.7+\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/NusantaraDev/Xiaomi_Kernel_land/commits/13312f0f2c1f9135934c3f68a80a261717c1503e"},{"sha":"ab50c732d66fa6d9c614ad4b5dda6500c4fe57b8","author":{"name":"Mikulas Patocka","email":"52f8f9962b7f38d8269c63c0859d68147c8d10f0@redhat.com"},"message":"dm crypt: fix error with too large bios\n\n[ Upstream commit 4e870e948fbabf62b78e8410f04c67703e7c816b ]\n\nWhen dm-crypt processes writes, it allocates a new bio in\ncrypt_alloc_buffer().  The bio is allocated from a bio set and it can\nhave at most BIO_MAX_PAGES vector entries, however the incoming bio can be\nlarger (e.g. if it was allocated by bcache).  If the incoming bio is\nlarger, bio_alloc_bioset() fails and an error is returned.\n\nTo avoid the error, we test for a too large bio in the function\ncrypt_map() and use dm_accept_partial_bio() to split the bio.\ndm_accept_partial_bio() trims the current bio to the desired size and\nasks DM core to send another bio with the rest of the data.\n\nSigned-off-by: Mikulas Patocka <mpatocka@redhat.com>\nSigned-off-by: Mike Snitzer <snitzer@redhat.com>\nCc: stable@vger.kernel.org # v3.16+\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/NusantaraDev/Xiaomi_Kernel_land/commits/ab50c732d66fa6d9c614ad4b5dda6500c4fe57b8"},{"sha":"01d0c457d826d81481c8f4485ada438d0d565ce6","author":{"name":"Eric Biggers","email":"6f6115196800bbe9712b3f04c7e40093bb382fc5@google.com"},"message":"dm crypt: fix free of bad values after tfm allocation failure\n\n[ Upstream commit 5d0be84ec0cacfc7a6d6ea548afdd07d481324cd ]\n\nIf crypt_alloc_tfms() had to allocate multiple tfms and it failed before\nthe last allocation, then it would call crypt_free_tfms() and could free\npointers from uninitialized memory -- due to the crypt_free_tfms() check\nfor non-zero cc->tfms[i].  Fix by allocating zeroed memory.\n\nSigned-off-by: Eric Biggers <ebiggers@google.com>\nSigned-off-by: Mike Snitzer <snitzer@redhat.com>\nCc: stable@vger.kernel.org\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/NusantaraDev/Xiaomi_Kernel_land/commits/01d0c457d826d81481c8f4485ada438d0d565ce6"},{"sha":"0b764b2ea1ac39a0d41f49250c8b21b244710025","author":{"name":"Tejun Heo","email":"546b05909706652891a87f7bfe385ae147f61f91@kernel.org"},"message":"kernfs: don't depend on d_find_any_alias() when generating notifications\n\n[ Upstream commit df6a58c5c5aa8ecb1e088ecead3fa33ae70181f1 ]\n\nkernfs_notify_workfn() sends out file modified events for the\nscheduled kernfs_nodes.  Because the modifications aren't from\nuserland, it doesn't have the matching file struct at hand and can't\nuse fsnotify_modify().  Instead, it looked up the inode and then used\nd_find_any_alias() to find the dentry and used fsnotify_parent() and\nfsnotify() directly to generate notifications.\n\nThe assumption was that the relevant dentries would have been pinned\nif there are listeners, which isn't true as inotify doesn't pin\ndentries at all and watching the parent doesn't pin the child dentries\neven for dnotify.  This led to, for example, inotify watchers not\ngetting notifications if the system is under memory pressure and the\nmatching dentries got reclaimed.  It can also be triggered through\n/proc/sys/vm/drop_caches or a remount attempt which involves shrinking\ndcache.\n\nfsnotify_parent() only uses the dentry to access the parent inode,\nwhich kernfs can do easily.  Update kernfs_notify_workfn() so that it\nuses fsnotify() directly for both the parent and target inodes without\ngoing through d_find_any_alias().  While at it, supply the target file\nname to fsnotify() from kernfs_node->name.\n\nSigned-off-by: Tejun Heo <tj@kernel.org>\nReported-by: Evgeny Vereshchagin <evvers@ya.ru>\nFixes: d911d9874801 (\"kernfs: make kernfs_notify() trigger inotify events too\")\nCc: John McCutchan <john@johnmccutchan.com>\nCc: Robert Love <rlove@rlove.org>\nCc: Eric Paris <eparis@parisplace.org>\nCc: stable@vger.kernel.org # v3.16+\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/NusantaraDev/Xiaomi_Kernel_land/commits/0b764b2ea1ac39a0d41f49250c8b21b244710025"},{"sha":"cc318bc6819922ad17dbcbb5e0ac5164bcbb60d2","author":{"name":"Miklos Szeredi","email":"84cd5483a2f9acd1c37251cba7c2908448f221b8@redhat.com"},"message":"ovl: remove posix_acl_default from workdir\n\n[ Upstream commit c11b9fdd6a612f376a5e886505f1c54c16d8c380 ]\n\nClear out posix acl xattrs on workdir and also reset the mode after\ncreation so that an inherited sgid bit is cleared.\n\nSigned-off-by: Miklos Szeredi <mszeredi@redhat.com>\nCc: <stable@vger.kernel.org>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/NusantaraDev/Xiaomi_Kernel_land/commits/cc318bc6819922ad17dbcbb5e0ac5164bcbb60d2"},{"sha":"f45724343a4a5399386f8df3e548445fc9056c48","author":{"name":"Miklos Szeredi","email":"84cd5483a2f9acd1c37251cba7c2908448f221b8@redhat.com"},"message":"ovl: listxattr: use strnlen()\n\n[ Upstream commit 7cb35119d067191ce9ebc380a599db0b03cbd9d9 ]\n\nBe defensive about what underlying fs provides us in the returned xattr\nlist buffer.  If it's not properly null terminated, bail out with a warning\ninsead of BUG.\n\nSigned-off-by: Miklos Szeredi <mszeredi@redhat.com>\nCc: <stable@vger.kernel.org>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>","distinct":true,"url":"https://api.github.com/repos/NusantaraDev/Xiaomi_Kernel_land/commits/f45724343a4a5399386f8df3e548445fc9056c48"}]}
{"actor":{"display_login":"AyraHikari"}}