{"push_id":713231769,"size":1000,"distinct_size":38,"ref":"refs/heads/linux-3.10.33","head":"939be5719d6681e4ca282348b622b66d55559aad","before":"f291039d191d11784bb04854dfc66191060808c6","commits":[{"sha":"359772477cc4c410a6d785a3de51d85cd0b6aeba","author":{"email":"39bb74b16720293e1449e36465485b27216fbd6d@gmail.com","name":"Ricardo Ribalda Delgado"},"message":"PCI: Generate uppercase hex for modalias interface class\n\ncommit 89ec3dcf17fd3fa009ecf8faaba36828dd6bc416 upstream.\n\nSome implementations of modprobe fail to load the driver for a PCI device\nautomatically because the \"interface\" part of the modalias from the kernel\nis lowercase, and the modalias from file2alias is uppercase.\n\nThe \"interface\" is the low-order byte of the Class Code, defined in PCI\nr3.0, Appendix D.  Most interface types defined in the spec do not use\nalpha characters, so they won't be affected.  For example, 00h, 01h, 10h,\n20h, etc. are unaffected.\n\nPrint the \"interface\" byte of the Class Code in uppercase hex, as we\nalready do for the Vendor ID, Device ID, Class, etc.\n\n[bhelgaas: changelog]\nSigned-off-by: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>\nSigned-off-by: Bjorn Helgaas <bhelgaas@google.com>\nAcked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/surkovalex/linux/commits/359772477cc4c410a6d785a3de51d85cd0b6aeba"},{"sha":"28330aa4e0dc1232ecfb18c7456a5c456f5c6e97","author":{"email":"1542dc81552e668e197a396f69e655c1621c300d@redhat.com","name":"Stanislaw Gruszka"},"message":"rt2800: correct BBP1_TX_POWER_CTRL mask\n\ncommit 01f7feeaf4528bec83798316b3c811701bac5d3e upstream.\n\nTwo bits control TX power on BBP_R1 register. Correct the mask,\notherwise we clear additional bit on BBP_R1 register, what can have\nunknown, possible negative effect.\n\nSigned-off-by: Stanislaw Gruszka <sgruszka@redhat.com>\nSigned-off-by: John W. Linville <linville@tuxdriver.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/surkovalex/linux/commits/28330aa4e0dc1232ecfb18c7456a5c456f5c6e97"},{"sha":"90f9a6a427abd19c8d304ecbac034deb39d0737c","author":{"email":"7dbc6498a90ff1ada42fc224430b4f763baa5c5c@intel.com","name":"Loic Poulain"},"message":"Bluetooth: Fix HCI H5 corrupted ack value\n\ncommit 4807b51895dce8aa650ebebc51fa4a795ed6b8b8 upstream.\n\nIn this expression: seq = (seq - 1) % 8\nseq (u8) is implicitly converted to an int in the arithmetic operation.\nSo if seq value is 0, operation is ((0 - 1) % 8) => (-1 % 8) => -1.\nThe new seq value is 0xff which is an invalid ACK value, we expect 0x07.\nIt leads to frequent dropped ACK and retransmission.\nFix this by using '&' binary operator instead of '%'.\n\nSigned-off-by: Loic Poulain <loic.poulain@intel.com>\nSigned-off-by: Marcel Holtmann <marcel@holtmann.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/surkovalex/linux/commits/90f9a6a427abd19c8d304ecbac034deb39d0737c"},{"sha":"41ba8fa07c9aa5c18ba3fd14917b53c4367d3ea7","author":{"email":"7a5a1e9c8ae63f4352f75d36a9cd6b8f98c86384@realsil.com.cn","name":"Champion Chen"},"message":"Bluetooth: Fix issue with USB suspend in btusb driver\n\ncommit 85560c4a828ec9c8573840c9b66487b6ae584768 upstream.\n\nSuspend could fail for some platforms because\nbtusb_suspend==> btusb_stop_traffic ==> usb_kill_anchored_urbs.\n\nWhen btusb_bulk_complete returns before system suspend and resubmits\nan URB, the system cannot enter suspend state.\n\nSigned-off-by: Champion Chen <champion_chen@realsil.com.cn>\nSigned-off-by: Larry Finger <Larry.Finger@lwfinger.net>\nSigned-off-by: Marcel Holtmann <marcel@holtmann.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/surkovalex/linux/commits/41ba8fa07c9aa5c18ba3fd14917b53c4367d3ea7"},{"sha":"2e8fee8128715f3d250f92ef8d12a06c23a15101","author":{"email":"adb0658383f88ec6beb1fb7689ba0dac7c1c4882@oracle.com","name":"Junxiao Bi"},"message":"mm: clear __GFP_FS when PF_MEMALLOC_NOIO is set\n\ncommit 934f3072c17cc8886f4c043b47eeeb1b12f8de33 upstream.\n\ncommit 21caf2fc1931 (\"mm: teach mm by current context info to not do I/O\nduring memory allocation\") introduces PF_MEMALLOC_NOIO flag to avoid doing\nI/O inside memory allocation, __GFP_IO is cleared when this flag is set,\nbut __GFP_FS implies __GFP_IO, it should also be cleared.  Or it may still\nrun into I/O, like in superblock shrinker.  And this will make the kernel\nrun into the deadlock case described in that commit.\n\nSee Dave Chinner's comment about io in superblock shrinker:\n\nFilesystem shrinkers do indeed perform IO from the superblock shrinker and\nhave for years.  Even clean inodes can require IO before they can be freed\n- e.g.  on an orphan list, need truncation of post-eof blocks, need to\nwait for ordered operations to complete before it can be freed, etc.\n\nIOWs, Ext4, btrfs and XFS all can issue and/or block on arbitrary amounts\nof IO in the superblock shrinker context.  XFS, in particular, has been\ndoing transactions and IO from the VFS inode cache shrinker since it was\nfirst introduced....\n\nFix this by clearing __GFP_FS in memalloc_noio_flags(), this function has\nmasked all the gfp_mask that will be passed into fs for the processes\nsetting PF_MEMALLOC_NOIO in the direct reclaim path.\n\nv1 thread at: https://lkml.org/lkml/2014/9/3/32\n\nSigned-off-by: Junxiao Bi <junxiao.bi@oracle.com>\nCc: Dave Chinner <david@fromorbit.com>\nCc: joyce.xue <xuejiufei@huawei.com>\nCc: Ming Lei <ming.lei@canonical.com>\nCc: Trond Myklebust <trond.myklebust@primarydata.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/surkovalex/linux/commits/2e8fee8128715f3d250f92ef8d12a06c23a15101"},{"sha":"9345b4559ec8826ec13dd91d95a8cab81748c307","author":{"email":"32f7bf5a1f07a8b363256f1773dbeada59d65244@opteya.com","name":"Yann Droneaud"},"message":"fanotify: enable close-on-exec on events' fd when requested in fanotify_init()\n\ncommit 0b37e097a648aa71d4db1ad108001e95b69a2da4 upstream.\n\nAccording to commit 80af258867648 (\"fanotify: groups can specify their\nf_flags for new fd\"), file descriptors created as part of file access\nnotification events inherit flags from the event_f_flags argument passed\nto syscall fanotify_init(2)[1].\n\nUnfortunately O_CLOEXEC is currently silently ignored.\n\nIndeed, event_f_flags are only given to dentry_open(), which only seems to\ncare about O_ACCMODE and O_PATH in do_dentry_open(), O_DIRECT in\nopen_check_o_direct() and O_LARGEFILE in generic_file_open().\n\nIt's a pity, since, according to some lookup on various search engines and\nhttp://codesearch.debian.net/, there's already some userspace code which\nuse O_CLOEXEC:\n\n- in systemd's readahead[2]:\n\n    fanotify_fd = fanotify_init(FAN_CLOEXEC|FAN_NONBLOCK, O_RDONLY|O_LARGEFILE|O_CLOEXEC|O_NOATIME);\n\n- in clsync[3]:\n\n    #define FANOTIFY_EVFLAGS (O_LARGEFILE|O_RDONLY|O_CLOEXEC)\n\n    int fanotify_d = fanotify_init(FANOTIFY_FLAGS, FANOTIFY_EVFLAGS);\n\n- in examples [4] from \"Filesystem monitoring in the Linux\n  kernel\" article[5] by Aleksander Morgado:\n\n    if ((fanotify_fd = fanotify_init (FAN_CLOEXEC,\n                                      O_RDONLY | O_CLOEXEC | O_LARGEFILE)) < 0)\n\nAdditionally, since commit 48149e9d3a7e (\"fanotify: check file flags\npassed in fanotify_init\").  having O_CLOEXEC as part of fanotify_init()\nsecond argument is expressly allowed.\n\nSo it seems expected to set close-on-exec flag on the file descriptors if\nuserspace is allowed to request it with O_CLOEXEC.\n\nBut Andrew Morton raised[6] the concern that enabling now close-on-exec\nmight break existing applications which ask for O_CLOEXEC but expect the\nfile descriptor to be inherited across exec().\n\nIn the other hand, as reported by Mihai Dontu[7] close-on-exec on the file\ndescriptor returned as part of file access notify can break applications\ndue to deadlock.  So close-on-exec is needed for most applications.\n\nMore, applications asking for close-on-exec are likely expecting it to be\nenabled, relying on O_CLOEXEC being effective.  If not, it might weaken\ntheir security, as noted by Jan Kara[8].\n\nSo this patch replaces call to macro get_unused_fd() by a call to function\nget_unused_fd_flags() with event_f_flags value as argument.  This way\nO_CLOEXEC flag in the second argument of fanotify_init(2) syscall is\ninterpreted and close-on-exec get enabled when requested.\n\n[1] http://man7.org/linux/man-pages/man2/fanotify_init.2.html\n[2] http://cgit.freedesktop.org/systemd/systemd/tree/src/readahead/readahead-collect.c?id=v208#n294\n[3] https://github.com/xaionaro/clsync/blob/v0.2.1/sync.c#L1631\n    https://github.com/xaionaro/clsync/blob/v0.2.1/configuration.h#L38\n[4] http://www.lanedo.com/~aleksander/fanotify/fanotify-example.c\n[5] http://www.lanedo.com/2013/filesystem-monitoring-linux-kernel/\n[6] http://lkml.kernel.org/r/20141001153621.65e9258e65a6167bf2e4cb50@linux-foundation.org\n[7] http://lkml.kernel.org/r/20141002095046.3715eb69@mdontu-l\n[8] http://lkml.kernel.org/r/20141002104410.GB19748@quack.suse.cz\n\nLink: http://lkml.kernel.org/r/cover.1411562410.git.ydroneaud@opteya.com\nSigned-off-by: Yann Droneaud <ydroneaud@opteya.com>\nReviewed-by: Jan Kara <jack@suse.cz>\nReviewed by: Heinrich Schuchardt <xypron.glpk@gmx.de>\nTested-by: Heinrich Schuchardt <xypron.glpk@gmx.de>\nCc: Mihai Don\\u021bu <mihai.dontu@gmail.com>\nCc: Pádraig Brady <P@draigBrady.com>\nCc: Heinrich Schuchardt <xypron.glpk@gmx.de>\nCc: Jan Kara <jack@suse.cz>\nCc: Valdis Kletnieks <Valdis.Kletnieks@vt.edu>\nCc: Michael Kerrisk-manpages <mtk.manpages@gmail.com>\nCc: Lino Sanfilippo <LinoSanfilippo@gmx.de>\nCc: Richard Guy Briggs <rgb@redhat.com>\nCc: Eric Paris <eparis@redhat.com>\nCc: Al Viro <viro@zeniv.linux.org.uk>\nCc: Michael Kerrisk <mtk.manpages@gmail.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/surkovalex/linux/commits/9345b4559ec8826ec13dd91d95a8cab81748c307"},{"sha":"42abc5125d0cd1abba9d21133010dcea1f3a0e8f","author":{"email":"e642b69ed2fc111e09ffdc37feb733a52253340d@oracle.com","name":"Sasha Levin"},"message":"kernel: add support for gcc 5\n\ncommit 71458cfc782eafe4b27656e078d379a34e472adf upstream.\n\nWe're missing include/linux/compiler-gcc5.h which is required now\nbecause gcc branched off to v5 in trunk.\n\nJust copy the relevant bits out of include/linux/compiler-gcc4.h,\nno new code is added as of now.\n\nThis fixes a build error when using gcc 5.\n\nSigned-off-by: Sasha Levin <sasha.levin@oracle.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/surkovalex/linux/commits/42abc5125d0cd1abba9d21133010dcea1f3a0e8f"},{"sha":"9fa1d75bead1cfe2718d4e81fd039ea4006da745","author":{"email":"74f0c009df510614346aa771cd21959b78cdb413@linux.intel.com","name":"Andy Shevchenko"},"message":"spi: dw-mid: terminate ongoing transfers at exit\n\ncommit 8e45ef682cb31fda62ed4eeede5d9745a0a1b1e2 upstream.\n\nDo full clean up at exit, means terminate all ongoing DMA transfers.\n\nSigned-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/surkovalex/linux/commits/9fa1d75bead1cfe2718d4e81fd039ea4006da745"},{"sha":"9f81e4deb5a6807fc2495e61ce080df7de51e3b8","author":{"email":"71355f653a2d7244204587a815c7fb1aad59a43e@linaro.org","name":"Victor Kamensky"},"message":"arm64: compat: fix compat types affecting struct compat_elf_prpsinfo\n\ncommit 971a5b6fe634bb7b617d8c5f25b6a3ddbc600194 upstream.\n\nThe compat_elf_prpsinfo structure does not match the arch/arm struct\nelf_pspsinfo definition. As result NT_PRPSINFO note in core file\ncreated by arm64 kernel for aarch32 (compat) process has wrong size.\nSo gdb cannot display command that caused process crash.\n\nFix is to change size of __compat_uid_t, __compat_gid_t so it would\nmatch size of similar fields in arch/arm case.\n\nSigned-off-by: Victor Kamensky <victor.kamensky@linaro.org>\nAcked-by: Arnd Bergmann <arnd@arndb.de>\nSigned-off-by: Catalin Marinas <catalin.marinas@arm.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/surkovalex/linux/commits/9f81e4deb5a6807fc2495e61ce080df7de51e3b8"},{"sha":"aff3c48530a9bd58edf42d94684234244c957a6b","author":{"email":"5d78902c885bda21bab1f3f4d20718dff0167f20@gmail.com","name":"Anatol Pomozov"},"message":"ALSA: pcm: use the same dma mmap codepath both for arm and arm64\n\ncommit a011e213f3700233ed2a676f1ef0a74a052d7162 upstream.\n\nThis avoids following kernel crash when try to playback on arm64\n\n[  107.497203] [<ffffffc00046b310>] snd_pcm_mmap_data_fault+0x90/0xd4\n[  107.503405] [<ffffffc0001541ac>] __do_fault+0xb0/0x498\n[  107.508565] [<ffffffc0001576a0>] handle_mm_fault+0x224/0x7b0\n[  107.514246] [<ffffffc000092640>] do_page_fault+0x11c/0x310\n[  107.519738] [<ffffffc000081100>] do_mem_abort+0x38/0x98\n\nTested: backported to 3.14 and tried to playback on arm64 machine\n\nSigned-off-by: Anatol Pomozov <anatol.pomozov@gmail.com>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/surkovalex/linux/commits/aff3c48530a9bd58edf42d94684234244c957a6b"},{"sha":"8205fae0f07db86ca05108a478d5f8b7e5fe2737","author":{"email":"4596b3305151c7ee743192a95d394341e3d3b644@suse.de","name":"Takashi Iwai"},"message":"ALSA: emu10k1: Fix deadlock in synth voice lookup\n\ncommit 95926035b187cc9fee6fb61385b7da9c28123f74 upstream.\n\nThe emu10k1 voice allocator takes voice_lock spinlock.  When there is\nno empty stream available, it tries to release a voice used by synth,\nand calls get_synth_voice.  The callback function,\nsnd_emu10k1_synth_get_voice(), however, also takes the voice_lock,\nthus it deadlocks.\n\nThe fix is simply removing the voice_lock holds in\nsnd_emu10k1_synth_get_voice(), as this is always called in the\nspinlock context.\n\nReported-and-tested-by: Arthur Marsh <arthur.marsh@internode.on.net>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/surkovalex/linux/commits/8205fae0f07db86ca05108a478d5f8b7e5fe2737"},{"sha":"4148f813c2ef303eb500a6b9a360783c3217e810","author":{"email":"b2e9715322aad7c9d0466aa7e5e3022f0db2cc3a@gmail.com","name":"Vlad Catoi"},"message":"ALSA: usb-audio: Add support for Steinberg UR22 USB interface\n\ncommit f0b127fbfdc8756eba7437ab668f3169280bd358 upstream.\n\nAdding support for Steinberg UR22 USB interface via quirks table patch\n\nSee Ubuntu bug report:\nhttps://bugs.launchpad.net/ubuntu/+source/linux/+bug/1317244\nAlso see threads:\nhttp://linux-audio.4202.n7.nabble.com/Support-for-Steinberg-UR22-Yamaha-USB-chipset-0499-1509-tc82888.html#a82917\nhttp://www.steinberg.net/forums/viewtopic.php?t=62290\n\nTested by at least 4 people judging by the threads.\nDid not test MIDI interface, but audio output and capture both are\nfunctional. Built 3.17 kernel with this driver on Ubuntu 14.04 & tested with mpg123\nPatch applied to 3.13 Ubuntu kernel works well enough for daily use.\n\nSigned-off-by: Vlad Catoi <vladcatoi@gmail.com>\nAcked-by: Clemens Ladisch <clemens@ladisch.de>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/surkovalex/linux/commits/4148f813c2ef303eb500a6b9a360783c3217e810"},{"sha":"26aca22946dc127ee5f72d031aa6dfe7f1328b44","author":{"email":"627575320a9526cb6c91021c9940202b0e84c416@atmel.com","name":"Ludovic Desroches"},"message":"ARM: at91/PMC: don't forget to write PMC_PCDR register to disable clocks\n\ncommit cfa1950e6c6b72251e80adc736af3c3d2907ab0e upstream.\n\nWhen introducing support for sama5d3, the write to PMC_PCDR register has\nbeen accidentally removed.\n\nReported-by: Nathalie Cyrille <nathalie.cyrille@atmel.com>\nSigned-off-by: Ludovic Desroches <ludovic.desroches@atmel.com>\nSigned-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/surkovalex/linux/commits/26aca22946dc127ee5f72d031aa6dfe7f1328b44"},{"sha":"f52c88e8e124f72eca2dc700c476b2b38f288f28","author":{"email":"0cc5db7488e13b393f245aa6263acec5e92fdcc5@samsung.com","name":"Chao Yu"},"message":"ecryptfs: avoid to access NULL pointer when write metadata in xattr\n\ncommit 35425ea2492175fd39f6116481fe98b2b3ddd4ca upstream.\n\nChristopher Head 2014-06-28 05:26:20 UTC described:\n\"I tried to reproduce this on 3.12.21. Instead, when I do \"echo hello > foo\"\nin an ecryptfs mount with ecryptfs_xattr specified, I get a kernel crash:\n\nBUG: unable to handle kernel NULL pointer dereference at           (null)\nIP: [<ffffffff8110eb39>] fsstack_copy_attr_all+0x2/0x61\nPGD d7840067 PUD b2c3c067 PMD 0\nOops: 0002 [#1] SMP\nModules linked in: nvidia(PO)\nCPU: 3 PID: 3566 Comm: bash Tainted: P           O 3.12.21-gentoo-r1 #2\nHardware name: ASUSTek Computer Inc. G60JX/G60JX, BIOS 206 03/15/2010\ntask: ffff8801948944c0 ti: ffff8800bad70000 task.ti: ffff8800bad70000\nRIP: 0010:[<ffffffff8110eb39>]  [<ffffffff8110eb39>] fsstack_copy_attr_all+0x2/0x61\nRSP: 0018:ffff8800bad71c10  EFLAGS: 00010246\nRAX: 00000000000181a4 RBX: ffff880198648480 RCX: 0000000000000000\nRDX: 0000000000000004 RSI: ffff880172010450 RDI: 0000000000000000\nRBP: ffff880198490e40 R08: 0000000000000000 R09: 0000000000000000\nR10: ffff880172010450 R11: ffffea0002c51e80 R12: 0000000000002000\nR13: 000000000000001a R14: 0000000000000000 R15: ffff880198490e40\nFS:  00007ff224caa700(0000) GS:ffff88019fcc0000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000000 CR3: 00000000bb07f000 CR4: 00000000000007e0\nStack:\nffffffff811826e8 ffff8800a39d8000 0000000000000000 000000000000001a\nffff8800a01d0000 ffff8800a39d8000 ffffffff81185fd5 ffffffff81082c2c\n00000001a39d8000 53d0abbc98490e40 0000000000000037 ffff8800a39d8220\nCall Trace:\n[<ffffffff811826e8>] ? ecryptfs_setxattr+0x40/0x52\n[<ffffffff81185fd5>] ? ecryptfs_write_metadata+0x1b3/0x223\n[<ffffffff81082c2c>] ? should_resched+0x5/0x23\n[<ffffffff8118322b>] ? ecryptfs_initialize_file+0xaf/0xd4\n[<ffffffff81183344>] ? ecryptfs_create+0xf4/0x142\n[<ffffffff810f8c0d>] ? vfs_create+0x48/0x71\n[<ffffffff810f9c86>] ? do_last.isra.68+0x559/0x952\n[<ffffffff810f7ce7>] ? link_path_walk+0xbd/0x458\n[<ffffffff810fa2a3>] ? path_openat+0x224/0x472\n[<ffffffff810fa7bd>] ? do_filp_open+0x2b/0x6f\n[<ffffffff81103606>] ? __alloc_fd+0xd6/0xe7\n[<ffffffff810ee6ab>] ? do_sys_open+0x65/0xe9\n[<ffffffff8157d022>] ? system_call_fastpath+0x16/0x1b\nRIP  [<ffffffff8110eb39>] fsstack_copy_attr_all+0x2/0x61\nRSP <ffff8800bad71c10>\nCR2: 0000000000000000\n---[ end trace df9dba5f1ddb8565 ]---\"\n\nIf we create a file when we mount with ecryptfs_xattr_metadata option, we will\nencounter a crash in this path:\n->ecryptfs_create\n  ->ecryptfs_initialize_file\n    ->ecryptfs_write_metadata\n      ->ecryptfs_write_metadata_to_xattr\n        ->ecryptfs_setxattr\n          ->fsstack_copy_attr_all\nIt's because our dentry->d_inode used in fsstack_copy_attr_all is NULL, and it\nwill be initialized when ecryptfs_initialize_file finish.\n\nSo we should skip copying attr from lower inode when the value of ->d_inode is\ninvalid.\n\nSigned-off-by: Chao Yu <chao2.yu@samsung.com>\nSigned-off-by: Tyler Hicks <tyhicks@canonical.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/surkovalex/linux/commits/f52c88e8e124f72eca2dc700c476b2b38f288f28"},{"sha":"816b571ac0e9eb9700df1ebc99702f9ad04e8607","author":{"email":"4645f7897fd33786a2ee1264d590b3c400559d85@linuxfoundation.org","name":"Greg Kroah-Hartman"},"message":"Linux 3.10.59","distinct":false,"url":"https://api.github.com/repos/surkovalex/linux/commits/816b571ac0e9eb9700df1ebc99702f9ad04e8607"},{"sha":"3ad3add775181f56f51ed14324ed4e7f1c9d3d1e","author":{"email":"6bd3f43fd5b2b5689bccc97f6d09e3eb28307598@rab.in","name":"Rabin Vincent"},"message":"tracing/syscalls: Ignore numbers outside NR_syscalls' range\n\ncommit 086ba77a6db00ed858ff07451bedee197df868c9 upstream.\n\nARM has some private syscalls (for example, set_tls(2)) which lie\noutside the range of NR_syscalls.  If any of these are called while\nsyscall tracing is being performed, out-of-bounds array access will\noccur in the ftrace and perf sys_{enter,exit} handlers.\n\n # trace-cmd record -e raw_syscalls:* true && trace-cmd report\n ...\n true-653   [000]   384.675777: sys_enter:            NR 192 (0, 1000, 3, 4000022, ffffffff, 0)\n true-653   [000]   384.675812: sys_exit:             NR 192 = 1995915264\n true-653   [000]   384.675971: sys_enter:            NR 983045 (76f74480, 76f74000, 76f74b28, 76f74480, 76f76f74, 1)\n true-653   [000]   384.675988: sys_exit:             NR 983045 = 0\n ...\n\n # trace-cmd record -e syscalls:* true\n [   17.289329] Unable to handle kernel paging request at virtual address aaaaaace\n [   17.289590] pgd = 9e71c000\n [   17.289696] [aaaaaace] *pgd=00000000\n [   17.289985] Internal error: Oops: 5 [#1] PREEMPT SMP ARM\n [   17.290169] Modules linked in:\n [   17.290391] CPU: 0 PID: 704 Comm: true Not tainted 3.18.0-rc2+ #21\n [   17.290585] task: 9f4dab00 ti: 9e710000 task.ti: 9e710000\n [   17.290747] PC is at ftrace_syscall_enter+0x48/0x1f8\n [   17.290866] LR is at syscall_trace_enter+0x124/0x184\n\nFix this by ignoring out-of-NR_syscalls-bounds syscall numbers.\n\nCommit cd0980fc8add \"tracing: Check invalid syscall nr while tracing syscalls\"\nadded the check for less than zero, but it should have also checked\nfor greater than NR_syscalls.\n\nLink: http://lkml.kernel.org/p/1414620418-29472-1-git-send-email-rabin@rab.in\n\nFixes: cd0980fc8add \"tracing: Check invalid syscall nr while tracing syscalls\"\nSigned-off-by: Rabin Vincent <rabin@rab.in>\nSigned-off-by: Steven Rostedt <rostedt@goodmis.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/surkovalex/linux/commits/3ad3add775181f56f51ed14324ed4e7f1c9d3d1e"},{"sha":"4449361e6feca3caa91749ad3f8333f9ac5502ab","author":{"email":"1b548d10035ae428195c41f5d55eedb1437ccd8a@resnulli.us","name":"Jiri Pirko"},"message":"ipv4: fix nexthop attlen check in fib_nh_match\n\n[ Upstream commit f76936d07c4eeb36d8dbb64ebd30ab46ff85d9f7 ]\n\nfib_nh_match does not match nexthops correctly. Example:\n\nip route add 172.16.10/24 nexthop via 192.168.122.12 dev eth0 \\\n                          nexthop via 192.168.122.13 dev eth0\nip route del 172.16.10/24 nexthop via 192.168.122.14 dev eth0 \\\n                          nexthop via 192.168.122.15 dev eth0\n\nDel command is successful and route is removed. After this patch\napplied, the route is correctly matched and result is:\nRTNETLINK answers: No such process\n\nPlease consider this for stable trees as well.\n\nFixes: 4e902c57417c4 (\"[IPv4]: FIB configuration using struct fib_config\")\nSigned-off-by: Jiri Pirko <jiri@resnulli.us>\nAcked-by: Eric Dumazet <edumazet@google.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/surkovalex/linux/commits/4449361e6feca3caa91749ad3f8333f9ac5502ab"},{"sha":"9744aac69371ecac7ac6bef8a7a4a65d4e949dfa","author":{"email":"b99cd88b367a456ee0285b35cf353cd9429a32d5@primordial.ca","name":"Ian Morgan"},"message":"ax88179_178a: fix bonding failure\n\n[ Upstream commit 95ff88688781db2f64042e69bd499e518bbb36e5 ]\n\nThe following patch fixes a bug which causes the ax88179_178a driver to be\nincapable of being added to a bond.\n\nWhen I brought up the issue with the bonding maintainers, they indicated\nthat the real problem was with the NIC driver which must return zero for\nsuccess (of setting the MAC address). I see that several other NIC drivers\nfollow that pattern by either simply always returing zero, or by passing\nthrough a negative (error) result while rewriting any positive return code\nto zero. With that same philisophy applied to the ax88179_178a driver, it\nallows it to work correctly with the bonding driver.\n\nI believe this is suitable for queuing in -stable, as it's a small, simple,\nand obvious fix that corrects a defect with no other known workaround.\n\nThis patch is against vanilla 3.17(.0).\n\nSigned-off-by: Ian Morgan <imorgan@primordial.ca>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/surkovalex/linux/commits/9744aac69371ecac7ac6bef8a7a4a65d4e949dfa"},{"sha":"9a8955adfba0821f5b354d400303436b6e4b2e13","author":{"email":"92a5505f10e70d6be04c6ea75cda66fdd7decf37@parallels.com","name":"Vasily Averin"},"message":"ipv4: dst_entry leak in ip_send_unicast_reply()\n\n[ Upstream commit 4062090e3e5caaf55bed4523a69f26c3265cc1d2 ]\n\nip_setup_cork() called inside ip_append_data() steals dst entry from rt to cork\nand in case errors in __ip_append_data() nobody frees stolen dst entry\n\nFixes: 2e77d89b2fa8 (\"net: avoid a pair of dst_hold()/dst_release() in ip_append_data()\")\nSigned-off-by: Vasily Averin <vvs@parallels.com>\nAcked-by: Eric Dumazet <edumazet@google.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/surkovalex/linux/commits/9a8955adfba0821f5b354d400303436b6e4b2e13"},{"sha":"f6ca437d7c4e250e454ed29e0e66d47fdc430d1d","author":{"email":"73675debcd8a436be48ec22211dcf44fe0df0a64@decadent.org.uk","name":"Ben Hutchings"},"message":"drivers/net: macvtap and tun depend on INET\n\n[ Upstream commit de11b0e8c569b96c2cf6a811e3805b7aeef498a3 ]\n\nThese drivers now call ipv6_proxy_select_ident(), which is defined\nonly if CONFIG_INET is enabled.  However, they have really depended\non CONFIG_INET for as long as they have allowed sending GSO packets\nfrom userland.\n\nReported-by: kbuild test robot <fengguang.wu@intel.com>\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>\nFixes: f43798c27684 (\"tun: Allow GSO using virtio_net_hdr\")\nFixes: b9fb9ee07e67 (\"macvtap: add GSO/csum offload support\")\nFixes: 5188cd44c55d (\"drivers/net, ipv6: Select IPv6 fragment idents for virtio UFO packets\")\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/surkovalex/linux/commits/f6ca437d7c4e250e454ed29e0e66d47fdc430d1d"}]}