3.16-stable review patch. If anyone has any objections, please let me know.
--
From: bob picco
[ Upstream commit ee6a9333fa58e11577c1b531b8e0f5ffc0fd6f50 ]
This patch attempts to do a few things. The highlights are: 1) enable
SPARSE_IRQ unconditionally, 2) kills off !SPARSE_IR
3.16-stable review patch. If anyone has any objections, please let me know.
--
From: "David S. Miller"
[ Upstream commit d195b71bad4347d2df51072a537f922546a904f1 ]
swapper_low_pmd_dir and swapper_pud_dir are actually completely
useless and unnecessary.
We just need swapper_pg
3.16-stable review patch. If anyone has any objections, please let me know.
--
From: "David S. Miller"
[ Upstream commit 8bccf5b313180faefce38e0d1140f76e0f327d28 ]
Christopher reports that perf_event_print_debug() can crash in uniprocessor
builds. The crash is due to pcr_ops
3.16-stable review patch. If anyone has any objections, please let me know.
--
From: Dave Kleikamp
[ Upstream commit 1cef94c36bd4d79b5ae3a3df99ee0d76d6a4a6dc ]
This is the longest boot string that silo supports.
Signed-off-by: Dave Kleikamp
Cc: Bob Picco
Cc: David S. Miller
3.16-stable review patch. If anyone has any objections, please let me know.
--
From: "David S. Miller"
[ Upstream commit 06090e8ed89ea2113a236befb41f71d51f100e60 ]
It is not sufficient to only implement get_user_pages_fast(), you
must also implement the atomic version __get_us
3.16-stable review patch. If anyone has any objections, please let me know.
--
From: "David S. Miller"
[ Upstream commit bb4e6e85daa52a9f6210fa06a5ec6269598a202b ]
In order to accomodate embedded per-cpu allocation with large numbers
of cpus and numa nodes, we have to use as m
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: David Sterba
commit 2fad4e83e12591eb3bd213875b9edc2d18e93383 upstream.
The transaction thread may want to do more work, namely it pokes the
cleaner ktread that will start processing uncleaned
3.16-stable review patch. If anyone has any objections, please let me know.
--
From: "David S. Miller"
[ Upstream commit 0dd5b7b09e13dae32869371e08e1048349fd040c ]
If max_phys_bits needs to be > 43 (f.e. for T4 chips), things like
DEBUG_PAGEALLOC stop working because the 3-lev
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Josef Bacik
commit 1d52c78afbbf80b58299e076a159617d6b42fe3c upstream.
When doing log replay we may have to update inodes, which traditionally goes
through our delayed inode stuff. This will t
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Josef Bacik
commit bbe9051441effce51c9a533d2c56440df64db2d7 upstream.
Marc Merlin sent me a broken fs image months ago where it would blow up in the
upper->checked BUG_ON() in build_backref_tr
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Sage Weil
commit 42383020beb1cfb05f5d330cc311931bc4917a97 upstream.
We check whether transid is already committed via last_trans_committed and
then search through trans_list for pending transa
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Bryan O'Donoghue
commit a68df7066a6f974db6069e0b93c498775660a114 upstream.
This patch is to enable the USB gadget device for Intel Quark X1000
Signed-off-by: Bryan O'Donoghue
Signed-off-by:
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Xiubo Li
commit d6b41cb06044a7d895db82bdd54f6e4219970510 upstream.
Since we cannot make sure the 'val_count' will always be none zero
here, and then if it equals to zero, the kmemdup() will re
This is the start of the stable review cycle for the 3.14.23 release.
There are 100 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Thu Oct 30 03:34:43 UTC 2014.
Anything recei
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Filipe Manana
commit 766b5e5ae78dd04a93a275690a49e23d7dcb1f39 upstream.
During an incremental send, when we finish processing an inode (corresponding to
a regular file) we would assume the gap
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Joe Lawrence
commit db7157d4cfce6edf052452fb1d327d4d11b67f4c upstream.
Once calling scsi_host_put, be careful to not access qla_hw_data through
the Scsi_Host private data (ie, scsi_qla_host ba
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Arun Easi
commit 75554b68ac1e018bca00d68a430b92ada8ab52dd upstream.
Signed-off-by: Arun Easi
Signed-off-by: Saurav Kashyap
Signed-off-by: Christoph Hellwig
Signed-off-by: Greg Kroah-Hartman
Hello,
On 2014-10-28 07:29, Andrew Morton wrote:
On Tue, 28 Oct 2014 15:24:44 +1100 Stephen Rothwell
wrote:
Today's linux-next merge of the akpm-current tree got a conflict in
mm/cma.c between commit 16195ddd4ebc ("mm: cma: Ensure that
reservations never cross the low/high mem boundary") fro
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
commit 471b095dfe0d693a8d624cbc716d1ee4d74eb437 upstream.
An empty firmware request name will trigger warnings when building
device names. Make sure this is caught earlier and reject
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Pankaj Dubey
commit 5336be8416a71b5568d2cf54a2f2066abe9f2a53 upstream.
If LOG_DEVICE is defined and map->dev is NULL it will lead to NULL
pointer dereference. This patch fixes this issue by ad
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Chris J Arges
commit 4089b71cc820a426d601283c92fcd4ffeb5139c2 upstream.
When using a virtual SCSI disk in a VMWare VM if blkdev_issue_zeroout is used
data can be improperly zeroed out using th
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Xuelin Shi
commit 87cea76384257e6ac3fa4791b6a6b9d0335f7457 upstream.
the partial xor result must be kept until the next
tx is generated.
Signed-off-by: Xuelin Shi
Signed-off-by: Dan Williams
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Christian Borntraeger
commit f346026e55f1efd3949a67ddd1dcea7c1b9a615e upstream.
We must not fallthrough if the conditions for external call are not met.
Signed-off-by: Christian Borntraeger
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: "K. Y. Srinivasan"
commit fdeebcc62279119dbeafbc1a2e39e773839025fd upstream.
Posting messages to the host can fail because of transient resource
related failures. Correctly deal with these fai
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: "K. Y. Srinivasan"
commit 98d731bb064a9d1817a6ca9bf8b97051334a7cfe upstream.
Eliminate calls to BUG_ON() in vmbus_close_internal().
We have chosen to potentially leak memory, than crash the gu
On Mon, Oct 27, 2014 at 11:17:02PM +0100, Mikael Svantesson wrote:
> Signed-off-by: Mikael Svantesson
The patch is corrupt (and in a totally weird way as well). Please read
the first paragraph for Documentation/email-clients.txt.
regards,
dan carpenter
--
To unsubscribe from this list: send th
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: "K. Y. Srinivasan"
commit 66be653083057358724d56d817e870e53fb81ca7 upstream.
Eliminate calls to BUG_ON() by properly handling errors. In cases where
rollback is possible, we will return the ap
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: David Matlack
commit ee3d1570b58677885b4552bce8217fda7b226a68 upstream.
vcpu exits and memslot mutations can run concurrently as long as the
vcpu does not aquire the slots mutex. Thus it is th
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: "K. Y. Srinivasan"
commit 72c6b71c245dac8f371167d97ef471b367d0b66b upstream.
Eliminate the call to BUG_ON() by waiting for the host to respond. We are
trying to reclaim the ownership of memory
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: David Matlack
commit 2ea75be3219571d0ec009ce20d9971e54af96e09 upstream.
vcpu ioctls can hang the calling thread if issued while a vcpu is running.
However, invalid ioctls can happen when users
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Shevchenko
commit b41583e7299046abdc578c33f25ed83ee95b9b31 upstream.
In case of 8 bit mode and DMA usage we end up with every second byte written as
0. We have to respect bits_per_word se
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Bryan O'Donoghue
commit ee1b5b165c0a2f04d2107e634e51f05d0eb107de upstream.
Quark x1000 advertises PGE via the standard CPUID method
PGE bits exist in Quark X1000's PTEs. In order to flush
an i
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Xiubo Li
commit 2c98e0c1cc6b8e86f1978286c3d4e0769ee9d733 upstream.
If 'map->dev' is NULL and there will lead dev_name() to be NULL pointer
dereference. So before dev_name(), we need to have ch
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Adamson
commit d1f456b0b9545f1606a54cd17c20775f159bd2ce upstream.
Commit 2f60ea6b8ced ("NFSv4: The NFSv4.0 client must send RENEW calls if it
holds a delegation") set the NFS4_RENEW_TIME
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Josef Ahmad
commit bb048713bba3ead39f6112910906d9fe3f88ede7 upstream.
This patch adds the PCI id for Intel Quark ILB.
It will be used for GPIO and Multifunction device driver.
Signed-off-by:
Chanwoo Choi wrote:
>
> This patch add Exynos4415's SoC ID.
>
Since the CPU ID has been removed as per comments, need to update the commit
message accordingly.
> Exynos4415 is based on the 32-bit RISC
> processor for Smartphone. Exynos4415 uses Cortex A9 quad-cores and has a
> target
> speed of
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Petazzoni
commit 56fab6e189441d714a2bfc8a64f3df9c0749dff7 upstream.
Geert Uytterhoeven reported a warning when building pci-mvebu:
drivers/pci/host/pci-mvebu.c: In function 'mvebu_ge
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Oren Givon
commit 4f08970f5284dce486f0e2290834aefb2a262189 upstream.
Add 4 missing PCI IDs for the 7260 series.
Signed-off-by: Oren Givon
Signed-off-by: Emmanuel Grumbach
Signed-off-by: Gre
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Loic Poulain
commit 4807b51895dce8aa650ebebc51fa4a795ed6b8b8 upstream.
In this expression: seq = (seq - 1) % 8
seq (u8) is implicitly converted to an int in the arithmetic operation.
So if seq
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Ricardo Ribalda Delgado
commit 89ec3dcf17fd3fa009ecf8faaba36828dd6bc416 upstream.
Some implementations of modprobe fail to load the driver for a PCI device
automatically because the "interface
The old property is supported. See "[PATCH v1 1/10]" ^^
(of_is_system_power_controller supports both properties...)
2014-10-28 5:34 GMT+01:00 Alexandre Courbot :
> On Tue, Oct 28, 2014 at 1:42 AM, Felipe Balbi wrote:
>> On Mon, Oct 27, 2014 at 04:26:52PM +, Romain Perier wrote:
>>> Signed-off
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Stanislaw Gruszka
commit 01f7feeaf4528bec83798316b3c811701bac5d3e upstream.
Two bits control TX power on BBP_R1 register. Correct the mask,
otherwise we clear additional bit on BBP_R1 register
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hedberg
commit 72c6fb915ff2d30ae14053edee4f0d30019bad76 upstream.
The l2cap_create_le_flowctl_pdu() function that l2cap_segment_le_sdu()
calls is perfectly capable of doing packet fragme
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Willy Tarreau
commit af958a38a60c7ca3d8a39c918c1baa2ff7b6b233 upstream.
This reverts commit 206a81c ("lzo: properly check for overruns").
As analysed by Willem Pinckaers, this fix is still in
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Willy Tarreau
commit d98a0526434d27e261f622cf9d2e0028b5ff1a00 upstream.
Add a complete description of the LZO format as processed by the
decompressor. I have not found a public specification o
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Junxiao Bi
commit 934f3072c17cc8886f4c043b47eeeb1b12f8de33 upstream.
commit 21caf2fc1931 ("mm: teach mm by current context info to not do I/O
during memory allocation") introduces PF_MEMALLOC_
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
commit df817ba35736db2d62b07de6f050a4db53492ad8 upstream.
The current open/lock state recovery unfortunately does not handle errors
such as NFS4ERR_CONN_NOT_BOUND_TO_SESSION co
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Frans Klaver
commit dc3187564e61260f49eceb21a4e7eb5e4428e90a upstream.
If the chosen baud rate is large enough (e.g. 3.5 megabaud), the
calculated n values in serial_omap_is_baud_mode16() may
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Willy Tarreau
commit 72cf90124e87d975d0b2114d930808c58b4c05e4 upstream.
This fix ensures that we never meet an integer overflow while adding
255 while parsing a variable length encoding. It wo
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andreas Henriksson
commit b65e0fb3d046cc65d0a3c45d43de351fb363271b upstream.
As discovered on a custom board similar to at91sam9263ek and basing
its devicetree on that one apparently the pin m
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
commit a4339b7b686b4acc8b6de2b07d7bacbe3ae44b83 upstream.
If a NFSv4.x server returns NFS4ERR_STALE_CLIENTID in response to a
CREATE_SESSION or SETCLIENTID_CONFIRM in order to
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: David Dueck
commit 0a51d644c20f5c88fd3a659119d1903f74927082 upstream.
Otherwise the clock for can0 will never get enabled.
Signed-off-by: David Dueck
Signed-off-by: Anthony Harivel
Acked-by
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: "klightsp...@killerwolves.net"
commit ace8578182dc347b043c0825b9873f62fdaa5b77 upstream.
The bootloader on the Netgear ReadyNAS RN102 uses Hardware BCH ECC
(strength = 4), while the pxa3xx NAN
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Arnaud Ebalard
commit 225b94cdf719d0bc522a354bdafc18e5da5ff83b upstream.
The bootloader on the Netgear ReadyNAS RN104 uses Hardware BCH
ECC (strength = 4), while the pxa3xx NAND driver by defa
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Ludovic Desroches
commit cfa1950e6c6b72251e80adc736af3c3d2907ab0e upstream.
When introducing support for sama5d3, the write to PMC_PCDR register has
been accidentally removed.
Reported-by: Na
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Dave Chinner
commit 0d085a529b427d97710e6a41f8a4f23e1757cd12 upstream.
XFS has been having trouble with stray delayed allocation extents
beyond EOF for a long time. Recent changes to the colla
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Alexey Kardashevskiy
commit 9410e0185e65394c0c6d046033904b53b97a9423 upstream.
rtas_call() accepts and returns values in CPU endianness.
The ddw_query_response and ddw_create_response structs
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: "David S. Miller"
[ Upstream commit 58556104e9cd0107a7a8d2692cf04ef31669f6e4 ]
nmi_cpu_busy() is a SMP function call that just makes sure that all of the
cpus are spinning using cpu cycles whi
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Dmitry Kasatkin
commit b151d6b00bbb798c58f2f21305e7d43fa763f34f upstream.
On ima_file_free(), newly created empty files are not labeled with
an initial security.ima value, because the iversion
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: "David S. Miller"
[ Upstream commit 8bccf5b313180faefce38e0d1140f76e0f327d28 ]
Christopher reports that perf_event_print_debug() can crash in uniprocessor
builds. The crash is due to pcr_ops
Commit-ID: 3c325f8233c35fb35dec3744ba01634aab4ea36a
Gitweb: http://git.kernel.org/tip/3c325f8233c35fb35dec3744ba01634aab4ea36a
Author: Weijie Yang
AuthorDate: Fri, 24 Oct 2014 17:00:34 +0800
Committer: Ingo Molnar
CommitDate: Tue, 28 Oct 2014 07:36:50 +0100
x86, cma: Reserve DMA contig
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Anatol Pomozov
commit a011e213f3700233ed2a676f1ef0a74a052d7162 upstream.
This avoids following kernel crash when try to playback on arm64
[ 107.497203] [] snd_pcm_mmap_data_fault+0x90/0xd4
[
Hi Daniel,
On Mon, Oct 20, 2014 at 9:55 PM, Daniel Lezcano
wrote:
> Following the logic of the previous patch, retrieve from the idle task the
> expected timer sleep duration and pass it to the cpuidle framework.
>
> Take the opportunity to remove the unused headers in the menu.c file.
>
> This p
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Daniel Hellstrom
[ Upstream commit d1105287aabe88dbb3af825140badaa05cf0442c ]
dma_zalloc_coherent() calls dma_alloc_coherent(__GFP_ZERO)
but the sparc32 implementations sbus_alloc_coherent() a
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Shevchenko
commit 8e45ef682cb31fda62ed4eeede5d9745a0a1b1e2 upstream.
Do full clean up at exit, means terminate all ongoing DMA transfers.
Signed-off-by: Andy Shevchenko
Signed-off-by: M
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 95926035b187cc9fee6fb61385b7da9c28123f74 upstream.
The emu10k1 voice allocator takes voice_lock spinlock. When there is
no empty stream available, it tries to release a vo
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Harsha Priya
commit b450b17c156e264bc44a198046d3ebaaef5a041d upstream.
This patch sets the headphones mode to default before suspending
which helps avoid the pop noise on headphones
Signed-of
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Vlad Catoi
commit f0b127fbfdc8756eba7437ab668f3169280bd358 upstream.
Adding support for Steinberg UR22 USB interface via quirks table patch
See Ubuntu bug report:
https://bugs.launchpad.net/u
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Sasha Levin
commit 71458cfc782eafe4b27656e078d379a34e472adf upstream.
We're missing include/linux/compiler-gcc5.h which is required now
because gcc branched off to v5 in trunk.
Just copy the
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Allen Pais
The following patch adds support for correctly
recognising M6 and M7 cpu type.
Signed-off-by: Allen Pais
Signed-off-by: David S. Miller
Signed-off-by: Greg Kroah-Hartman
---
arc
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: bob picco
The T5 (niagara5) has different PCR related HV fast trap values and a new
HV API Group. This patch utilizes these and shares when possible with niagara4.
We use the same sparc_pmu ni
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Allen Pais
Signed-off-by: Allen Pais
Signed-off-by: David S. Miller
Signed-off-by: Greg Kroah-Hartman
---
arch/sparc/kernel/setup_64.c |8
1 file changed, 8 insertions(+)
---
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: "David S. Miller"
[ Upstream commit 4397bed080598001e88f612deb8b080bb1cc2322 ]
Now that we use 4-level page tables, we can provide up to 53-bits of
virtual address space to the user.
Adjust t
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: "David S. Miller"
[ Upstream commit 8c82dc0e883821c098c8b0b130ffebabf9aab5df ]
As currently coded the KTSB accesses in the kernel only support up to
47 bits of physical addressing.
Adjust the
Greetings,
Well, I want to be able to have my cake and eat it too. I want to be able to
have the standard VGA/"hardware" classic console (not the framebuffer) but
I still want the /dev/dri/cardX devices so that I can use DRI under Xorg.
Is this possible and if not, why not?
(I do hope I'm n
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: "David S. Miller"
[ Upstream commit 0dd5b7b09e13dae32869371e08e1048349fd040c ]
If max_phys_bits needs to be > 43 (f.e. for T4 chips), things like
DEBUG_PAGEALLOC stop working because the 3-lev
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: bob picco
[ Upstream commit 3dee9df54836d5f844f3d58281d3f3e6331b467f ]
We have seen an issue with guest boot into LDOM that causes early boot failures
because of no matching rules for node ide
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: "David S. Miller"
Make sure, at compile time, that the kernel can properly support
whatever MAX_PHYS_ADDRESS_BITS is defined to.
On M7 chips, use a max_phys_bits value of 49.
Based upon a pat
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: "David S. Miller"
[ Upstream commit bdcf81b658ebc4c2640c3c2c55c8b31c601b6996 ]
Inconsistently, the raw_* IRQ routines do not interact with and update
the irqflags tracing and lockdep state, wh
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: "David S. Miller"
[ Upstream commit bb4e6e85daa52a9f6210fa06a5ec6269598a202b ]
In order to accomodate embedded per-cpu allocation with large numbers
of cpus and numa nodes, we have to use as m
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Sowmini Varadhan
[ Upstream commit c21c4ab0d6921f7160a43216fa6973b5924de561 ]
The request_irq() needs to be done from ldc_alloc()
to avoid the following (caught by lockdep)
[004a0738
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Dave Kleikamp
[ Upstream commit 1cef94c36bd4d79b5ae3a3df99ee0d76d6a4a6dc ]
This is the longest boot string that silo supports.
Signed-off-by: Dave Kleikamp
Cc: Bob Picco
Cc: David S. Miller
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: "David S. Miller"
[ Upstream commit d195b71bad4347d2df51072a537f922546a904f1 ]
swapper_low_pmd_dir and swapper_pud_dir are actually completely
useless and unnecessary.
We just need swapper_pg
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: bob picco
[ Upstream commit 4ccb9272892c33ef1c19a783cfa87103b30c2784 ]
We've witnessed a few TLB events causing the machine to power off because
of prom_halt. In one case it was some nfs relat
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: "David S. Miller"
[ Upstream commit e2653143d7d79a49f1a961aeae1d82612838b12c ]
This breaks the stack end corruption detection facility.
What that facility does it write a magic value to "end_
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Josef Bacik
commit 1d52c78afbbf80b58299e076a159617d6b42fe3c upstream.
When doing log replay we may have to update inodes, which traditionally goes
through our delayed inode stuff. This will t
Hi Daniel,
On Thu, Oct 23, 2014 at 2:31 PM, Daniel Lezcano
wrote:
> When the pmqos latency requirement is set to zero that means "poll in all the
> cases".
>
> That is correctly implemented on x86 but not on the other archs.
>
> As how is written the code, if the latency request is zero, the gove
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: "David S. Miller"
[ Upstream commit 06090e8ed89ea2113a236befb41f71d51f100e60 ]
It is not sufficient to only implement get_user_pages_fast(), you
must also implement the atomic version __get_us
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: "David S. Miller"
We changed PAGE_OFFSET to be a variable rather than a constant,
but this reference here in the hibernate assembler got missed.
Signed-off-by: David S. Miller
Signed-off-by:
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Sage Weil
commit 42383020beb1cfb05f5d330cc311931bc4917a97 upstream.
We check whether transid is already committed via last_trans_committed and
then search through trans_list for pending transa
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: bob picco
[ Upstream commit ee6a9333fa58e11577c1b531b8e0f5ffc0fd6f50 ]
This patch attempts to do a few things. The highlights are: 1) enable
SPARSE_IRQ unconditionally, 2) kills off !SPARSE_IR
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit a1480dcc3c706e309a4723446f2e84fedd5b upstream.
Accessing do_remount_sb should require global CAP_SYS_ADMIN, but
only one of the two call sites was appropriately prot
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Christian Borntraeger
commit f346026e55f1efd3949a67ddd1dcea7c1b9a615e upstream.
We must not fallthrough if the conditions for external call are not met.
Signed-off-by: Christian Borntraeger
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: "K. Y. Srinivasan"
commit 66be653083057358724d56d817e870e53fb81ca7 upstream.
Eliminate calls to BUG_ON() by properly handling errors. In cases where
rollback is possible, we will return the ap
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
commit 471b095dfe0d693a8d624cbc716d1ee4d74eb437 upstream.
An empty firmware request name will trigger warnings when building
device names. Make sure this is caught earlier and reject
* Eric Paris wrote:
> On Mon, 2014-10-27 at 10:02 -0700, H. Peter Anvin wrote:
> > On 10/27/2014 06:55 AM, Eric Paris wrote:
> > > My patch was already committed to the -tip urgent branch. I believe any
> > > optimization should be based on that branch, Richard. If you are trying
> > > to wran
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: "K. Y. Srinivasan"
commit fdeebcc62279119dbeafbc1a2e39e773839025fd upstream.
Posting messages to the host can fail because of transient resource
related failures. Correctly deal with these fai
On Tue, 28 Oct 2014 15:24:44 +1100 Stephen Rothwell
wrote:
> Today's linux-next merge of the akpm-current tree got a conflict in
> mm/cma.c between commit 16195ddd4ebc ("mm: cma: Ensure that
> reservations never cross the low/high mem boundary") from the
> dma-mapping tree and commit 2a70e5a7867
Hi Masami,
On 10/27/2014 06:09 PM, Masami Hiramatsu wrote:
Hi Hermant,
This patch is actually what you need for suppressing the result
messages when adding/removing probe events from sdt event tracing.
You just need to set "verbose=-1" around adding/removing probes.
Thank you for working on t
В Пн, 27/10/2014 в 20:54 +0100, Oleg Nesterov пишет:
> task_struct is only protected by RCU if it was found on a RCU protected
> list (say, for_each_process() or find_task_by_vpid()).
>
> And as Kirill pointed out rq->curr isn't protected by RCU, the scheduler
> drops the (potentially) last refere
1 - 100 of 1344 matches
Mail list logo
