-
Notifications
You must be signed in to change notification settings - Fork 53.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
e906c090ca17ed30ed0e826df3c4d095e5f5c865 #51
Commits on Aug 4, 2013
-
usb: dwc3: fix wrong bit mask in dwc3_event_type
commit 1974d49 upstream. Per dwc3 2.50a spec, the is_devspec bit is used to distinguish the Device Endpoint-Specific Event or Device-Specific Event (DEVT). If the bit is 1, the event is represented Device-Specific Event, then use [7:1] bits as Device Specific Event to marked the type. It has 7 bits, and we can see the reserved8_31 variable name which means from 8 to 31 bits marked reserved, actually there are 24 bits not 25 bits between that. And 1 + 7 + 24 = 32, the event size is 4 byes. So in dwc3_event_type, the bit mask should be: is_devspec [0] 1 bit type [7:1] 7 bits reserved8_31 [31:8] 24 bits This patch should be backported to kernels as old as 3.2, that contain the commit 72246da "usb: Introduce DesignWare USB3 DRD Driver". Signed-off-by: Huang Rui <ray.huang@amd.com> Signed-off-by: Felipe Balbi <balbi@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 76d54f0 - Browse repository at this point
Copy the full SHA 76d54f0View commit details -
usb: dwc3: gadget: don't prevent gadget from being probed if we fail
commit cdcedd6 upstream. In case we fail our ->udc_start() callback, we should be ready to accept another modprobe following the failed one. We had forgotten to clear dwc->gadget_driver back to NULL and, because of that, we were preventing gadget driver modprobe from being retried. Signed-off-by: Felipe Balbi <balbi@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 1b5c94b - Browse repository at this point
Copy the full SHA 1b5c94bView commit details -
USB: ti_usb_3410_5052: fix dynamic-id matching
commit 1fad564 upstream. The driver failed to take the dynamic ids into account when determining the device type and therefore all devices were detected as 2-port devices when using the dynamic-id interface. Match on the usb-serial-driver field instead of doing redundant id-table searches. Reported-by: Anders Hammarquist <iko@iko.pp.se> Signed-off-by: Johan Hovold <jhovold@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 9f510a8 - Browse repository at this point
Copy the full SHA 9f510a8View commit details -
USB: misc: Add Manhattan Hi-Speed USB DVI Converter to sisusbvga
commit 58fc90d upstream. Signed-off-by: Jóhann B. Guðmundsson <johannbg@fedoraproject.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 06b1905 - Browse repository at this point
Copy the full SHA 06b1905View commit details -
usb: Clear both buffers when clearing a control transfer TT buffer.
commit 2c7b871 upstream. Control transfers have both IN and OUT (or SETUP) packets, so when clearing TT buffers for a control transfer it's necessary to send two HUB_CLEAR_TT_BUFFER requests to the hub. Signed-off-by: William Gulland <wgulland@google.com> Acked-by: Alan Stern <stern@rowland.harvard.edu> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 9e91498 - Browse repository at this point
Copy the full SHA 9e91498View commit details -
staging: comedi: COMEDI_CANCEL ioctl should wake up read/write
commit 69acbaa upstream. Comedi devices can do blocking read() or write() (or poll()) if an asynchronous command has been set up, blocking for data (for read()) or buffer space (for write()). Various events associated with the asynchronous command will wake up the blocked reader or writer (or poller). It is also possible to force the asynchronous command to terminate by issuing a `COMEDI_CANCEL` ioctl. That shuts down the asynchronous command, but does not currently wake up the blocked reader or writer (or poller). If the blocked task could be woken up, it would see that the command is no longer active and return. The caller of the `COMEDI_CANCEL` ioctl could attempt to wake up the blocked task by sending a signal, but that's a nasty workaround. Change `do_cancel_ioctl()` to wake up the wait queue after it returns from `do_cancel()`. `do_cancel()` can propagate an error return value from the low-level comedi driver's cancel routine, but it always shuts the command down regardless, so `do_cancel_ioctl()` can wake up he wait queue regardless of the return value from `do_cancel()`. Signed-off-by: Ian Abbott <abbotti@mev.co.uk> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for cf63fbd - Browse repository at this point
Copy the full SHA cf63fbdView commit details -
Btrfs: fix lock leak when resuming snapshot deletion
commit fec386a upstream. We aren't setting path->locks[level] when we resume a snapshot deletion which means we won't unlock the buffer when we free the path. This causes deadlocks if we happen to re-allocate the block before we've evicted the extent buffer from cache. Thanks, Reported-by: Alex Lyakas <alex.btrfs@zadarastorage.com> Signed-off-by: Josef Bacik <jbacik@fusionio.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 849f48a - Browse repository at this point
Copy the full SHA 849f48aView commit details -
Btrfs: re-add root to dead root list if we stop dropping it
commit d29a9f6 upstream. If we stop dropping a root for whatever reason we need to add it back to the dead root list so that we will re-start the dropping next transaction commit. The other case this happens is if we recover a drop because we will add a root without adding it to the fs radix tree, so we can leak it's root and commit root extent buffer, adding this to the dead root list makes this cleanup happen. Thanks, Reported-by: Alex Lyakas <alex.btrfs@zadarastorage.com> Signed-off-by: Josef Bacik <jbacik@fusionio.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for e94d695 - Browse repository at this point
Copy the full SHA e94d695View commit details -
xen/blkback: Check device permissions before allowing OP_DISCARD
commit 604c499 upstream. We need to make sure that the device is not RO or that the request is not past the number of sectors we want to issue the DISCARD operation for. This fixes CVE-2013-2140. Acked-by: Jan Beulich <JBeulich@suse.com> Acked-by: Ian Campbell <Ian.Campbell@citrix.com> [v1: Made it pr_warn instead of pr_debug] Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 8f5a285 - Browse repository at this point
Copy the full SHA 8f5a285View commit details -
ata: Fix DVD not dectected at some platform with Wellsburg PCH
commit eac27f0 upstream. There is a patch b55f84e "ata_piix: Fix DVD not dectected at some Haswell platforms" to fix an issue of DVD not recognized on Haswell Desktop platform with Lynx Point. Recently, it is also found the same issue at some platformas with Wellsburg PCH. So deliver a similar patch to fix it by disables 32bit PIO in IDE mode. Signed-off-by: Youquan Song <youquan.song@intel.com> Signed-off-by: Tejun Heo <tj@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 82627ff - Browse repository at this point
Copy the full SHA 82627ffView commit details -
libata: make it clear that sata_inic162x is experimental
commit bb96961 upstream. sata_inic162x never reached a state where it's reliable enough for production use and data corruption is a relatively common occurrence. Make the driver generate warning about the issues and mark the Kconfig option as experimental. If the situation doesn't improve, we'd be better off making it depend on CONFIG_BROKEN. Let's wait for several cycles and see if the kernel message draws any attention. Signed-off-by: Tejun Heo <tj@kernel.org> Reported-by: Martin Braure de Calignon <braurede@free.fr> Reported-by: Ben Hutchings <ben@decadent.org.uk> Reported-by: risc4all@yahoo.com Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for af5697c - Browse repository at this point
Copy the full SHA af5697cView commit details -
powerpc/modules: Module CRC relocation fix causes perf issues
commit 0e0ed64 upstream. Module CRCs are implemented as absolute symbols that get resolved by a linker script. We build an intermediate .o that contains an unresolved symbol for each CRC. genksysms parses this .o, calculates the CRCs and writes a linker script that "resolves" the symbols to the calculated CRC. Unfortunately the ppc64 relocatable kernel sees these CRCs as symbols that need relocating and relocates them at boot. Commit d4703ae (module: handle ppc64 relocating kcrctabs when CONFIG_RELOCATABLE=y) added a hook to reverse the bogus relocations. Part of this patch created a symbol at 0x0: # head -2 /proc/kallsyms 0000000000000000 T reloc_start c000000000000000 T .__start This reloc_start symbol is causing lots of confusion to perf. It thinks reloc_start is a massive function that stretches from 0x0 to 0xc000000000000000 and we get various cryptic errors out of perf, including: problem incrementing symbol count, skipping event This patch removes the reloc_start linker script label and instead defines it as PHYSICAL_START. We also need to wrap it with CONFIG_PPC64 because the ppc32 kernel can set a non zero PHYSICAL_START at compile time and we wouldn't want to subtract it from the CRCs in that case. Signed-off-by: Anton Blanchard <anton@samba.org> Acked-by: Rusty Russell <rusty@rustcorp.com.au> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for ef445a3 - Browse repository at this point
Copy the full SHA ef445a3View commit details -
ACPI / memhotplug: Fix a stale pointer in error path
commit d19f503 upstream. device->driver_data needs to be cleared when releasing its data, mem_device, in an error path of acpi_memory_device_add(). The function evaluates the _CRS of memory device objects, and fails when it gets an unexpected resource or cannot allocate memory. A kernel crash or data corruption may occur when the kernel accesses the stale pointer. Signed-off-by: Toshi Kani <toshi.kani@hp.com> Reviewed-by: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 5201cbf - Browse repository at this point
Copy the full SHA 5201cbfView commit details -
dm verity: fix inability to use a few specific devices sizes
commit b1bf2de upstream. Fix a boundary condition that caused failure for certain device sizes. The problem is reported at http://code.google.com/p/cryptsetup/issues/detail?id=160 For certain device sizes the number of hashes at a specific level was calculated incorrectly. It happens for example for a device with data and metadata block size 4096 that has 16385 blocks and algorithm sha256. The user can test if he is affected by this bug by running the "veritysetup verify" command and also by activating the dm-verity kernel driver and reading the whole block device. If it passes without an error, then the user is not affected. The condition for the bug is: Split the total number of data blocks (data_block_bits) into bit strings, each string has hash_per_block_bits bits. hash_per_block_bits is rounddown(log2(metadata_block_size/hash_digest_size)). Equivalently, you can say that you convert data_blocks_bits to 2^hash_per_block_bits base. If there some zero bit string below the most significant bit string and at least one bit below this zero bit string is set, then the bug happens. The same bug exists in the userspace veritysetup tool, so you must use fixed veritysetup too if you want to use devices that are affected by this boundary condition. Signed-off-by: Mikulas Patocka <mpatocka@redhat.com> Cc: Milan Broz <gmazyland@gmail.com> Signed-off-by: Alasdair G Kergon <agk@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 0990072 - Browse repository at this point
Copy the full SHA 0990072View commit details -
drm/radeon: fix endian issues with DP handling (v3)
commit 34be8c9 upstream. The atom interpreter expects data in LE format, so swap the message buffer as apprioriate. v2: properly handle non-dw aligned byte counts. v3: properly handle remainder Signed-off-by: Alex Deucher <alexander.deucher@amd.com> Cc: Dong He <hedonghust@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 0322310 - Browse repository at this point
Copy the full SHA 0322310View commit details -
drm/radeon: fix combios tables on older cards
commit cef1d00 upstream. Noticed that my old Radeon 7500 hung after printing drm: GPU not posted. posting now... when it wasn't selected as the primary card the BIOS. Some digging revealed that it was hanging in combios_parse_mmio_table() while parsing the ASIC INIT 3 table. Looking at the BIOS ROM for the card, it becomes obvious that there is no ASIC INIT 3 table in the BIOS. The code is just processing random garbage. No surprise it hangs! Why do I say that there is no ASIC INIT 3 table is the BIOS? This table is found through the MISC INFO table. The MISC INFO table can be found at offset 0x5e in the COMBIOS header. But the header is smaller than that. The COMBIOS header starts at offset 0x126. The standard PCI Data Structure (the bit that starts with 'PCIR') lives at offset 0x180. That means that the COMBIOS header can not be larger than 0x5a bytes and therefore cannot contain a MISC INFO table. I looked at a dozen or so BIOS images, some my own, some downloaded from: <http://www.techpowerup.com/vgabios/index.php?manufacturer=ATI&page=1> It is fairly obvious that the size of the COMBIOS header can be found at offset 0x6 of the header. Not sure if it is a 16-bit number or just an 8-bit number, but that doesn't really matter since the tables seems to be always smaller than 256 bytes. So I think combios_get_table_offset() should check if the requested table is present. This can be done by checking the offset against the size of the header. See the diff below. The diff is against the WIP OpenBSD codebase that roughly corresponds to Linux 3.8.13 at this point. But I don't think this bit of the code changed much since then. For what it is worth: Signed-off-by: Mark Kettenis <kettenis@openbsd.org> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for b076cb4 - Browse repository at this point
Copy the full SHA b076cb4View commit details -
drm/radeon: improve dac adjust heuristics for legacy pdac
commit 03ed8cf upstream. Hopefully avoid more quirks in the future due to bogus vbios dac data. Signed-off-by: Alex Deucher <alexander.deucher@amd.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for e41f203 - Browse repository at this point
Copy the full SHA e41f203View commit details -
drm/radeon/atom: initialize more atom interpretor elements to 0
commit 42a2182 upstream. The ProcessAuxChannel table on some rv635 boards assumes the divmul members are initialized to 0 otherwise we get an invalid fb offset since it has a bad mask set when setting the fb base. While here initialize all the atom interpretor elements to 0. Fixes: https://bugzilla.kernel.org/show_bug.cgi?id=60639 Signed-off-by: Alex Deucher <alexander.deucher@amd.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 1996c98 - Browse repository at this point
Copy the full SHA 1996c98View commit details -
USB: serial: ftdi_sio: add more RT Systems ftdi devices
commit fed1f1e upstream. RT Systems makes many usb serial cables based on the ftdi_sio driver for programming various amateur radios. This patch is a full listing of their current product offerings and should allow these cables to all be recognized. Signed-off-by: Rick Farina (Zero_Chaos) <zerochaos@gentoo.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 428f268 - Browse repository at this point
Copy the full SHA 428f268View commit details -
commit acfec9a upstream. Eric Sandeen has found a nasty livelock in sget() - take a mount(2) about to fail. The superblock is on ->fs_supers, ->s_umount is held exclusive, ->s_active is 1. Along comes two more processes, trying to mount the same thing; sget() in each is picking that superblock, bumping ->s_count and trying to grab ->s_umount. ->s_active is 3 now. Original mount(2) finally gets to deactivate_locked_super() on failure; ->s_active is 2, superblock is still ->fs_supers because shutdown will *not* happen until ->s_active hits 0. ->s_umount is dropped and now we have two processes chasing each other: s_active = 2, A acquired ->s_umount, B blocked A sees that the damn thing is stillborn, does deactivate_locked_super() s_active = 1, A drops ->s_umount, B gets it A restarts the search and finds the same superblock. And bumps it ->s_active. s_active = 2, B holds ->s_umount, A blocked on trying to get it ... and we are in the earlier situation with A and B switched places. The root cause, of course, is that ->s_active should not grow until we'd got MS_BORN. Then failing ->mount() will have deactivate_locked_super() shut the damn thing down. Fortunately, it's easy to do - the key point is that grab_super() is called only for superblocks currently on ->fs_supers, so it can bump ->s_count and grab ->s_umount first, then check MS_BORN and bump ->s_active; we must never increment ->s_count for superblocks past ->kill_sb(), but grab_super() is never called for those. The bug is pretty old; we would've caught it by now, if not for accidental exclusion between sget() for block filesystems; the things like cgroup or e.g. mtd-based filesystems don't have anything of that sort, so they get bitten. The right way to deal with that is obviously to fix sget()... Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 257e1c5 - Browse repository at this point
Copy the full SHA 257e1c5View commit details -
md/raid5: fix interaction of 'replace' and 'recovery'.
commit f94c0b6 upstream. If a device in a RAID4/5/6 is being replaced while another is being recovered, then the writes to the replacement device currently don't happen, resulting in corruption when the replacement completes and the new drive takes over. This is because the replacement writes are only triggered when 's.replacing' is set and not when the similar 's.sync' is set (which is the case during resync and recovery - it means all devices need to be read). So schedule those writes when s.replacing is set as well. In this case we cannot use "STRIPE_INSYNC" to record that the replacement has happened as that is needed for recording that any parity calculation is complete. So introduce STRIPE_REPLACED to record if the replacement has happened. For safety we should also check that STRIPE_COMPUTE_RUN is not set. This has a similar effect to the "s.locked == 0" test. The latter ensure that now IO has been flagged but not started. The former checks if any parity calculation has been flagged by not started. We must wait for both of these to complete before triggering the 'replace'. Add a similar test to the subsequent check for "are we finished yet". This possibly isn't needed (is subsumed in the STRIPE_INSYNC test), but it makes it more obvious that the REPLACE will happen before we think we are finished. Finally if a NeedReplace device is not UPTODATE then that is an error. We really must trigger a warning. This bug was introduced in commit 9a3e110 (md/raid5: detect and handle replacements during recovery.) which introduced replacement for raid5. That was in 3.3-rc3, so any stable kernel since then would benefit from this fix. Reported-by: qindehua <13691222965@163.com> Tested-by: qindehua <qindehua@163.com> Signed-off-by: NeilBrown <neilb@suse.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 0761d07 - Browse repository at this point
Copy the full SHA 0761d07View commit details -
md/raid10: remove use-after-free bug.
commit 0eb25bb upstream. We always need to be careful when calling generic_make_request, as it can start a chain of events which might free something that we are using. Here is one place I wasn't careful enough. If the wbio2 is not in use, then it might get freed at the first generic_make_request call. So perform all necessary tests first. This bug was introduced in 3.3-rc3 (24afd80) and can cause an oops, so fix is suitable for any -stable since then. Signed-off-by: NeilBrown <neilb@suse.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for aa2f8ab - Browse repository at this point
Copy the full SHA aa2f8abView commit details -
xen/evtchn: avoid a deadlock when unbinding an event channel
commit 179fbd5 upstream. Unbinding an event channel (either with the ioctl or when the evtchn device is closed) may deadlock because disable_irq() is called with port_user_lock held which is also locked by the interrupt handler. Think of the IOCTL_EVTCHN_UNBIND is being serviced, the routine has just taken the lock, and an interrupt happens. The evtchn_interrupt is invoked, tries to take the lock and spins forever. A quick glance at the code shows that the spinlock is a local IRQ variant. Unfortunately that does not help as "disable_irq() waits for the interrupt handler on all CPUs to stop running. If the irq occurs on another VCPU, it tries to take port_user_lock and can't because the unbind ioctl is holding it." (from David). Hence we cannot depend on the said spinlock to protect us. We could make it a system wide IRQ disable spinlock but there is a better way. We can piggyback on the fact that the existence of the spinlock is to make get_port_user() checks be up-to-date. And we can alter those checks to not depend on the spin lock (as it's protected by u->bind_mutex in the ioctl) and can remove the unnecessary locking (this is IOCTL_EVTCHN_UNBIND) path. In the interrupt handler we cannot use the mutex, but we do not need it. "The unbind disables the irq before making the port user stale, so when you clear it you are guaranteed that the interrupt handler that might use that port cannot be running." (from David). Hence this patch removes the spinlock usage on the teardown path and piggybacks on disable_irq happening before we muck with the get_port_user() data. This ensures that the interrupt handler will never run on stale data. Signed-off-by: David Vrabel <david.vrabel@citrix.com> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> [v1: Expanded the commit description a bit] Signed-off-by: Jonghwan Choi <jhbird.choi@samsung.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 8924588 - Browse repository at this point
Copy the full SHA 8924588View commit details -
firewire: fix libdc1394/FlyCap2 iso event regression
commit 0699a73 upstream. Commit 18d6271 (firewire: prevent dropping of completed iso packet header data) was intended to be an obvious bug fix, but libdc1394 and FlyCap2 depend on the old behaviour by ignoring all returned information and thus not noticing that not all packets have been received yet. The result was that the video frame buffers would be saved before they contained the correct data. Reintroduce the old behaviour for old clients. Tested-by: Stepan Salenikovich <stepan.salenikovich@gmail.com> Tested-by: Josep Bosch <jep250@gmail.com> Cc: <stable@vger.kernel.org> # 3.4+ Signed-off-by: Clemens Ladisch <clemens@ladisch.de> Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for a90a3ad - Browse repository at this point
Copy the full SHA a90a3adView commit details -
zfcp: status read buffers on first adapter open with link down
commit 9edf7d7 upstream. Commit 64deb6e "[SCSI] zfcp: Use status_read_buf_num provided by FCP channel" started using a value returned by the channel but only evaluated the value if the fabric link is up. Commit 8d88cf3 "[SCSI] zfcp: Update status read mempool" introduced mempool resizings based on the above value. On setting an FCP device online for the very first time since boot, a new zeroed adapter object is allocated. If the link is down, the number of status read requests remains zero. Since just the config data exchange is incomplete, we proceed with adapter open recovery. However, we unconditionally call mempool_resize with adapter->stat_read_buf_num == 0 in this case. This causes a kernel message "kernel BUG at mm/mempool.c:131!" in process "zfcperp<FCP-device-bus-ID>" with last function mempool_resize in Krnl PSW and zfcp_erp_thread in the Call Trace. Don't evaluate channel values which are invalid on link down. The number of status read requests is always valid, evaluated, and set to a positive minimum greater than zero. The adapter open recovery can proceed and the channel has status read buffers to inform us on a future link up event. While we are not aware of any other code path that could result in mempool resize attempts of size zero, we still also initialize the number of status read buffers to be posted to a static minimum number on adapter object allocation. Backported for 3.4-stable. commit a53c8fa since v3.6-rc1 unified copyright messages, e.g: revise such messages 'Copyright IBM Corporation' as 'Copyright IBM Corp', so updated the messages as a53c8fa did. Signed-off-by: Steffen Maier <maier@linux.vnet.ibm.com> Cc: <stable@vger.kernel.org> #2.6.35+ Signed-off-by: James Bottomley <JBottomley@Parallels.com> Signed-off-by: Zhouping Liu <zliu@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 17a9afa - Browse repository at this point
Copy the full SHA 17a9afaView commit details -
s390: move dummy io_remap_pfn_range() to asm/pgtable.h
commit 4f2e290 upstream. Commit b4cbb19 ("vm: add vm_iomap_memory() helper function") added a helper function wrapper around io_remap_pfn_range(), and every other architecture defined it in <asm/pgtable.h>. The s390 choice of <asm/io.h> may make sense, but is not very convenient for this case, and gratuitous differences like that cause unexpected errors like this: mm/memory.c: In function 'vm_iomap_memory': mm/memory.c:2439:2: error: implicit declaration of function 'io_remap_pfn_range' [-Werror=implicit-function-declaration] Glory be the kbuild test robot who noticed this, bisected it, and reported it to the guilty parties (ie me). Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Cc: Martin Schwidefsky <schwidefsky@de.ibm.com> Cc: Heiko Carstens <heiko.carstens@de.ibm.com> [bwh: Backported to 3.2: the macro was not defined, so this is an addition and not a move] Signed-off-by: Ben Hutchings <ben@decadent.org.uk> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for c733e1a - Browse repository at this point
Copy the full SHA c733e1aView commit details -
virtio: support unlocked queue poll
commit cc22988 upstream. This adds a way to check ring empty state after enable_cb outside any locks. Will be used by virtio_net. Note: there's room for more optimization: caller is likely to have a memory barrier already, which means we might be able to get rid of a barrier here. Deferring this optimization until we do some benchmarking. Signed-off-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: David S. Miller <davem@davemloft.net> [wg: Backported to 3.2] Signed-off-by: Wolfram Gloger <wmglo@dent.med.uni-muenchen.de> [bwh: Backported to 3.4: adjust context] Signed-off-by: Ben Hutchings <ben@decadent.org.uk> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 2010fa3 - Browse repository at this point
Copy the full SHA 2010fa3View commit details -
virtio_net: fix race in RX VQ processing
commit cbdadbb upstream virtio net called virtqueue_enable_cq on RX path after napi_complete, so with NAPI_STATE_SCHED clear - outside the implicit napi lock. This violates the requirement to synchronize virtqueue_enable_cq wrt virtqueue_add_buf. In particular, used event can move backwards, causing us to lose interrupts. In a debug build, this can trigger panic within START_USE. Jason Wang reports that he can trigger the races artificially, by adding udelay() in virtqueue_enable_cb() after virtio_mb(). However, we must call napi_complete to clear NAPI_STATE_SCHED before polling the virtqueue for used buffers, otherwise napi_schedule_prep in a callback will fail, causing us to lose RX events. To fix, call virtqueue_enable_cb_prepare with NAPI_STATE_SCHED set (under napi lock), later call virtqueue_poll with NAPI_STATE_SCHED clear (outside the lock). Reported-by: Jason Wang <jasowang@redhat.com> Tested-by: Jason Wang <jasowang@redhat.com> Acked-by: Jason Wang <jasowang@redhat.com> Signed-off-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: David S. Miller <davem@davemloft.net> [wg: Backported to 3.2] Signed-off-by: Wolfram Gloger <wmglo@dent.med.uni-muenchen.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 40a017c - Browse repository at this point
Copy the full SHA 40a017cView commit details -
mm/memory-hotplug: fix lowmem count overflow when offline pages
commit cea27eb upstream. The logic for the memory-remove code fails to correctly account the Total High Memory when a memory block which contains High Memory is offlined as shown in the example below. The following patch fixes it. Before logic memory remove: MemTotal: 7603740 kB MemFree: 6329612 kB Buffers: 94352 kB Cached: 872008 kB SwapCached: 0 kB Active: 626932 kB Inactive: 519216 kB Active(anon): 180776 kB Inactive(anon): 222944 kB Active(file): 446156 kB Inactive(file): 296272 kB Unevictable: 0 kB Mlocked: 0 kB HighTotal: 7294672 kB HighFree: 5704696 kB LowTotal: 309068 kB LowFree: 624916 kB After logic memory remove: MemTotal: 7079452 kB MemFree: 5805976 kB Buffers: 94372 kB Cached: 872000 kB SwapCached: 0 kB Active: 626936 kB Inactive: 519236 kB Active(anon): 180780 kB Inactive(anon): 222944 kB Active(file): 446156 kB Inactive(file): 296292 kB Unevictable: 0 kB Mlocked: 0 kB HighTotal: 7294672 kB HighFree: 5181024 kB LowTotal: 4294752076 kB LowFree: 624952 kB [mhocko@suse.cz: fix CONFIG_HIGHMEM=n build] Signed-off-by: Wanpeng Li <liwanp@linux.vnet.ibm.com> Reviewed-by: Michal Hocko <mhocko@suse.cz> Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> Cc: David Rientjes <rientjes@google.com> Cc: <stable@vger.kernel.org> [2.6.24+] Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Zhouping Liu <zliu@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 19d22ea - Browse repository at this point
Copy the full SHA 19d22eaView commit details -
Configuration menu - View commit details
-
Copy full SHA for 7b17c57 - Browse repository at this point
Copy the full SHA 7b17c57View commit details
Commits on Aug 7, 2013
-
mm: add a field to store names for private anonymous memory
Userspace processes often have multiple allocators that each do anonymous mmaps to get memory. When examining memory usage of individual processes or systems as a whole, it is useful to be able to break down the various heaps that were allocated by each layer and examine their size, RSS, and physical memory usage. This patch adds a user pointer to the shared union in vm_area_struct that points to a null terminated string inside the user process containing a name for the vma. vmas that point to the same address will be merged, but vmas that point to equivalent strings at different addresses will not be merged. Userspace can set the name for a region of memory by calling prctl(PR_SET_VMA, PR_SET_VMA_ANON_NAME, start, len, (unsigned long)name); Setting the name to NULL clears it. The names of named anonymous vmas are shown in /proc/pid/maps as [anon:<name>] and in /proc/pid/smaps in a new "Name" field that is only present for named vmas. If the userspace pointer is no longer valid all or part of the name will be replaced with "<fault>". The idea to store a userspace pointer to reduce the complexity within mm (at the expense of the complexity of reading /proc/pid/mem) came from Dave Hansen. This results in no runtime overhead in the mm subsystem other than comparing the anon_name pointers when considering vma merging. The pointer is stored in a union with fieds that are only used on file-backed mappings, so it does not increase memory usage. Change-Id: Ie2ffc0967d4ffe7ee4c70781313c7b00cf7e3092 Signed-off-by: Colin Cross <ccross@android.com>
Configuration menu - View commit details
-
Copy full SHA for e394997 - Browse repository at this point
Copy the full SHA e394997View commit details
Commits on Aug 11, 2013
-
ALSA: compress: fix the return value for SNDRV_COMPRESS_VERSION
commit a8d3060 upstream. the return value of SNDRV_COMPRESS_VERSION always return default -ENOTTY as the return value was never updated for this call assign return value from put_user() Reported-by: Haynes <hgeorge@codeaurora.org> Signed-off-by: Vinod Koul <vinod.koul@intel.com> Signed-off-by: Takashi Iwai <tiwai@suse.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 353f59c - Browse repository at this point
Copy the full SHA 353f59cView commit details -
serial/mxs-auart: fix race condition in interrupt handler
commit d970d7f upstream. The handler needs to ack the pending events before actually handling them. Otherwise a new event might come in after it it considered non-pending or handled and is acked then without being handled. So this event is only noticed when the next interrupt happens. Without this patch an i.MX28 based machine running an rt-patched kernel regularly hangs during boot. Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for d11699e - Browse repository at this point
Copy the full SHA d11699eView commit details -
serial/mxs-auart: increase time to wait for transmitter to become idle
commit 079a036 upstream. Without this patch the driver waits ~1 ms for the UART to become idle. At 115200n8 this time is (theoretically) enough to transfer 11.5 characters (= 115200 bits/s / (10 Bits/char) * 1ms). As the mxs-auart has a fifo size of 16 characters the clock is gated too early. The problem is worse for lower baud rates. This only happens to really shut down the transmitter in the middle of a transfer if /dev/ttyAPPx isn't opened in userspace (e.g. by a getty) but was at least once (because the bootloader doesn't disable the transmitter). So increase the timeout to 20 ms which should be enough for 9600n8, too. Moreover skip gating the clock if the timeout is elapsed. Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 1775496 - Browse repository at this point
Copy the full SHA 1775496View commit details -
ath9k_htc: do some initial hardware configuration
commit dc2a87f upstream. Currently we configure harwdare and clock, only after interface start. In this case, if we reload module or reboot PC without configuring adapter, firmware will freeze. There is no software way to reset adpter. This patch add initial configuration and set it in disabled state, to avoid this freeze. Behaviour of this patch should be similar to: ifconfig wlan0 up; ifconfig wlan0 down. Bug: qca/open-ath9k-htc-firmware#1 Tested-by: Bo Shi <cnshibo@gmail.com> Signed-off-by: Oleksij Rempel <linux@rempel-privat.de> Signed-off-by: John W. Linville <linville@tuxdriver.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for a73957d - Browse repository at this point
Copy the full SHA a73957dView commit details -
nl80211: fix mgmt tx status and testmode reporting for netns
commit a0ec570 upstream. These two events were sent to the default network namespace. This caused AP mode in a non-default netns to not work correctly. Mgmt tx status was multicasted to a different (default) netns instead of the one the AP was in. Signed-off-by: Michal Kazior <michal.kazior@tieto.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 1053689 - Browse repository at this point
Copy the full SHA 1053689View commit details -
mac80211: fix duplicate retransmission detection
commit 6b0f327 upstream. The duplicate retransmission detection code in mac80211 erroneously attempts to do the check for every frame, even frames that don't have a sequence control field or that don't use it (QoS-Null frames.) This is problematic because it causes the code to access data beyond the end of the SKB and depending on the data there will drop packets erroneously. Correct the code to not do duplicate detection for such frames. I found this error while testing AP powersave, it lead to retransmitted PS-Poll frames being dropped entirely as the data beyond the end of the SKB was always zero. Signed-off-by: Johannes Berg <johannes.berg@intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for cfc9326 - Browse repository at this point
Copy the full SHA cfc9326View commit details -
ixgbe: Fix Tx Hang issue with lldpad on 82598EB
commit 1eb9ac1 upstream. This patch fixes an issue with the 82598EB device, where lldpad is causing Tx Hangs on the card as soon as it attempts to configure DCB for the device. The adapter will continually Tx hang and reset in a loop. Signed-off-by: Jacob Keller <jacob.e.keller@intel.com> Tested-by: Phil Schmitt <phillip.j.schmitt@intel.com> Tested-by: Jack Morgan <jack.morgan@intel.com> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 167ef7a - Browse repository at this point
Copy the full SHA 167ef7aView commit details -
commit e2288b6 upstream. Since we clear QUEUE_STARTED in rt2x00queue_stop_queue(), following call to rt2x00queue_pause_queue() reduce to noop, i.e we do not stop queue in mac80211. To fix that introduce rt2x00queue_pause_queue_nocheck() function, which will stop queue in mac80211 directly. Note that rt2x00_start_queue() explicitly set QUEUE_PAUSED bit. Note also that reordering operations i.e. first call to rt2x00queue_pause_queue() and then clear QUEUE_STARTED bit, will race with rt2x00queue_unpause_queue(), so calling ieee80211_stop_queue() directly is the only available solution to fix the problem without major rework. Signed-off-by: Stanislaw Gruszka <stf_xl@wp.pl> Signed-off-by: John W. Linville <linville@tuxdriver.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for f1b3ecc - Browse repository at this point
Copy the full SHA f1b3eccView commit details -
mwifiex: Add missing endian conversion.
commit 83e612f upstream. Both type and pkt_len variables are in host endian and these should be in Little Endian in the payload. Signed-off-by: Tomasz Moń <desowin@gmail.com> Acked-by: Bing Zhao <bzhao@marvell.com> Signed-off-by: John W. Linville <linville@tuxdriver.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 33f91a1 - Browse repository at this point
Copy the full SHA 33f91a1View commit details -
ACPI / battery: Fix parsing _BIX return value
commit 016d5ba upstream. The _BIX method returns extended battery info as a package. According the ACPI spec (ACPI 5, Section 10.2.2.2), the first member of that package should be "Revision". However, the current ACPI battery driver treats the first member as "Power Unit" which should be the second member. This causes the result of _BIX return data parsing to be incorrect. Fix this by adding a new member called 'revision' to struct acpi_battery and adding the offsetof() information on it to extended_info_offsets[] as the first row. [rjw: Changelog] Reported-and-tested-by: Jan Hoffmann <jan.christian.hoffmann@gmail.com> References: http://bugzilla.kernel.org/show_bug.cgi?id=60519 Signed-off-by: Lan Tianyu <tianyu.lan@intel.com> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for ee9ef03 - Browse repository at this point
Copy the full SHA ee9ef03View commit details -
sched: Fix the broken sched_rr_get_interval()
commit a59f4e0 upstream. The caller of sched_sliced() should pass se.cfs_rq and se as the arguments, however in sched_rr_get_interval() we gave it rq.cfs_rq and se, which made the following computation obviously wrong. The change was introduced by commit: 7703493 sched: fix crash in sys_sched_rr_get_interval() ... 5 years ago, while it had been the correct 'cfs_rq_of' before the commit. The change seems to be irrelevant to the commit msg, which was to return a 0 timeslice for tasks that are on an idle runqueue. So I believe that was just a plain typo. Signed-off-by: Zhu Yanhai <gaoyang.zyh@taobao.com> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Paul Turner <pjt@google.com> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: Steven Rostedt <rostedt@goodmis.org> Cc: Andrew Morton <akpm@linux-foundation.org> Cc: Linus Torvalds <torvalds@linux-foundation.org> Link: http://lkml.kernel.org/r/1357621012-15039-1-git-send-email-gaoyang.zyh@taobao.com [ Since this is an ABI and an old bug, we'll test this via a slow upstream route, to hopefully discover any app breakage. ] Signed-off-by: Ingo Molnar <mingo@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 1836cd1 - Browse repository at this point
Copy the full SHA 1836cd1View commit details -
fanotify: info leak in copy_event_to_user()
commit de1e0c4 upstream. The ->reserved field isn't cleared so we leak one byte of stack information to userspace. Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com> Cc: Eric Paris <eparis@redhat.com> Cc: Al Viro <viro@zeniv.linux.org.uk> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Cc: Luis Henriques <luis.henriques@canonical.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 6c9ef83 - Browse repository at this point
Copy the full SHA 6c9ef83View commit details -
perf: Fix event group context move
commit 0231bb5 upstream. When we have group with mixed events (hw/sw) we want to end up with group leader being in hw context. So if group leader is initialy sw event, we move all the events under hw context. The move is done for each event by removing it from its context and adding it back into proper one. As a part of the removal the event is automatically disabled, which is not what we want at this stage of creating groups. The fix is to initialize event state after removal from sw context. This fix resulted from the following discussion: http://thread.gmane.org/gmane.linux.kernel.perf.user/1144 Reported-by: Andreas Hollmann <hollmann@in.tum.de> Signed-off-by: Jiri Olsa <jolsa@redhat.com> Cc: Arnaldo Carvalho de Melo <acme@redhat.com> Cc: Namhyung Kim <namhyung@kernel.org> Cc: Corey Ashford <cjashfor@linux.vnet.ibm.com> Cc: Frederic Weisbecker <fweisbec@gmail.com> Cc: Paul Mackerras <paulus@samba.org> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl> Cc: Stephane Eranian <eranian@google.com> Cc: Vince Weaver <vince@deater.net> Link: http://lkml.kernel.org/r/1359714225-4231-1-git-send-email-jolsa@redhat.com Signed-off-by: Ingo Molnar <mingo@kernel.org> Cc: Li Zefan <lizefan@huawei.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 5cbff87 - Browse repository at this point
Copy the full SHA 5cbff87View commit details -
x86, fpu: correct the asm constraints for fxsave, unbreak mxcsr.daz
commit eaa5a99 upstream. GCC will optimize mxcsr_feature_mask_init in arch/x86/kernel/i387.c: memset(&fx_scratch, 0, sizeof(struct i387_fxsave_struct)); asm volatile("fxsave %0" : : "m" (fx_scratch)); mask = fx_scratch.mxcsr_mask; if (mask == 0) mask = 0x0000ffbf; to memset(&fx_scratch, 0, sizeof(struct i387_fxsave_struct)); asm volatile("fxsave %0" : : "m" (fx_scratch)); mask = 0x0000ffbf; since asm statement doesn’t say it will update fx_scratch. As the result, the DAZ bit will be cleared. This patch fixes it. This bug dates back to at least kernel 2.6.12. Signed-off-by: H. Peter Anvin <hpa@linux.intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 7f72cb0 - Browse repository at this point
Copy the full SHA 7f72cb0View commit details -
drm/i915: quirk no PCH_PWM_ENABLE for Dell XPS13 backlight
commit e85843b upstream. BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=47941 BugLink: https://bugs.launchpad.net/bugs/1163720 BugLink: https://bugs.launchpad.net/bugs/1162026 Some machines suffer from non-functional backlight controls if BLM_PCH_PWM_ENABLE is set, so provide a quirk to avoid doing so. Apply this quirk to Dell XPS 13 models. [ kamal: backport to 3.4 ] Tested-by: Eric Griffith <EGriffith92@gmail.com> Tested-by: Kent Baxley <kent.baxley@canonical.com> Signed-off-by: Kamal Mostafa <kamal@canonical.com> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for be1932d - Browse repository at this point
Copy the full SHA be1932dView commit details -
perf: Use css_tryget() to avoid propping up css refcount
commit 9c5da09 upstream. An rmdir pushes css's ref count to zero. However, if the associated directory is open at the time, the dentry ref count is non-zero. If the fd for this directory is then passed into perf_event_open, it does a css_get(). This bounces the ref count back up from zero. This is a problem by itself. But what makes it turn into a crash is the fact that we end up doing an extra dput, since we perform a dput when css_put sees the ref count go down to zero. css_tryget() does not fall into that trap. So, we use that instead. Reproduction test-case for the bug: #include <unistd.h> #include <sys/types.h> #include <sys/stat.h> #include <fcntl.h> #include <linux/unistd.h> #include <linux/perf_event.h> #include <string.h> #include <errno.h> #include <stdio.h> #define PERF_FLAG_PID_CGROUP (1U << 2) int perf_event_open(struct perf_event_attr *hw_event_uptr, pid_t pid, int cpu, int group_fd, unsigned long flags) { return syscall(__NR_perf_event_open,hw_event_uptr, pid, cpu, group_fd, flags); } /* * Directly poke at the perf_event bug, since it's proving hard to repro * depending on where in the kernel tree. what moved? */ int main(int argc, char **argv) { int fd; struct perf_event_attr attr; memset(&attr, 0, sizeof(attr)); attr.exclude_kernel = 1; attr.size = sizeof(attr); mkdir("/dev/cgroup/perf_event/blah", 0777); fd = open("/dev/cgroup/perf_event/blah", O_RDONLY); perror("open"); rmdir("/dev/cgroup/perf_event/blah"); sleep(2); perf_event_open(&attr, fd, 0, -1, PERF_FLAG_PID_CGROUP); perror("perf_event_open"); close(fd); return 0; } Signed-off-by: Salman Qazi <sqazi@google.com> Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl> Acked-by: Tejun Heo <tj@kernel.org> Link: http://lkml.kernel.org/r/20120614223108.1025.2503.stgit@dungbeetle.mtv.corp.google.com Signed-off-by: Ingo Molnar <mingo@kernel.org> Cc: Li Zefan <lizefan@huawei.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 2d8be9c - Browse repository at this point
Copy the full SHA 2d8be9cView commit details -
arcnet: cleanup sizeof parameter
[ Upstream commit 087d273 ] This patch doesn't change the compiled code because ARC_HDR_SIZE is 4 and sizeof(int) is 4, but the intent was to use the header size and not the sizeof the header size. Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for c062773 - Browse repository at this point
Copy the full SHA c062773View commit details -
sysctl net: Keep tcp_syn_retries inside the boundary
[ Upstream commit 651e927 ] Limit the min/max value passed to the /proc/sys/net/ipv4/tcp_syn_retries. Signed-off-by: Michal Tesar <mtesar@redhat.com> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for f31dfea - Browse repository at this point
Copy the full SHA f31dfeaView commit details -
sctp: fully initialize sctp_outq in sctp_outq_init
[ Upstream commit c5c7774 ] In commit 2f94aab (refactor sctp_outq_teardown to insure proper re-initalization) we modified sctp_outq_teardown to use sctp_outq_init to fully re-initalize the outq structure. Steve West recently asked me why I removed the q->error = 0 initalization from sctp_outq_teardown. I did so because I was operating under the impression that sctp_outq_init would properly initalize that value for us, but it doesn't. sctp_outq_init operates under the assumption that the outq struct is all 0's (as it is when called from sctp_association_init), but using it in __sctp_outq_teardown violates that assumption. We should do a memset in sctp_outq_init to ensure that the entire structure is in a known state there instead. Signed-off-by: Neil Horman <nhorman@tuxdriver.com> Reported-by: "West, Steve (NSN - US/Fort Worth)" <steve.west@nsn.com> CC: Vlad Yasevich <vyasevich@gmail.com> CC: netdev@vger.kernel.org CC: davem@davemloft.net Acked-by: Vlad Yasevich <vyasevich@gmail.com> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for d9a6f71 - Browse repository at this point
Copy the full SHA d9a6f71View commit details -
ipv6: take rtnl_lock and mark mrt6 table as freed on namespace cleanup
[ Upstream commit 905a6f9 ] Otherwise we end up dereferencing the already freed net->ipv6.mrt pointer which leads to a panic (from Srivatsa S. Bhat): BUG: unable to handle kernel paging request at ffff882018552020 IP: [<ffffffffa0366b02>] ip6mr_sk_done+0x32/0xb0 [ipv6] PGD 290a067 PUD 207ffe0067 PMD 207ff1d067 PTE 8000002018552060 Oops: 0000 [#1] SMP DEBUG_PAGEALLOC Modules linked in: ebtable_nat ebtables nfs fscache nf_conntrack_ipv4 nf_defrag_ipv4 ipt_REJECT xt_CHECKSUM iptable_mangle iptable_filter ip_tables nfsd lockd nfs_acl exportfs auth_rpcgss autofs4 sunrpc 8021q garp bridge stp llc ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter +ip6_tables ipv6 vfat fat vhost_net macvtap macvlan vhost tun kvm_intel kvm uinput iTCO_wdt iTCO_vendor_support cdc_ether usbnet mii microcode i2c_i801 i2c_core lpc_ich mfd_core shpchp ioatdma dca mlx4_core be2net wmi acpi_cpufreq mperf ext4 jbd2 mbcache dm_mirror dm_region_hash dm_log dm_mod CPU: 0 PID: 7 Comm: kworker/u33:0 Not tainted 3.11.0-rc1-ea45e-a #4 Hardware name: IBM -[8737R2A]-/00Y2738, BIOS -[B2E120RUS-1.20]- 11/30/2012 Workqueue: netns cleanup_net task: ffff8810393641c0 ti: ffff881039366000 task.ti: ffff881039366000 RIP: 0010:[<ffffffffa0366b02>] [<ffffffffa0366b02>] ip6mr_sk_done+0x32/0xb0 [ipv6] RSP: 0018:ffff881039367bd8 EFLAGS: 00010286 RAX: ffff881039367fd8 RBX: ffff882018552000 RCX: dead000000200200 RDX: 0000000000000000 RSI: ffff881039367b68 RDI: ffff881039367b68 RBP: ffff881039367bf8 R08: ffff881039367b68 R09: 2222222222222222 R10: 2222222222222222 R11: 2222222222222222 R12: ffff882015a7a040 R13: ffff882014eb89c0 R14: ffff8820289e2800 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff88103fc00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffff882018552020 CR3: 0000000001c0b000 CR4: 00000000000407f0 Stack: ffff881039367c18 ffff882014eb89c0 ffff882015e28c00 0000000000000000 ffff881039367c18 ffffffffa034d9d1 ffff8820289e2800 ffff882014eb89c0 ffff881039367c58 ffffffff815bdecb ffffffff815bddf2 ffff882014eb89c0 Call Trace: [<ffffffffa034d9d1>] rawv6_close+0x21/0x40 [ipv6] [<ffffffff815bdecb>] inet_release+0xfb/0x220 [<ffffffff815bddf2>] ? inet_release+0x22/0x220 [<ffffffffa032686f>] inet6_release+0x3f/0x50 [ipv6] [<ffffffff8151c1d9>] sock_release+0x29/0xa0 [<ffffffff81525520>] sk_release_kernel+0x30/0x70 [<ffffffffa034f14b>] icmpv6_sk_exit+0x3b/0x80 [ipv6] [<ffffffff8152fff9>] ops_exit_list+0x39/0x60 [<ffffffff815306fb>] cleanup_net+0xfb/0x1a0 [<ffffffff81075e3a>] process_one_work+0x1da/0x610 [<ffffffff81075dc9>] ? process_one_work+0x169/0x610 [<ffffffff81076390>] worker_thread+0x120/0x3a0 [<ffffffff81076270>] ? process_one_work+0x610/0x610 [<ffffffff8107da2e>] kthread+0xee/0x100 [<ffffffff8107d940>] ? __init_kthread_worker+0x70/0x70 [<ffffffff8162a99c>] ret_from_fork+0x7c/0xb0 [<ffffffff8107d940>] ? __init_kthread_worker+0x70/0x70 Code: 20 48 89 5d e8 4c 89 65 f0 4c 89 6d f8 66 66 66 66 90 4c 8b 67 30 49 89 fd e8 db 3c 1e e1 49 8b 9c 24 90 08 00 00 48 85 db 74 06 <4c> 39 6b 20 74 20 bb f3 ff ff ff e8 8e 3c 1e e1 89 d8 4c 8b 65 RIP [<ffffffffa0366b02>] ip6mr_sk_done+0x32/0xb0 [ipv6] RSP <ffff881039367bd8> CR2: ffff882018552020 Reported-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com> Tested-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com> Signed-off-by: Hannes Frederic Sowa <hannes@stressinduktion.org> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 8d50892 - Browse repository at this point
Copy the full SHA 8d50892View commit details -
usbnet: do not pretend to support SG/TSO
[ Upstream commit 20f0170 ] usbnet doesn't support yet SG, so drivers should not advertise SG or TSO capabilities, as they allow TCP stack to build large TSO packets that need to be linearized and might use order-5 pages. This adds an extra copy overhead and possible allocation failures. Current code ignore skb_linearize() return code so crashes are even possible. Best is to not pretend SG/TSO is supported, and add this again when/if usbnet really supports SG for devices who could get a performance gain. Based on a prior patch from Freddy Xin <freddy@asix.com.tw> Signed-off-by: Eric Dumazet <edumazet@google.com> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for d8c47c3 - Browse repository at this point
Copy the full SHA d8c47c3View commit details -
net_sched: Fix stack info leak in cbq_dump_wrr().
[ Upstream commit a0db856 ] Make sure the reserved fields, and padding (if any), are fully initialized. Based upon a patch by Dan Carpenter and feedback from Joe Perches. Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 565144e - Browse repository at this point
Copy the full SHA 565144eView commit details -
af_key: more info leaks in pfkey messages
[ Upstream commit ff862a4 ] This is inspired by a5cc68f "af_key: fix info leaks in notify messages". There are some struct members which don't get initialized and could disclose small amounts of private information. Acked-by: Mathias Krause <minipli@googlemail.com> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com> Acked-by: Steffen Klassert <steffen.klassert@secunet.com> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 8e56df2 - Browse repository at this point
Copy the full SHA 8e56df2View commit details -
net_sched: info leak in atm_tc_dump_class()
[ Upstream commit 8cb3b9c ] The "pvc" struct has a hole after pvc.sap_family which is not cleared. Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com> Reviewed-by: Jiri Pirko <jiri@resnulli.us> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for d5c50d2 - Browse repository at this point
Copy the full SHA d5c50d2View commit details -
8139cp: Add dma_mapping_error checking
[ Upstream commit cf3c4c0 ] Self explanitory dma_mapping_error addition to the 8139 driver, based on this: https://bugzilla.redhat.com/show_bug.cgi?id=947250 It showed several backtraces arising for dma_map_* usage without checking the return code on the mapping. Add the check and abort the rx/tx operation if its failed. Untested as I have no hardware and the reporter has wandered off, but seems pretty straightforward. Signed-off-by: Neil Horman <nhorman@tuxdriver.com> CC: "David S. Miller" <davem@davemloft.net> CC: Francois Romieu <romieu@fr.zoreil.com> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 249b3ec - Browse repository at this point
Copy the full SHA 249b3ecView commit details
Commits on Aug 12, 2013
-
Configuration menu - View commit details
-
Copy full SHA for 67e6589 - Browse repository at this point
Copy the full SHA 67e6589View commit details -
net: wireless: bcmdhd: Remove chatty message from wl_cfgp2p_act_frm_s…
…earch Change-Id: I06ffddddf239443f3684f97a5c31b6872c89d769 Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
Dmitry Shmidt committedAug 12, 2013 Configuration menu - View commit details
-
Copy full SHA for 276c1af - Browse repository at this point
Copy the full SHA 276c1afView commit details
Commits on Aug 13, 2013
-
net: ipv6: add missing lock in ping_v6_sendmsg
Bug: 9469865 Change-Id: I5e9db559d22e35d27fa1df948b70c70ed8b42115 Signed-off-by: Lorenzo Colitti <lorenzo@google.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Configuration menu - View commit details
-
Copy full SHA for 3a018d2 - Browse repository at this point
Copy the full SHA 3a018d2View commit details -
net: ipv6: fix wrong ping_v6_sendmsg return value
ping_v6_sendmsg currently returns 0 on success. It should return the number of bytes written instead. Bug: 9469865 Change-Id: I14aad6018f0c3fd92dad315bc3ade04c0b3982e0 Signed-off-by: Lorenzo Colitti <lorenzo@google.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Configuration menu - View commit details
-
Copy full SHA for 5f0fd61 - Browse repository at this point
Copy the full SHA 5f0fd61View commit details
Commits on Aug 14, 2013
-
Input: Propagate hardware event timestamp to evdev.
Convey hardware timestamp associated with the current event packet. The use of these event codes by hardware drivers is optional. Used to reduce jitter and improve velocity tracking in ABS_MT devices. Change-Id: I89f3a958944f6a2979964ee372e61bad448061b6 Signed-off-by: Sasha Levitskiy <sanek@google.com>
Sasha Levitskiy authored and Michael Wright committedAug 14, 2013 Configuration menu - View commit details
-
Copy full SHA for e1c8581 - Browse repository at this point
Copy the full SHA e1c8581View commit details -
ion: chunk_heap: fix leak in allocated counter
buffer->size is controlled by the outer ion layer, don't modify it inside the heap. Instead, compute the rounded up allocated size on demand. Change-Id: I288ffc1221ce96cfe2591468502ac3279065bde4 Signed-off-by: Colin Cross <ccross@android.com>
Configuration menu - View commit details
-
Copy full SHA for cbacc5a - Browse repository at this point
Copy the full SHA cbacc5aView commit details -
ion: add free list size to heap debug files
Change-Id: I3c6309afdbd661a2f870fd1ba3fea9543e229882 Signed-off-by: Colin Cross <ccross@android.com>
Configuration menu - View commit details
-
Copy full SHA for 56334e0 - Browse repository at this point
Copy the full SHA 56334e0View commit details
Commits on Aug 15, 2013
-
SCSI: Don't attempt to send extended INQUIRY command if skip_vpd_page…
…s is set commit 7562523 upstream. If a device has the skip_vpd_pages flag set we should simply fail the scsi_get_vpd_page() call. Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com> Acked-by: Alan Stern <stern@rowland.harvard.edu> Tested-by: Stuart Foster <smf.linux@ntlworld.com> Signed-off-by: James Bottomley <JBottomley@Parallels.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 7eee85f - Browse repository at this point
Copy the full SHA 7eee85fView commit details -
SCSI: megaraid_sas: megaraid_sas driver init fails in kdump kernel
commit 6431f5d upstream. Problem: When Hardware IOMMU is on, megaraid_sas driver initialization fails in kdump kernel with LSI MegaRAID controller(device id-0x73). Actually this issue needs fix in firmware, but for firmware running in field, this driver fix is proposed to resolve the issue. At firmware initialization time, if firmware does not come to ready state, driver will reset the adapter and retry for firmware transition to ready state unconditionally(not only executed for kdump kernel). Signed-off-by: Sumit Saxena <sumit.saxena@lsi.com> Signed-off-by: Kashyap Desai <kashyap.desai@lsi.com> Signed-off-by: James Bottomley <JBottomley@Parallels.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 3b8d21f - Browse repository at this point
Copy the full SHA 3b8d21fView commit details -
ext4: make sure group number is bumped after a inode allocation race
commit a34eb50 upstream. When we try to allocate an inode, and there is a race between two CPU's trying to grab the same inode, _and_ this inode is the last free inode in the block group, make sure the group number is bumped before we continue searching the rest of the block groups. Otherwise, we end up searching the current block group twice, and we end up skipping searching the last block group. So in the unlikely situation where almost all of the inodes are allocated, it's possible that we will return ENOSPC even though there might be free inodes in that last block group. Signed-off-by: "Theodore Ts'o" <tytso@mit.edu> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for b2fea70 - Browse repository at this point
Copy the full SHA b2fea70View commit details -
hwmon: (adt7470) Fix incorrect return code check
commit 93d783b upstream. In adt7470_write_word_data(), which writes two bytes using i2c_smbus_write_byte_data(), the return codes are incorrectly AND-ed together when they should be OR-ed together. The return code of i2c_smbus_write_byte_data() is zero for success. The upshot is only the first byte was ever written to the hardware. The 2nd byte was never written out. I noticed that trying to set the fan speed limits was not working correctly on my system. Setting the fan speed limits is the only code that uses adt7470_write_word_data(). After making the change the limit settings work and the alarms work also. Signed-off-by: Curt Brune <curt@cumulusnetworks.com> Signed-off-by: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for b9ea0ce - Browse repository at this point
Copy the full SHA b9ea0ceView commit details -
virtio: console: fix race with port unplug and open/close
commit 057b82b upstream. There's a window between find_port_by_devt() returning a port and us taking a kref on the port, where the port could get unplugged. Fix it by taking the reference in find_port_by_devt() itself. Problem reported and analyzed by Mateusz Guzik. Reported-by: Mateusz Guzik <mguzik@redhat.com> Signed-off-by: Amit Shah <amit.shah@redhat.com> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for d0bfaac - Browse repository at this point
Copy the full SHA d0bfaacView commit details -
virtio: console: fix race in port_fops_open() and port unplug
commit 671bdea upstream. Between open() being called and processed, the port can be unplugged. Check if this happened, and bail out. A simple test script to reproduce this is: while true; do for i in $(seq 1 100); do echo $i > /dev/vport0p3; done; done; This opens and closes the port a lot of times; unplugging the port while this is happening triggers the bug. Signed-off-by: Amit Shah <amit.shah@redhat.com> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 9c040cb - Browse repository at this point
Copy the full SHA 9c040cbView commit details -
virtio: console: clean up port data immediately at time of unplug
commit ea3768b upstream. We used to keep the port's char device structs and the /sys entries around till the last reference to the port was dropped. This is actually unnecessary, and resulted in buggy behaviour: 1. Open port in guest 2. Hot-unplug port 3. Hot-plug a port with the same 'name' property as the unplugged one This resulted in hot-plug being unsuccessful, as a port with the same name already exists (even though it was unplugged). This behaviour resulted in a warning message like this one: -------------------8<--------------------------------------- WARNING: at fs/sysfs/dir.c:512 sysfs_add_one+0xc9/0x130() (Not tainted) Hardware name: KVM sysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:04.0/virtio0/virtio-ports/vport0p1' Call Trace: [<ffffffff8106b607>] ? warn_slowpath_common+0x87/0xc0 [<ffffffff8106b6f6>] ? warn_slowpath_fmt+0x46/0x50 [<ffffffff811f2319>] ? sysfs_add_one+0xc9/0x130 [<ffffffff811f23e8>] ? create_dir+0x68/0xb0 [<ffffffff811f2469>] ? sysfs_create_dir+0x39/0x50 [<ffffffff81273129>] ? kobject_add_internal+0xb9/0x260 [<ffffffff812733d8>] ? kobject_add_varg+0x38/0x60 [<ffffffff812734b4>] ? kobject_add+0x44/0x70 [<ffffffff81349de4>] ? get_device_parent+0xf4/0x1d0 [<ffffffff8134b389>] ? device_add+0xc9/0x650 -------------------8<--------------------------------------- Instead of relying on guest applications to release all references to the ports, we should go ahead and unregister the port from all the core layers. Any open/read calls on the port will then just return errors, and an unplug/plug operation on the host will succeed as expected. This also caused buggy behaviour in case of the device removal (not just a port): when the device was removed (which means all ports on that device are removed automatically as well), the ports with active users would clean up only when the last references were dropped -- and it would be too late then to be referencing char device pointers, resulting in oopses: -------------------8<--------------------------------------- PID: 6162 TASK: ffff8801147ad500 CPU: 0 COMMAND: "cat" #0 [ffff88011b9d5a90] machine_kexec at ffffffff8103232b #1 [ffff88011b9d5af0] crash_kexec at ffffffff810b9322 #2 [ffff88011b9d5bc0] oops_end at ffffffff814f4a50 #3 [ffff88011b9d5bf0] die at ffffffff8100f26b #4 [ffff88011b9d5c20] do_general_protection at ffffffff814f45e2 #5 [ffff88011b9d5c50] general_protection at ffffffff814f3db5 [exception RIP: strlen+2] RIP: ffffffff81272ae2 RSP: ffff88011b9d5d00 RFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff880118901c18 RCX: 0000000000000000 RDX: ffff88011799982c RSI: 00000000000000d0 RDI: 3a303030302f3030 RBP: ffff88011b9d5d38 R8: 0000000000000006 R9: ffffffffa0134500 R10: 0000000000001000 R11: 0000000000001000 R12: ffff880117a1cc10 R13: 00000000000000d0 R14: 0000000000000017 R15: ffffffff81aff700 ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018 #6 [ffff88011b9d5d00] kobject_get_path at ffffffff8126dc5d #7 [ffff88011b9d5d40] kobject_uevent_env at ffffffff8126e551 #8 [ffff88011b9d5dd0] kobject_uevent at ffffffff8126e9eb #9 [ffff88011b9d5de0] device_del at ffffffff813440c7 -------------------8<--------------------------------------- So clean up when we have all the context, and all that's left to do when the references to the port have dropped is to free up the port struct itself. Reported-by: chayang <chayang@redhat.com> Reported-by: YOGANANTH SUBRAMANIAN <anantyog@in.ibm.com> Reported-by: FuXiangChun <xfu@redhat.com> Reported-by: Qunfang Zhang <qzhang@redhat.com> Reported-by: Sibiao Luo <sluo@redhat.com> Signed-off-by: Amit Shah <amit.shah@redhat.com> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 9f92faf - Browse repository at this point
Copy the full SHA 9f92fafView commit details -
virtio: console: fix raising SIGIO after port unplug
commit 92d3453 upstream. SIGIO should be sent when a port gets unplugged. It should only be sent to prcesses that have the port opened, and have asked for SIGIO to be delivered. We were clearing out guest_connected before calling send_sigio_to_port(), resulting in a sigio not getting sent to processes. Fix by setting guest_connected to false after invoking the sigio function. Signed-off-by: Amit Shah <amit.shah@redhat.com> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 183c6a6 - Browse repository at this point
Copy the full SHA 183c6a6View commit details -
virtio: console: return -ENODEV on all read operations after unplug
commit 96f97a8 upstream. If a port gets unplugged while a user is blocked on read(), -ENODEV is returned. However, subsequent read()s returned 0, indicating there's no host-side connection (but not indicating the device went away). This also happened when a port was unplugged and the user didn't have any blocking operation pending. If the user didn't monitor the SIGIO signal, they won't have a chance to find out if the port went away. Fix by returning -ENODEV on all read()s after the port gets unplugged. write() already behaves this way. Signed-off-by: Amit Shah <amit.shah@redhat.com> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for a57425e - Browse repository at this point
Copy the full SHA a57425eView commit details -
ext4: fix mount/remount error messages for incompatible mount options
commit 6ae6514 upstream. Commit 5688978 ("ext4: improve handling of conflicting mount options") introduced incorrect messages shown while choosing wrong mount options. First of all, both cases of incorrect mount options, "data=journal,delalloc" and "data=journal,dioread_nolock" result in the same error message. Secondly, the problem above isn't solved for remount option: the mismatched parameter is simply ignored. Moreover, ext4_msg states that remount with options "data=journal,delalloc" succeeded, which is not true. To fix it up, I added a simple check after parse_options() call to ensure that data=journal and delalloc/dioread_nolock parameters are not present at the same time. Signed-off-by: Piotr Sarna <p.sarna@partner.samsung.com> Acked-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com> Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 6cd4531 - Browse repository at this point
Copy the full SHA 6cd4531View commit details -
cifs: extend the buffer length enought for sprintf() using
commit 057d633 upstream. For cifs_set_cifscreds() in "fs/cifs/connect.c", 'desc' buffer length is 'CIFSCREDS_DESC_SIZE' (56 is less than 256), and 'ses->domainName' length may be "255 + '\0'". The related sprintf() may cause memory overflow, so need extend related buffer enough to hold all things. It is also necessary to be sure of 'ses->domainName' must be less than 256, and define the related macro instead of hard code number '256'. Signed-off-by: Chen Gang <gang.chen@asianux.com> Reviewed-by: Jeff Layton <jlayton@redhat.com> Reviewed-by: Shirish Pargaonkar <shirishpargaonkar@gmail.com> Reviewed-by: Scott Lovenberg <scott.lovenberg@gmail.com> Signed-off-by: Steve French <smfrench@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 3fbcb7f - Browse repository at this point
Copy the full SHA 3fbcb7fView commit details -
usb: core: don't try to reset_device() a port that got just disconnected
commit 481f2d4 upstream. The USB hub driver's event handler contains a check to catch SuperSpeed devices that transitioned into the SS.Inactive state and tries to fix them with a reset. It decides whether to do a plain hub port reset or call the usb_reset_device() function based on whether there was a device attached to the port. However, there are device/hub combinations (found with a JetFlash Transcend mass storage stick (8564:1000) on the root hub of an Intel LynxPoint PCH) which can transition to the SS.Inactive state on disconnect (and stay there long enough for the host to notice). In this case, above-mentioned reset check will call usb_reset_device() on the stale device data structure. The kernel will send pointless LPM control messages to the no longer connected device address and can even cause several 5 second khubd stalls on some (buggy?) host controllers, before finally accepting the device's fate amongst a flurry of error messages. This patch makes the choice of reset dependent on the port status that has just been read from the hub in addition to the existence of an in-kernel data structure for the device, and only proceeds with the more extensive reset if both are valid. Signed-off-by: Julius Werner <jwerner@chromium.org> Signed-off-by: Sarah Sharp <sarah.a.sharp@linux.intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 8b45ff8 - Browse repository at this point
Copy the full SHA 8b45ff8View commit details -
debugfs: debugfs_remove_recursive() must not rely on list_empty(d_sub…
…dirs) commit 776164c upstream. debugfs_remove_recursive() is wrong, 1. it wrongly assumes that !list_empty(d_subdirs) means that this dir should be removed. This is not that bad by itself, but: 2. if d_subdirs does not becomes empty after __debugfs_remove() it gives up and silently fails, it doesn't even try to remove other entries. However ->d_subdirs can be non-empty because it still has the already deleted !debugfs_positive() entries. 3. simple_release_fs() is called even if __debugfs_remove() fails. Suppose we have dir1/ dir2/ file2 file1 and someone opens dir1/dir2/file2. Now, debugfs_remove_recursive(dir1/dir2) succeeds, and dir1/dir2 goes away. But debugfs_remove_recursive(dir1) silently fails and doesn't remove this directory. Because it tries to delete (the already deleted) dir1/dir2/file2 again and then fails due to "Avoid infinite loop" logic. Test-case: #!/bin/sh cd /sys/kernel/debug/tracing echo 'p:probe/sigprocmask sigprocmask' >> kprobe_events sleep 1000 < events/probe/sigprocmask/id & echo -n >| kprobe_events [ -d events/probe ] && echo "ERR!! failed to rm probe" And after that it is not possible to create another probe entry. With this patch debugfs_remove_recursive() skips !debugfs_positive() files although this is not strictly needed. The most important change is that it does not try to make ->d_subdirs empty, it simply scans the whole list(s) recursively and removes as much as possible. Link: http://lkml.kernel.org/r/20130726151256.GC19472@redhat.com Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: Oleg Nesterov <oleg@redhat.com> Signed-off-by: Steven Rostedt <rostedt@goodmis.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 65280b8 - Browse repository at this point
Copy the full SHA 65280b8View commit details -
tracing: Fix fields of struct trace_iterator that are zeroed by mistake
commit ed5467d upstream. tracing_read_pipe zeros all fields bellow "seq". The declaration contains a comment about that, but it doesn't help. The first field is "snapshot", it's true when current open file is snapshot. Looks obvious, that it should not be zeroed. The second field is "started". It was converted from cpumask_t to cpumask_var_t (v2.6.28-4983-g4462344), in other words it was converted from cpumask to pointer on cpumask. Currently the reference on "started" memory is lost after the first read from tracing_read_pipe and a proper object will never be freed. The "started" is never dereferenced for trace_pipe, because trace_pipe can't have the TRACE_FILE_ANNOTATE options. Link: http://lkml.kernel.org/r/1375463803-3085183-1-git-send-email-avagin@openvz.org Signed-off-by: Andrew Vagin <avagin@openvz.org> Signed-off-by: Steven Rostedt <rostedt@goodmis.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 99593eb - Browse repository at this point
Copy the full SHA 99593ebView commit details -
SCSI: nsp32: use mdelay instead of large udelay constants
commit b497ceb upstream. ARM cannot handle udelay for more than 2 miliseconds, so we should use mdelay instead for those. Signed-off-by: Arnd Bergmann <arnd@arndb.de> Acked-by: GOTO Masanori <gotom@debian.or.jp> Cc: YOKOTA Hiroshi <yokota@netlab.is.tsukuba.ac.jp> Cc: "James E.J. Bottomley" <JBottomley@parallels.com> Cc: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 4bcdbdd - Browse repository at this point
Copy the full SHA 4bcdbddView commit details -
vfs: d_obtain_alias() needs to use "/" as default name.
commit b911a6b upstream. NFS appears to use d_obtain_alias() to create the root dentry rather than d_make_root. This can cause 'prepend_path()' to complain that the root has a weird name if an NFS filesystem is lazily unmounted. e.g. if "/mnt" is an NFS mount then { cd /mnt; umount -l /mnt ; ls -l /proc/self/cwd; } will cause a WARN message like WARNING: at /home/git/linux/fs/dcache.c:2624 prepend_path+0x1d7/0x1e0() ... Root dentry has weird name <> to appear in kernel logs. So change d_obtain_alias() to use "/" rather than "" as the anonymous name. Signed-off-by: NeilBrown <neilb@suse.de> Cc: Trond Myklebust <Trond.Myklebust@netapp.com> Cc: Al Viro <viro@zeniv.linux.org.uk> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> [bwh: Backported to 3.2: use named initialisers instead of QSTR_INIT()] Signed-off-by: Ben Hutchings <ben@decadent.org.uk> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 7a0117d - Browse repository at this point
Copy the full SHA 7a0117dView commit details -
perf tools: Add anonymous huge page recognition
commit d0528b5 upstream. Judging anonymous memory's vm_area_struct, perf_mmap_event's filename will be set to "//anon" indicating this vma belongs to anonymous memory. Once hugepage is used, vma's vm_file points to hugetlbfs. In this way, this vma will not be regarded as anonymous memory by is_anon_memory() in perf user space utility. Signed-off-by: Joshua Zhu <zhu.wen-jie@hp.com> Cc: Akihiro Nagai <akihiro.nagai.hw@hitachi.com> Cc: Andi Kleen <andi@firstfloor.org> Cc: David Ahern <dsahern@gmail.com> Cc: Ingo Molnar <mingo@redhat.com> Cc: Jiri Olsa <jolsa@redhat.com> Cc: Joshua Zhu <zhu.wen-jie@hp.com> Cc: Namhyung Kim <namhyung@kernel.org> Cc: Paul Mackerras <paulus@samba.org> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl> Cc: Vinson Lee <vlee@freedesktop.org> Link: http://lkml.kernel.org/r/1357363797-3550-1-git-send-email-zhu.wen-jie@hp.com Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 03bca23 - Browse repository at this point
Copy the full SHA 03bca23View commit details -
Configuration menu - View commit details
-
Copy full SHA for 13cbe0f - Browse repository at this point
Copy the full SHA 13cbe0fView commit details
Commits on Aug 20, 2013
-
perf/arm: Fix armpmu_map_hw_event()
commit b88a259 upstream. Fix constraint check in armpmu_map_hw_event(). Reported-and-tested-by: Vince Weaver <vincent.weaver@maine.edu> Signed-off-by: Ingo Molnar <mingo@kernel.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 2e42d79 - Browse repository at this point
Copy the full SHA 2e42d79View commit details -
fs/proc/task_mmu.c: fix buffer overflow in add_page_map()
commit 8c82962 upstream. Recently we met quite a lot of random kernel panic issues after enabling CONFIG_PROC_PAGE_MONITOR. After debuggind we found this has something to do with following bug in pagemap: In struct pagemapread: struct pagemapread { int pos, len; pagemap_entry_t *buffer; bool v2; }; pos is number of PM_ENTRY_BYTES in buffer, but len is the size of buffer, it is a mistake to compare pos and len in add_page_map() for checking buffer is full or not, and this can lead to buffer overflow and random kernel panic issue. Correct len to be total number of PM_ENTRY_BYTES in buffer. [akpm@linux-foundation.org: document pagemapread.pos and .len units, fix PM_ENTRY_BYTES definition] Signed-off-by: Yonghua Zheng <younghua.zheng@gmail.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>
Configuration menu - View commit details
-
Copy full SHA for d77d525 - Browse repository at this point
Copy the full SHA d77d525View commit details -
drm/i915/lvds: ditch ->prepare special case
commit 520c41c upstream. LVDS is the first output where dpms on/off and prepare/commit don't perfectly match. Now the idea behind this special case seems to be that for simple resolution changes on the LVDS we don't need to stop the pipe, because (at least on newer chips) we can adjust the panel fitter on the fly. There are a few problems with the current code though: - We still stop and restart the pipe unconditionally, because the crtc helper code isn't flexible enough. - We show some ugly flickering, especially when changing crtcs (this the crtc helper would actually take into account, but we don't implement the encoder->get_crtc callback required to make this work properly). So it doesn't even work as advertised. I agree that it would be nice to do resolution changes on LVDS (and also eDP) whithout blacking the screen where the panel fitter allows to do that. But imo we should implement this as a special case a few layers up in the mode set code, akin to how we already detect simple framebuffer changes (and only update the required registers with ->mode_set_base). Until this is all in place, make our lives easier and just rip it out. Also note that this seems to fix actual bugs with enabling the lvds output, see: http://lists.freedesktop.org/archives/intel-gfx/2012-July/018614.html Acked-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Takashi Iwai <tiwai@suse.de> Cc: Giacomo Comes <comes@naic.edu> Tested-by: Takashi Iwai <tiwai@suse.de> Signed-Off-by: Daniel Vetter <daniel.vetter@ffwll.ch> Cc: Haitao Zhang <haitao.zhang@canonical.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for b381f38 - Browse repository at this point
Copy the full SHA b381f38View commit details -
MIPS: Expose missing pci_io{map,unmap} declarations
commit 7885761 upstream. The GENERIC_PCI_IOMAP does not depend on CONFIG_PCI so move it to the CONFIG_MIPS symbol so it's always selected for MIPS. This fixes the missing pci_iomap declaration for MIPS. Moreover, the pci_iounmap function was not defined in the io.h header file if the CONFIG_PCI symbol is not set, but it should since MIPS is not using CONFIG_GENERIC_IOMAP. This fixes the following problem on a allyesconfig: drivers/net/ethernet/3com/3c59x.c:1031:2: error: implicit declaration of function 'pci_iomap' [-Werror=implicit-function-declaration] drivers/net/ethernet/3com/3c59x.c:1044:3: error: implicit declaration of function 'pci_iounmap' [-Werror=implicit-function-declaration] Signed-off-by: Markos Chandras <markos.chandras@imgtec.com> Acked-by: Steven J. Hill <Steven.Hill@imgtec.com> Cc: linux-mips@linux-mips.org Patchwork: https://patchwork.linux-mips.org/patch/5478/ Signed-off-by: Ralf Baechle <ralf@linux-mips.org> Cc: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 01aeb48 - Browse repository at this point
Copy the full SHA 01aeb48View commit details -
microblaze: Update microblaze defconfigs
commit d0e0454 upstream. The main reason is 0-day testing system which can directly use these defconfigs for testing. Enable support for all xilinx drivers which Microblaze can use and disable dependency on external rootfs.cpio. There is only one exception which is axi ethernet driver which still uses NO_IRQ which is not defined for Microblaze. Signed-off-by: Michal Simek <michal.simek@xilinx.com> Cc: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 7b21e1d - Browse repository at this point
Copy the full SHA 7b21e1dView commit details -
sound: Fix make allmodconfig on MIPS
commit d4702b1 upstream. The compile of soundcard.c is broken on MIPS when allmodconfig is used because of the missing MAX_DMA_CHANNELS definition. As a simple workaround, just add a Kconfig dependency. Reported-by: Andrew Morton <akpm@linux-foundation.org> Cc: Ralf Baechle <ralf@linux-mips.org> Signed-off-by: Takashi Iwai <tiwai@suse.de> Cc: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 2f540fd - Browse repository at this point
Copy the full SHA 2f540fdView commit details -
sound: Fix make allmodconfig on MIPS correctly
commit a62ee23 upstream. Commit d4702b1 ("sound: Fix make allmodconfig on MIPS") added a (negative) dependency on ISA_DMA_SUPPORT_BROKEN. Since that Kconfig symbol doesn't exist, this dependency will always evaluate to true. Apparently GENERIC_ISA_DMA_SUPPORT_BROKEN was meant to be used here. Signed-off-by: Paul Bolle <pebolle@tiscali.nl> Signed-off-by: Takashi Iwai <tiwai@suse.de> Cc: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 9eae332 - Browse repository at this point
Copy the full SHA 9eae332View commit details -
HID: microsoft: do not use compound literal - fix build
commit 6b90466 upstream. In patch "HID: microsoft: fix invalid rdesc for 3k kbd" I fixed support for MS 3k keyboards. However the added check using memcmp and a compound statement breaks build on architectures where memcmp is a macro with parameters. hid-microsoft.c:51:18: error: macro "memcmp" passed 6 arguments, but takes just 3 On x86_64, memcmp is a function, so I did not see the error. Signed-off-by: Jiri Slaby <jslaby@suse.cz> Reported-by: Geert Uytterhoeven <geert@linux-m68k.org> Signed-off-by: Jiri Kosina <jkosina@suse.cz> Cc: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for ec3c697 - Browse repository at this point
Copy the full SHA ec3c697View commit details -
vm: add no-mmu vm_iomap_memory() stub
commit 3c0b9de upstream. I think we could just move the full vm_iomap_memory() function into util.h or similar, but I didn't get any reply from anybody actually using nommu even to this trivial patch, so I'm not going to touch it any more than required. Here's the fairly minimal stub to make the nommu case at least potentially work. It doesn't seem like anybody cares, though. Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Cc: Geert Uytterhoeven <geert@linux-m68k.org> Cc: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for cd1be30 - Browse repository at this point
Copy the full SHA cd1be30View commit details -
cris: posix_types.h, include asm-generic/posix_types.h
commit 74f077d upstream. Without that I cannot build anything: In file included from include/linux/page-flags.h:8:0, from kernel/bounds.c:9: include/linux/types.h:25:1: error: unknown type name '__kernel_ino_t' include/linux/types.h:29:1: error: unknown type name '__kernel_off_t' ... Signed-off-by: Jiri Slaby <jslaby@suse.cz> Cc: Mikael Starvik <starvik@axis.com> Signed-off-by: Jesper Nilsson <jesper.nilsson@axis.com> Cc: linux-cris-kernel@axis.com Cc: Geert Uytterhoeven <geert@linux-m68k.org> Cc: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 38045ae - Browse repository at this point
Copy the full SHA 38045aeView commit details -
cris: Remove old legacy "-traditional" flag from arch-v10/lib/Makefile
commit 7b91747 upstream. Most of these have been purged years ago. This one silently lived on until commit 69349c2 "kconfig: fix IS_ENABLED to not require all options to be defined" In the above, we use some macro trickery to create a conditional that is valid in CPP and in C usage. However that trickery doesn't sit well if you have the legacy "-traditional" flag enabled. You'll get: AS arch/cris/arch-v10/lib/checksum.o In file included from <command-line>:4:0: include/linux/kconfig.h:23:0: error: syntax error in macro parameter list make[2]: *** [arch/cris/arch-v10/lib/checksum.o] Error 1 Everything builds fine w/o "-traditional" so simply drop it from this location as well. Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com> Signed-off-by: Jesper Nilsson <jesper.nilsson@axis.com> Cc: Geert Uytterhoeven <geert@linux-m68k.org> Cc: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 5acea25 - Browse repository at this point
Copy the full SHA 5acea25View commit details -
CRIS: Add _sdata to vmlinux.lds.S
commit 473e162 upstream. Fixes link error: LD vmlinux kernel/built-in.o: In function `core_kernel_data': (.text+0x13e44): undefined reference to `_sdata' Signed-off-by: Jesper Nilsson <jesper.nilsson@axis.com> Cc: Guenter Roeck <linux@roeck-us.net> Cc: Geert Uytterhoeven <geert@linux-m68k.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 4d5b24d - Browse repository at this point
Copy the full SHA 4d5b24dView commit details -
futex: Take hugepages into account when generating futex_key
commit 13d60f4 upstream. The futex_keys of process shared futexes are generated from the page offset, the mapping host and the mapping index of the futex user space address. This should result in an unique identifier for each futex. Though this is not true when futexes are located in different subpages of an hugepage. The reason is, that the mapping index for all those futexes evaluates to the index of the base page of the hugetlbfs mapping. So a futex at offset 0 of the hugepage mapping and another one at offset PAGE_SIZE of the same hugepage mapping have identical futex_keys. This happens because the futex code blindly uses page->index. Steps to reproduce the bug: 1. Map a file from hugetlbfs. Initialize pthread_mutex1 at offset 0 and pthread_mutex2 at offset PAGE_SIZE of the hugetlbfs mapping. The mutexes must be initialized as PTHREAD_PROCESS_SHARED because PTHREAD_PROCESS_PRIVATE mutexes are not affected by this issue as their keys solely depend on the user space address. 2. Lock mutex1 and mutex2 3. Create thread1 and in the thread function lock mutex1, which results in thread1 blocking on the locked mutex1. 4. Create thread2 and in the thread function lock mutex2, which results in thread2 blocking on the locked mutex2. 5. Unlock mutex2. Despite the fact that mutex2 got unlocked, thread2 still blocks on mutex2 because the futex_key points to mutex1. To solve this issue we need to take the normal page index of the page which contains the futex into account, if the futex is in an hugetlbfs mapping. In other words, we calculate the normal page mapping index of the subpage in the hugetlbfs mapping. Mappings which are not based on hugetlbfs are not affected and still use page->index. Thanks to Mel Gorman who provided a patch for adding proper evaluation functions to the hugetlbfs code to avoid exposing hugetlbfs specific details to the futex code. [ tglx: Massaged changelog ] Signed-off-by: Zhang Yi <zhang.yi20@zte.com.cn> Reviewed-by: Jiang Biao <jiang.biao2@zte.com.cn> Tested-by: Ma Chenggong <ma.chenggong@zte.com.cn> Reviewed-by: 'Mel Gorman' <mgorman@suse.de> Acked-by: 'Darren Hart' <dvhart@linux.intel.com> Cc: 'Peter Zijlstra' <peterz@infradead.org> Link: http://lkml.kernel.org/r/000101ce71a6%24a83c5880%24f8b50980%24@com Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Cc: Mike Galbraith <mgalbraith@suse.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for a42efb7 - Browse repository at this point
Copy the full SHA a42efb7View commit details -
frv: Use correct size for task_struct allocation
commit cce4517 upstream. alloc_task_struct_node() allocates THREAD_SIZE and maintains some weird refcount in the allocated memory. This never blew up as task_struct size on 32bit machines was always less than THREAD_SIZE Allocate just sizeof(struct task_struct) and get rid of the magic refcounting. Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Acked-by: David Howells <dhowells@redhat.com> Link: http://lkml.kernel.org/r/20120503085033.898475542@linutronix.de Cc: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 0a2436e - Browse repository at this point
Copy the full SHA 0a2436eView commit details -
frv: Use core allocator for task_struct
commit c6ae063 upstream. There is no point having a copy of the core allocator. Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Acked-by: David Howells <dhowells@redhat.com> Link: http://lkml.kernel.org/r/20120503085033.967140188@linutronix.de Cc: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for fa04660 - Browse repository at this point
Copy the full SHA fa04660View commit details -
powerpc/numa: Avoid stupid uninitialized warning from gcc
commit aa709f3 upstream. Newer gcc are being a bit blind here (it's pretty obvious we don't reach the code path using the array if we haven't initialized the pointer) but none of that is performance critical so let's just silence it. Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org> Cc: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 30d0376 - Browse repository at this point
Copy the full SHA 30d0376View commit details -
alpha: makefile: don't enforce small data model for kernel builds
commit cd8d233 upstream. Due to all of the goodness being packed into today's kernels, the resulting image isn't as slim as it once was. In light of this, don't pass -msmall-data to gcc, which otherwise results in link failures due to impossible relocations when compiling anything but the most trivial configurations. Reviewed-by: Matt Turner <mattst88@gmail.com> Cc: Richard Henderson <rth@twiddle.net> Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru> Tested-by: Thorsten Kranzkowski <dl8bcu@dl8bcu.de> Signed-off-by: Will Deacon <will.deacon@arm.com> Signed-off-by: Michael Cree <mcree@orcon.net.nz> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Cc: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for efb5fbe - Browse repository at this point
Copy the full SHA efb5fbeView commit details -
md/raid1,raid10: use freeze_array in place of raise_barrier in variou…
…s places. commit e2d5992 upstream. Various places in raid1 and raid10 are calling raise_barrier when they really should call freeze_array. The former is only intended to be called from "make_request". The later has extra checks for 'nr_queued' and makes a call to flush_pending_writes(), so it is safe to call it from within the management thread. Using raise_barrier will sometimes deadlock. Using freeze_array should not. As 'freeze_array' currently expects one request to be pending (in handle_read_error - the only previous caller), we need to pass it the number of pending requests (extra) to ignore. The deadlock was made particularly noticeable by commits 050b661 (raid10) and 6b740b8 (raid1) which appeared in 3.4, so the fix is appropriate for any -stable kernel since then. This patch probably won't apply directly to some early kernels and will need to be applied by hand. Cc: stable@vger.kernel.org Reported-by: Alexander Lyakas <alex.bolshoy@gmail.com> Signed-off-by: NeilBrown <neilb@suse.de> [adjust context to make it can be apply on top of 3.4 ] Signed-off-by: Jack Wang <jinpu.wang@profitbricks.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 1b9203b - Browse repository at this point
Copy the full SHA 1b9203bView commit details -
commit de36e66 upstream. Based on copy from microblaze add ucmpdi2 implementation. This fixes build of niu driver which failed with: drivers/built-in.o: In function `niu_get_nfc': niu.c:(.text+0x91494): undefined reference to `__ucmpdi2' This driver will never be used on a sparc32 system, but patch added to fix build breakage with all*config builds. Signed-off-by: Sam Ravnborg <sam@ravnborg.org> Signed-off-by: David S. Miller <davem@davemloft.net> Cc: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for d326e4a - Browse repository at this point
Copy the full SHA d326e4aView commit details -
sparc32: Add ucmpdi2.o to obj-y instead of lib-y.
commit 74c7b28 upstream. Otherwise if no references exist in the static kernel image, we won't export the symbol properly to modules. Signed-off-by: David S. Miller <davem@davemloft.net> Cc: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 22a327d - Browse repository at this point
Copy the full SHA 22a327dView commit details -
MIPS: Rewrite pfn_valid to work in modules, too.
Upstream commit 8b92321. This fixes: MODPOST 393 modules ERROR: "min_low_pfn" [arch/mips/kvm/kvm.ko] undefined! make[3]: *** [__modpost] Error 1 It would have been possible to just export min_low_pfn but in the end pfn_valid should return 1 for any pfn argument for which a struct page exists so using min_low_pfn was wrong anyway. [Backport to 3.4 kernel. Applies cleanly on top of current 3.4 patch queue, and fixes "make ARCH=mips allmodconfig; make ARCH=mips" build problem. - Guenter] Signed-off-by: Ralf Baechle <ralf@linux-mips.org> Signed-off-by: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 938b7f3 - Browse repository at this point
Copy the full SHA 938b7f3View commit details -
af_key: initialize satype in key_notify_policy_flush()
commit 85dfb74 upstream. This field was left uninitialized. Some user daemons perform check against this field. Signed-off-by: Nicolas Dichtel <nicolas.dichtel@6wind.com> Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com> Cc: Luis Henriques <luis.henriques@canonical.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 1a5abb4 - Browse repository at this point
Copy the full SHA 1a5abb4View commit details -
commit eca396d upstream. If device was put into a sleep and system was restarted or module reloaded, we have to wake device up before sending other commands. Otherwise it will fail to start with Microcode error. Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com> Signed-off-by: John W. Linville <linville@tuxdriver.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 179dfb0 - Browse repository at this point
Copy the full SHA 179dfb0View commit details -
iwl4965: reset firmware after rfkill off
commit 788f7a5 upstream. Using rfkill switch can make firmware unstable, what cause various Microcode errors and kernel warnings. Reseting firmware just after rfkill off (radio on) helped with that. Resolve: https://bugzilla.redhat.com/show_bug.cgi?id=977053 Reported-and-tested-by: Justin Pearce <whitefox@guardianfox.net> Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com> Signed-off-by: John W. Linville <linville@tuxdriver.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 6e819f5 - Browse repository at this point
Copy the full SHA 6e819f5View commit details -
can: pcan_usb: fix wrong memcpy() bytes length
commit 3c322a5 upstream. Fix possibly wrong memcpy() bytes length since some CAN records received from PCAN-USB could define a DLC field in range [9..15]. In that case, the real DLC value MUST be used to move forward the record pointer but, only 8 bytes max. MUST be copied into the data field of the struct can_frame object of the skb given to the network core. Signed-off-by: Stephane Grosjean <s.grosjean@peak-system.com> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 2efb739 - Browse repository at this point
Copy the full SHA 2efb739View commit details -
usb: add two quirky touchscreen
commit 304ab4a upstream. These devices tend to become unresponsive after S3 Signed-off-by: Oliver Neukum <oneukum@suse.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 40d0288 - Browse repository at this point
Copy the full SHA 40d0288View commit details -
USB: mos7720: fix broken control requests
commit ef6c8c1 upstream. The parallel-port code of the drivers used a stack allocated control-request buffer for asynchronous (and possibly deferred) control requests. This not only violates the no-DMA-from-stack requirement but could also lead to corrupt control requests being submitted. Signed-off-by: Johan Hovold <jhovold@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for d36f8a9 - Browse repository at this point
Copy the full SHA d36f8a9View commit details -
xtensa: fix linker script transformation for .text.unlikely
commit f6a03a1 upstream. Now that binutils generate *.unlikely sections which don't follow documented (info as) literal section naming rules, section name transformation script doesn't work well resulting in the following errors at vmlinux link time: main.c:(.text.unlikely+0x3): dangerous relocation: l32r: literal placed after use: .literal.unlikely Fix section name transformation script by adding specific rule for .text.unlikely sections. Signed-off-by: Max Filippov <jcmvbkbc@gmail.com> Signed-off-by: Chris Zankel <chris@zankel.net> Cc: Geert Uytterhoeven <geert@linux-m68k.org> Cc: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 85d43e3 - Browse repository at this point
Copy the full SHA 85d43e3View commit details -
xtensa: replace xtensa-specific _f{data,text} by _s{data,text}
commit 5e7b6ed upstream. commit a2d063a ("extable, core_kernel_data(): Make sure all archs define _sdata") missed xtensa. Xtensa does have a start of data marker, but calls it _fdata, causing kernel/built-in.o:(.text+0x964): undefined reference to `_sdata' _stext was already defined, but it was duplicated by _fdata. Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org> Cc: Steven Rostedt <rostedt@goodmis.org> Cc: Chris Zankel <chris@zankel.net> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Cc: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for ca4e6a5 - Browse repository at this point
Copy the full SHA ca4e6a5View commit details -
ARM: 7809/1: perf: fix event validation for software group leaders
commit c95eb31 upstream. It is possible to construct an event group with a software event as a group leader and then subsequently add a hardware event to the group. This results in the event group being validated by adding all members of the group to a fake PMU and attempting to allocate each event on their respective PMU. Unfortunately, for software events wthout a corresponding arm_pmu, this results in a kernel crash attempting to dereference the ->get_event_idx function pointer. This patch fixes the problem by checking explicitly for software events and ignoring those in event validation (since they can always be scheduled). We will probably want to revisit this for 3.12, since the validation checks don't appear to work correctly when dealing with multiple hardware PMUs anyway. Reported-by: Vince Weaver <vincent.weaver@maine.edu> Tested-by: Vince Weaver <vincent.weaver@maine.edu> Tested-by: Mark Rutland <mark.rutland@arm.com> Signed-off-by: Will Deacon <will.deacon@arm.com> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 40c3660 - Browse repository at this point
Copy the full SHA 40c3660View commit details -
m68k: Truncate base in do_div()
commit ea077b1 upstream. Explicitly truncate the second operand of do_div() to 32 bits to guard against bogus code calling it with a 64-bit divisor. [Thorsten] After upgrading from 3.2 to 3.10, mounting a btrfs volume fails with: btrfs: setting nodatacow, compression disabled btrfs: enabling auto recovery btrfs: disk space caching is enabled *** ZERO DIVIDE *** FORMAT=2 Current process id is 722 BAD KERNEL TRAP: 00000000 Modules linked in: evdev mac_hid ext4 crc16 jbd2 mbcache btrfs xor lzo_compress zlib_deflate raid6_pq crc32c libcrc32c PC: [<319535b2>] __btrfs_map_block+0x11c/0x119a [btrfs] SR: 2000 SP: 30c1fab4 a2: 30f0faf0 d0: 00000000 d1: 00001000 d2: 00000000 d3: 00000000 d4: 00010000 d5: 00000000 a0: 3085c72c a1: 3085c72c Process mount (pid: 722, task=30f0faf0) Frame format=2 instr addr=319535ae Stack from 30c1faec: 00000000 00000020 00000000 00001000 00000000 01401000 30253928 300ffc00 00a843ac 3026f640 00000000 00010000 0009e250 00d106c0 00011220 00000000 00001000 301c6830 0009e32a 000000ff 00000009 3085c72c 00000000 00000000 30c1fd14 00000000 00000020 00000000 30c1fd14 0009e26c 00000020 00000003 00000000 0009dd8a 300b0b6c 30253928 00a843ac 00001000 00000000 00000000 0000a008 3194e76a 30253928 00a843ac 00001000 00000000 00000000 00000002 Call Trace: [<00001000>] kernel_pg_dir+0x0/0x1000 [...] Code: 222e ff74 2a2e ff5c 2c2e ff60 4c45 1402 <2d40> ff64 2d41 ff68 2205 4c2e 1800 ff68 4c04 0800 2041 d1c0 2206 4c2e 1400 ff68 [Geert] As diagnosed by Andreas, fs/btrfs/volumes.c:__btrfs_map_block() calls do_div(stripe_nr, stripe_len); with stripe_len u64, while do_div() assumes the divisor is a 32-bit number. Due to the lack of truncation in the m68k-specific implementation of do_div(), the division is performed using the upper 32-bit word of stripe_len, which is zero. This was introduced by commit 53b381b ("Btrfs: RAID5 and RAID6"), which changed the divisor from map->stripe_len (struct map_lookup.stripe_len is int) to a 64-bit temporary. Reported-by: Thorsten Glaser <tg@debian.org> Signed-off-by: Andreas Schwab <schwab@linux-m68k.org> Tested-by: Thorsten Glaser <tg@debian.org> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for aa1f7bc - Browse repository at this point
Copy the full SHA aa1f7bcView commit details -
m68k/atari: ARAnyM - Fix NatFeat module support
commit e8184e1 upstream. As pointed out by Andreas Schwab, pointers passed to ARAnyM NatFeat calls should be physical addresses, not virtual addresses. Fortunately on Atari, physical and virtual kernel addresses are the same, as long as normal kernel memory is concerned, so this usually worked fine without conversion. But for modules, pointers to literal strings are located in vmalloc()ed memory. Depending on the version of ARAnyM, this causes the nf_get_id() call to just fail, or worse, crash ARAnyM itself with e.g. Gotcha! Illegal memory access. Atari PC = $968c This is a big issue for distro kernels, who want to have all drivers as loadable modules in an initrd. Add a wrapper for nf_get_id() that copies the literal to the stack to work around this issue. Reported-by: Thorsten Glaser <tg@debian.org> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for dadf2af - Browse repository at this point
Copy the full SHA dadf2afView commit details -
jbd2: Fix use after free after error in jbd2_journal_dirty_metadata()
commit 91aa11f upstream. When jbd2_journal_dirty_metadata() returns error, __ext4_handle_dirty_metadata() stops the handle. However callers of this function do not count with that fact and still happily used now freed handle. This use after free can result in various issues but very likely we oops soon. The motivation of adding __ext4_journal_stop() into __ext4_handle_dirty_metadata() in commit 9ea7a0d seems to be only to improve error reporting. So replace __ext4_journal_stop() with ext4_journal_abort_handle() which was there before that commit and add WARN_ON_ONCE() to dump stack to provide useful information. Reported-by: Sage Weil <sage@inktank.com> Signed-off-by: Jan Kara <jack@suse.cz> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 9cfae3e - Browse repository at this point
Copy the full SHA 9cfae3eView commit details -
Configuration menu - View commit details
-
Copy full SHA for 67db9db - Browse repository at this point
Copy the full SHA 67db9dbView commit details
Commits on Aug 21, 2013
-
ion: convert map_kernel to return ERR_PTR
ion is going to stop accepting NULL as an error value, use ERR_PTR. Change-Id: I030e8b72138904e38a4a5d225beaaa98427651fb Signed-off-by: Colin Cross <ccross@android.com>
Configuration menu - View commit details
-
Copy full SHA for 721f35a - Browse repository at this point
Copy the full SHA 721f35aView commit details -
IS_ERR_OR_NULL is often part of a bad pattern that can accidentally return 0 on error: if (IS_ERR_OR_NULL(ptr)) return PTR_ERR(ptr); It also usually means that the errors of a function are not well defined. Replace all uses in ion.c by ensure that the return type of any function in ion is an ERR_PTR. Specify that the expected return value from map_kernel or map_dma heap ops is ERR_PTR, and warn if a heap returns NULL. Change-Id: I6e7ea0d2e62fa08d4e372a7ef6da649f7a62289c Signed-off-by: Colin Cross <ccross@android.com>
Configuration menu - View commit details
-
Copy full SHA for 16575fa - Browse repository at this point
Copy the full SHA 16575faView commit details -
ion: replace userspace handle cookies with idr
Userspace handles should not leak kernel virtual addresses to userspace. They have to be validated by looking them up in an rbtree anyways, so replace them with an idr and validate them by using idr_find to convert the id number to the struct ion_handle pointer. Change-Id: Iab5667ba6f3a73256fec3949b23a9a6f8e14a283 Signed-off-by: Colin Cross <ccross@android.com>
Configuration menu - View commit details
-
Copy full SHA for 1262ab1 - Browse repository at this point
Copy the full SHA 1262ab1View commit details -
ion: index client->handles rbtree by buffer
The only remaining users of the client->handles rbtree are iterating through it like a list. Keep the rbtree, but change its index to be the buffer address instead of the handle address, which makes ion_handle_lookup a fast rbtree search. Change-Id: Ie7d974b3a5d9831c0d664de85ddae8db3c3abdf9 Signed-off-by: Colin Cross <ccross@android.com>
Configuration menu - View commit details
-
Copy full SHA for 70770ea - Browse repository at this point
Copy the full SHA 70770eaView commit details
Commits on Aug 23, 2013
-
ion: don't use id 0 for handle cookie
ion userspace clients think that the cookie is a pointer, so they use NULL to check if the handle has been initialized. Set the first id number to 1. Change-Id: Ifb9af6029a8b08f57e41bc6160cc11e11001a2a9 Signed-off-by: Colin Cross <ccross@android.com>
Configuration menu - View commit details
-
Copy full SHA for ce4de44 - Browse repository at this point
Copy the full SHA ce4de44View commit details
Commits on Aug 24, 2013
-
ARM: 7743/1: compressed/head.S: work around new binutils warning
commit da94a82 upstream. In August 2012, Matthew Gretton-Dann checked a change into binutils labelled "Error on obsolete & warn on deprecated registers", apparently as part of ARMv8 support. Apparently, this was supposed to emit the message "Warning: This coprocessor register access is deprecated in ARMv8" when using certain mcr/mrc instructions and building for ARMv8. Unfortunately, the message that is actually emitted appears to be '(null)', which is less helpful in comparison. Even more unfortunately, this is biting us on every single kernel build with a new gas, because arch/arm/boot/compressed/head.S and some other files in that directory are built with -march=all since kernel commit 80cec14 "[ARM] Add -march=all to assembly file build in arch/arm/boot/compressed" back in v2.6.28. This patch reverts Russell's nice solution and instead marks the head.S file to be built for armv7-a, which fortunately lets us build all instructions in that file without warnings even on the broken binutils. Without this patch, building anything results in: arch/arm/boot/compressed/head.S: Assembler messages: arch/arm/boot/compressed/head.S:565: Warning: (null) arch/arm/boot/compressed/head.S:676: Warning: (null) arch/arm/boot/compressed/head.S:698: Warning: (null) arch/arm/boot/compressed/head.S:722: Warning: (null) arch/arm/boot/compressed/head.S:726: Warning: (null) arch/arm/boot/compressed/head.S:957: Warning: (null) arch/arm/boot/compressed/head.S:996: Warning: (null) arch/arm/boot/compressed/head.S:997: Warning: (null) arch/arm/boot/compressed/head.S:1027: Warning: (null) arch/arm/boot/compressed/head.S:1035: Warning: (null) arch/arm/boot/compressed/head.S:1046: Warning: (null) arch/arm/boot/compressed/head.S:1060: Warning: (null) arch/arm/boot/compressed/head.S:1092: Warning: (null) arch/arm/boot/compressed/head.S:1094: Warning: (null) arch/arm/boot/compressed/head.S:1095: Warning: (null) arch/arm/boot/compressed/head.S:1102: Warning: (null) arch/arm/boot/compressed/head.S:1134: Warning: (null) Signed-off-by: Arnd Bergmann <arnd@arndb.de> Cc: stable@vger.kernel.org Cc: Matthew Gretton-Dann <matthew.gretton-dann@arm.com> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> [ccross: cherry-picked to 3.4] Change-Id: If1c4c1a9f3f721a45d9833f2a36f1b7ce58c5e9a Signed-off-by: Colin Cross <ccross@android.com>
Configuration menu - View commit details
-
Copy full SHA for 6215187 - Browse repository at this point
Copy the full SHA 6215187View commit details
Commits on Aug 27, 2013
-
net: wireless: bcmdhd: Update to version 1.88.41
- Fix sched scan processing - Fix NDO processing - Do not wake dhd_dpc process if not necessary - Remove unnecessary defines and ifdefs - Fix SDIO bus wakeup code when idletime was zero case - Fix OOB interrupt handler was not registered when WLAN on failed case - Clean up ARP Packet filter code - Clean up P2P ESCAN source code - Clean up TDLS code Change-Id: I6b9a15f0d49c80d72183fd6e9f4b6bb01e450cd4 Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
Dmitry Shmidt committedAug 27, 2013 Configuration menu - View commit details
-
Copy full SHA for 3d32419 - Browse repository at this point
Copy the full SHA 3d32419View commit details
Commits on Aug 29, 2013
-
workqueue: fix possible stall on try_to_grab_pending() of a delayed w…
…ork item commit 3aa6249 upstream. Currently, when try_to_grab_pending() grabs a delayed work item, it leaves its linked work items alone on the delayed_works. The linked work items are always NO_COLOR and will cause future cwq_activate_first_delayed() increase cwq->nr_active incorrectly, and may cause the whole cwq to stall. For example, state: cwq->max_active = 1, cwq->nr_active = 1 one work in cwq->pool, many in cwq->delayed_works. step1: try_to_grab_pending() removes a work item from delayed_works but leaves its NO_COLOR linked work items on it. step2: Later on, cwq_activate_first_delayed() activates the linked work item increasing ->nr_active. step3: cwq->nr_active = 1, but all activated work items of the cwq are NO_COLOR. When they finish, cwq->nr_active will not be decreased due to NO_COLOR, and no further work items will be activated from cwq->delayed_works. the cwq stalls. Fix it by ensuring the target work item is activated before stealing PENDING in try_to_grab_pending(). This ensures that all the linked work items are activated without incorrectly bumping cwq->nr_active. tj: Updated comment and description. Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com> Signed-off-by: Tejun Heo <tj@kernel.org> [lizf: backported to 3.4: adjust context] Signed-off-by: Li Zefan <lizefan@huawei.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 31eafff - Browse repository at this point
Copy the full SHA 31eafffView commit details -
workqueue: consider work function when searching for busy work items
commit a2c1c57 upstream. To avoid executing the same work item concurrenlty, workqueue hashes currently busy workers according to their current work items and looks up the the table when it wants to execute a new work item. If there already is a worker which is executing the new work item, the new item is queued to the found worker so that it gets executed only after the current execution finishes. Unfortunately, a work item may be freed while being executed and thus recycled for different purposes. If it gets recycled for a different work item and queued while the previous execution is still in progress, workqueue may make the new work item wait for the old one although the two aren't really related in any way. In extreme cases, this false dependency may lead to deadlock although it's extremely unlikely given that there aren't too many self-freeing work item users and they usually don't wait for other work items. To alleviate the problem, record the current work function in each busy worker and match it together with the work item address in find_worker_executing_work(). While this isn't complete, it ensures that unrelated work items don't interact with each other and in the very unlikely case where a twisted wq user triggers it, it's always onto itself making the culprit easy to spot. Signed-off-by: Tejun Heo <tj@kernel.org> Reported-by: Andrey Isakov <andy51@gmx.ru> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=51701 [lizf: Backported to 3.4: - Adjust context - Incorporate earlier logging cleanup in process_one_work() from 044c782 ('workqueue: fix checkpatch issues')] Signed-off-by: Li Zefan <lizefan@huawei.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 55e3e1f - Browse repository at this point
Copy the full SHA 55e3e1fView commit details -
zd1201: do not use stack as URB transfer_buffer
commit 1206ff4 upstream. Patch fixes zd1201 not to use stack as URB transfer_buffer. URB buffers need to be DMA-able, which stack is not. Patch is only compile tested. Signed-off-by: Jussi Kivilinna <jussi.kivilinna@iki.fi> Signed-off-by: John W. Linville <linville@tuxdriver.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 523578f - Browse repository at this point
Copy the full SHA 523578fView commit details -
xen/events: initialize local per-cpu mask for all possible events
commit 84ca7a8 upstream. The sizeof() argument in init_evtchn_cpu_bindings() is incorrect resulting in only the first 64 (or 32 in 32-bit guests) ports having their bindings being initialized to VCPU 0. In most cases this does not cause a problem as request_irq() will set the irq affinity which will set the correct local per-cpu mask. However, if the request_irq() is called on a VCPU other than 0, there is a window between the unmasking of the event and the affinity being set were an event may be lost because it is not locally unmasked on any VCPU. If request_irq() is called on VCPU 0 then local irqs are disabled during the window and the race does not occur. Fix this by initializing all NR_EVENT_CHANNEL bits in the local per-cpu masks. Signed-off-by: David Vrabel <david.vrabel@citrix.com> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for a347944 - Browse repository at this point
Copy the full SHA a347944View commit details -
drm/i915: Invalidate TLBs for the rings after a reset
commit 884020b upstream. After any "soft gfx reset" we must manually invalidate the TLBs associated with each ring. Empirically, it seems that a suspend/resume or D3-D0 cycle count as a "soft reset". The symptom is that the hardware would fail to note the new address for its status page, and so it would continue to write the shadow registers and breadcrumbs into the old physical address (now used by something completely different, scary). Whereas the driver would read the new status page and never see any progress, it would appear that the GPU hung immediately upon resume. Based on a patch by naresh kumar kachhi <naresh.kumar.kacchi@intel.com> Reported-by: Thiago Macieira <thiago@kde.org> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=64725 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Tested-by: Thiago Macieira <thiago@kde.org> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 05dd708 - Browse repository at this point
Copy the full SHA 05dd708View commit details -
of: fdt: fix memory initialization for expanded DT
commit 9e40127 upstream. Already existing property flags are filled wrong for properties created from initial FDT. This could cause problems if this DYNAMIC device-tree functions are used later, i.e. properties are attached/detached/replaced. Simply dumping flags from the running system show, that some initial static (not allocated via kzmalloc()) nodes are marked as dynamic. I putted some debug extensions to property_proc_show(..) : .. + if (OF_IS_DYNAMIC(pp)) + pr_err("DEBUG: xxx : OF_IS_DYNAMIC\n"); + if (OF_IS_DETACHED(pp)) + pr_err("DEBUG: xxx : OF_IS_DETACHED\n"); when you operate on the nodes (e.g.: ~$ cat /proc/device-tree/*some_node*) you will see that those flags are filled wrong, basically in most cases it will dump a DYNAMIC or DETACHED status, which is in not true. (BTW. this OF_IS_DETACHED is a own define for debug purposes which which just make a test_bit(OF_DETACHED, &x->_flags) If nodes are dynamic kernel is allowed to kfree() them. But it will crash attempting to do so on the nodes from FDT -- they are not allocated via kzmalloc(). Signed-off-by: Wladislav Wiebe <wladislav.kw@gmail.com> Acked-by: Alexander Sverdlin <alexander.sverdlin@nsn.com> Signed-off-by: Rob Herring <rob.herring@calxeda.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 00d0f98 - Browse repository at this point
Copy the full SHA 00d0f98View commit details -
nilfs2: remove double bio_put() in nilfs_end_bio_write() for BIO_EOPN…
…OTSUPP error commit 2df37a1 upstream. Remove double call of bio_put() in nilfs_end_bio_write() for the case of BIO_EOPNOTSUPP error detection. The issue was found by Dan Carpenter and he suggests first version of the fix too. Signed-off-by: Vyacheslav Dubeyko <slava@dubeyko.com> Reported-by: Dan Carpenter <dan.carpenter@oracle.com> Acked-by: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp> Tested-by: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp> 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>
Configuration menu - View commit details
-
Copy full SHA for 6ed4392 - Browse repository at this point
Copy the full SHA 6ed4392View commit details -
nilfs2: fix issue with counting number of bio requests for BIO_EOPNOT…
…SUPP error detection commit 4bf93b5 upstream. Fix the issue with improper counting number of flying bio requests for BIO_EOPNOTSUPP error detection case. The sb_nbio must be incremented exactly the same number of times as complete() function was called (or will be called) because nilfs_segbuf_wait() will call wail_for_completion() for the number of times set to sb_nbio: do { wait_for_completion(&segbuf->sb_bio_event); } while (--segbuf->sb_nbio > 0); Two functions complete() and wait_for_completion() must be called the same number of times for the same sb_bio_event. Otherwise, wait_for_completion() will hang or leak. Signed-off-by: Vyacheslav Dubeyko <slava@dubeyko.com> Cc: Dan Carpenter <dan.carpenter@oracle.com> Acked-by: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp> Tested-by: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp> 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>
Configuration menu - View commit details
-
Copy full SHA for 03fec5c - Browse repository at this point
Copy the full SHA 03fec5cView commit details -
Hostap: copying wrong data prism2_ioctl_giwaplist()
commit 909bd59 upstream. We want the data stored in "addr" and "qual", but the extra ampersands mean we are copying stack data instead. Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com> Signed-off-by: John W. Linville <linville@tuxdriver.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 807b3da - Browse repository at this point
Copy the full SHA 807b3daView commit details -
libata: apply behavioral quirks to sil3826 PMP
commit 8ffff94 upstream. Fixing support for the Silicon Image 3826 port multiplier, by applying to it the same quirks applied to the Silicon Image 3726. Specifically fixes the repeated timeout/reset process which previously afflicted the 3726, as described from line 290. Slightly based on notes from: https://bugzilla.redhat.com/show_bug.cgi?id=890237 Signed-off-by: Terry Suereth <terry.suereth@gmail.com> Signed-off-by: Tejun Heo <tj@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 41f2be6 - Browse repository at this point
Copy the full SHA 41f2be6View commit details -
SCSI: zfcp: fix lock imbalance by reworking request queue locking
commit d79ff14 upstream. This patch adds wait_event_interruptible_lock_irq_timeout(), which is a straight-forward descendant of wait_event_interruptible_timeout() and wait_event_interruptible_lock_irq(). The zfcp driver used to call wait_event_interruptible_timeout() in combination with some intricate and error-prone locking. Using wait_event_interruptible_lock_irq_timeout() as a replacement nicely cleans up that locking. This rework removes a situation that resulted in a locking imbalance in zfcp_qdio_sbal_get(): BUG: workqueue leaked lock or atomic: events/1/0xffffff00/10 last function: zfcp_fc_wka_port_offline+0x0/0xa0 [zfcp] It was introduced by commit c2af754 "[SCSI] zfcp: Do not wait for SBALs on stopped queue", which had a new code path related to ZFCP_STATUS_ADAPTER_QDIOUP that took an early exit without a required lock being held. The problem occured when a special, non-SCSI I/O request was being submitted in process context, when the adapter's queues had been torn down. In this case the bug surfaced when the Fibre Channel port connection for a well-known address was closed during a concurrent adapter shut-down procedure, which is a rare constellation. This patch also fixes these warnings from the sparse tool (make C=1): drivers/s390/scsi/zfcp_qdio.c:224:12: warning: context imbalance in 'zfcp_qdio_sbal_check' - wrong count at exit drivers/s390/scsi/zfcp_qdio.c:244:5: warning: context imbalance in 'zfcp_qdio_sbal_get' - unexpected unlock Last but not least, we get rid of that crappy lock-unlock-lock sequence at the beginning of the critical section. It is okay to call zfcp_erp_adapter_reopen() with req_q_lock held. Reported-by: Mikulas Patocka <mpatocka@redhat.com> Reported-by: Heiko Carstens <heiko.carstens@de.ibm.com> Signed-off-by: Martin Peschke <mpeschke@linux.vnet.ibm.com> Signed-off-by: Steffen Maier <maier@linux.vnet.ibm.com> Signed-off-by: James Bottomley <JBottomley@Parallels.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 09c7565 - Browse repository at this point
Copy the full SHA 09c7565View commit details -
SCSI: zfcp: fix schedule-inside-lock in scsi_device list loops
commit 924dd58 upstream. BUG: sleeping function called from invalid context at kernel/workqueue.c:2752 in_atomic(): 1, irqs_disabled(): 1, pid: 360, name: zfcperp0.0.1700 CPU: 1 Not tainted 3.9.3+ #69 Process zfcperp0.0.1700 (pid: 360, task: 0000000075b7e080, ksp: 000000007476bc30) <snip> Call Trace: ([<00000000001165de>] show_trace+0x106/0x154) [<00000000001166a0>] show_stack+0x74/0xf4 [<00000000006ff646>] dump_stack+0xc6/0xd4 [<000000000017f3a0>] __might_sleep+0x128/0x148 [<000000000015ece8>] flush_work+0x54/0x1f8 [<00000000001630de>] __cancel_work_timer+0xc6/0x128 [<00000000005067ac>] scsi_device_dev_release_usercontext+0x164/0x23c [<0000000000161816>] execute_in_process_context+0x96/0xa8 [<00000000004d33d8>] device_release+0x60/0xc0 [<000000000048af48>] kobject_release+0xa8/0x1c4 [<00000000004f4bf2>] __scsi_iterate_devices+0xfa/0x130 [<000003ff801b307a>] zfcp_erp_strategy+0x4da/0x1014 [zfcp] [<000003ff801b3caa>] zfcp_erp_thread+0xf6/0x2b0 [zfcp] [<000000000016b75a>] kthread+0xf2/0xfc [<000000000070c9de>] kernel_thread_starter+0x6/0xc [<000000000070c9d8>] kernel_thread_starter+0x0/0xc Apparently, the ref_count for some scsi_device drops down to zero, triggering device removal through execute_in_process_context(), while the lldd error recovery thread iterates through a scsi device list. Unfortunately, execute_in_process_context() decides to immediately execute that device removal function, instead of scheduling asynchronous execution, since it detects process context and thinks it is safe to do so. But almost all calls to shost_for_each_device() in our lldd are inside spin_lock_irq, even in thread context. Obviously, schedule() inside spin_lock_irq sections is a bad idea. Change the lldd to use the proper iterator function, __shost_for_each_device(), in combination with required locking. Occurences that need to be changed include all calls in zfcp_erp.c, since those might be executed in zfcp error recovery thread context with a lock held. Other occurences of shost_for_each_device() in zfcp_fsf.c do not need to be changed (no process context, no surrounding locking). The problem was introduced in Linux 2.6.37 by commit b62a8d9 "[SCSI] zfcp: Use SCSI device data zfcp_scsi_dev instead of zfcp_unit". Reported-by: Christian Borntraeger <borntraeger@de.ibm.com> Signed-off-by: Martin Peschke <mpeschke@linux.vnet.ibm.com> Signed-off-by: Steffen Maier <maier@linux.vnet.ibm.com> Signed-off-by: James Bottomley <JBottomley@Parallels.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 3c30535 - Browse repository at this point
Copy the full SHA 3c30535View commit details -
x86/xen: do not identity map UNUSABLE regions in the machine E820
commit 3bc38cb upstream. If there are UNUSABLE regions in the machine memory map, dom0 will attempt to map them 1:1 which is not permitted by Xen and the kernel will crash. There isn't anything interesting in the UNUSABLE region that the dom0 kernel needs access to so we can avoid making the 1:1 mapping and treat it as RAM. We only do this for dom0, as that is where tboot case shows up. A PV domU could have an UNUSABLE region in its pseudo-physical map and would need to be handled in another patch. This fixes a boot failure on hosts with tboot. tboot marks a region in the e820 map as unusable and the dom0 kernel would attempt to map this region and Xen does not permit unusable regions to be mapped by guests. (XEN) 0000000000000000 - 0000000000060000 (usable) (XEN) 0000000000060000 - 0000000000068000 (reserved) (XEN) 0000000000068000 - 000000000009e000 (usable) (XEN) 0000000000100000 - 0000000000800000 (usable) (XEN) 0000000000800000 - 0000000000972000 (unusable) tboot marked this region as unusable. (XEN) 0000000000972000 - 00000000cf200000 (usable) (XEN) 00000000cf200000 - 00000000cf38f000 (reserved) (XEN) 00000000cf38f000 - 00000000cf3ce000 (ACPI data) (XEN) 00000000cf3ce000 - 00000000d0000000 (reserved) (XEN) 00000000e0000000 - 00000000f0000000 (reserved) (XEN) 00000000fe000000 - 0000000100000000 (reserved) (XEN) 0000000100000000 - 0000000630000000 (usable) Signed-off-by: David Vrabel <david.vrabel@citrix.com> [v1: Altered the patch and description with domU's with UNUSABLE regions] Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for fc431b0 - Browse repository at this point
Copy the full SHA fc431b0View commit details -
Configuration menu - View commit details
-
Copy full SHA for f571d16 - Browse repository at this point
Copy the full SHA f571d16View commit details
Commits on Sep 3, 2013
-
cpufreq: interactive: fix show_target_loads and show_above_hispeed_delay
Remove a trailing whitespace from target_loads and above_hispeed_delay. Problem happens when user-space program tried to restore parameters that saved before changing parameters. In this case was returned error(EINVAL). Change-Id: I5a74e3824602cd6f2b74651adda5ec1b627e61e9 Signed-off-by: Minsung Kim <ms925.kim@samsung.com>
Configuration menu - View commit details
-
Copy full SHA for e116c66 - Browse repository at this point
Copy the full SHA e116c66View commit details
Commits on Sep 4, 2013
-
net: wireless: bcmdhd: Update to version 1.88.42
- Add batched scan implementation Change-Id: I48a36f753597734b2a8865a53f15df30c5ae0d36 Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
Dmitry Shmidt committedSep 4, 2013 Configuration menu - View commit details
-
Copy full SHA for 53c74f2 - Browse repository at this point
Copy the full SHA 53c74f2View commit details -
net: wireless: bcmdhd: Update to version 1.88.45
1. Remove WL_SUPPORT_AUTO_CHANNEL codes 2. add codes for WL_IFACE_COMB_NUM_CHANNELS and WL_CFG80211_P2P_DEV_IF to support concurent mode. (Google Bug : [9892309] support Wifi direct 5GHZ channels) but, remove the WL_IFACE_COM_NUM_CHANELS in Makefile 3. refactoring the codes for hidden ap roaming Signed-off-by: Ecco Park <eccopark@broadcom.com> Conflicts: drivers/net/wireless/bcmdhd/Makefile drivers/net/wireless/bcmdhd/wl_android.c drivers/net/wireless/bcmdhd/wl_cfg80211.c drivers/net/wireless/bcmdhd/wl_cfgp2p.c drivers/net/wireless/bcmdhd/wl_cfgp2p.h Change-Id: If8283f26714196aa971c186c57758c0e64ce87df
Ecco Park authored and Dmitry Shmidt committedSep 4, 2013 Configuration menu - View commit details
-
Copy full SHA for e222a63 - Browse repository at this point
Copy the full SHA e222a63View commit details
Commits on Sep 6, 2013
-
net: wireless: bcmdhd: enable WL_IFACE_COMB_NUM_CHANNELS
Signed-off-by: Ecco Park <eccopark@broadcom.com>
Ecco Park authored and Dmitry Shmidt committedSep 6, 2013 Configuration menu - View commit details
-
Copy full SHA for 1e73c22 - Browse repository at this point
Copy the full SHA 1e73c22View commit details -
USB: gadget: android: fix build
This lets us build the android gadget again. Signed-off-by: Emilio López <turl@linux-sunxi.org>
Configuration menu - View commit details
-
Copy full SHA for ff1c8a9 - Browse repository at this point
Copy the full SHA ff1c8a9View commit details -
video:sunxi:Fix compilation with -j1
__hdle is also defined in bsp_display.h
Configuration menu - View commit details
-
Copy full SHA for 2fba51a - Browse repository at this point
Copy the full SHA 2fba51aView commit details -
Configuration menu - View commit details
-
Copy full SHA for 74e1edd - Browse repository at this point
Copy the full SHA 74e1eddView commit details -
Configuration menu - View commit details
-
Copy full SHA for dc0cc9f - Browse repository at this point
Copy the full SHA dc0cc9fView commit details -
sunxi-usb: fix the alignment calculation for non-aligned buffer worka…
…round Fix alignment calculation that sets alignment off by one. New code uses pointer type sizes for correct calculation. Signed-off-by: Jussi Kivilinna <jussi.kivilinna@iki.fi> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for d2cd3a0 - Browse repository at this point
Copy the full SHA d2cd3a0View commit details -
Add Full Duplex support to SPI (v2)
This patch adds full duplex support to the spi_sunxi driver. v2 - Fix compile error when CONFIG_SUN4I_SPI_NDMA is set. Signed-off-by: Simon Ratcliffe <simon@proatomic.com.au> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 359aa83 - Browse repository at this point
Copy the full SHA 359aa83View commit details -
Rename sunx5i-ir to sunxi-ir as start of unification
No code changes took place and internally the ir driver doesn't call itself sunxi Signed-off-by: Oliver Schinagl <oliver@schinagl.nl> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for bf916ac - Browse repository at this point
Copy the full SHA bf916acView commit details -
All check patch things where cleaned up (except debug printing and line length). Also most/all FGPA references where removed. They where commented out or defined-out anyway. Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for aadbe5b - Browse repository at this point
Copy the full SHA aadbe5bView commit details -
Unify sun4i and sun5i IR driver
This unifies the two drivers into one. It still needs to be compiled per arch. While both IR0 an IR1 are defined for sun4i (2 IR controllers) only IR0 is actually used in the code. Signed-off-by: Oliver Schinagl <oliver@schinagl.nl> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 761568a - Browse repository at this point
Copy the full SHA 761568aView commit details -
Drop sun3i from stage/sunxi-3.4
This patchset drops the sun3i architecture from the kernel tree. The main reason is that it is unsupported, unmaintained and untested. It is in a bitrotten state and nobody uses it anymore. If anybody wants to step up and clean up, unify and maintain sun3i, this is your last chance! Signed-off-by: Oliver Schinagl <oliver@schinagl.nl> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 9f478cc - Browse repository at this point
Copy the full SHA 9f478ccView commit details -
sunxi-8250: Fix uart init for A13
The A13 does not have uart2, but it does have uart3. Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 8bbf194 - Browse repository at this point
Copy the full SHA 8bbf194View commit details -
sunxi-usb: common: make stack spinlock static instead
Signed-off-by: Jussi Kivilinna <jussi.kivilinna@mbnet.fi> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 97729fc - Browse repository at this point
Copy the full SHA 97729fcView commit details -
sunxi-usb: ehci: fix the FIXME for sw_ehci_hc_driver.reset
[v2]: - Use 'ehci-hcd.c:ehci_setup()' as it does about the same that v1 replicated into 'ehci-sunxi.c'. - As ehci_setup() is used, we can also remove duplicate code from sw_ehci_hcd_probe(). Signed-off-by: Jussi Kivilinna <jussi.kivilinna@mbnet.fi> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 3970ca2 - Browse repository at this point
Copy the full SHA 3970ca2View commit details -
sunxi-usb: ohci: convert to use platform device resources
[v2]: - Use SW_USB_OHCI_LEN for resource size Signed-off-by: Jussi Kivilinna <jussi.kivilinna@mbnet.fi> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for afc9d9c - Browse repository at this point
Copy the full SHA afc9d9cView commit details -
sunxi-usb: ehci: convert to use platform device resources
[v2]: - Use SW_USB_EHCI_LEN for resource size Signed-off-by: Jussi Kivilinna <jussi.kivilinna@mbnet.fi> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for e8469c0 - Browse repository at this point
Copy the full SHA e8469c0View commit details -
sunxi-hci: common: remove unused first entries from EHCI&OHCI platfor…
…m device arrays Signed-off-by: Jussi Kivilinna <jussi.kivilinna@mbnet.fi> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for b0ac301 - Browse repository at this point
Copy the full SHA b0ac301View commit details -
sunxi-usb: Fix the length of OHCI and EHCI registers
Signed-off-by: Arokux <arokux@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for 623d7e5 - Browse repository at this point
Copy the full SHA 623d7e5View commit details -
sunxi-usb: Use DEFINE_RES_* macros to simplify code
Signed-off-by: Arokux <arokux@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for d3e93b4 - Browse repository at this point
Copy the full SHA d3e93b4View commit details -
sunxi-usb: Do not check usb_disabled()
usb_disabled() is checked in the {e,o}hci-hcd.c Signed-off-by: Arokux <arokux@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for 0d4b962 - Browse repository at this point
Copy the full SHA 0d4b962View commit details -
sunxi-usb: Remove unused includes
Signed-off-by: Arokux <arokux@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for 4cde7d7 - Browse repository at this point
Copy the full SHA 4cde7d7View commit details -
sunxi-usb: Remove a bunch of no-op functions
Signed-off-by: Arokux <arokux@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for a4c7057 - Browse repository at this point
Copy the full SHA a4c7057View commit details -
sunxi-usb: Remove unused struct members
Signed-off-by: Arokux <arokux@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for 5f1b1af - Browse repository at this point
Copy the full SHA 5f1b1afView commit details -
sunxi-usb: Add a helper function dbg_clocks(...)
Signed-off-by: Arokux <arokux@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for 31cffd7 - Browse repository at this point
Copy the full SHA 31cffd7View commit details -
sunxi-usb: Use defines instead of magic numbers
Signed-off-by: Arokux <arokux@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for 2818563 - Browse repository at this point
Copy the full SHA 2818563View commit details -
sunxi-usb: Simplify code by introducing a local variable
Signed-off-by: Arokux <arokux@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for 46f10eb - Browse repository at this point
Copy the full SHA 46f10ebView commit details -
sunxi-usb: Remove unused struct members
Signed-off-by: Arokux <arokux@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for e73a879 - Browse repository at this point
Copy the full SHA e73a879View commit details -
sunxi-usb: Drop unused defines
Signed-off-by: Arokux <arokux@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for ec9aca1 - Browse repository at this point
Copy the full SHA ec9aca1View commit details -
sunxi-usb: Remove print_ehci_info in favor of print_sw_hci
Signed-off-by: Arokux <arokux@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for f033b02 - Browse repository at this point
Copy the full SHA f033b02View commit details -
sunxi-usb: Remove output of constants from print_sw_info
Signed-off-by: Arokux <arokux@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for c16733c - Browse repository at this point
Copy the full SHA c16733cView commit details -
sunxi-usb: Use defines instead of struct members
Signed-off-by: Arokux <arokux@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for c2b0e6a - Browse repository at this point
Copy the full SHA c2b0e6aView commit details -
sunxi-usb: Move usb includes to source file
Signed-off-by: Arokux <arokux@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for 4806c5d - Browse repository at this point
Copy the full SHA 4806c5dView commit details -
sunxi-usb: Remove useless defines
Signed-off-by: Arokux <arokux@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for 3ce3958 - Browse repository at this point
Copy the full SHA 3ce3958View commit details -
sw_hci_sunxi: Fix OHCI controller not working on sun5i
When allwinner removed the second pair of host controllers from sun5i, they also changed the irq for the first ohci controller from IRQNO_USB3 to IRNO_USB2. Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 48c84ee - Browse repository at this point
Copy the full SHA 48c84eeView commit details -
sunxi-hci: Remove unused defines
Note: These defines are indeed used in musb, but they are defined there. Signed-off-by: Arokux <arokux@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for b5d7a1a - Browse repository at this point
Copy the full SHA b5d7a1aView commit details -
sunxi-hci: Turn info messages into debug ones
Signed-off-by: Arokux <arokux@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for 4b763c1 - Browse repository at this point
Copy the full SHA 4b763c1View commit details -
The function UsbPhyInit is only called for usbc1 and usbc2. There is another UsbPhyInit in musb for usbc0. Signed-off-by: Arokux <arokux@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for 55e8d48 - Browse repository at this point
Copy the full SHA 55e8d48View commit details -
sunxi-hci: Simplify code by using BIT macro
Signed-off-by: Arokux <arokux@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for 231b8b5 - Browse repository at this point
Copy the full SHA 231b8b5View commit details -
musb: add host-mode sunxi support
This patch adds preliminary host-mode SUNXI support to MUSB OTG driver. Platform device is currently defined within 'musb_sunxi', so to use driver you need to built it into kernel image (CONFIG_USB_MUSB_SUNXI=y) or build as module and manually modprobe 'musb_sunxi'. Later patches will move platform device definition to correct place and set up automatic module probing. 2013-08-08: - host-mode appears to work now. - some AllWinner hacks have not been included; still everything appear to run ok (hub, mass-storage, mouse, wifi). Notes: - Allwinner OTG driver is based on musb. * for example, AW driver contains changes from upstream commits 78322c1, f82a689, ae5ad29, etc. - sw_usb has DMA code disabled and PIO only mode is used. - Allwinner/sunxi musb register offsets are different from Texas Instruments'. Currently this is not problem, as musb only supports one "Platform Glue Layer" at a time (see ifdefs in current code). If multiarch is added to musb, musb needs to be changed to support different register mappings on runtime. Signed-off-by: Jussi Kivilinna <jussi.kivilinna@iki.fi> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for d1eb7fe - Browse repository at this point
Copy the full SHA d1eb7feView commit details -
sunxi PWM driver with script.bin support
Here is my modified version of David H. Wilkins PWM driver, changes are: - Added script.bin support for [pwm0_para] and [pwm1_para]: pwm_used, pwm_period, pwm_duty_percent - Added initial setup based on script.bin settings - Removed bug that caused the PWM to pause quickly when changing parameters - Dropped debug/dump functions TODO: - Implement duty_percent=0 to set pwm line to 0 - right now it goes to 100% - Change the script_bin settings loader for pwm_period to allow text based values (100ms, 10hz,...) - Merge h & c file Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 0e012cf - Browse repository at this point
Copy the full SHA 0e012cfView commit details -
sunxi-pwm: Only register devices when enabled in the fex file
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 10176a5 - Browse repository at this point
Copy the full SHA 10176a5View commit details -
sunxi-hci: Simplify and add comments to USBC_Phy_Write
Signed-off-by: Arokux <arokux@gmail.com> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 0415051 - Browse repository at this point
Copy the full SHA 0415051View commit details -
sunxi-hci: Use read*/write* instead of no-op defines
Signed-off-by: Arokux <arokux@gmail.com> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 888b688 - Browse repository at this point
Copy the full SHA 888b688View commit details -
sunxi-hci: Move GPIO init code to the common place
Signed-off-by: Arokux <arokux@gmail.com> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 9542dfe - Browse repository at this point
Copy the full SHA 9542dfeView commit details -
sunxi-codec: Some boards don't have a audio_pa_ctrl pin
So allow using the codec without it. Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 7ebb7ce - Browse repository at this point
Copy the full SHA 7ebb7ceView commit details -
sunxi-usbc0: Add sun7i / A20 support
Since the dma code in the sunxi-usbc0 is not used, the linux-3.3-cb2 sources simply ifdef out some code which does not compile with the new sun7i dma-controller code. Other then that there are no changes, as the usbc0 is identical. Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for eb0bd20 - Browse repository at this point
Copy the full SHA eb0bd20View commit details -
sunxi-usbc0: Misc fixes from sun7i sources
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for c2db3b5 - Browse repository at this point
Copy the full SHA c2db3b5View commit details -
sunxi-usbc0: Stop parsing fex file sections for usbc1 and usbc2
The usbc0 code should not care about the usbc1 and usbc2 sections, making it not care stops the usbc0 init code from errorring out when usbc1 or usbc2 do not have a usb_id_gpio or usb_det_vbus_gpio entry. Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for b65fcc9 - Browse repository at this point
Copy the full SHA b65fcc9View commit details -
A10: brightness on HDMI output
From day one of playing around with my Cubieboard I noticed that the brightness of the picture on HDMI was much too high. Find a quick fix included. This patch does the following: 1.) matrixconv.x3x is initialized always, not just in case out_color_range == DISP_COLOR_RANGE_16_255 2.) matrixconv.x33 is set to zero, because this component should not contribute to the output 3.) matrixresult.x33 is set to 0xe8 instead of 0x400 Especially the last thing opens a few more questions. In chapters 35.5.34, 35.5.36 and 35.5.38 the A10 user manual says, that "the value (of the register) equals to coefficient * 2^4". Now, it appears that (at least my device) wants "coefficient * 2^2". Is the document wrong or are there different hardware revisions ? The current patch only affects RGB with "enhancer" disabled. But if the the other code paths were written assuming "2^4" then another (small) patch is needed. Did someone ever try YUV output ? Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 5c551e6 - Browse repository at this point
Copy the full SHA 5c551e6View commit details -
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 033e160 - Browse repository at this point
Copy the full SHA 033e160View commit details -
musb: sunxi: fix file encoding to utf-8
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for a8b18db - Browse repository at this point
Copy the full SHA a8b18dbView commit details -
musb: sunxi: split 'struct sw_hcd_io' to clock and gpio parts
In preparation for moving Allwinner script/fex parts outside of drivers/usb/musb/ (to arch/arm/plat-sunxi/). Signed-off-by: Jussi Kivilinna <jussi.kivilinna@iki.fi> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for a2155f3 - Browse repository at this point
Copy the full SHA a2155f3View commit details -
musb: sunxi: fix glue pointer for sunxi_musb_exit()
Patch corrects sunxi_musb_exit() to fetch correct glue pointer. Signed-off-by: Jussi Kivilinna <jussi.kivilinna@iki.fi> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 86a7be6 - Browse repository at this point
Copy the full SHA 86a7be6View commit details -
musb: sunxi: split platform_device setup to separate file
Signed-off-by: Jussi Kivilinna <jussi.kivilinna@iki.fi> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 5eac3d5 - Browse repository at this point
Copy the full SHA 5eac3d5View commit details -
musb: sunxi: move gpio to platform side
Move the (troublesome) gpio(/script/fex) parts to platform setup side. Signed-off-by: Jussi Kivilinna <jussi.kivilinna@iki.fi> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 79371a6 - Browse repository at this point
Copy the full SHA 79371a6View commit details -
musb: sunxi: move USBC_ConfigFIFO_Base to platform setup side
This part modifies IO-register that is outside of musb->mregs, so move this part to platform setup side. Signed-off-by: Jussi Kivilinna <jussi.kivilinna@iki.fi> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 085f83a - Browse repository at this point
Copy the full SHA 085f83aView commit details -
musb: sunxi: replace pr_dbg with pr_debug
Signed-off-by: Jussi Kivilinna <jussi.kivilinna@iki.fi> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 2e97e09 - Browse repository at this point
Copy the full SHA 2e97e09View commit details -
musb: sunxi: use DEFINE_RES_* macros
This simplifies the resource definition. Signed-off-by: Jussi Kivilinna <jussi.kivilinna@iki.fi> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 0f31705 - Browse repository at this point
Copy the full SHA 0f31705View commit details -
msub: sunxi: check sunxi arch at runtime
Signed-off-by: Jussi Kivilinna <jussi.kivilinna@iki.fi> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 04bc16e - Browse repository at this point
Copy the full SHA 04bc16eView commit details -
musb: sunxi: remove flushing of pending interrupts from musb_sunxi_en…
…able() Flushing interrupts here prevents peripheral mode from working. Signed-off-by: Jussi Kivilinna <jussi.kivilina@iki.fi> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for c56d918 - Browse repository at this point
Copy the full SHA c56d918View commit details -
musb: sunxi: make peripheral mode work
Patch makes peripheral/device-mode with sunxi-musb in addition to host-mode. Script/fex setup is also read to set up correct mode (with OTG setup wired to device-mode). Signed-off-by: Jussi Kivilinna <jussi.kivilinna@iki.fi> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 51fe43b - Browse repository at this point
Copy the full SHA 51fe43bView commit details -
sunxi: Fix end of nand-iomem reservation being off by one
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 1431f52 - Browse repository at this point
Copy the full SHA 1431f52View commit details -
sunxi-nand: Drop no-op opfn function
Since the nand code uses auto-start, and does not do an explicit start anywhere, the opfn callback only gets called with a SW_DMAOP_START op_code as a result of calling sw_dma_enqueue, and the only place the nand code calls sw_dma_enqueue nanddma_completed_flag is already set to 0 before calling sw_dma_enqueue, turning the opfn into a nop. Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 1552e2d - Browse repository at this point
Copy the full SHA 1552e2dView commit details -
sunxi-ohci: Use a define instead of a magic number
Signed-off-by: Arokux <arokux@gmail.com> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 8648a48 - Browse repository at this point
Copy the full SHA 8648a48View commit details -
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for ec1b9ca - Browse repository at this point
Copy the full SHA ec1b9caView commit details -
sunxi-emac: Use physical rather then virtual address for rx by dma
After the port to the dma_compat.h code sunxi_dma_enqueue should be passed a physical buffer address, but this was overseen. This did not cause any problem in practice because: 1) DMA_CPU_TRRESHOLD is set to 2000, and since ethernet's MTU is 1518 bytes this is never reached, so the dma rx code path is never used 2) Even when the DMA_CPU_TRRESHOLD is lowered, the virt address will work too since the only difference is bit 31 of the address and that seems to be ignored by the address decoder Still this ough to be fixed and that is what this patch does, while at it also switch to using dma_map_single / dma_unmap_single rather then DIY cache flushing. Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 086c3c9 - Browse repository at this point
Copy the full SHA 086c3c9View commit details -
sunxi-nand: move dma-config to dma_for_nand
This groups all dma related code together. Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 3830948 - Browse repository at this point
Copy the full SHA 3830948View commit details -
sunxi-nand: More dead code removal
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 70577d0 - Browse repository at this point
Copy the full SHA 70577d0View commit details -
sunxi-nand: Make init a bit more quiet
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for b5312a4 - Browse repository at this point
Copy the full SHA b5312a4View commit details -
sunxi-nand: Remove __cpuc_flush_dcache_area call
All callers of NAND_Config_Start_DMA call dma_map_single on the buffer before calling NAND_Config_Start_DMA, which already takes care of cache flushing, so the extra explicit flush is not necessary. Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for a8f82bc - Browse repository at this point
Copy the full SHA a8f82bcView commit details -
sunxi-nand: Add support for sun7i / A20
After thoroughly reviewing a diff between the sun5i and sun7i sources I've come to the conclusion that the nand controller is identical. So all this patch does is use dma_compat.h to make the sunxi-nand dma code work with both sun4i/sun5i and sun7i. Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 38cae4f - Browse repository at this point
Copy the full SHA 38cae4fView commit details -
sunxi-key*: Improve Kconfig help text
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 6c8be26 - Browse repository at this point
Copy the full SHA 6c8be26View commit details -
sun4i-keyboard: Make loading controlled through fex
Wether or not a board actually has the evaluation board style tablet buttons hooked up to adc0 through a resistor network is something which cannot be autodetected and thus typically belongs in the fex file. Note this patch makes the new behavior of not registering the input-dev unless there is: [tabletkeys_para] tabletkeys_used = 1 In the fex-file configurable from Kconfig and default its to off, for compatility with old setups / fex files. Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 922efe9 - Browse repository at this point
Copy the full SHA 922efe9View commit details -
sun4i-keyboard: Allow overriding of key-codes from fex file
This is needed for IE the a13-olinuxino which has the enter key in the place where the allwinner evaluation board has the search key. Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 82ba928 - Browse repository at this point
Copy the full SHA 82ba928View commit details -
sunxi-mci: Add support for sun5i
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 7bb42b4 - Browse repository at this point
Copy the full SHA 7bb42b4View commit details -
mmc: make MMC_SUNXI depend on !MMC_SUNXI_NEW to avoid conflicts
Signed-off-by: Alejandro Mery <amery@geeks.cl>
Configuration menu - View commit details
-
Copy full SHA for 7e1c5ae - Browse repository at this point
Copy the full SHA 7e1c5aeView commit details -
Fix 2GB memory issue for allwinner A20 platform
The following patch is based on hans latest sunxi-3.4 branch From 4e56df0aa856425a988ed3ff962a246e4976fd1c Mon Sep 17 00:00:00 2001 From: benn <benn@cubietech.com> Date: Thu, 22 Aug 2013 15:44:01 +0800 Subject: [PATCH 1/2] disp: fix 2GB memory issue When there is 2GB memory on allwinner A20 platform, the bus address is differrent from the physical address for display controller. To solve such a problem, we introduce the following macros to do the translation Signed-off-by: benn <benn@cubietech.com> Signed-off-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Henrik Nordstrom <henrik@henriknordstrom.net>
Configuration menu - View commit details
-
Copy full SHA for 482ce7a - Browse repository at this point
Copy the full SHA 482ce7aView commit details -
mali: add ca7-virtex820-m400-2 platform for allwinner a20
This patch have benn tested on cubieboard2/cubietruck(2GB memroy) 1. add new platform 2. fix 2GB memory issue Signed-off-by: benn <benn@cubietech.com> Signed-off-by: Henrik Nordstrom <henrik@henriknordstrom.net>
Configuration menu - View commit details
-
Copy full SHA for cba0a9b - Browse repository at this point
Copy the full SHA cba0a9bView commit details -
drivers/gpu/mali/mali/arch drivers/gpu/mali/ump/arch Signed-off-by: benn <benn@cubietech.com> Signed-off-by: Henrik Nordstrom <henrik@henriknordstrom.net>
Configuration menu - View commit details
-
Copy full SHA for 839a527 - Browse repository at this point
Copy the full SHA 839a527View commit details -
sun4i_dev_ace: Fix wrong irqno at a20
Signed-off-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Henrik Nordstrom <henrik@henriknordstrom.net>
Configuration menu - View commit details
-
Copy full SHA for 204919b - Browse repository at this point
Copy the full SHA 204919bView commit details -
gpio: sunxi: Add GPIO support to A20
Also supports GPIO IRQs Signed-off-by: Ryan Press <ryan@presslab.us> Signed-off-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Henrik Nordstrom <henrik@henriknordstrom.net>
Configuration menu - View commit details
-
Copy full SHA for da621ae - Browse repository at this point
Copy the full SHA da621aeView commit details -
gpio: sunxi: Fix GPIO to_irq bug with some drivers
Some drivers (like rotary_encoder) will ask for the IRQ before requesting the GPIO. This fails because the eint hasn't been set up yet. This patch requests the eint every time. Signed-off-by: Ryan Press <ryan@presslab.us> Signed-off-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Henrik Nordstrom <henrik@henriknordstrom.net>
Configuration menu - View commit details
-
Copy full SHA for dc010a6 - Browse repository at this point
Copy the full SHA dc010a6View commit details -
mali: fix compilation for sun[45]i
Signed-off-by: Alejandro Mery <amery@geeks.cl>
Configuration menu - View commit details
-
Copy full SHA for c27e1d9 - Browse repository at this point
Copy the full SHA c27e1d9View commit details -
usb:sunxi:Fix "device not recognized" problem during android boot (3.4)
3.4 requires this fix top of 1ef1517. Now behavior is same as with 3.0. Signed-off-by: Jari Helaakoski <tekkuli@gmail.com> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 44a6e1b - Browse repository at this point
Copy the full SHA 44a6e1bView commit details -
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 0396055 - Browse repository at this point
Copy the full SHA 0396055View commit details -
mali: Fix regression on sun4i and sun5i caused by adding sun7i support
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 641f0da - Browse repository at this point
Copy the full SHA 641f0daView commit details -
serial: sunxi: Fix kernel stall
When opening/closing a serial port many times the kernel will eventually crash with a 'rcu_preempt self-detected stall'. Adding some code from the Allwinner source fixes this issue. Also rename some functions as the core seems different than the DesignWare core. Signed-off-by: Ryan Press <ryan@presslab.us> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 2ca2d62 - Browse repository at this point
Copy the full SHA 2ca2d62View commit details -
usb:host:ehci-sunxi:Fix usb resume.
This patch fixes usb functionality after android resume. Fix was found from original Allwinner codes. Signed-off-by: Jari Helaakoski <tekkuli@gmail.com> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 1e8c5d7 - Browse repository at this point
Copy the full SHA 1e8c5d7View commit details
Commits on Sep 8, 2013
-
jfs: fix readdir cookie incompatibility with NFSv4
commit 4451244 upstream. NFSv4 reserves readdir cookie values 0-2 for special entries (. and ..), but jfs allows a value of 2 for a non-special entry. This incompatibility can result in the nfs client reporting a readdir loop. This patch doesn't change the value stored internally, but adds one to the value exposed to the iterate method. Signed-off-by: Dave Kleikamp <dave.kleikamp@oracle.com> [bwh: Backported to 3.2: - Adjust context - s/ctx->pos/filp->f_pos/] Tested-by: Christian Kujau <lists@nerdbynature.de> Signed-off-by: Ben Hutchings <ben@decadent.org.uk> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for e446ef9 - Browse repository at this point
Copy the full SHA e446ef9View commit details -
ALSA: opti9xx: Fix conflicting driver object name
commit fb61549 upstream. The recent commit to delay the release of kobject triggered NULL dereferences of opti9xx drivers. The cause is that all snd-opti92x-ad1848, snd-opti92x-cs4231 and snd-opti93x drivers register the PnP card driver with the very same name, and also snd-opti92x-ad1848 and -cs4231 drivers register the ISA driver with the same name, too. When these drivers are built in, quick "register-release-and-re-register" actions occur, and this results in Oops because of the same name is assigned to the kobject. The fix is simply to assign individual names. As a bonus, by using KBUILD_MODNAME, the patch reduces more lines than it adds. The fix is based on the suggestion by Russell King. Reported-and-tested-by: Fengguang Wu <fengguang.wu@intel.com> Signed-off-by: Takashi Iwai <tiwai@suse.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for aa51891 - Browse repository at this point
Copy the full SHA aa51891View commit details -
powerpc: Work around gcc miscompilation of __pa() on 64-bit
commit bdbc29c upstream. On 64-bit, __pa(&static_var) gets miscompiled by recent versions of gcc as something like: addis 3,2,.LANCHOR1+4611686018427387904@toc@ha addi 3,3,.LANCHOR1+4611686018427387904@toc@l This ends up effectively ignoring the offset, since its bottom 32 bits are zero, and means that the result of __pa() still has 0xC in the top nibble. This happens with gcc 4.8.1, at least. To work around this, for 64-bit we make __pa() use an AND operator, and for symmetry, we make __va() use an OR operator. Using an AND operator rather than a subtraction ends up with slightly shorter code since it can be done with a single clrldi instruction, whereas it takes three instructions to form the constant (-PAGE_OFFSET) and add it on. (Note that MEMORY_START is always 0 on 64-bit.) Signed-off-by: Paul Mackerras <paulus@samba.org> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 7a72233 - Browse repository at this point
Copy the full SHA 7a72233View commit details -
powerpc/hvsi: Increase handshake timeout from 200ms to 400ms.
commit d220980 upstream. This solves a problem observed in kexec'ed kernel where 200ms timeout is too short and bootconsole fails to initialize. Console did eventually become workable but much later into the boot process. Observed timeout was around 260ms, but I decided to make it a little bigger for more reliability. This has been tested on Power7 machine with Petitboot as a primary bootloader and PowerNV firmware. Signed-off-by: Eugene Surovegin <surovegin@google.com> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 2ad23b7 - Browse repository at this point
Copy the full SHA 2ad23b7View commit details -
commit a8f28cf upstream. Building regmap.o triggers this GCC warning: drivers/base/regmap/regmap.c: In function ‘regmap_raw_read’: drivers/base/regmap/regmap.c:1172:6: warning: ‘ret’ may be used uninitialized in this function [-Wmaybe-uninitialized] Long story short: Jakub Jelinek pointed out that there is a type mismatch between 'num' in regmap_volatile_range() and 'val_count' in regmap_raw_read(). And indeed, converting 'num' to the type of 'val_count' (ie, size_t) makes this warning go away. Signed-off-by: Paul Bolle <pebolle@tiscali.nl> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for ff289c1 - Browse repository at this point
Copy the full SHA ff289c1View commit details -
drivers/base/memory.c: fix show_mem_removable() to handle missing sec…
…tions commit 21ea9f5 upstream. "cat /sys/devices/system/memory/memory*/removable" crashed the system. The problem is that show_mem_removable() is passing a bad pfn to is_mem_section_removable(), which causes if (!node_online(page_to_nid(page))) to blow up. Why is it passing in a bad pfn? The reason is that show_mem_removable() will loop sections_per_block times. sections_per_block is 16, but mem->section_count is 8, indicating holes in this memory block. Checking that the memory section is present before checking to see if the memory section is removable fixes the problem. harp5-sys:~ # cat /sys/devices/system/memory/memory*/removable 0 1 1 1 1 1 1 1 1 1 1 1 1 1 BUG: unable to handle kernel paging request at ffffea00c3200000 IP: [<ffffffff81117ed1>] is_pageblock_removable_nolock+0x1/0x90 PGD 83ffd4067 PUD 37bdfce067 PMD 0 Oops: 0000 [#1] SMP Modules linked in: autofs4 binfmt_misc rdma_ucm rdma_cm iw_cm ib_addr ib_srp scsi_transport_srp scsi_tgt ib_ipoib ib_cm ib_uverbs ib_umad iw_cxgb3 cxgb3 mdio mlx4_en mlx4_ib ib_sa mlx4_core ib_mthca ib_mad ib_core fuse nls_iso8859_1 nls_cp437 vfat fat joydev loop hid_generic usbhid hid hwperf(O) numatools(O) dm_mod iTCO_wdt ipv6 iTCO_vendor_support igb i2c_i801 ioatdma i2c_algo_bit ehci_pci pcspkr lpc_ich i2c_core ehci_hcd ptp sg mfd_core dca rtc_cmos pps_core mperf button xhci_hcd sd_mod crc_t10dif usbcore usb_common scsi_dh_emc scsi_dh_hp_sw scsi_dh_alua scsi_dh_rdac scsi_dh gru(O) xvma(O) xfs crc32c libcrc32c thermal sata_nv processor piix mptsas mptscsih scsi_transport_sas mptbase megaraid_sas fan thermal_sys hwmon ext3 jbd ata_piix ahci libahci libata scsi_mod CPU: 4 PID: 5991 Comm: cat Tainted: G O 3.11.0-rc5-rja-uv+ #10 Hardware name: SGI UV2000/ROMLEY, BIOS SGI UV 2000/3000 series BIOS 01/15/2013 task: ffff88081f034580 ti: ffff880820022000 task.ti: ffff880820022000 RIP: 0010:[<ffffffff81117ed1>] [<ffffffff81117ed1>] is_pageblock_removable_nolock+0x1/0x90 RSP: 0018:ffff880820023df8 EFLAGS: 00010287 RAX: 0000000000040000 RBX: ffffea00c3200000 RCX: 0000000000000004 RDX: ffffea00c30b0000 RSI: 00000000001c0000 RDI: ffffea00c3200000 RBP: ffff880820023e38 R08: 0000000000000000 R09: 0000000000000001 R10: 0000000000000000 R11: 0000000000000001 R12: ffffea00c33c0000 R13: 0000160000000000 R14: 6db6db6db6db6db7 R15: 0000000000000001 FS: 00007ffff7fb2700(0000) GS:ffff88083fc80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffea00c3200000 CR3: 000000081b954000 CR4: 00000000000407e0 Call Trace: show_mem_removable+0x41/0x70 dev_attr_show+0x2a/0x60 sysfs_read_file+0xf7/0x1c0 vfs_read+0xc8/0x130 SyS_read+0x5d/0xa0 system_call_fastpath+0x16/0x1b Signed-off-by: Russ Anderson <rja@sgi.com> Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com> Cc: Yinghai Lu <yinghai@kernel.org> Reviewed-by: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.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>
Configuration menu - View commit details
-
Copy full SHA for 6e99f32 - Browse repository at this point
Copy the full SHA 6e99f32View commit details -
drm/vmwgfx: Split GMR2_REMAP commands if they are to large
commit 6e4dcff upstream. This fixes the piglit test texturing/max-texture-size causing the VM to die due to a too large SVGA command. Signed-off-by: Jakob Bornecrantz <jakob@vmware.com> Reviewed-by: Biran Paul <brianp@vmware.com> Reviewed-by: Zack Rusin <zackr@vmware.com> Signed-off-by: Dave Airlie <airlied@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 73bc40b - Browse repository at this point
Copy the full SHA 73bc40bView commit details -
drm/i915: ivb: fix edp voltage swing reg val
commit 77fa4cb upstream. Fix the typo introduced in commit 1a2eb46 Author: Keith Packard <keithp@keithp.com> Date: Wed Nov 16 16:26:07 2011 -0800 drm/i915: Hook up Ivybridge eDP This fixes eDP link-training failures and cases where all voltage swing /pre-emphasis levels were tried and failed during clock recovery and - as a fallback - we go on to do channel equalization with the last voltage swing/pre-emphasis level which will succeed. Both issues can lead to a blank screen. v2: - improve commit message Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=64880 Tested-by: Jeremy Moles <cubicool@gmail.com> Signed-off-by: Imre Deak <imre.deak@intel.com> Reviewed-by: Paulo Zanoni <paulo.r.zanoni@intel.com> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 5817e3c - Browse repository at this point
Copy the full SHA 5817e3cView commit details -
SUNRPC: Fix memory corruption issue on 32-bit highmem systems
commit 347e223 upstream. Some architectures, such as ARM-32 do not return the same base address when you call kmap_atomic() twice on the same page. This causes problems for the memmove() call in the XDR helper routine "_shift_data_right_pages()", since it defeats the detection of overlapping memory ranges, and has been seen to corrupt memory. The fix is to distinguish between the case where we're doing an inter-page copy or not. In the former case of we know that the memory ranges cannot possibly overlap, so we can additionally micro-optimise by replacing memmove() with memcpy(). Reported-by: Mark Young <MYoung@nvidia.com> Reported-by: Matt Craighead <mcraighead@nvidia.com> Cc: Bruce Fields <bfields@fieldses.org> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com> Tested-by: Matt Craighead <mcraighead@nvidia.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 52b331e - Browse repository at this point
Copy the full SHA 52b331eView commit details -
ath9k_htc: Restore skb headroom when returning skb to mac80211
commit d2e9fc1 upstream. ath9k_htc adds padding between the 802.11 header and the payload during TX by moving the header. When handing the frame back to mac80211 for TX status handling the header is not moved back into its original position. This can result in a too small skb headroom when entering ath9k_htc again (due to a soft retransmission for example) causing an skb_under_panic oops. Fix this by moving the 802.11 header back into its original position before returning the frame to mac80211 as other drivers like rt2x00 or ath5k do. Reported-by: Marc Kleine-Budde <mkl@blackshift.org> Signed-off-by: Helmut Schaa <helmut.schaa@googlemail.com> Tested-by: Marc Kleine-Budde <mkl@blackshift.org> Signed-off-by: Marc Kleine-Budde <mkl@blackshift.org> Signed-off-by: John W. Linville <linville@tuxdriver.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 837049a - Browse repository at this point
Copy the full SHA 837049aView commit details -
iwl4965: fix rfkill set state regression
commit b2fcc0a upstream. My current 3.11 fix: commit 788f7a5 Author: Stanislaw Gruszka <sgruszka@redhat.com> Date: Thu Aug 1 12:07:55 2013 +0200 iwl4965: reset firmware after rfkill off broke rfkill notification to user-space . I missed that bug, because I compiled without CONFIG_RFKILL, sorry about that. Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com> Signed-off-by: John W. Linville <linville@tuxdriver.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 32cdf90 - Browse repository at this point
Copy the full SHA 32cdf90View commit details -
ACPI / EC: Add ASUSTEK L4R to quirk list in order to validate ECDT
commit 524f42f upstream. The ECDT of ASUSTEK L4R doesn't provide correct command and data I/O ports. The DSDT provides the correct information instead. For this reason, add this machine to quirk list for ECDT validation and use the EC information from the DSDT. [rjw: Changelog] References: https://bugzilla.kernel.org/show_bug.cgi?id=60765 Reported-and-tested-by: Daniele Esposti <expo@expobrain.net> Signed-off-by: Lan Tianyu <tianyu.lan@intel.com> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for 3f661fb - Browse repository at this point
Copy the full SHA 3f661fbView commit details -
target: Fix trailing ASCII space usage in INQUIRY vendor+model
commit ee60bdd upstream. This patch fixes spc_emulate_inquiry_std() to add trailing ASCII spaces for INQUIRY vendor + model fields following SPC-4 text: "ASCII data fields described as being left-aligned shall have any unused bytes at the end of the field (i.e., highest offset) and the unused bytes shall be filled with ASCII space characters (20h)." This addresses a problem with Falconstor NSS multipathing. Reported-by: Tomas Molota <tomas.molota@lightstorm.sk> Signed-off-by: Nicholas Bellinger <nab@linux-iscsi.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for e51c435 - Browse repository at this point
Copy the full SHA e51c435View commit details -
SCSI: sg: Fix user memory corruption when SG_IO is interrupted by a s…
…ignal commit 35dc248 upstream. There is a nasty bug in the SCSI SG_IO ioctl that in some circumstances leads to one process writing data into the address space of some other random unrelated process if the ioctl is interrupted by a signal. What happens is the following: - A process issues an SG_IO ioctl with direction DXFER_FROM_DEV (ie the underlying SCSI command will transfer data from the SCSI device to the buffer provided in the ioctl) - Before the command finishes, a signal is sent to the process waiting in the ioctl. This will end up waking up the sg_ioctl() code: result = wait_event_interruptible(sfp->read_wait, (srp_done(sfp, srp) || sdp->detached)); but neither srp_done() nor sdp->detached is true, so we end up just setting srp->orphan and returning to userspace: srp->orphan = 1; write_unlock_irq(&sfp->rq_list_lock); return result; /* -ERESTARTSYS because signal hit process */ At this point the original process is done with the ioctl and blithely goes ahead handling the signal, reissuing the ioctl, etc. - Eventually, the SCSI command issued by the first ioctl finishes and ends up in sg_rq_end_io(). At the end of that function, we run through: write_lock_irqsave(&sfp->rq_list_lock, iflags); if (unlikely(srp->orphan)) { if (sfp->keep_orphan) srp->sg_io_owned = 0; else done = 0; } srp->done = done; write_unlock_irqrestore(&sfp->rq_list_lock, iflags); if (likely(done)) { /* Now wake up any sg_read() that is waiting for this * packet. */ wake_up_interruptible(&sfp->read_wait); kill_fasync(&sfp->async_qp, SIGPOLL, POLL_IN); kref_put(&sfp->f_ref, sg_remove_sfp); } else { INIT_WORK(&srp->ew.work, sg_rq_end_io_usercontext); schedule_work(&srp->ew.work); } Since srp->orphan *is* set, we set done to 0 (assuming the userspace app has not set keep_orphan via an SG_SET_KEEP_ORPHAN ioctl), and therefore we end up scheduling sg_rq_end_io_usercontext() to run in a workqueue. - In workqueue context we go through sg_rq_end_io_usercontext() -> sg_finish_rem_req() -> blk_rq_unmap_user() -> ... -> bio_uncopy_user() -> __bio_copy_iov() -> copy_to_user(). The key point here is that we are doing copy_to_user() on a workqueue -- that is, we're on a kernel thread with current->mm equal to whatever random previous user process was scheduled before this kernel thread. So we end up copying whatever data the SCSI command returned to the virtual address of the buffer passed into the original ioctl, but it's quite likely we do this copying into a different address space! As suggested by James Bottomley <James.Bottomley@hansenpartnership.com>, add a check for current->mm (which is NULL if we're on a kernel thread without a real userspace address space) in bio_uncopy_user(), and skip the copy if we're on a kernel thread. There's no reason that I can think of for any caller of bio_uncopy_user() to want to do copying on a kernel thread with a random active userspace address space. Huge thanks to Costa Sapuntzakis <costa@purestorage.com> for the original pointer to this bug in the sg code. Signed-off-by: Roland Dreier <roland@purestorage.com> Tested-by: David Milburn <dmilburn@redhat.com> Cc: Jens Axboe <axboe@kernel.dk> Signed-off-by: James Bottomley <JBottomley@Parallels.com> [lizf: backported to 3.4: - Use __bio_for_each_segment() instead of bio_for_each_segment_all()] Signed-off-by: Li Zefan <lizefan@huawei.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Configuration menu - View commit details
-
Copy full SHA for d3ba218 - Browse repository at this point
Copy the full SHA d3ba218View commit details -
Configuration menu - View commit details
-
Copy full SHA for 58055a0 - Browse repository at this point
Copy the full SHA 58055a0View commit details
Commits on Sep 9, 2013
-
net: wireless: bcmdhd: Update Location Service code
updated the dhd_pno.c based on new firmware which will be released today. updated the wl_anroid.c based on Robert's requirement Signed-off-by: Ecco Park <eccopark@broadcom.com> Conflicts: drivers/net/wireless/bcmdhd/common/include/proto/bcmevent.h Change-Id: I270755fe4c041ea1282afaed9d120c9b83c2bc0c
Ecco Park authored and Dmitry Shmidt committedSep 9, 2013 Configuration menu - View commit details
-
Copy full SHA for 6735234 - Browse repository at this point
Copy the full SHA 6735234View commit details
Commits on Sep 11, 2013
-
sunxi:usb: Fix OTG Kconfig selection
After sunxi_sub was merged otg was disabled by default this patch fixes this Signed-off-by: Alexsey Shestacov <wingrime@linux-sunxi.org>
Configuration menu - View commit details
-
Copy full SHA for 417364c - Browse repository at this point
Copy the full SHA 417364cView commit details -
snd:sunxi: Make sunxi audio builds by default
After sound merge sunxi sound was disabled by default in kconifg this patch make seamless config update possible Signed-off-by: Alexsey Shestacov <wingrime@linux-sunxi.org>
Configuration menu - View commit details
-
Copy full SHA for cff8577 - Browse repository at this point
Copy the full SHA cff8577View commit details -
Signed-off-by: Alejandro Mery <amery@geeks.cl>
Configuration menu - View commit details
-
Copy full SHA for 6f21438 - Browse repository at this point
Copy the full SHA 6f21438View commit details
Commits on Sep 12, 2013
-
Configuration menu - View commit details
-
Copy full SHA for 6554b8c - Browse repository at this point
Copy the full SHA 6554b8cView commit details -
Merge tag 'v3.4.61' into reference-3.4
This is the 3.4.61 stable release
Configuration menu - View commit details
-
Copy full SHA for 5edd488 - Browse repository at this point
Copy the full SHA 5edd488View commit details -
Configuration menu - View commit details
-
Copy full SHA for 5dda514 - Browse repository at this point
Copy the full SHA 5dda514View commit details
Commits on Sep 16, 2013
-
pwm-sunxi: pwm-sunxi.h is a local include
use correct #include statement for local includes. Was breaking in-tree builds.
Configuration menu - View commit details
-
Copy full SHA for 9ee9fc5 - Browse repository at this point
Copy the full SHA 9ee9fc5View commit details