https://github.com/raspberrypi/linux

sort by:
Revision Author Date Message Commit Date
8f768c5 Merge pull request #506 from jfasch/rpi-3.11.y-fix-gpio_to_irq Please pull: NEED_MACH_GPIO_H vs. gpio_to_irq() woes 19 January 2014, 19:15:56 UTC
c0066b2 Revert "bcm2708: fix gpio_to_irq() name clash" This reverts commit e59870081d5f6af31e77078dec77a8343daddb47. Conflicts: arch/arm/mach-bcm2708/bcm2708_gpio.c 19 January 2014, 17:12:00 UTC
71397e1 gpio: support low and high level interrupts 10 January 2014, 15:55:52 UTC
e598700 bcm2708: fix gpio_to_irq() name clash <mach/gpio.h> has gpio_to_irq() defined as a macro. the macro is obviously intended as the direct implementation of that functionality. unfortunately the gpio subsystem offers a public function of the same name through <linux/gpio.h>. one has to be very careful to include <mach/gpio.h> before <linux/gpio.h> - otherwise the code will compile but only work by chance. board code will certainly not work - the gpio driver is simply not loaded at that time. fix the clash by renaming the offending macros from <mach/gpio.h>, together with their uses. 10 January 2014, 15:55:40 UTC
639f74a config: Enable V4L / MMAL driver 05 December 2013, 16:35:46 UTC
6e34d39 bcm2835: add v4l2 camera device - Supports raw YUV capture, preview, JPEG and H264. - Uses videobuf2 for data transfer, using dma_buf. - Uses 3.6.10 timestamping - Camera power based on use - Uses immutable input mode on video encoder Signed-off-by: Daniel Stone <daniels@collabora.com> Signed-off-by: Luke Diamand <luked@broadcom.com> 05 December 2013, 16:35:29 UTC
e77224a vchiq: export additional symbols Signed-off-by: Daniel Stone <daniels@collabora.com> 05 December 2013, 16:35:22 UTC
c41d62b vchiq: fix the shim message release Signed-off-by: Daniel Stone <daniels@collabora.com> 05 December 2013, 16:35:11 UTC
9ae4464 vchiq: create_pagelist copes with vmalloc memory Signed-off-by: Daniel Stone <daniels@collabora.com> 05 December 2013, 16:35:05 UTC
5044f91 lirc_rpi: Don't register with lirc_dev if we can't claim gpio pins Currently the lirc_rpi module always registers a new lirc device. In case the gpio pins can't be claimed it exits without unregistering. Skip registering with lirc_dev if pins can't be claimed. Also, don't free gpio pins that we haven't claimed. 30 November 2013, 17:05:06 UTC
4f8569e lirc_rpi: Fix return from incompatible pointer type warnings 30 November 2013, 17:05:03 UTC
3735a8f dwc_otg: Don't issue traffic to LS devices in FS mode Issuing low-speed packets when the root port is in full-speed mode causes the root port to stop responding. Explicitly fail when enqueuing URBs to a LS endpoint on a FS bus. 30 November 2013, 16:42:29 UTC
8470b50 dwc_otg: Fix for occasional lockup on boot when doing a USB reset 30 November 2013, 16:42:28 UTC
7b92b68 dwc_otg: Enable NAK holdoff for control split transactions Certain low-speed devices take a very long time to complete a data or status stage of a control transaction, producing NAK responses until they complete internal processing - the USB2.0 spec limit is up to 500mS. This causes the same type of interrupt storm as seen with USB-serial dongles prior to c8edb238. In certain circumstances, usually while booting, this interrupt storm could cause SD card timeouts. 30 November 2013, 16:42:27 UTC
6711f1f Add Ubiquiti WifiStation USB id to ath9k wifi driver 30 November 2013, 16:42:25 UTC
55c5079 Support for cheap Ralink 3070 WiFi plug See: https://github.com/raspberrypi/linux/pull/321 30 November 2013, 16:42:24 UTC
e2d4c1c dwc_otg: prevent leaking URBs during enqueue A dwc_otg_urb would get leaked if the HCD enqueue function failed for any reason. Free the URB at the appropriate points. 30 November 2013, 16:42:23 UTC
5ae62fe dwc_otg: prevent crashes on host port disconnects Fix several issues resulting in crashes or inconsistent state if a Model A root port was disconnected. - Clean up queue heads properly in kill_urbs_in_qh_list by removing the empty QHs from the schedule lists - Set the halt status properly to prevent IRQ handlers from using freed memory - Add fiq_split related cleanup for saved registers - Make microframe scheduling reclaim host channels if active during a disconnect - Abort URBs with -ESHUTDOWN status response, informing device drivers so they respond in a more correct fashion and don't try to resubmit URBs - Prevent IRQ handlers from attempting to handle channel interrupts if the associated URB was dequeued (and the driver state was cleared) 30 November 2013, 16:42:21 UTC
f631155 dwc_otg: make fiq_split_enable imply fiq_fix_enable Failing to set up the FIQ correctly would result in "IRQ 32: nobody cared" errors in dmesg. 30 November 2013, 16:42:20 UTC
1d4c3cf dwc_otg: fix potential sleep while atomic during urb enqueue Fixes a regression introduced with eb1b482a. Kmalloc called from dwc_otg_hcd_qtd_add / dwc_otg_hcd_qtd_create did not always have the GPF_ATOMIC flag set. Force this flag when inside the larger critical section. 30 November 2013, 16:42:19 UTC
9b40a4c dwc_otg: fiq_split: use TTs with more granularity This fixes certain issues with split transaction scheduling. - Isochronous multi-packet OUT transactions now hog the TT until they are completed - this prevents hubs aborting transactions if they get a periodic start-split out-of-order - Don't perform TT allocation on non-periodic endpoints - this allows simultaneous use of the TT's bulk/control and periodic transaction buffers This commit will mainly affect USB audio playback. 30 November 2013, 16:42:17 UTC
a2c3bdb dwc_otg: make channel halts with unknown state less damaging If the IRQ received a channel halt interrupt through the FIQ with no other bits set, the IRQ would not release the host channel and never complete the URB. Add catchall handling to treat as a transaction error and retry. 30 November 2013, 16:42:16 UTC
e6268bc dwc_otg: prevent BUG() in TT allocation if hub address is > 16 A fixed-size array is used to track TT allocation. This was previously set to 16 which caused a crash because dwc_otg_hcd_allocate_port would read past the end of the array. This was hit if a hub was plugged in which enumerated as addr > 16, due to previous device resets or unplugs. Also add #ifdef FIQ_DEBUG around hcd->hub_port_alloc[], which grows to a large size if 128 hub addresses are supported. This field is for debug only for tracking which frame an allocate happened in. 30 November 2013, 16:42:15 UTC
307ebcc dwc_otg: prevent OOPSes during device disconnects The dwc_otg_urb_enqueue function is thread-unsafe. In particular the access of urb->hcpriv, usb_hcd_link_urb_to_ep, dwc_otg_urb->qtd and friends does not occur within a critical section and so if a device was unplugged during activity there was a high chance that the usbcore hub_thread would try to disable the endpoint with partially- formed entries in the URB queue. This would result in BUG() or null pointer dereferences. Fix so that access of urb->hcpriv, enqueuing to the hardware and adding to usbcore endpoint URB lists is contained within a single critical section. 30 November 2013, 16:42:13 UTC
3e2bdfa dwc_otg: whitespace cleanup in dwc_otg_urb_enqueue 30 November 2013, 16:42:12 UTC
6a111e5 Fix function tracing 30 November 2013, 16:42:11 UTC
017f185 dwc_otg: fiq: prevent FIQ thrash and incorrect state passing to IRQ In the case of a transaction to a device that had previously aborted due to an error, several interrupts are enabled to reset the error count when a device responds. This has the side-effect of making the FIQ thrash because the hardware will generate multiple instances of a NAK on an IN bulk/interrupt endpoint and multiple instances of ACK on an OUT bulk/interrupt endpoint. Make the FIQ mask and clear the associated interrupts. Additionally, on non-split transactions make sure that only unmasked interrupts are cleared. This caused a hard-to-trigger but serious race condition when you had the combination of an endpoint awaiting error recovery and a transaction completed on an endpoint - due to the sequencing and timing of interrupts generated by the dwc_otg core, it was possible to confuse the IRQ handler. 30 November 2013, 16:42:09 UTC
a58fb16 dwc_otg: mask correct interrupts after transaction error recovery The dwc_otg driver will unmask certain interrupts on a transaction that previously halted in the error state in order to reset the QTD error count. The various fine-grained interrupt handlers do not consider that other interrupts besides themselves were unmasked. By disabling the two other interrupts only ever enabled in DMA mode for this purpose, we can avoid unnecessary function calls in the IRQ handler. This will also prevent an unneccesary FIQ interrupt from being generated if the FIQ is enabled. 30 November 2013, 16:42:08 UTC
678e241 dcw_otg: avoid logging function that can cause panics See: https://github.com/raspberrypi/firmware/issues/21 Thanks to cleverca22 for fix 30 November 2013, 16:42:07 UTC
28398ff sdhci-bcm2807: Increase sync_after_dma timeout The current timeout is being hit with some cards that complete successfully with a longer timeout. The timeout is not handled well, and is believed to be a code path that causes corruption. 872a8ff suggests that crappy cards can take up to 3 seconds to respond 30 November 2013, 16:42:06 UTC
98ddedc Fix for deprecated/undefined create_proc_entry in RTL8192cu driver 30 November 2013, 16:42:04 UTC
dcc9fd2 dwc_otg: fix device attributes and avoid kernel warnings on boot 30 November 2013, 16:42:03 UTC
5cdfd00 USB fix using a FIQ to implement split transactions This commit adds a FIQ implementaion that schedules the split transactions using a FIQ so we don't get held off by the interrupt latency of Linux 30 November 2013, 16:42:02 UTC
aa0fb96 dwc_otg: Call usb_hcd_unlink_urb_from_ep with lock held in completion handler usb_hcd_unlink_urb_from_ep must be called with the HCD lock held. Calling it asynchronously in the tasklet was not safe (regression in c4564d4a1a0a9b10d4419e48239f5d99e88d2667). This change unlinks it from the endpoint prior to queueing it for handling in the tasklet, and also adds a check to ensure the urb is OK to be unlinked before doing so. NULL pointer dereference kernel oopses had been observed in usb_hcd_giveback_urb when a USB device was unplugged/replugged during data transfer. This effect was reproduced using automated USB port power control, hundreds of replug events were performed during active transfers to confirm that the problem was eliminated. 30 November 2013, 16:42:00 UTC
d4cd602 bcm2708_fb: DMA acceleration for fb_copyarea Based on http://www.raspberrypi.org/phpBB3/viewtopic.php?p=62425#p62425 Also used Simon's dmaer_master module as a reference for tweaking DMA settings for better performance. For now busylooping only. IRQ support might be added later. With non-overclocked Raspberry Pi, the performance is ~360 MB/s for simple copy or ~260 MB/s for two-pass copy (used when dragging windows to the right). In the case of using DMA channel 0, the performance improves to ~440 MB/s. For comparison, VFP optimized CPU copy can only do ~114 MB/s in the same conditions (hindered by reading uncached source buffer). Signed-off-by: Siarhei Siamashka <siarhei.siamashka@gmail.com> 30 November 2013, 16:41:59 UTC
7648617 fbdev: add FBIOCOPYAREA ioctl Based on the patch authored by Ali Gholami Rudi at https://lkml.org/lkml/2009/7/13/153 Provide an ioctl for userspace applications, but only if this operation is hardware accelerated (otherwide it does not make any sense). Signed-off-by: Siarhei Siamashka <siarhei.siamashka@gmail.com> 30 November 2013, 16:41:58 UTC
8bda66c Speed up console framebuffer imageblit function Especially on platforms with a slower CPU but a relatively high framebuffer fill bandwidth, like current ARM devices, the existing console monochrome imageblit function used to draw console text is suboptimal for common pixel depths such as 16bpp and 32bpp. The existing code is quite general and can deal with several pixel depths. By creating special case functions for 16bpp and 32bpp, by far the most common pixel formats used on modern systems, a significant speed-up is attained which can be readily felt on ARM-based devices like the Raspberry Pi and the Allwinner platform, but should help any platform using the fb layer. The special case functions allow constant folding, eliminating a number of instructions including divide operations, and allow the use of an unrolled loop, eliminating instructions with a variable shift size, reducing source memory access instructions, and eliminating excessive branching. These unrolled loops also allow much better code optimization by the C compiler. The code that selects which optimized variant is used is also simplified, eliminating integer divide instructions. The speed-up, measured by timing 'cat file.txt' in the console, varies between 40% and 70%, when testing on the Raspberry Pi and Allwinner ARM-based platforms, depending on font size and the pixel depth, with the greater benefit for 32bpp. Signed-off-by: Harm Hanemaaijer <fgenfb@yahoo.com> 30 November 2013, 16:41:56 UTC
14f37b3 rtl8192cu: select required config options to allow builds without other wifi modules. Thanks UrsusArctos 30 November 2013, 16:41:55 UTC
a3446d4 Add missing ids for Netgear WNA1000N and D-Link Alpha 30 November 2013, 16:41:54 UTC
96ede82 mmc: suppress sdcard warnings we are happy about by default 30 November 2013, 16:41:52 UTC
b8055de Merge pull request #286 from martinezjavier/rpi-3.6.y-dev add mmap support and some cleanups to bcm2835 ALSA driver 30 November 2013, 16:41:51 UTC
b200d06 dwc_otg: fix NAK holdoff and allow on split transactions only This corrects a bug where if a single active non-periodic endpoint had at least one transaction in its qh, on frnum == MAX_FRNUM the qh would get skipped and never get queued again. This would result in a silent device until error detection (automatic or otherwise) would either reset the device or flush and requeue the URBs. Additionally the NAK holdoff was enabled for all transactions - this would potentially stall a HS endpoint for 1ms if a previous error state enabled this interrupt and the next response was a NAK. Fix so that only split transactions get held off. 30 November 2013, 16:41:50 UTC
6e6baa5 Added Device IDs for August DVB-T 205 30 November 2013, 16:41:49 UTC
fbb8034 dwc_otg: implement tasklet for returning URBs to usbcore hcd layer The dwc_otg driver interrupt handler for transfer completion will spend a very long time with interrupts disabled when a URB is completed - this is because usb_hcd_giveback_urb is called from within the handler which for a USB device driver with complicated processing (e.g. webcam) will take an exorbitant amount of time to complete. This results in missed completion interrupts for other USB packets which lead to them being dropped due to microframe overruns. This patch splits returning the URB to the usb hcd layer into a high-priority tasklet. This will have most benefit for isochronous IN transfers but will also have incidental benefit where multiple periodic devices are active at once. 30 November 2013, 16:41:47 UTC
f766294 Add bitbanging pullups, use them for w1-gpio Allows parasite power to work, uses module option pullup=1 30 November 2013, 16:41:46 UTC
a51aa9b dwc_otg: add handling of SPLIT transaction data toggle errors Previously a data toggle error on packets from a USB1.1 device behind a TT would result in the Pi locking up as the driver never handled the associated interrupt. Patch adds basic retry mechanism and interrupt acknowledgement to cater for either a chance toggle error or for devices that have a broken initial toggle state (FT8U232/FT232BM). 30 November 2013, 16:41:45 UTC
fd41760 dwc_otg: fix potential use-after-free case in interrupt handler If a transaction had previously aborted, certain interrupts are enabled to track error counts and reset where necessary. On IN endpoints the host generates an ACK interrupt near-simultaneously with completion of transfer. In the case where this transfer had previously had an error, this results in a use-after-free on the QTD memory space with a 1-byte length being overwritten to 0x00. 30 November 2013, 16:41:43 UTC
32d0cf4 Add retry on error and tidy of temperature driver 30 November 2013, 16:41:42 UTC
ed1c6eb Added inverted transmitter support 30 November 2013, 16:41:41 UTC
daa0033 dwc_otg: Fix incorrect URB allocation error handling If the memory allocation for a dwc_otg_urb failed, the kernel would OOPS because for some reason a member of the *unallocated* struct was set to zero. Error handling changed to fail correctly. 30 November 2013, 16:41:39 UTC
acd0b2f dwc_otg: Fix unsafe access of QTD during URB enqueue In dwc_otg_hcd_urb_enqueue during qtd creation, it was possible that the transaction could complete almost immediately after the qtd was assigned to a host channel during URB enqueue, which meant the qtd pointer was no longer valid having been completed and removed. Usually, this resulted in an OOPS during URB submission. By predetermining whether transactions need to be queued or not, this unsafe pointer access is avoided. This bug was only evident on the Pi model A where a device was attached that had no periodic endpoints (e.g. USB pendrive or some wlan devices). 30 November 2013, 16:41:38 UTC
c106e6a Changed wording on logging. Previously, we received errors like this: mmc0: could read SD Status register (SSR) at the 3th attempt A more sensible response is now returned. A typo also fixed in comments. 30 November 2013, 16:41:37 UTC
286394f Add hwrng (hardware random number generator) driver 30 November 2013, 16:41:36 UTC
b7d1d1f dwc_otg: fix bug in dwc_otg_hcd.c resulting in silent kernel memory corruption, escalating to OOPS under high USB load. 30 November 2013, 16:41:34 UTC
6319075 Default to dwc_otp.lpm_enable=0 30 November 2013, 16:41:33 UTC
0778fdd lirc: added support for RaspberryPi GPIO 30 November 2013, 16:41:32 UTC
9f4f0b7 Add Simon Hall's dma helper module, useful in future for X acceleration 30 November 2013, 16:41:31 UTC
5fa498b Make sure we wait for the reset to finish 30 November 2013, 16:41:29 UTC
8537659 Lazy CRC quirk: Implemented retrying mechanisms for SD SSR and SCR, disabled missing_status and spurious CRC ACMD51 quirks by default (should be fixed by the retrying-mechanishm) 30 November 2013, 16:41:28 UTC
38d795c Allow the number of cycles delay between sdcard peripheral writes to be specified on command line with sdhci-bcm2708.cycle_delay 30 November 2013, 16:41:27 UTC
3088383 Enable multiple ALSA channels 30 November 2013, 16:41:25 UTC
2c6acfd Added hwmon/thermal driver for reporting core temperature. Thanks Dorian 30 November 2013, 16:41:24 UTC
895f4ea Add NAK holdoff scheme. Enabled by default, disable with dwc_otg.nak_holdoff_enable=0. Thanks gsh 30 November 2013, 16:41:23 UTC
9def74a config: add missing options from 3.6.y kernel 30 November 2013, 16:41:21 UTC
2a73080 Add cpufreq driver 30 November 2013, 16:41:20 UTC
9599a47 Avoid dynamic memory allocation for channel lock in USB driver. Thanks ddv2005. 30 November 2013, 16:41:18 UTC
7992c1c Add device ID (330d) 30 November 2013, 16:41:17 UTC
4c00936 Add non-mainline source for rtl8192cu wireless driver version 3.4.4_4749 as this is widely used. Disabled older rtlwifi driver 30 November 2013, 16:41:15 UTC
d0b3d83 Add FIQ patch to dwc_otg driver. Enable with dwc_otg.fiq_fix_enable=1. Should give about 10% more ARM performance. Thanks to Gordon and Costas 30 November 2013, 16:41:14 UTC
77c249f Add low-latency mode to sdcard driver. Disable with sdhci-bcm2708.enable_llm=0. Thanks ddv2005. 30 November 2013, 16:41:12 UTC
5c35145 enabling the realtime clock 1-wire chip DS1307 and 1-wire on GPIO4 (as a module) 30 November 2013, 16:41:11 UTC
6cdb9e4 Fix spinlock recursion in sdhci-bcm2708.c 30 November 2013, 16:41:10 UTC
dfcfd01 Add module parameter for missing_status quirk. sdhci-bcm2708.missing_status=0 may improve interrupt latency 30 November 2013, 16:41:08 UTC
ff21c01 sdhci-bcm2708: use multiblock-type transfers for single blocks There are issues with both single block reads (missed completion) and writes (data loss in some cases!). Just don't do single block transfers anymore, and treat them like multiblock transfers. This adds a quirk for this and uses it. 30 November 2013, 16:41:07 UTC
1fe6122 sdhci-bcm2708: use extension FIFO to buffer DMA transfers The additional FIFO might speed up transfers in some cases. 30 November 2013, 16:41:05 UTC
28c35b4 Add sync_after_dma module parameter 30 November 2013, 16:41:04 UTC
f5e893a Add Chris Boot's i2c and spi drivers. 30 November 2013, 16:41:03 UTC
79af05b Use ndelay rather than udelay. Thanks lb 30 November 2013, 16:41:02 UTC
79067bc sdhci-bcm2708: raise DMA sync timeout Commit d64b84c by accident reduced the maximum overall DMA sync timeout. The maximum overall timeout was reduced from 100ms to 30ms, which isn't enough for many cards. Increase it to 150ms, just to be extra safe. According to commit 872a8ff in the MMC subsystem, some cards require crazy long timeouts (3s), but as we're busy-waiting, and shouldn't delay for such a long time, let's hope 150ms will be enough for most cards. 30 November 2013, 16:41:00 UTC
1b2799f Allow emmc clock to be specified as command line parameter 30 November 2013, 16:40:59 UTC
b61f1da sdhci-bcm2708: assume 50 MHz eMMC clock 80 MHz clock isnt't suited well to be dividable to get SD clocks of 25 MHz (default mode) or 50 MHz (high speed mode). 50 MHz are perfect to drive the SD interface at ideal frequencies. 30 November 2013, 16:40:57 UTC
66be34f sdhci-bcm2708: add allow_highspeed parameter Add a parameter to disable high-speed mode for the few cards that still might have problems. High-speed mode is enabled by default. 30 November 2013, 16:40:56 UTC
d83d876 sdhci-bcm2708: add additional quirks Some additional quirks are needed for correct operation. There's no SDHCI capabilities register documented, and it always reads zero, so add SDHCI_QUIRK_MISSING_CAPS. Apparently SDHCI_QUIRK_NO_HISPD_BIT is needed for many cards to work correctly in high-speed mode, so add it as well. 30 November 2013, 16:40:55 UTC
b919096 sdhci-bcm2708: remove custom clock handling The custom clock handling code is redundant and buggy. The MMC/SDHCI subsystem does a better job than it, so remove it for good. 30 November 2013, 16:40:53 UTC
71d7990 sdhci-bcm2708: speed up DMA sync Experiments show that it doesn't really take that long to sync, so we can reduce the poll interval slightly. Might improve performance a bit. 30 November 2013, 16:40:52 UTC
27e2e27 sdcard patch improvements from naren 30 November 2013, 16:40:51 UTC
d623b3e possible fix for sdcard missing status. Thank naren 30 November 2013, 16:40:49 UTC
15a947b Allow mac address to be set in smsc95xx Signed-off-by: popcornmix <popcornmix@gmail.com> 30 November 2013, 16:40:48 UTC
ada51e9 bcm2708: alsa sound driver Signed-off-by: popcornmix <popcornmix@gmail.com> 30 November 2013, 16:40:47 UTC
52c91da cma: Add vc_cma driver to enable use of CMA Signed-off-by: popcornmix <popcornmix@gmail.com> 30 November 2013, 16:40:45 UTC
327abc7 bcm2708 vchiq driver Signed-off-by: popcornmix <popcornmix@gmail.com> 30 November 2013, 16:40:44 UTC
bcd5205 bcm2708 framebuffer driver Signed-off-by: popcornmix <popcornmix@gmail.com> 30 November 2013, 16:40:43 UTC
df1d40e bcm2708 watchdog driver Signed-off-by: popcornmix <popcornmix@gmail.com> 30 November 2013, 16:40:41 UTC
de8d084 Add dwc_otg driver Signed-off-by: popcornmix <popcornmix@gmail.com> 30 November 2013, 16:40:40 UTC
38d421e Add quick config. This is designed for quick compiling when developing. No modules are needed and it includes all Pi specific drivers 30 November 2013, 16:40:39 UTC
468387e Main bcm2708 linux port Signed-off-by: popcornmix <popcornmix@gmail.com> 30 November 2013, 16:40:37 UTC
5ee54f3 Linux 3.11.10 29 November 2013, 18:42:37 UTC
4004afd exec/ptrace: fix get_dumpable() incorrect tests commit d049f74f2dbe71354d43d393ac3a188947811348 upstream. The get_dumpable() return value is not boolean. Most users of the function actually want to be testing for non-SUID_DUMP_USER(1) rather than SUID_DUMP_DISABLE(0). The SUID_DUMP_ROOT(2) is also considered a protected state. Almost all places did this correctly, excepting the two places fixed in this patch. Wrong logic: if (dumpable == SUID_DUMP_DISABLE) { /* be protective */ } or if (dumpable == 0) { /* be protective */ } or if (!dumpable) { /* be protective */ } Correct logic: if (dumpable != SUID_DUMP_USER) { /* be protective */ } or if (dumpable != 1) { /* be protective */ } Without this patch, if the system had set the sysctl fs/suid_dumpable=2, a user was able to ptrace attach to processes that had dropped privileges to that user. (This may have been partially mitigated if Yama was enabled.) The macros have been moved into the file that declares get/set_dumpable(), which means things like the ia64 code can see them too. CVE-2013-2929 Reported-by: Vasily Kulikov <segoon@openwall.com> Signed-off-by: Kees Cook <keescook@chromium.org> Cc: "Luck, Tony" <tony.luck@intel.com> Cc: Oleg Nesterov <oleg@redhat.com> Cc: "Eric W. Biederman" <ebiederm@xmission.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 29 November 2013, 18:42:17 UTC
4d29088 Revert "ima: policy for RAMFS" commit 08de59eb144d7c41351a467442f898d720f0f15f upstream. This reverts commit 4c2c392763a682354fac65b6a569adec4e4b5387. Everything in the initramfs should be measured and appraised, but until the initramfs has extended attribute support, at least measured. Signed-off-by: Mimi Zohar <zohar@us.ibm.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 29 November 2013, 18:42:16 UTC
ca23559 Bluetooth: revert: "Bluetooth: Add missing reset_resume dev_pm_ops" commit b1a8014471b01dd862de9f91bbbff1296afac42d upstream. Many btusb devices have 2 modes, a hid mode and a bluetooth hci mode. These devices default to hid mode for BIOS use. This means that after having been reset they will revert to HID mode, and are no longer usable as a HCI. Therefor it is a very bad idea to just blindly make reset_resume point to the regular resume handler. Note that the btusb driver has no clue how to switch these devices from hid to hci mode, this is done in userspace through udev rules, so the proper way to deal with this is to not have a reset-resume handler and instead let the usb-system re-enumerate the device, and re-run the udev rules. I must also note, that the commit message for the commit causing this problem has a very weak motivation for the change: "Add missing reset_resume dev_pm_ops. Missing reset_resume results in the following message after power management device test. This change sets reset_resume to btusb_resume(). [ 2506.936134] btusb 1-1.5:1.0: no reset_resume for driver btusb? [ 2506.936137] btusb 1-1.5:1.1: no reset_resume for driver btusb?" Making a change solely to silence a warning while also changing important behavior (normal resume handling versus re-enumeration) requires a commit message with a proper explanation why it is safe to do so, which clearly lacks here, and unsurprisingly it turns out to not be safe to make this change. Reverting the commit in question fixes bt no longer working on my Dell E6430 after a suspend/resume, and I believe it likely also fixes the following bugs: https://bugzilla.redhat.com/show_bug.cgi?id=988481 https://bugzilla.redhat.com/show_bug.cgi?id=1010649 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213239 This reverts commit 502f769662978a2fe99d0caed5e53e3006107381. Cc: Shuah Khan <shuah.kh@samsung.com> Cc: Gustavo Padovan <gustavo.padovan@collabora.co.uk> Signed-off-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 29 November 2013, 18:42:16 UTC
back to top