boot_time is represented as a struct timespec.
struct timespec and CURRENT_TIME are not y2038 safe.
Overall, the plan is to use timespec64 and ktime_t for
all internal kernel representation of timestamps.
CURRENT_TIME will also be removed.
boot_time is used to construct the nfs client boot verifie
3.2.82-rc1 review patch. If anyone has any objections, please let me know.
--
From: Dmitry Torokhov
commit 226ba707744a51acb4244724e09caacb1d96aed9 upstream.
The touchpad in HP Pavilion 14-ab057ca reports it's version as 12 and
according to Elan both 11 and 12 are valid IC typ
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Mark Brown
commit 68b356eb3d9f5e38910fb62e22a78e2a18d544ae upstream.
Currently the ad7266 driver treats any failure to get vref as though the
regulator were not present but this means that if
jfs uses nanosecond granularity for filesystem timestamps.
Only this assignment is not using nanosecond granularity.
Use current_time() to get the right granularity.
Signed-off-by: Deepa Dinamani
Cc: Dave Kleikamp
Acked-by: Dave Kleikamp
Reviewed-by: Arnd Bergmann
Cc: jfs-discuss...@lists.sour
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Martin Schwidefsky
commit 532c34b5fbf1687df63b3fcd5b2846312ac943c6 upstream.
The sclp_ctl_ioctl_sccb function uses two copy_from_user calls to
retrieve the sclp request from user space. The fi
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Lars Persson
commit 4d46a67a3eb827ccf1125959936fd51ba318dabc upstream.
The lazy cache flushing implemented in the MIPS kernel suffers from a
race condition that is exposed by do_set_pte() in m
On 08/10/2016 09:18 AM, Enric Balletbo i Serra wrote:
This patch adds and entry to the sysfs to start firmware upload process
on the specified device with the requested firmware.
The uploading of the firmware needs only to happen once per firmware
upgrade, as the firmware is stored in persistent
Hi Christoph,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 118253a593bd1c57de2d1193df1ccffe1abe745b
commit: abec1a806e0c3cf168999667d5fb6218398ef12a percpu: Make __verify_pcu_ptr
handle per cpu pointers to arrays
On Sat 13-08-16 13:34:29, Mikulas Patocka wrote:
>
>
> On Fri, 12 Aug 2016, Michal Hocko wrote:
>
> > On Thu 04-08-16 14:49:41, Mikulas Patocka wrote:
> >
> > > On Wed, 3 Aug 2016, Michal Hocko wrote:
> > >
> > > > But the device congestion is not the only condition required for the
> > > > th
This is in preparation for the change that transitions
filesystem timestamps to use 64 bit time and hence make
them y2038 safe.
CURRENT_TIME macro will be deleted before merging the
aforementioned patch.
Filesystems will use current_time() instead of
CURRENT_TIME.
Use ktime_get_real_seconds() her
This patch adds new function f_uac1_newapi that
uses recently created u_audio api. This makes
f_uac1_newapi implementation much simpler by
reusing existing u_audio core utilities.
This also drops previous f_uac1 approach (write
audio samples directly to existing ALSA sound
card) and moves to more
CURRENT_TIME is not y2038 safe.
The macro will be deleted and all the references to it
will be replaced by ktime_get_* apis.
struct timespec is also not y2038 safe.
Retain timespec for timestamp representation here as ceph
uses it internally everywhere.
These references will be changed to use stru
On Sun, 14 Aug 2016, Tom Yan wrote:
On 14 August 2016 at 18:07, Tom Yan wrote:
On 14 August 2016 at 18:01, Pavel Machek wrote:
Since SATA support was merged, certainly since v2.4, and from way
before /dev/disk/by-id existed.
I have no idea how "SATA before USB" had been done in the past (
CURRENT_TIME is not y2038 safe.
Replace it with ktime_get_real_ts64().
Inode time formats are already 64 bit long and
accommodates time64_t.
Signed-off-by: Deepa Dinamani
Cc: Evgeniy Dushistov
---
fs/ufs/ialloc.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/fs/ufs/i
CURRENT_TIME_SEC is not y2038 safe. current_time() will
be transitioned to use 64 bit time along with vfs in a
separate patch.
There is no plan to transition CURRENT_TIME_SEC to use
y2038 safe time interfaces.
current_time() returns timestamps according to the
granularities set in the inode's supe
CURRENT_TIME is not y2038 safe.
CURRENT_TIME macro is also not appropriate for filesystems
as it doesn't use the right granularity for filesystem
timestamps.
Logical Volume Integrity format is described to have the
same timestamp format for "Recording Date and time" as
the other [a,c,m]timestamps
From: Michal Hocko
throttle_vm_writeout has been introduced back in 2005 to fix OOMs caused
by excessive pageout activity during the reclaim. Too many pages could
be put under writeback therefore LRUs would be full of unreclaimable pages
until the IO completes and in turn the OOM killer could be
The current_fs_time() api is being changed to use vfs
struct inode* as an argument instead of struct super_block*.
Set the new mds client request r_stamp field using
ktime_get_real_ts() instead of using current_fs_time().
Also, since r_stamp is used as mtime on the server, use
timespec_trunc() to
btrfs_root_item maintains the ctime for root updates.
This is not part of vfs_inode.
Since current_time() uses struct inode* as an argument
as Linus suggested, this cannot be used to update root
times unless, we modify the signature to use inode.
Since btrfs uses nanosecond time granularity, it c
CURRENT_TIME is not y2038 safe.
Use y2038 safe ktime_get_real_seconds() here for timestamps.
struct heartbeat_block's hb_seq and deletetion time are already
64 bits wide and accommodate times beyond y2038.
Also use y2038 safe ktime_get_real_ts64() for on disk inode
timestamps.
These are also wide
Simplify f_uac2 by removing platform driver/device
creation; use composite's usb_gadget device as
parent for sound card and for debug prints.
This removes extra layer of code without any functional
change.
Signed-off-by: Ruslan Bilovol
---
drivers/usb/gadget/function/f_uac2.c | 107 +
Btw, why hasn't this been CC'd to linux-scsi at the very least? The
SCSI disk (sd) driver is obviously the sociopath here. It should
really differentiate disks from libata and usb-storage/uas, and wait
for at least a minute to see if there's gonna be an ATA drive popping
up before enumerating disks
3.2.82-rc1 review patch. If anyone has any objections, please let me know.
--
From: William Breathitt Gray
commit 32a5a0c047343b11f581f663a2309cf43d13466f upstream.
The isa_bus_init function must be called before drivers which utilize
the ISA bus driver are registered. A race
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Johannes Thumshirn
commit 305c2e71b3d733ec065cb716c76af7d554bd5571 upstream.
Now that we've done a more comprehensive fix with the intermediate
target state we can remove the previous hack int
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Ricky Liang
commit affa80bd97f7ca282d1faa91667b3ee9e4c590e6 upstream.
When running a 32-bit userspace on a 64-bit kernel, the UI_SET_PHYS
ioctl needs to be treated with special care, as it has
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Kangjie Lu
commit 9a47e9cff994f37f7f0dbd9ae23740d0f64f9fe6 upstream.
The stack object “r1” has a total size of 32 bytes. Its field
“event” and “val” both contain 4 bytes padding. These 8 bytes
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Jason Gunthorpe
commit 8c5122e45a10a9262f872b53f151a592e870f905 upstream.
When this code was reworked for IBoE support the order of assignments
for the sl_tclass_flowlabel got flipped around r
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Geert Uytterhoeven
commit 834392a7d92677ff2bdc1c709b1171ee585b55c9 upstream.
uart_write_console() never existed, not even when the "new
uart_write_console function" was documented.
Fixes: 67a
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Hari Bathini
commit 8ed8ab40047a570fdd8043a40c104a57248dd3fd upstream.
Some of the interrupt vectors on 64-bit POWER server processors are only
32 bytes long (8 instructions), which is not eno
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Wolfgang Grandegger
commit 43200a4480cbbe660309621817f54cbb93907108 upstream.
At high bus load it could happen that "at91_poll()" enters with all RX
message boxes filled up. If then at the end
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Florian Westphal
commit 0188346f21e6546498c2a0f84888797ad4063fc5 upstream.
Always returned 0.
Signed-off-by: Florian Westphal
Signed-off-by: Pablo Neira Ayuso
Signed-off-by: Ben Hutchings
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Wei Fang
commit 72d8c36ec364c82bf1bf0c64dfa1041cfaf139f7 upstream.
sas_ata_strategy_handler() adds the works of the ata error handler to
system_unbound_wq. This workqueue asynchronously runs w
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Vineet Gupta
commit f52e126cc7476196f44f3c313b7d9f0699a881fc upstream.
With recent binutils update to support dwarf CFI pseudo-ops in gas, we
now get .eh_frame vs. .debug_frame. Although the c
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Russell Currey
commit 871e178e0f2c4fa788f694721a10b4758d494ce1 upstream.
In the "ibm,configure-pe" and "ibm,configure-bridge" RTAS calls, the
spec states that values of 9900-9905 can be return
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Paul Mackerras
commit f024ee098476a3e620232e4a78cfac505f121245 upstream.
This moves the transactional memory state save and restore sequences
out of the guest entry/exit paths into separate pr
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: lei liu
commit f0d09463c59c2d764a6c6d492cbe6d2c77f27153 upstream.
More ZTE device ids.
Signed-off-by: lei liu
[properly sort them - gregkh]
Signed-off-by: Greg Kroah-Hartman
Signed-off-by:
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Sven Eckelmann
commit d285f52cc0f23564fd61976d43fd5b991b4828f6 upstream.
The undefined behavior sanatizer detected an signed integer overflow in a
setup with near perfect link quality
UBS
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Michael Ellerman
commit 8bbc9b7b001eaab8abf7e9e24edf1bb285c8d825 upstream.
Currently we have a check in hash_preload() against the psize, which is
only included when CONFIG_PPC_MM_SLICES is en
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Florian Westphal
commit 329a0807124f12fe1c8032f95d8a8eb47047fb0e upstream.
Signed-off-by: Florian Westphal
Signed-off-by: Pablo Neira Ayuso
[bwh: Backported to 3.16: adjust context]
Signed-o
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Michal Suchanek
commit 719bd6542044efd9b338a53dba1bef45f40ca169 upstream.
The trasfer timeout is fixed at 1000 ms. Reading a 4Mbyte flash over
1MHz SPI bus takes way longer than that. Calculat
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Catalin Marinas
commit 5bb1cc0ff9a6b68871970737e6c4c16919928d8b upstream.
Currently, pmd_present() only checks for a non-zero value, returning
true even after pmd_mknotpresent() (which only cl
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 1c306f7f62a38ee5f05f0ee994dfe82d654cf47c upstream.
We removed this initialization but it is required. Let's put it back.
Fixes: 895106a577c4 ('i40e: trivial fixes')
Sign
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Brian King
commit 54e430bbd490e18ab116afa4cd90dcc45787b3df upstream.
If we fall back to using LSI on the Croc or Crocodile chip we need to
clear the interrupt so we don't hang the system.
Tes
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Ross Lagerwall
commit f0f393877c71ad227d36705d61d1e4062bc29cf5 upstream.
Commit ff1e22e7a638 ("xen/events: Mask a moving irq") open-coded
irq_move_irq() but left out checking if the IRQ is dis
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Gregor Boirie
commit d43a41152f8e9e4c0d19850884d1fada076dee10 upstream.
Temperature channels report scaled samples in Celsius although expected as
milli degree Celsius in Documentation/ABI/tes
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Ville Syrjälä
commit 3017cd63f26fc655d56875aaf497153ba60e9edf upstream.
With netconsole (at least) the pr_err("... disablingn") call can
recurse back into the dma-debug code, where it'll try
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit c5c0c55598cefc826d6cfb0a417eeaee3631715c upstream.
Private data, URBs and buffers allocated for Epic devices during
attach were never released on errors (e.g. missing endpo
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Omar Sandoval
commit 8ba8682107ee2ca3347354e018865d8e1967c5f4 upstream.
get_task_ioprio() accesses the task->io_context without holding the task
lock and thus can race with exit_io_context(),
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: "Guilherme G. Piccoli"
commit 8445a87f7092bc8336ea1305be9306f26b846d93 upstream.
Commit 39baadbf36ce ("powerpc/eeh: Remove eeh information from pci_dn")
changed the pci_dn struct by removing i
3.2.82-rc1 review patch. If anyone has any objections, please let me know.
--
From: Kangjie Lu
commit 9a47e9cff994f37f7f0dbd9ae23740d0f64f9fe6 upstream.
The stack object “r1” has a total size of 32 bytes. Its field
“event” and “val” both contain 4 bytes padding. These 8 bytes
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Jiri Slaby
commit 7e1b1fc4dabd6ec8e28baa0708866e13fa93c9b3 upstream.
Modules which register drivers via standard path (driver_register) in
parallel can cause a warning:
WARNING: CPU: 2 PID: 34
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Mikulas Patocka
commit 44d51706b4685f965cd32acde3fe0fcc1e6198e8 upstream.
Commit ce657611baf9 ("hpfs: kstrdup() out of memory handling") checks if
the kstrdup function returns NULL due to out-
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Michal Suchanek
commit 6d9fe44bd73d567d04d3a68a2d2fa521ab9532f2 upstream.
When testing SPI without DMA I noticed that filling the FIFO on the
spi controller causes timeout.
Always leave room
3.2.82-rc1 review patch. If anyone has any objections, please let me know.
--
From: Michael Ellerman
commit aac55d7573c5d46ed9a62818d5d3e69dd2060105 upstream.
With Linux page size of 64K and hardware only supporting 4K HPTE, if we
use subpage protection, we always fail for the
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Marc Zyngier
commit d4b9e0790aa764c0b01e18d4e8d33e93ba36d51f upstream.
The ARM architecture mandates that when changing a page table entry
from a valid entry to another valid entry, an invalid
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: "Naveen N. Rao"
commit 844e3be47693f92a108cb1fb3b0606bf25e9c7a6 upstream.
Classic BPF JIT was never ported completely to work on little endian
powerpc. However, it can be enabled and will cras
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Raghava Aditya Renukunta
commit fc4bf75ea300a5e62a2419f89dd0e22189dd7ab7 upstream.
Typically under error conditions, it is possible for aac_command_thread()
to miss the wakeup from kthread_sto
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Linus Walleij
commit 19ced623db2fe91604d69f7d86b03144c5107739 upstream.
The hash buffer is really HASH_BLOCK_SIZE bytes, someone
must have thought that memmove takes n*u32 words by mistake.
Te
3.2.82-rc1 review patch. If anyone has any objections, please let me know.
--
From: Kangjie Lu
commit 4116def2337991b39919f3b448326e21c40e0dbb upstream.
The last field "flags" of object "minfo" is not initialized.
Copying this object out may leak kernel stack data.
Assign 0 to
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Florian Fainelli
commit 69fc58a57e56bf5e39b48809aefffdaa1b04c945 upstream.
If we have a system which uses fixed PHY devices and calls
fixed_phy_register() then fixed_phy_unregister() we can ex
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: James Hogan
commit 5daebc477da4dfeb31ae193d83084def58fd2697 upstream.
Commit 85efde6f4e0d ("make exported headers use strict posix types")
changed the asm-generic siginfo.h to use the __kernel
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Vik Heyndrickx
commit 20878232c52329f92423d27a60e48b6a6389e0dd upstream.
Systems show a minimal load average of 0.00, 0.01, 0.05 even when they
have no load at all.
Uptime and /proc/loadavg o
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Simon Wunderlich
commit 0b3dd7dfb81ad8af53791ea2bb64b83bac1b7d32 upstream.
If a VLAN tagged frame is received and the corresponding VLAN is not
configured on the soft interface, it will splat
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Ben Hutchings
commit 999653786df6954a31044528ac3f7a5dadca08f4 upstream.
Use set_posix_acl, which includes proper permission checks, instead of
calling ->set_acl directly. Without this anyone
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Adrian Hunter
commit 1c447116d017a98c90f8f71c8c5a611e0aa42178 upstream.
Some eMMCs set the partition switch timeout too low.
Now typically eMMCs are considered a critical component (e.g. beca
This is the start of the stable review cycle for the 3.16.37 release.
There are 305 patches in this series, which will be posted as responses
to this one. If anyone has any issues with these being applied, please
let me know.
As I've accumulated an unusually long patch series, I'm allowing a
long
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Prarit Bhargava
commit da77b67195de1c65bef4908fa29967c4d0af2da2 upstream.
Commit b894157145e4 ("x86/PCI: Mark Broadwell-EP Home Agent & PCU as having
non-compliant BARs") marked Home Agent 0 &
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Richard Weinberger
commit 1900149c835ab5b48bea31a823ea5e5a401fb560 upstream.
Ezequiel reported that he's facing UBI going into read-only
mode after power cut. It turned out that this behavior
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: "Steven Rostedt (Red Hat)"
commit 9b94a8fba501f38368aef6ac1b30e7335252a220 upstream.
The size variable to change the ring buffer in ftrace is a long. The
nr_pages used to update the ring buffe
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Shaokun Zhang
commit 20c27a4270c775d7ed661491af8ac03264d60fc6 upstream.
__sync_icache_dcache unconditionally skips the cache maintenance for
anonymous pages, under the assumption that flushing
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Heiko Carstens
commit c34a69059d7876e0793eb410deedfb08ccb22b02 upstream.
The identity mapping is suboptimal for the last 2GB frame. The mapping
will be established with a mix of 4KB and 1MB ma
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Sai Gurrappadi
commit e43e94c1eda76dabd686ddf6f7825f54d747b310 upstream.
Currently, the userspace governor only updates frequency on GOV_LIMITS
if policy->cur falls outside policy->{min/max}.
3.2.82-rc1 review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit f18ebc211e259d4f591e39e74b2aa2de226c9a1d upstream.
The problem with ornamental, do-nothing gotos is that they lead to
"forgot to set the error code" bugs. We should be ret
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Peter Hurley
commit 2ce3c10c0c3e0d418c1a7a4c838319ba42c75388 upstream.
This reverts commit c4dc304677e8d566572c4738d95c48be150c6606.
This fix is superseded by commit 52bce7f8d4fc633c9a9d0646ee
3.2.82-rc1 review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 38327424b40bcebe2de92d07312c89360ac9229a upstream.
If __key_link_begin() failed then "edit" would be uninitialized. I've
added a check to fix that.
This allows a random u
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Geert Uytterhoeven
commit 309124e2648d668a0c23539c5078815660a4a850 upstream.
According to full-history-linux commit d3794f4fa7c3edc3 ("[PATCH] M68k
update (part 25)"), port operations are allo
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Hans de Goede
commit 81099f97bd31e25ff2719a435b1860fc3876122f upstream.
Properly sort all the entries by vendor id.
Signed-off-by: Hans de Goede
Signed-off-by: Greg Kroah-Hartman
Signed-off
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Peter Zijlstra
commit 2e636d5e66c35dfcbaf617aa8fa963f6847478fe upstream.
Vikram reported that his ARM64 compiler managed to 'optimize' away the
preempt_count manipulations in code like:
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
commit 75ff39ccc1bd5d3c455b6822ab09e533c551f758 upstream.
Yue Cao claims that current host rate limiting of challenge ACKS
(RFC 5961) could leak enough information to allow a pati
3.2.82-rc1 review patch. If anyone has any objections, please let me know.
--
From: Ross Lagerwall
commit f0f393877c71ad227d36705d61d1e4062bc29cf5 upstream.
Commit ff1e22e7a638 ("xen/events: Mask a moving irq") open-coded
irq_move_irq() but left out checking if the IRQ is disa
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Luis de Bethencourt
commit ef3149eb3ddb7f9125e11c90f8330e371b55cffd upstream.
sca3000_read_ctrl_reg() returns a negative number on failure, check for
this instead of zero.
Signed-off-by: Luis
struct timespec is not y2038 safe.
Use time64_t which is y2038 safe to represent orphan
scan times.
time64_t is sufficient here as only the seconds delta
times are relevant.
Also use appropriate time functions that return time in
time64_t format. Time functions now return monotonic
time instead of
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Johannes Thumshirn
commit f05795d3d771f30a7bdc3a138bf714b06d42aa95 upstream.
Add intermediate STARGET_REMOVE state to scsi_target_state to avoid
running into the BUG_ON() in scsi_target_reap()
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Schemmel Hans-Christoph
commit 444f94e9e625f6ec6bbe2cb232a6451c637f35a3 upstream.
Added support for Gemalto's Cinterion PH8 and AHxx products
with 2 RmNet Interfaces and products with 1 RmNet
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Mark Bloch
commit 2fa2d4fb1166d1ef35f0aacac6165d53ab1b89c7 upstream.
Fix array overrun when going over callback table.
In declaration of callback table, the max size isn't provided and
in regi
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 22aab38e7b59fd79ce1045006be69a9abab58e5a upstream.
Instead to being true/false, the "handled" is true/uninitialized.
Presumably this doesn't cause that many problems in re
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Tony Lindgren
commit 0ac3c0a4025f41748a083bdd4970cb3ede802b15 upstream.
With many repeated suspend resume cycles, the pin specific wakeirq
may not always work on omaps. This is because the wri
3.2.82-rc1 review patch. If anyone has any objections, please let me know.
--
From: Andrew Goodbody
commit 7b2c17f829545df27a910e8d82e133c21c9a8c9c upstream.
Ensure that the endpoint is stopped by clearing REQPKT before
clearing DATAERR_NAKTIMEOUT before rotating the queue on
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Dave Gerlach
commit c998c07836f985b24361629dc98506ec7893e7a0 upstream.
Currently the 'registered' member of the cpuidle_device struct is set
to 1 during cpuidle_register_device. In this same f
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Bin Liu
commit d246dcb2331c5783743720e6510892eb1d2801d9 upstream.
[ 40.467381] =
[ 40.473013] [ INFO: possible recursive locking detected ]
[
3.2.82-rc1 review patch. If anyone has any objections, please let me know.
--
From: Duan Jiong
commit 6d57e9078e880a3dd232d579f42ac437a8f1ef7b upstream.
a lot of code has either the memset or an inefficient copy
from a static array that contains the all-zeros Ethernet address.
3.2.82-rc1 review patch. If anyone has any objections, please let me know.
--
From: Scott Bauer
commit 93a2001bdfd5376c3dc2158653034c20392d15c5 upstream.
This patch validates the num_values parameter from userland during the
HIDIOCGUSAGES and HIDIOCSUSAGES commands. Previously
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit 1f62ff34a90471d1b735bac2c79e894afc7c59bc upstream.
dev_dbg_ratelimited() is a macro that ignores its first argument when DEBUG is
not set, which can lead to unused variabl
> Really now, this is basic fixes and cleanups,
I agree to this view to some degree.
> you have been asked many times in the past to move on beyond these,
It is more useful when more severe bugs or bigger software improvements can be
found.
Which source code clean-ups are picked better up by o
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Ashutosh Dixit
commit 9bf292bfca94694a721449e3fd752493856710f6 upstream.
The MIC VOP driver does two successive reads from user space to read a
variable length data structure. Kernel memory co
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Jiri Slaby
commit 6798df4c5fe0a7e6d2065cf79649a794e5ba7114 upstream.
When csw->con_startup() fails in do_register_con_driver, we return no
error (i.e. 0). This was changed back in 2006 by comm
CURRENT_TIME_SEC is not y2038 safe.
Replace use of CURRENT_TIME_SEC with ktime_get_real_seconds
in segment timestamps used by GC algorithm including the
segment mtime timestamps.
Signed-off-by: Deepa Dinamani
Reviewed-by: Arnd Bergmann
Cc: Jaegeuk Kim
Cc: Changman Lee
Cc: linux-f2fs-de...@lis
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: Florian Westphal
commit 09d9686047dbbe1cf4faa558d3ecc4aae2046054 upstream.
This looks like refactoring, but its also a bug fix.
Problem is that the compat path (32bit iptables, 64bit kernel)
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: "xypron.g...@gmx.de"
commit 1740c29a46b30a2f157afc473156f157e599d4c2 upstream.
ehea_get_port may return NULL. Do not dereference NULL value.
Fixes: 8c4877a4128e ("ehea: Use the standard loggi
3.16.37-rc1 review patch. If anyone has any objections, please let me know.
--
From: William Breathitt Gray
commit 32a5a0c047343b11f581f663a2309cf43d13466f upstream.
The isa_bus_init function must be called before drivers which utilize
the ISA bus driver are registered. A race
101 - 200 of 919 matches
Mail list logo
