{"push_id":637295879,"size":45,"distinct_size":0,"ref":"refs/heads/grsec-stable2","head":"3cdece969e37debb1c9b7e2e667f2d0222099de1","before":"e5c635ac169b5cce766b0d4047443c71fd38fdf6","commits":[{"sha":"f858097eb8433b0c28ceaca8e992b338fb392772","author":{"email":"51909cde9c974b33f1f2fb15bb7fd44a1b667281@canonical.com","name":"Hui Wang"},"message":"ALSA: hda - Add one more node in the EAPD supporting candidate list\n\ncommit af95b41426e0b58279f8ff0ebe420df49a4e96b8 upstream.\n\nWe have a HP machine which use the codec node 0x17 connecting the\ninternal speaker, and from the node capability, we saw the EAPD,\nif we don't set the EAPD on for this node, the internal speaker\ncan't output any sound.\n\nBugLink: https://bugs.launchpad.net/bugs/1436745\nSigned-off-by: Hui Wang <hui.wang@canonical.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/linux-scraping/linux-grsecurity/commits/f858097eb8433b0c28ceaca8e992b338fb392772"},{"sha":"6a8bc76409acd4bc64250f43f974d4e6463a39fa","author":{"email":"9dbf5f200e3e3b93daa933e81c0863fd5447a596@gmail.com","name":"Dmitry M. Fedin"},"message":"ALSA: usb - Creative USB X-Fi Pro SB1095 volume knob support\n\ncommit 3dc8523fa7412e731441c01fb33f003eb3cfece1 upstream.\n\nAdds an entry for Creative USB X-Fi to the rc_config array in\nmixer_quirks.c to allow use of volume knob on the device.\nAdds support for newer X-Fi Pro card, known as \"Model No. SB1095\"\nwith USB ID \"041e:3237\"\n\nSigned-off-by: Dmitry M. Fedin <dmitry.fedin@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/linux-scraping/linux-grsecurity/commits/6a8bc76409acd4bc64250f43f974d4e6463a39fa"},{"sha":"328927c7aaf8d7743ccd1f0df514155ff46af694","author":{"email":"f9c437feeb6aa4c634d1401f9d6bbc3a81a20705@realtek.com","name":"Kailang Yang"},"message":"ALSA: hda/realtek - Make more stable to get pin sense for ALC283\n\ncommit a59d7199f62b8336570972dcc288321d0ec999fe upstream.\n\nPin sense will active when power pin is wake up.\nPower pin will not wake up immediately during resume state.\nAdd some delay to wait for power pin activated.\n\nSigned-off-by: Kailang Yang <kailang@realtek.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/linux-scraping/linux-grsecurity/commits/328927c7aaf8d7743ccd1f0df514155ff46af694"},{"sha":"613adacd18f72858ccf92aed9ce0735b14dc25c5","author":{"email":"4596b3305151c7ee743192a95d394341e3d3b644@suse.de","name":"Takashi Iwai"},"message":"ALSA: hda - Fix headphone pin config for Lifebook T731\n\ncommit cc7016ab1a22fb26f388c2fb2b692b89897cbc3e upstream.\n\nSome BIOS version of Fujitsu Lifebook T731 seems to set up the\nheadphone pin (0x21) without the assoc number 0x0f while it's set only\nto the output on the docking port (0x1a).  With the recent commit\n[03ad6a8c93b6: ALSA: hda - Fix \"PCM\" name being used on one DAC when\n there are two DACs], this resulted in the weird mixer element\nmapping where the headphone on the laptop is assigned as a shared\nvolume with the speaker and the docking port is assigned as an\nindividual headphone.\n\nThis patch improves the situation by correcting the headphone pin\nconfig to the more appropriate value.\n\nReported-and-tested-by: Taylor Smock <smocktaylor@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/linux-scraping/linux-grsecurity/commits/613adacd18f72858ccf92aed9ce0735b14dc25c5"},{"sha":"2a4188fdc3846b89f2ee85fcd64ca708d9fa96be","author":{"email":"ba324ca7b1c77fc20bb970d5aff6eea9377918a5@rasmusvillemoes.dk","name":"Rasmus Villemoes"},"message":"PCI/AER: Avoid info leak in __print_tlp_header()\n\ncommit a1b7f2f6367944d445c6853035830a35c6343939 upstream.\n\nCommit fab4c256a58b (\"PCI/AER: Add a TLP header print helper\") introduced\nthe helper function __print_tlp_header(), but contrary to the intention,\nthe behaviour did change: Since we're taking the address of the parameter\nt, the first 4 or 8 bytes printed will be the value of the pointer t\nitself, and the remaining 12 or 8 bytes will be who-knows-what (something\nfrom the stack).\n\nWe want to show the values of the four members of the struct\naer_header_log_regs; that can be done without ugly and error-prone casts.\nOn little-endian this should produce the same output as originally\nintended, and since no-one has complained about getting garbage output so\nfar, I think big-endian should be ok too.\n\nFixes: fab4c256a58b (\"PCI/AER: Add a TLP header print helper\")\nSigned-off-by: Rasmus Villemoes <linux@rasmusvillemoes.dk>\nSigned-off-by: Bjorn Helgaas <bhelgaas@google.com>\nAcked-by: Borislav Petkov <bp@suse.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/2a4188fdc3846b89f2ee85fcd64ca708d9fa96be"},{"sha":"4188b15dbacf9d21b3308d3c5d798b20a459e9a7","author":{"email":"af669d95a4c0de051445d4cafdbb2c5c4a2838be@synopsys.com","name":"Vineet Gupta"},"message":"ARC: SA_SIGINFO ucontext regs off-by-one\n\ncommit 6914e1e3f63caa829431160f0f7093292daef2d5 upstream.\n\nThe regfile provided to SA_SIGINFO signal handler as ucontext was off by\none due to pt_regs gutter cleanups in 2013.\n\nBefore handling signal, user pt_regs are copied onto user_regs_struct and copied\nback later. Both structs are binary compatible. This was all fine until\ncommit 2fa919045b72 (ARC: pt_regs update #2) which removed the empty stack slot\nat top of pt_regs (corresponding to first pad) and made the corresponding\nfixup in struct user_regs_struct (the pad in there was moved out of\n@scratch - not removed altogether as it is part of ptrace ABI)\n\n struct user_regs_struct {\n+       long pad;\n        struct {\n-               long pad;\n                long bta, lp_start, lp_end,....\n        } scratch;\n ...\n }\n\nThis meant that now user_regs_struct was off by 1 reg w.r.t pt_regs and\nsignal code needs to user_regs_struct.scratch to reflect it as pt_regs,\nwhich is what this commit does.\n\nThis problem was hidden for 2 years, because both save/restore, despite\nusing wrong location, were using the same location. Only an interim\ninspection (reproducer below) exposed the issue.\n\n     void handle_segv(int signo, siginfo_t *info, void *context)\n     {\n \tucontext_t *uc = context;\n\tstruct user_regs_struct *regs = &(uc->uc_mcontext.regs);\n\n\tprintf(\"regs %x %x\\n\",               <=== prints 7 8 (vs. 8 9)\n               regs->scratch.r8, regs->scratch.r9);\n     }\n\n     int main()\n     {\n\tstruct sigaction sa;\n\n\tsa.sa_sigaction = handle_segv;\n\tsa.sa_flags = SA_SIGINFO;\n\tsigemptyset(&sa.sa_mask);\n\tsigaction(SIGSEGV, &sa, NULL);\n\n\tasm volatile(\n\t\"mov\tr7, 7\t\\n\"\n\t\"mov\tr8, 8\t\\n\"\n\t\"mov\tr9, 9\t\\n\"\n\t\"mov\tr10, 10\t\\n\"\n\t:::\"r7\",\"r8\",\"r9\",\"r10\");\n\n\t*((unsigned int*)0x10) = 0;\n     }\n\nFixes: 2fa919045b72ec892e \"ARC: pt_regs update #2: Remove unused gutter at start of pt_regs\"\nSigned-off-by: Vineet Gupta <vgupta@synopsys.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/4188b15dbacf9d21b3308d3c5d798b20a459e9a7"},{"sha":"93aad6489861adb737296b48c9f4484ab7b04b7c","author":{"email":"16a9a54ddf4259952e3c118c763138e83693d7fd@perches.com","name":"Joe Perches"},"message":"selinux: fix sel_write_enforce broken return value\n\ncommit 6436a123a147db51a0b06024a8350f4c230e73ff upstream.\n\nReturn a negative error value like the rest of the entries in this function.\n\nSigned-off-by: Joe Perches <joe@perches.com>\nAcked-by:  Stephen Smalley <sds@tycho.nsa.gov>\n[PM: tweaked subject line]\nSigned-off-by: Paul Moore <pmoore@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/93aad6489861adb737296b48c9f4484ab7b04b7c"},{"sha":"79ea2bfc7d9cac1949bec2cb09b622becb7d54b6","author":{"email":"73675debcd8a436be48ec22211dcf44fe0df0a64@decadent.org.uk","name":"Ben Hutchings"},"message":"tcp: Fix crash in TCP Fast Open\n\nCommit 355a901e6cf1 (\"tcp: make connect() mem charging friendly\")\nchanged tcp_send_syn_data() to perform an open-coded copy of the 'syn'\nskb rather than using skb_copy_expand().\n\nThe open-coded copy does not cover the skb_shared_info::gso_segs\nfield, so in the new skb it is left set to 0.  When this commit was\nbackported into stable branches between 3.10.y and 3.16.7-ckty\ninclusive, it triggered the BUG() in tcp_transmit_skb().\n\nSince Linux 3.18 the GSO segment count is kept in the\ntcp_skb_cb::tcp_gso_segs field and tcp_send_syn_data() does copy the\ntcp_skb_cb structure to the new skb, so mainline and newer stable\nbranches are not affected.\n\nSet skb_shared_info::gso_segs to the correct value of 1.\n\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>\nAcked-by: Eric Dumazet <edumazet@google.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/79ea2bfc7d9cac1949bec2cb09b622becb7d54b6"},{"sha":"5ab0f4da798ac88c2f320806b872212cabbc7f5d","author":{"email":"a2ce9d316ca04d17b520237d2846a218b8284e52@suse.cz","name":"David Sterba"},"message":"btrfs: simplify insert_orphan_item\n\ncommit 9c4f61f01d269815bb7c37be3ede59c5587747c6 upstream.\n\nWe can search and add the orphan item in one go,\nbtrfs_insert_orphan_item will find out if the item already exists.\n\nSigned-off-by: David Sterba <dsterba@suse.cz>\nCc: Chris Mason <clm@fb.com>\nCc: Roman Mamedov <rm@romanrm.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/5ab0f4da798ac88c2f320806b872212cabbc7f5d"},{"sha":"485d37770f43e476566ec83c8059c81989a86301","author":{"email":"3ca62a2ad87376be2697209a1770e1afdbbba220@dev.mellanox.co.il","name":"Eli Cohen"},"message":"IB/core: Avoid leakage from kernel to user space\n\ncommit 377b513485fd885dea1083a9a5430df65b35e048 upstream.\n\nClear the reserved field of struct ib_uverbs_async_event_desc which is\ncopied to user space.\n\nSigned-off-by: Eli Cohen <eli@mellanox.com>\nReviewed-by: Yann Droneaud <ydroneaud@opteya.com>\nSigned-off-by: Roland Dreier <roland@purestorage.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/485d37770f43e476566ec83c8059c81989a86301"},{"sha":"f40fc98d0b046ba153442b3bfd7887437f2ebd30","author":{"email":"6b41bc22832538725abdc962fdc02083b44a8dd9@mellanox.com","name":"Shachar Raindel"},"message":"IB/uverbs: Prevent integer overflow in ib_umem_get address arithmetic\n\ncommit 8494057ab5e40df590ef6ef7d66324d3ae33356b upstream.\n\nProperly verify that the resulting page aligned end address is larger\nthan both the start address and the length of the memory area requested.\n\nBoth the start and length arguments for ib_umem_get are controlled by\nthe user. A misbehaving user can provide values which will cause an\ninteger overflow when calculating the page aligned end address.\n\nThis overflow can cause also miscalculation of the number of pages\nmapped, and additional logic issues.\n\nAddresses: CVE-2014-8159\nSigned-off-by: Shachar Raindel <raindel@mellanox.com>\nSigned-off-by: Jack Morgenstein <jackm@mellanox.com>\nSigned-off-by: Or Gerlitz <ogerlitz@mellanox.com>\nSigned-off-by: Roland Dreier <roland@purestorage.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/f40fc98d0b046ba153442b3bfd7887437f2ebd30"},{"sha":"98163132369d94dbd1d6268d7f549342fa6c4e7a","author":{"email":"643a80aaf16a8332d6a70921c14d4bb265446494@intel.com","name":"Emmanuel Grumbach"},"message":"iwlwifi: dvm: run INIT firmware again upon .start()\n\ncommit 9c8928f5176766bec79f272bd47b7124e11cccbd upstream.\n\nThe assumption before this patch was that we don't need to\nrun again the INIT firmware after the system booted. The\nINIT firmware runs calibrations which impact the physical\nlayer's behavior.\nUsers reported that it may be helpful to run these\ncalibrations again every time the interface is brought up.\nThe penatly is minimal, since the calibrations run fast.\nThis fixes:\nhttps://bugzilla.kernel.org/show_bug.cgi?id=94341\n\nSigned-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/98163132369d94dbd1d6268d7f549342fa6c4e7a"},{"sha":"95d7ade78a9dc90b71396d1ddb9da403e03418f2","author":{"email":"551ae05ce198473af5b9da594240f54df5f81e31@gmail.com","name":"Sudip Mukherjee"},"message":"nbd: fix possible memory leak\n\ncommit ff6b8090e26ef7649ef0cc6b42389141ef48b0cf upstream.\n\nwe have already allocated memory for nbd_dev, but we were not\nreleasing that memory and just returning the error value.\n\nSigned-off-by: Sudip Mukherjee <sudip@vectorindia.org>\nAcked-by: Paul Clements <Paul.Clements@SteelEye.com>\nSigned-off-by: Markus Pargmann <mpa@pengutronix.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/95d7ade78a9dc90b71396d1ddb9da403e03418f2"},{"sha":"4c605b1d706cff4c4c43e1d0712d19478ef880ab","author":{"email":"9eae2d327ddc4c2ff66f290d0aa6288f14fc5928@cn.fujitsu.com","name":"Gu Zheng"},"message":"mm/memory hotplug: postpone the reset of obsolete pgdat\n\ncommit b0dc3a342af36f95a68fe229b8f0f73552c5ca08 upstream.\n\nQiu Xishi reported the following BUG when testing hot-add/hot-remove node under\nstress condition:\n\n  BUG: unable to handle kernel paging request at 0000000000025f60\n  IP: next_online_pgdat+0x1/0x50\n  PGD 0\n  Oops: 0000 [#1] SMP\n  ACPI: Device does not support D3cold\n  Modules linked in: fuse nls_iso8859_1 nls_cp437 vfat fat loop dm_mod coretemp mperf crc32c_intel ghash_clmulni_intel aesni_intel ablk_helper cryptd lrw gf128mul glue_helper aes_x86_64 pcspkr microcode igb dca i2c_algo_bit ipv6 megaraid_sas iTCO_wdt i2c_i801 i2c_core iTCO_vendor_support tg3 sg hwmon ptp lpc_ich pps_core mfd_core acpi_pad rtc_cmos button ext3 jbd mbcache sd_mod crc_t10dif scsi_dh_alua scsi_dh_rdac scsi_dh_hp_sw scsi_dh_emc scsi_dh ahci libahci libata scsi_mod [last unloaded: rasf]\n  CPU: 23 PID: 238 Comm: kworker/23:1 Tainted: G           O 3.10.15-5885-euler0302 #1\n  Hardware name: HUAWEI TECHNOLOGIES CO.,LTD. Huawei N1/Huawei N1, BIOS V100R001 03/02/2015\n  Workqueue: events vmstat_update\n  task: ffffa800d32c0000 ti: ffffa800d32ae000 task.ti: ffffa800d32ae000\n  RIP: 0010: next_online_pgdat+0x1/0x50\n  RSP: 0018:ffffa800d32afce8  EFLAGS: 00010286\n  RAX: 0000000000001440 RBX: ffffffff81da53b8 RCX: 0000000000000082\n  RDX: 0000000000000000 RSI: 0000000000000082 RDI: 0000000000000000\n  RBP: ffffa800d32afd28 R08: ffffffff81c93bfc R09: ffffffff81cbdc96\n  R10: 00000000000040ec R11: 00000000000000a0 R12: ffffa800fffb3440\n  R13: ffffa800d32afd38 R14: 0000000000000017 R15: ffffa800e6616800\n  FS:  0000000000000000(0000) GS:ffffa800e6600000(0000) knlGS:0000000000000000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 0000000000025f60 CR3: 0000000001a0b000 CR4: 00000000001407e0\n  DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n  DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n  Call Trace:\n    refresh_cpu_vm_stats+0xd0/0x140\n    vmstat_update+0x11/0x50\n    process_one_work+0x194/0x3d0\n    worker_thread+0x12b/0x410\n    kthread+0xc6/0xd0\n    ret_from_fork+0x7c/0xb0\n\nThe cause is the \"memset(pgdat, 0, sizeof(*pgdat))\" at the end of\ntry_offline_node, which will reset all the content of pgdat to 0, as the\npgdat is accessed lock-free, so that the users still using the pgdat\nwill panic, such as the vmstat_update routine.\n\nprocess A:\t\t\t\toffline node XX:\n\nvmstat_updat()\n   refresh_cpu_vm_stats()\n     for_each_populated_zone()\n       find online node XX\n     cond_resched()\n\t\t\t\t\toffline cpu and memory, then try_offline_node()\n\t\t\t\t\tnode_set_offline(nid), and memset(pgdat, 0, sizeof(*pgdat))\n       zone = next_zone(zone)\n         pg_data_t *pgdat = zone->zone_pgdat;  // here pgdat is NULL now\n           next_online_pgdat(pgdat)\n             next_online_node(pgdat->node_id);  // NULL pointer access\n\nSo the solution here is postponing the reset of obsolete pgdat from\ntry_offline_node() to hotadd_new_pgdat(), and just resetting\npgdat->nr_zones and pgdat->classzone_idx to be 0 rather than the memset\n0 to avoid breaking pointer information in pgdat.\n\nSigned-off-by: Gu Zheng <guz.fnst@cn.fujitsu.com>\nReported-by: Xishi Qiu <qiuxishi@huawei.com>\nSuggested-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>\nCc: David Rientjes <rientjes@google.com>\nCc: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>\nCc: Taku Izumi <izumi.taku@jp.fujitsu.com>\nCc: Tang Chen <tangchen@cn.fujitsu.com>\nCc: Xie XiuQi <xiexiuqi@huawei.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/linux-scraping/linux-grsecurity/commits/4c605b1d706cff4c4c43e1d0712d19478ef880ab"},{"sha":"da715490285d40afb34148891a2b720043633ad8","author":{"email":"760e7dab2836853c63805033e514668301fa9c47@peloton-tech.com","name":"Brian Silverman"},"message":"sched: Fix RLIMIT_RTTIME when PI-boosting to RT\n\ncommit 746db9443ea57fd9c059f62c4bfbf41cf224fe13 upstream.\n\nWhen non-realtime tasks get priority-inheritance boosted to a realtime\nscheduling class, RLIMIT_RTTIME starts to apply to them. However, the\ncounter used for checking this (the same one used for SCHED_RR\ntimeslices) was not getting reset. This meant that tasks running with a\nnon-realtime scheduling class which are repeatedly boosted to a realtime\none, but never block while they are running realtime, eventually hit the\ntimeout without ever running for a time over the limit. This patch\nresets the realtime timeslice counter when un-PI-boosting from an RT to\na non-RT scheduling class.\n\nI have some test code with two threads and a shared PTHREAD_PRIO_INHERIT\nmutex which induces priority boosting and spins while boosted that gets\nkilled by a SIGXCPU on non-fixed kernels but doesn't with this patch\napplied. It happens much faster with a CONFIG_PREEMPT_RT kernel, and\ndoes happen eventually with PREEMPT_VOLUNTARY kernels.\n\nSigned-off-by: Brian Silverman <brian@peloton-tech.com>\nSigned-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nCc: austin@peloton-tech.com\nLink: http://lkml.kernel.org/r/1424305436-6716-1-git-send-email-brian@peloton-tech.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/da715490285d40afb34148891a2b720043633ad8"},{"sha":"d8b274f40cb5cf5ef5cd18f9830a60233011b631","author":{"email":"546b05909706652891a87f7bfe385ae147f61f91@kernel.org","name":"Tejun Heo"},"message":"writeback: add missing INITIAL_JIFFIES init in global_update_bandwidth()\n\ncommit 7d70e15480c0450d2bfafaad338a32e884fc215e upstream.\n\nglobal_update_bandwidth() uses static variable update_time as the\ntimestamp for the last update but forgets to initialize it to\nINITIALIZE_JIFFIES.\n\nThis means that global_dirty_limit will be 5 mins into the future on\n32bit and some large amount jiffies into the past on 64bit.  This\nisn't critical as the only effect is that global_dirty_limit won't be\nupdated for the first 5 mins after booting on 32bit machines,\nespecially given the auxiliary nature of global_dirty_limit's role -\nprotecting against global dirty threshold's sudden dips; however, it\ndoes lead to unintended suboptimal behavior.  Fix it.\n\nFixes: c42843f2f0bb (\"writeback: introduce smoothed global dirty limit\")\nSigned-off-by: Tejun Heo <tj@kernel.org>\nAcked-by: Jan Kara <jack@suse.cz>\nCc: Wu Fengguang <fengguang.wu@intel.com>\nCc: Jens Axboe <axboe@kernel.dk>\nSigned-off-by: Jens Axboe <axboe@fb.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/d8b274f40cb5cf5ef5cd18f9830a60233011b631"},{"sha":"fbcec5461485e43b7a3324aa06b5a22e1b872e41","author":{"email":"546b05909706652891a87f7bfe385ae147f61f91@kernel.org","name":"Tejun Heo"},"message":"writeback: fix possible underflow in write bandwidth calculation\n\ncommit c72efb658f7c8b27ca3d0efb5cfd5ded9fcac89e upstream.\n\nFrom 1ebf33901ecc75d9496862dceb1ef0377980587c Mon Sep 17 00:00:00 2001\nFrom: Tejun Heo <tj@kernel.org>\nDate: Mon, 23 Mar 2015 00:08:19 -0400\n\n2f800fbd777b (\"writeback: fix dirtied pages accounting on redirty\")\nintroduced account_page_redirty() which reverts stat updates for a\nredirtied page, making BDI_DIRTIED no longer monotonically increasing.\n\nbdi_update_write_bandwidth() uses the delta in BDI_DIRTIED as the\nbasis for bandwidth calculation.  While unlikely, since the above\npatch, the newer value may be lower than the recorded past value and\nunderflow the bandwidth calculation leading to a wild result.\n\nFix it by subtracing min of the old and new values when calculating\ndelta.  AFAIK, there hasn't been any report of it happening but the\nresulting erratic behavior would be non-critical and temporary, so\nit's possible that the issue is happening without being reported.  The\nrisk of the fix is very low, so tagged for -stable.\n\nSigned-off-by: Tejun Heo <tj@kernel.org>\nCc: Jens Axboe <axboe@kernel.dk>\nCc: Jan Kara <jack@suse.cz>\nCc: Wu Fengguang <fengguang.wu@intel.com>\nCc: Greg Thelen <gthelen@google.com>\nFixes: 2f800fbd777b (\"writeback: fix dirtied pages accounting on redirty\")\nSigned-off-by: Jens Axboe <axboe@fb.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/fbcec5461485e43b7a3324aa06b5a22e1b872e41"},{"sha":"76a1444b9961eca2697f4b121a40e76b70e87a82","author":{"email":"fe08d3c717adf2ae63592e4c9aec6e3e404d8e3e@davemloft.net","name":"David Miller"},"message":"radeon: Do not directly dereference pointers to BIOS area.\n\ncommit f2c9e560b406f2f6b14b345c7da33467dee9cdf2 upstream.\n\nUse readb() and memcpy_fromio() accessors instead.\n\nReviewed-by: Christian König <christian.koenig@amd.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Alex Deucher <alexander.deucher@amd.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/76a1444b9961eca2697f4b121a40e76b70e87a82"},{"sha":"fd4ce47308e2987035ddc3293757914b2dcff2a4","author":{"email":"8172f793ca553050868d487fd13b508d19cae503@cardoe.com","name":"Doug Goldstein"},"message":"USB: ftdi_sio: Added custom PID for Synapse Wireless product\n\ncommit 4899c054a90439477b24da8977db8d738376fe90 upstream.\n\nSynapse Wireless uses the FTDI VID with a custom PID of 0x9090 for their\nSNAP Stick 200 product.\n\nSigned-off-by: Doug Goldstein <cardoe@cardoe.com>\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/fd4ce47308e2987035ddc3293757914b2dcff2a4"},{"sha":"244f310987d1764dfdf890b43c13b883dada745d","author":{"email":"8172f793ca553050868d487fd13b508d19cae503@cardoe.com","name":"Doug Goldstein"},"message":"USB: ftdi_sio: Use jtag quirk for SNAP Connect E10\n\ncommit b229a0f840f774d29d8fedbf5deb344ca36b7f1a upstream.\n\nThis patch uses the existing CALAO Systems ftdi_8u2232c_probe in order\nto avoid attaching a TTY to the JTAG port as this board is based on the\nCALAO Systems reference design and needs the same fix up.\n\nSigned-off-by: Doug Goldstein <cardoe@cardoe.com>\n[johan: clean up probe logic ]\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/linux-scraping/linux-grsecurity/commits/244f310987d1764dfdf890b43c13b883dada745d"}]}