On Sun, 15 Nov 2015 08:00:22 +0100 Pavel Machek wrote:
> Kernel complains:
>
> [5.256044] [ cut here ]
> [5.259267] WARNING: CPU: 0 PID: 1 at
> arch/x86/mm/dump_pagetables.c:225 note_page+0x5ec/0x790()
> [5.262668] x86/mm: Found insecure W+X mapping at address
> -Original Message-
> From: Lyude [mailto:cp...@redhat.com]
> Sent: Sunday, November 22, 2015 9:45 PM
> To: Koenig, Christian; Daniel Stone
> Cc: Deucher, Alexander; David Airlie; dri-devel; Linux Kernel Mailing List;
> Jerome Glisse; Benjamin Tissoires
> Subject: Re: [PATCH] drm/radeon:
Add support for the IR receiver as present on the Radxa Rock 2 Square
board.
Signed-off-by: Sjoerd Simons
---
arch/arm/boot/dts/rk3288-rock2-square.dts | 13 +
1 file changed, 13 insertions(+)
diff --git a/arch/arm/boot/dts/rk3288-rock2-square.dts
Namhyung,
On Thu, Nov 19, 2015 at 02:53:17PM -0300, Arnaldo Carvalho de Melo wrote:
> From: Namhyung Kim
>
> It's to track the count of occurrences of the callchains.
Please explain why you do something like this in the changelog, even just a
single
line to tell which feature is going to use
On Mon, Nov 23, 2015 at 03:19:19PM +0100, Frederic Weisbecker wrote:
> On Thu, Nov 19, 2015 at 09:28:28PM +0100, Peter Zijlstra wrote:
> > On Thu, Nov 19, 2015 at 04:47:33PM +0100, Frederic Weisbecker wrote:
> > > +++ b/include/linux/vtime.h
> > > @@ -17,9 +17,20 @@ static inline bool
On 11/23/2015 03:14 PM, Fengguang Wu wrote:
>> Need to add RT in the subject like "[PATCH RT]". Then perhaps Fengguang
>> can have his tests either ignore these or test against the -rt trees.
>
> Yes sure. Shall I apply RT patches to this tree/branch?
>
>
On Mon, Nov 23, 2015 at 12:35:44PM +0200, Sagi Grimberg wrote:
>
>> So Maybe we should have:
>> void ib_drain_qp(struct ib_qp *qp)
>
> Christoph suggested that this flushing would be taken care
> of by rdma_disconnect which sounds even better I think..
Note that will only work once we've
Dear Greg,
Could you please also add upstream commit
899f0c1c7dbcc487fdc8756a49ff70b1d5d75f89
There was a merge conflict in the 4-1.y tree with another back-ported
patch. But in 3.14 this shouldn't be the case.
--
Thanks & regrads,
Soeren
On 11/06/2015 08:24 PM, Greg Kroah-Hartman wrote:
Em Sat, Nov 21, 2015 at 11:23:55AM +0100, Jiri Olsa escreveu:
> Adding missing parent_val callchain_node initialization.
> It's causing segfault in perf top:
Thanks, applied.
- Arnaldo
> $ sudo perf top -g
> perf: Segmentation fault
> backtrace
>
On Mon, 23 Nov 2015, Charles Keepax wrote:
> On Mon, Nov 23, 2015 at 11:30:41AM +, Mark Brown wrote:
> > On Mon, Nov 23, 2015 at 10:25:22AM +, Richard Fitzgerald wrote:
> > > On Mon, 2015-11-23 at 11:11 +0100, Pavel Machek wrote:
> >
> > > > That's what I'm saying. It is good to know who
With the introduction of cpu capacity bindings, CPU capacities can now be
extracted from DT. Add parsing of such information at boot time. We keep
code that can produce same information, based on different DT properties
and hard-coded values, as fall-back for backward compatibility.
Cc: Russell
Better $SUBJECT for ya'll -- so it doesn't get lost in the noise.
> Mark, Alexandre,
>
> Enjoy!
>
> The following changes since commit 1ec218373b8ebda821aec00bb156a9c94fad9cd4:
>
> Linux 4.4-rc2 (2015-11-22 16:45:59 -0800)
>
> are available in the git repository at:
>
>
Add a sysfs cpu_capacity attribute with which it is possible to read and
write (thus over-writing default values) CPUs capacity. This might be
useful in situation where there is no way to get proper default values
at boot time.
The new attribute shows up as:
Add a sysfs cpu_capacity attribute with which it is possible to read and
write (thus over-writing default values) CPUs capacity. This might be
useful in situation where there is no way to get proper default values
at boot time.
The new attribute shows up as:
Add Juno cpu capacity bindings information.
Cc: Rob Herring
Cc: Pawel Moll
Cc: Mark Rutland
Cc: Ian Campbell
Cc: Kumar Gala
Cc: Catalin Marinas
Cc: Will Deacon
Cc: Liviu Dudau
Cc: Sudeep Holla
Cc: Arnd Bergmann
Cc: Jon Medhurst
Cc: Olof Johansson
Cc: Robin Murphy
Cc:
Add TC2 cpu capacity binding information.
Cc: Liviu Dudau
Cc: Sudeep Holla
Cc: Lorenzo Pieralisi
Cc: Rob Herring
Cc: Pawel Moll
Cc: Mark Rutland
Cc: Ian Campbell
Cc: Kumar Gala
Cc: Russell King
Cc: devicet...@vger.kernel.org
Signed-off-by: Juri Lelli
---
With the introduction of cpu capacity bindings, CPU capacities can now be
extracted from DT. Add parsing of such information at boot time. Also,
store such information using per CPU variables, as we do for arm.
Cc: Catalin Marinas
Cc: Will Deacon
Cc: Mark Brown
Cc: Sudeep Holla
Signed-off-by:
ARM systems may be configured to have cpus with different power/performance
characteristics within the same chip. In this case, additional information
has to be made available to the kernel (the scheduler in particular) for it
to be aware of such differences and take decisions accordingly.
Instead of looping through all cpus calling set_capacity_scale, we can
initialise cpu_scale per-cpu variables to SCHED_CAPACITY_SCALE with their
definition.
Cc: Russell King
Signed-off-by: Juri Lelli
---
arch/arm/kernel/topology.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff
Hi all,
ARM systems may be configured to have CPUs with different power/performance
characteristics within the same chip. In this case, additional information has
to be made available to the kernel (the scheduler in particular) for it to be
aware of such differences and take decisions
Mark, Alexandre,
Enjoy!
The following changes since commit 1ec218373b8ebda821aec00bb156a9c94fad9cd4:
Linux 4.4-rc2 (2015-11-22 16:45:59 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git
tags/ib-mfd-regulator-rtc-v4.5
for you to
Since d8a1cb757550 ("PCI/MSI: Let pci_msi_get_domain use struct
device::msi_domain"), we use the MSI domain associated to the PCI device.
But finding a MSI domain doesn't mean that the domain is implemented
using the generic MSI domain API, and a number of MSI controllers
are still using the
use of_property_read_u8() for u8 values
Signed-off-by: Saurabh Sengar
---
drivers/mtd/nand/orion_nand.c | 22 +++---
1 file changed, 7 insertions(+), 15 deletions(-)
diff --git a/drivers/mtd/nand/orion_nand.c b/drivers/mtd/nand/orion_nand.c
index ee83749..1a68145 100644
---
Dear Jiri,
You should also add upstream commit 899f0c1c7dbcc487fdc8756a49ff70b1d5d75f89
Greg had a merge conflict in 4-1.y with another back-ported patch. But
in 3.12 this shouldn't be the case.
--
Cheers,
Soeren
On 11/23/2015 02:08 PM, Jiri Slaby wrote:
From: Soeren Grunewald
On Mon, 23 Nov 2015 17:28:05 +0900
Joonsoo Kim wrote:
> On Fri, Nov 20, 2015 at 11:42:25AM -0500, Steven Rostedt wrote:
> > On Fri, 20 Nov 2015 15:33:25 +0900
> > Joonsoo Kim wrote:
> >
> >
> > > Steven, is it possible to add tracepoint to inlined fucntion such as
> > > get_page() in
Always try to load modules for RC keymaps when the kernel supports
modules, not just when the RC Core is build as a module. Fixes
module autoloading issues when the core is builtin but the keymaps
are not.
Signed-off-by: Sjoerd Simons
---
drivers/media/rc/rc-main.c | 2 +-
1 file changed, 1
On Thu, Nov 19, 2015 at 09:28:28PM +0100, Peter Zijlstra wrote:
> On Thu, Nov 19, 2015 at 04:47:33PM +0100, Frederic Weisbecker wrote:
> > +++ b/include/linux/vtime.h
> > @@ -17,9 +17,20 @@ static inline bool vtime_accounting_cpu_enabled(void) {
> > return true; }
> > #endif /*
On 23/11/15 15:11, vas...@iit.demokritos.gr wrote:
> Ok I will send the .config when I get back home. I have all kernels I
> build in .deb archive. The problem is that the debian kernel build
> procedure does not hold somewhere in the deb file the git commit hash.
>
> Fow which kernel would you
On Mon, 23 Nov 2015 22:14:08 +0800
Fengguang Wu wrote:
> > Need to add RT in the subject like "[PATCH RT]". Then perhaps Fengguang
> > can have his tests either ignore these or test against the -rt trees.
>
> Yes sure. Shall I apply RT patches to this tree/branch?
>
>
Em Sun, Nov 22, 2015 at 07:11:56PM +0900, Taeung Song escreveu:
> Add perf-config document to describe the perf configuration
> and a subcommand 'list’.
Worked this time, applied, will continue processing the other patches
soon.
- Arnaldo
> Cc: Namhyung Kim
> Cc: Jiri Olsa
> Signed-off-by:
On Mon, Nov 23, 2015 at 4:56 AM, Saurabh Sengar wrote:
> use of_propert_read_u32() for reading int value,
> it can help reducing number of variables used
>
> Signed-off-by: Saurabh Sengar
Acked-by: Dan Streetman
> ---
> drivers/crypto/nx/nx-842-powernv.c | 11 ---
> 1 file changed, 4
url:
> > https://github.com/0day-ci/linux/commits/jianchuan-wang-windriver-com/locking_selftest-Save-restore-migrate_disable_atomic-in-locking-selftest/20151123-152217
> > config: x86_64-randconfig-x013-11230343 (attached as .config)
> > reproduce:
> > # save
On 11/23/2015 03:15 AM, Arnd Bergmann wrote:
> On Sunday 22 November 2015 21:36:45 Nicolas Pitre wrote:
>> On Sun, 22 Nov 2015, Arnd Bergmann wrote:
>>
>>> I've also found some /proc/cpuinfo output to cross-reference SoCs
>>> to their core names.
>>>
>>> variant partrevision
On 11/20/2015 02:23 PM, Juergen Gross wrote:
>
> As the BIOS obviously isn't disabling MTRR I don't think we have
> to go that route any longer.
ok.
>>
>> In the weekend I will return to 3.18-rc2 and I will try to verify my
>> bisection is correct. Double guessing your self is a terrible
use of_property_read_u8() for u8 variables,
also changed the return type to void as this function return type
is nowhere used.
Signed-off-by: Saurabh Sengar
---
drivers/thermal/samsung/exynos_tmu.c | 30 +-
1 file changed, 13 insertions(+), 17 deletions(-)
diff
Doug/Jaehoon,
Were there any follow ups to this thread [1] from March 30, 2015?
We are seeing HLE errors on 3.18 and we are trying to determine if a solution
was ever delivered.
On inspection, I can't find anything specific in recent kernels that address
this particular issue (was the actual root
The severe regression in alx ethernet driver is still present in the
latest released kernel. Patches have been posted in
https://bugzilla.kernel.org/show_bug.cgi?id=70761 There are reports
that these patches have resolved the problem. Could you please review
these patches and see if they can be
On Wed, 18 Nov 2015 23:04:12 +0100
Julia Lawall wrote:
> for_each_child_of_node performs an of_node_get on each iteration, so
> a break out of the loop requires an of_node_put.
>
> A simplified version of the semantic patch that fixes this problem is as
> follows (http://coccinelle.lip6.fr):
>
On 11/23/2015 02:44 PM, Arnd Bergmann wrote:
gcc correctly warns about both the adp8860 and adp8870 backlight
drivers using an uninitialized variable in their error handling
path:
drivers/video/backlight/adp8870_bl.c: In function
'adp8870_bl_ambient_light_zone_store':
On 23/11/2015 00:20, Mark Salter wrote:
> On Sun, 2015-11-22 at 00:56 +0800, Ming Lei wrote:
>> On Sat, 21 Nov 2015 12:30:14 +0100
>> Laurent Dufour wrote:
>>
>>> On 20/11/2015 13:10, Michael Ellerman wrote:
On Thu, 2015-11-19 at 00:23 -0800, Christoph Hellwig wrote:
> It's pretty
On ixp4xx, the readl() function returns an 'unsigned long' output
when indirect I/O is used. This is unlike any other platform, and
it causes lots of harmless compiler warnings, such as:
drivers/ata/libahci.c: In function 'ahci_show_host_version':
drivers/ata/libahci.c:254:22: warning: format
This one is a curious Kbuild glitch: The drivers/usb/phy/of.o file
is currently always built-in if CONFIG_OF is set, independent of
whether USB is modular or not.
For the case of CONFIG_USB=m && CONFIG_USB_GADGET=m && CONFIG_USB_PHY=n,
however the file is not built at all, because
in case of error no need to set num_tx and num_rx = 1, because in case of error
these variables will remain unchanged by of_property_read_u32 ie 1 only
Signed-off-by: Saurabh Sengar
---
drivers/net/ethernet/freescale/fec_main.c | 9 ++---
1 file changed, 2 insertions(+), 7 deletions(-)
For historic reasons, the tegra platform selects USB_ULPI from architecture
code, but that hasn't really made sense for a long time, as the only
user of that code is the Tegra EHCI driver that has its own Kconfig
symbol.
This removes the 'select' statements from mach-tegra and drivers/soc/tegra
On 11/23/2015 02:43 PM, Daniel Borkmann wrote:
On 11/21/2015 07:54 PM, Florian Westphal wrote:
Tejun Heo wrote:
On Sat, Nov 21, 2015 at 05:56:06PM +0100, Florian Westphal wrote:
+struct xt_cgroup_info_v1 {
+__u8has_path;
+__u8has_classid;
+__u8invert_path;
On Fri, Nov 20, 2015 at 11:21 AM, Allen Hung wrote:
> The usage Confidence is mandary to Windows Precision Touchpad devices. The
> appearance of this usage is checked in hidinput_connect but the quirk
> MT_QUIRK_VALID_IS_CONFIDENCE is not applied to device accordingly.
> Apply this quirk and also
gcc correctly warns about both the adp8860 and adp8870 backlight
drivers using an uninitialized variable in their error handling
path:
drivers/video/backlight/adp8870_bl.c: In function
'adp8870_bl_ambient_light_zone_store':
drivers/video/backlight/adp8870_bl.c:811:11: warning: 'reg_val' may be
On 11/21/2015 07:54 PM, Florian Westphal wrote:
Tejun Heo wrote:
On Sat, Nov 21, 2015 at 05:56:06PM +0100, Florian Westphal wrote:
+struct xt_cgroup_info_v1 {
+ __u8has_path;
+ __u8has_classid;
+ __u8invert_path;
+ __u8
selftest-Save-restore-migrate_disable_atomic-in-locking-selftest/20151123-152217
> config: x86_64-randconfig-x013-11230343 (attached as .config)
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> All errors (new ones prefixed by >>):
>
We can configure the bq27xxx_battery driver with neither the I2C
nor the platform driver backends, which leaves out all references
to some of the symbols, causing a couple of warnings in many
randconfig builds:
drivers/power/bq27xxx_battery.c:288:12: warning: 'bq27xxx_regs' defined but not
used
>>> On 23.11.15 at 14:27, wrote:
> On Monday 23 November 2015 06:45 PM, Jan Beulich wrote:
> On 23.11.15 at 14:03, wrote:
>>> I was wondering if u could answer a question in that respect:
>>> arch/arc/kernel/unwind.c
>>>
>>> If the binary search for a PC fails, it resorts to linear search,
MTD allows compile-time configuration of the possible CFI geometry
settings that are allowed by the kernel, but that includes a couple of
invalid configurations, where no bank width or no interleave setting
is allowed. These are then caught with a compile-time warning:
Folks,
This patch series is a response to the report that the EFI region
mappings trigger warnings when booting with CONFIG_DEBUG_WX enabled.
They allocate a new page table structure and ensure that all the
mappings we require during EFI runtime calls are only setup there.
It turns out that it
The x86 pageattr code is confused about the data that is stored in
cpa->pfn, sometimes it's treated as a page frame number, sometimes
it's treated as an unshifted physical address, and in one place it's
treated as a pte.
The result of this is that the mapping functions do not map the
intended
While _text is currently aligned to PAGE_SIZE in the vmlinux linker
script because it's based on CONFIG_PHYSICAL_ALIGN, it's always better
to be explicit about these things to be sure no alignment bugs are
lurking. There's no analogous enforcement for _end.
Dave provided an example of why the
When CONFIG_LBDAF is not set, sector_t is only 32-bits wide, which
means we cannot have devices with more than 2TB, and the code that
is trying to handle compatibility support for large devices in
md version 0.90 is meaningless but also causes a compile-time warning:
drivers/md/md.c: In function
Make it clear that the EFI page tables are only available during EFI
runtime calls since that subject has come up a fair numbers of times
in the past.
Additionally, add the EFI region start and end addresses to the table
so that it's possible to see at a glance where they fall in relation
to
This change is a prerequisite for pending patches that switch to a
dedicated EFI page table, instead of using 'trampoline_pgd' which
shares PGD entries with 'swapper_pg_dir'. The pending patches make it
impossible to dereference the runtime service function pointer without
first switching %cr3.
With commit e1a58320a38d ("x86/mm: Warn on W^X mappings") all users
booting on 64-bit UEFI machines see the following warning,
[ cut here ]
WARNING: CPU: 7 PID: 1 at arch/x86/mm/dump_pagetables.c:225
note_page+0x5dc/0x780()
x86/mm: Found insecure W+X mapping at
We are relying on the pre-existing mappings in 'trampoline_pgd' when
accessing function arguments in the EFI mixed mode thunking code.
Instead let's map memory explicitly so that things will continue to
work when we move to a separate page table in the future.
Reviewed-by: Borislav Petkov
Cc:
this patch does the following:
1 . remove unnecessary if, else condition
2 . reduce one variable
3 . change the return type of 2 functions to void as there return values
turn out to be 0 always after above changes
Signed-off-by: Saurabh Sengar
---
On Monday 23 November 2015 06:45 PM, Jan Beulich wrote:
On 23.11.15 at 14:03, wrote:
>> I was wondering if u could answer a question in that respect:
>> arch/arc/kernel/unwind.c
>>
>> If the binary search for a PC fails, it resorts to linear search, which for
>> our
>> case was taking 3
From: Johannes Berg
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 2cf5eb3ab7bb7f2e3a70edcef236cd62c87db030 upstream.
The code to send the RX PN data (for each TID) to the firmware
has a devastating bug: it overwrites the data for TID 0
We can end up allocating a new compression stream with GFP_KERNEL
from within the IO path, which may result is nested (recursive) IO
operations. That can introduce problems if the IO path in question
is a reclaimer, holding some locks that will deadlock nested IOs.
Allocate streams and working
From: Johannes Berg
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 5bd166872d8f99f156fac191299d24f828bb2348 upstream.
The code to send the RX PN data (for each TID) to the firmware
has a devastating bug: it overwrites the data for TID 0
From: Johannes Berg
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit b5a48134f8af08f5243328f8a0b05fc5ae7cf343 upstream.
The MODULE_FIRMWARE() for 3160 should be using the 7260 version as
it's done in the device configuration struct instead of
From: Mike Snitzer
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 4dcb8b57df3593dcb20481d9d6cf79d1dc1534be upstream.
btree_split_beneath()'s error path had an outstanding FIXME that speaks
directly to the potential for _not_ cleaning up a
From: Joerg Roedel
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit cbf3ccd09d683abf1cacd36e3640872ee912d99b upstream.
During device assignment/deassignment the flags in the DTE
get lost, which might cause spurious faults, for example
when
From: Laura Abbott
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit fd7cd061adcf5f7503515ba52b6a724642a839c8 upstream.
We received several reports of systems rebooting and powering on
after an attempted shutdown. Testing showed that setting
From: Cathy Avery
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit a54c8f0f2d7df525ff997e2afe71866a1a013064 upstream.
xen-blkfront will crash if the check to talk_to_blkback()
in blkback_changed()(XenbusStateInitWait) returns an error.
The
From: Mathias Nyman
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 3b4739b8951d650becbcd855d7d6f18ac98a9a85 upstream.
If a host fails to wake up a isochronous SuperSpeed device from U1/U2
in time for a isoch transfer it will generate a "No
From: Jes Sorensen
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 203d27b0226a05202438ddb39ef0ef1acb14a759 upstream.
This was introduced with 9e882242c6193ae6f416f2d8d8db0d9126bd996b
which changed the return value of submit_bio_wait() to
From: Dāvis Mosāns
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 2280521719e81919283b82902ac24058f87dfc1b upstream.
When pci_pool_alloc fails in mvs_task_prep then task->lldd_task stays
NULL but it's later used in mvs_abort_task as slot
From: Jes Sorensen
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 681ab4696062f5aa939c9e04d058732306a97176 upstream.
This was introduced with 9e882242c6193ae6f416f2d8d8db0d9126bd996b
which changed the return value of submit_bio_wait() to
From: Peter Zijlstra
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 275d7d44d802ef271a42dc87ac091a495ba72fc5 upstream.
Poma (on the way to another bug) reported an assertion triggering:
[] module_assert_mutex_or_preempt+0x49/0x90
[]
From: Herbert Xu
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 3fc89adb9fa4beff31374a4bf50b3d099d88ae83 upstream.
Currently a number of Crypto API operations may fail when a signal
occurs. This causes nasty problems as the caller of those
Fix checkpatch checks: "Blank lines aren't necessary before a close brace '}' "
Remove two unnecessary blank lines.
Signed-off-by: Christian Colic
---
drivers/staging/wlan-ng/cfg80211.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/staging/wlan-ng/cfg80211.c
From: Doron Tsur
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 0ca81a2840f77855bbad1b9f172c545c4dc9e6a4 upstream.
ib_send_cm_sidr_rep could sometimes erase the node from the sidr
(depending on errors in the process). Since
From: Soeren Grunewald
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 96a5d18bc1338786fecac73599f1681f59a59a8e upstream.
The Exar XR17V358 chip usually provides only 8 ports. But two chips can be
combined to act as a single 16 port chip.
From: Soeren Grunewald
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit be32c0cf0462c36f482b5ddcff1d8371be1e183c upstream.
The Exar XR17V358 can also be combined with a XR17V354 chip to act as a
single 12 port chip. This works the same way as
From: Charles Keepax
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 02915661dbb91b25b621ab3f387ab55311bded7f upstream.
Evaluation of revision D of WM5110 suggests updates to the register
patch for optimal performance. For the sake of
From: Will Deacon
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 9702970c7bd3e2d6fecb642a190269131d4ac16c upstream.
This reverts commit e306dfd06fcb44d21c80acb8e5a88d55f3d1cf63.
With this patch applied, we were the only architecture making
From: Dan Carpenter
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit e819cdb198319cccf4af4fc12ac4d796109d8c23 upstream.
These are signed values the come from the user, we put a cap on the
upper bounds but not on the lower bounds.
We use
On Sat, Nov 21, 2015 at 10:14:44PM +0800, Geliang Tang wrote:
> Use offset_in_page macro instead of (addr & ~PAGE_MASK).
>
> Signed-off-by: Geliang Tang
> ---
> include/linux/dma-mapping.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
I don't know which tree you're aiming at,
From: Hans de Goede
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 039ece38da45f5e6a94be3aa7611cf3634bc2461 upstream.
Allwinner A10 and A20 ARM SoCs have an AHCI sata controller which needs a
special register to be poked before starting the
From: Charles Keepax
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 81207880cef207cd89db863f9aa1d65f22b4f2a2 upstream.
Add a register patch for rev E and above that configures the location of
some write sequences to assist with the
From: Dan Williams
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit dbfe8ef5599a5370abc441fcdbb382b656563eb4 upstream.
Avoton AHCI occasionally sees drive probe timeouts at driver load time.
When this happens SCR_STATUS indicates device
From: Paul Moore
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 4a92843601ad0f5067f441d2f0dca55bbe18c076 upstream.
There is a problem with the audit system when multiple audit records
are created for the same path, each with a different
From: SeongJae Park
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit e1bde3b11fedace5042f0232339da90bc85666af upstream.
Fix the pointer-integer size mismatch warning below:
drivers/spi/spi-gpio.c: In function ‘spi_gpio_setup’:
From: Paul Moore
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit fcf22d8267ad2601fe9b6c549d1be96401c23e0b upstream.
Unfortunately, while commit 4a928436 ("audit: correctly record file
names with different path name types") fixed a problem
From: Dan Carpenter
3.12-stable review patch. If anyone has any objections, please let me know.
===
[ Upstream commit 50010c20597d14667eff0fdb628309986f195230 ]
This is decrementing the pointer, instead of the value stored in the
pointer. KASan detects it as an out of bounds
From: Tom Tucker
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 7e4359e2611f95a97037e2b6905eab52f28afbeb upstream.
The server regression was caused by the addition of rq_next_page
(afc59400d6c65bad66d4ad0b2daf879cbff8e23e). There were a few
From: "Lad, Prabhakar"
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 31f50e48e3e4ea9d503285a389d6a1b5349d66c0 upstream.
This patch fixes following build warning:
In file included from include/linux/printk.h:261:0,
from
From: Guillaume Nault
3.12-stable review patch. If anyone has any objections, please let me know.
===
[ Upstream commit 1acea4f6ce1b1c0941438aca75dd2e5c6b09db60 ]
We can't rely on PPPOX_ZOMBIE to decide whether to clear po->pppoe_dev.
PPPOX_ZOMBIE can be set by pppoe_disc_rcv()
From: Carol L Soto
3.12-stable review patch. If anyone has any objections, please let me know.
===
[ Upstream commit c02b05011fadf8e409e41910217ca689f2fc9d91 ]
When doing memcpy/memset of EQEs, we should use sizeof struct
mlx4_eqe as the base size and not caps.eqe_size which
From: Ani Sinha
3.12-stable review patch. If anyone has any objections, please let me know.
===
[ Upstream commit 44f49dd8b5a606870a1f21101522a0f9c4414784 ]
Fixes the following kernel BUG :
BUG: using __this_cpu_add() in preemptible [] code: bash/2758
caller is
From: Anton Blanchard
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 733187e29576041ceccf3b82092ca900fc929170 upstream.
commit f13c13a00512 (powerpc: Stop using non-architected shared_proc
field in lppaca) fixed a potential issue with
From: Ani Sinha
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit 6a2a2b3ae0759843b22c929881cc184b00cc63ff upstream.
Linux manpage for recvmsg and sendmsg calls does not explicitly mention setting
msg_namelen to 0 when
msg_name passed set as
From: Vasily Averin
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit aff09ce303f83bd370772349238482ae422a2341 upstream.
Currently bridge can silently drop ipv4 fragments.
If node have loaded nf_defrag_ipv4 module but have no
From: Holger Eitzenberger
3.12-stable review patch. If anyone has any objections, please let me know.
===
commit d954777324ffcba0b2f8119c102237426c654eeb upstream.
V3 of the NFQUEUE target ignores the --queue-bypass flag,
causing packets to be dropped when the userspace listener
701 - 800 of 2144 matches
Mail list logo
