3.12.30-rt40 + patch has been running your testcase, futextests and
stockfish concurrently (on a 28 core +ht box) for over an hour now.
On Sat, 2014-10-25 at 20:20 -0400, Brian Silverman wrote:
free_pi_state and exit_pi_state_list both clean up futex_pi_state's.
exit_pi_state_list takes the hb
On Sun, Oct 26, 2014 at 12:21:31AM +0200, Thomas Gleixner wrote:
On Sun, 26 Oct 2014, Thomas Gleixner wrote:
On Thu, 23 Oct 2014, Chris Friesen wrote:
Does the RT kernel just disallow this sort of algorithm?
Yes. For a good reason. Let's add thread C
A B
At Sat, 25 Oct 2014 11:41:15 -0200,
Mauro Carvalho Chehab wrote:
(re-sending from my third e-mail - somehow, the two emails I have at
Samsung didn't seem to be delivering to vger.kernel.org today)
Em Wed, 22 Oct 2014 14:26:41 -0500
Pierre-Louis Bossart pierre-louis.boss...@linux.intel.com
On Sun, Oct 26, 2014 at 08:42:57AM +0100, Peter Zijlstra wrote:
On Sun, Oct 26, 2014 at 12:21:31AM +0200, Thomas Gleixner wrote:
On Sun, 26 Oct 2014, Thomas Gleixner wrote:
On Thu, 23 Oct 2014, Chris Friesen wrote:
Does the RT kernel just disallow this sort of algorithm?
Yes. For
This patch set fixes two race conditions in the TPM subsystem:
* Two-phase initialization for struct tpm_chip so that device can
initialize fully initialize before exposing itself to the user
space. Also, in future TPM2 devices must be flagged before they
can be registered.
* Machines where
Merged transmit_cmd() functions in tpm-interface.c and tpm-sysfs.c.
Added tpm_ prefix for consistency sake. Changed cmd parameter as
opaque. This enables to use separate command structures for TPM1
and TPM2 commands in future. Loose coupling works fine here.
Signed-off-by: Jarkko Sakkinen
Traversal of the ACPI device tree was not done right. It should lookup
PPI only under the ACPI device that it is associated. Otherwise, it could
match to a wrong PPI interface if there are two TPM devices in the device
tree.
Removed global ACPI handle and version string from tpm_ppi.c as this
is
tpm_register_hardware() and tpm_remove_hardware() are called often
before initializing the device. This is wrong order since it could
be that main TPM driver needs a fully initialized chip to be able to
do its job. For example, now it is impossible to move common startup
functions such as
Use list_first_entry_or_null() for first_region() and first_queue_range().
list_first_entry() expects the list is not empty, so first_region() and
first_queue_range() never return NULL.
Thus use list_first_entry_or_null() instead.
Signed-off-by: Axel Lin axel@ingics.com
---
Don't call mutex_unlock() in the error patch if the mutex_lock() is not called.
Signed-off-by: Axel Lin axel@ingics.com
---
drivers/soc/ti/knav_qmss_queue.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/soc/ti/knav_qmss_queue.c
Return -ENOMEM if devm_kzalloc fails.
Signed-off-by: Axel Lin axel@ingics.com
---
drivers/soc/ti/knav_qmss_queue.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/soc/ti/knav_qmss_queue.c b/drivers/soc/ti/knav_qmss_queue.c
index d66aaf2..6f22d56 100644
---
Karol Wrona schrieb am 14.10.2014 16:37:
Adds stm32 bootloader protocol handling.
SPI transfers are done using DMA safe buffer which is allocated once per
spi upgrade life cycle. Now it supports only SPI bus but it looks that UART
or I2C are quite similar and it can be used as start platform
X550VB as many others Asus laptops need wapf4 quirk to make RFKILL
switch be functional. Otherwise system boots with wireless card
disabled and is only possible to enable it by suspend/resume.
Bug report:
http://bugzilla.redhat.com/show_bug.cgi?id=1089731#c23
Reported-and-tested-by: Vratislav
On Sat, Oct 25, 2014 at 01:42:46PM +0200, Pavel Machek wrote:
Since 3.17 we have only 2 minor iwlegacy changes on current linus tree.
If this is a regression it's probably caused by different subsystem
changes, most likely by PCI changes. If this is not regression, such
errors could be
On Fri, Oct 24, 2014 at 06:38:41PM +0200, Mike Galbraith wrote:
Whew, good, futex.c is hard. Heads up chess guys punt.
I wonder whether the barrier fix which got into 3.17 late fixes that
issue as well.
Yes, it did.
This is only about the lockup, right, not that the threads bounce around a
On 10/22/14 15:24, Mikulas Patocka wrote:
I uploaded the new version of SCSI/device-mapper XCOPY patches here:
http://people.redhat.com/~mpatocka/patches/kernel/xcopy/series.html
I am also sending the patches in the following emails.
Hello Mikulas,
Which is the base commit of this patch
On Sun 2014-10-26 11:33:15, Stanislaw Gruszka wrote:
On Sat, Oct 25, 2014 at 01:42:46PM +0200, Pavel Machek wrote:
Since 3.17 we have only 2 minor iwlegacy changes on current linus tree.
If this is a regression it's probably caused by different subsystem
changes, most likely by PCI
Hi!
On Sun, Oct 19, 2014 at 09:19:37PM +0200, Pavel Machek wrote:
I am trying to use nfsroot, so I can't use modules.
Why not?
(I am attaching full config, in case I missed something important).
I'm using the below config with 3.17 and g_ether works OK.
(My initramfs modprobes
On Sunday 26 October 2014 12:08:25 Pavel Machek wrote:
Hi!
On Sun, Oct 19, 2014 at 09:19:37PM +0200, Pavel Machek wrote:
I am trying to use nfsroot, so I can't use modules.
Why not?
(I am attaching full config, in case I missed something
important).
I'm using the below
Am Samstag, 25. Oktober 2014, 10:37:33 schrieb Johan Hovold:
[+CC: Felipe ]
On Sat, Oct 25, 2014 at 09:28:36AM +0200, Romain Perier wrote:
Hi Johan,
If that's still possible to do these changes, I am opened to suggestions.
Before v3.18 comes out, we can always change it with a
On Sat, Oct 25, 2014 at 04:24:52PM +0800, john.liuli wrote:
From: Li Liu john.li...@huawei.com
This set of patches try to implemet irqfd support of vhost-net
based on virtio-mmio.
I had posted a mail to talking about the status of vhost-net
on kvm-arm refer to
On Sat, Oct 25, 2014 at 04:24:54PM +0800, john.liuli wrote:
From: Li Liu john.li...@huawei.com
This irq handler will get the interrupt reason from a
shared memory. And will be assigned only while irqfd
enabled.
Signed-off-by: Li Liu john.li...@huawei.com
---
On Sun 2014-10-26 12:12:46, Pali Rohár wrote:
On Sunday 26 October 2014 12:08:25 Pavel Machek wrote:
Hi!
On Sun, Oct 19, 2014 at 09:19:37PM +0200, Pavel Machek wrote:
I am trying to use nfsroot, so I can't use modules.
Why not?
(I am attaching full config, in case I
On Sat, Oct 25, 2014 at 04:24:53PM +0800, john.liuli wrote:
From: Li Liu john.li...@huawei.com
Add a new register offset VIRTIO_MMIO_ISRMEM which help to
estblish a shared memory region between virtio-mmio driver
and qemu with two purposes:
1.Guest virtio-mmio driver can get the interrupt
Hi Sebastian,
Am Dienstag, 23. September 2014, 22:42:13 schrieb Heiko Stuebner:
This series adds devicetree support to the gpio-charger and fixes a small
issue with the return value of gpio_get_value.
changes since v3:
- remove of_match_ptr. All used of_xx function have stubs for !OF
and
What platforms have you tested the code on at this point ?
None. - My test computer does not provide the corresponding hardware for the
affected driver source files.
Regards,
Markus
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
This patch fixes sparse warning:
obsolete struct initializer, use C99 syntax
Signed-off-by: Peng Fan van.free...@gmail.com
---
drivers/tty/vt/vt.c | 16 ++--
1 file changed, 10 insertions(+), 6 deletions(-)
diff --git a/drivers/tty/vt/vt.c b/drivers/tty/vt/vt.c
index
Lv,
These two patches introduce a regression for Samsung notebooks and they no
longer get ACPI interrupts for plugging the power adapter or LID switches.
Multiple people have verified that reverting these patches makes the regression
go away.
Please see new comments in:
Hi,
Running 32 bit user space needs some work to be done with ioctls. I understand
that there are two options to implement:
1. Use only fixed size types. Pad IOCTLS params to multiple of 64 bits -
simple; don't know if it covers all compatibility issues;
2. 32 bit compatibility
unused variables are removed. These variables were only assigned some
values and after that they were never being used. So they are safe to
be removed , and it has been build tested.
Signed-off-by: Sudip Mukherjee su...@vectorindia.org
---
drivers/staging/rtl8712/hal_init.c| 9
Am 26.10.2014 um 01:08 schrieb Alexander Graf:
On 24.10.14 14:20, suravee.suthikulpa...@amd.com wrote:
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index 48b7437..e4c052f 100644
--- a/arch/arm64/Kconfig
+++ b/arch/arm64/Kconfig
@@ -137,6 +137,11 @@ source kernel/Kconfig.freezer
On Friday 24 October 2014 18:26:58 Michal Nazarewicz wrote:
On Fri, Oct 24 2014, Laurent Pinchart wrote:
Commit 95b0e655f914 (ARM: mm: don't limit default CMA region only to
low memory) extended CMA memory reservation to allow usage of high
memory. It relied on commit f7426b983a6a (mm: cma:
Hi Geert,
Thank you for the patch.
On Friday 24 October 2014 13:29:38 Geert Uytterhoeven wrote:
The TPU2 hardware block is found in many Renesas SH and ARM SoCs, but
s/TPU2/MTU2/
With this fixed,
Acked-by: Laurent Pinchart laurent.pinch...@ideasonboard.com
not in R-Car.
Signed-off-by:
Hi Geert,
Thank you for the patch.
On Friday 24 October 2014 13:31:52 Geert Uytterhoeven wrote:
The r8a7778 is very similar to the r8a7779, and already handled by
the current driver in the non-DT case.
Signed-off-by: Geert Uytterhoeven geert+rene...@glider.be
Acked-by: Laurent Pinchart
On Sun, 2014-10-26 at 11:39 +0100, Steinar H. Gunderson wrote:
On Fri, Oct 24, 2014 at 06:38:41PM +0200, Mike Galbraith wrote:
Whew, good, futex.c is hard. Heads up chess guys punt.
I wonder whether the barrier fix which got into 3.17 late fixes that
issue as well.
Yes, it did.
This
The need for performing read disturb is determined according to new
statistics collected per eraseblock:
- read counter: incremented at each read operation
reset at each erase
- last erase time stamp: updated at each erase
This patch adds the infrastructure for the above
One of the criteria to scrub an eraseblock due to read disturb issue is
if that eraseblock was read from more times then a pre-defined threshold.
This is verified at each LEB read according to the read counter
parameter of the read PEB.
An eraseblock that is found needs scrubbing is added to the
Make the in_wl_tree function public to be used outside of wl.c.
Rename it to ubi_in_wl_tree.
Signed-off-by: Tanya Brokhman tlin...@codeaurora.org
---
drivers/mtd/ubi/ubi.h | 1 +
drivers/mtd/ubi/wl.c | 18 +-
2 files changed, 10 insertions(+), 9 deletions(-)
diff --git
A given eraseblock can be read many times or not at all.
We do not have the account of such eraseblocks that have
not been accessed since a pre-defined threshold interval.
By means of scanning the entire flash device it is possible to identify
all such eraseblocks.
Add a sysfs entry to force scan
Fill in eraseblock statistics needed for read disturb decision making:
1. read counter: incremented at each read operation
reset at each erase operation
Saved only as part of the meta data in RAM
On attach: if fastmap data is missing a default value is assigned
2. last
On Sun, 2014-10-26 at 14:16 +0100, Mike Galbraith wrote:
On Sun, 2014-10-26 at 11:39 +0100, Steinar H. Gunderson wrote:
On Fri, Oct 24, 2014 at 06:38:41PM +0200, Mike Galbraith wrote:
Whew, good, futex.c is hard. Heads up chess guys punt.
I wonder whether the barrier fix which got
Am 26.10.2014 um 13:43 schrieb Andreas Färber afaer...@suse.de:
Am 26.10.2014 um 01:08 schrieb Alexander Graf:
On 24.10.14 14:20, suravee.suthikulpa...@amd.com wrote:
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index 48b7437..e4c052f 100644
--- a/arch/arm64/Kconfig
+++
Hi,
Am 24.10.2014 um 14:20 schrieb suravee.suthikulpa...@amd.com:
diff --git a/arch/arm64/boot/dts/Makefile b/arch/arm64/boot/dts/Makefile
index f8001a6..6c27047 100644
--- a/arch/arm64/boot/dts/Makefile
+++ b/arch/arm64/boot/dts/Makefile
@@ -1,6 +1,7 @@
dtb-$(CONFIG_ARCH_THUNDER) +=
On Sun, Oct 26, 2014 at 02:58:36PM +0100, Mike Galbraith wrote:
Can you try the below?
I can bake it into the kernel the next time I boot, but that is unlikely to
be anytime soon, I'm afraid. I'm maybe a bit surprised nobody else can
reproduce my issue; I assume it won't help if I give out shell
From: Lin Yongting linyongt...@gmail.com
The memset function never had unwinding annotations added.
Currently, when accessing NULL pointer by memset occurs the
backtrace shown will stop at memset or some completely unrelated
function. Add unwinding annotations in hopes of getting a more
useful
Currently we print the slabinfo header in the seq start method, which
makes it unusable for showing leaks, so we have leaks_show, which does
practically the same as s_show except it doesn't show the header.
However, we can print the header in the seq show method - we only need
to check if the
Let's use generic slab_start/next/stop for showing memcg caches info.
In contrast to the current implementation, this will work even if all
memcg caches' info doesn't fit into a seq buffer (a page), plus it
simply looks neater.
Actually, the main reason I do this isn't mere cleanup. I'm going to
On Sat, 25 Oct 2014, Brian Silverman wrote:
On Sat, 25 Oct 2014, Thomas Gleixner wrote:
pi_state_free and exit_pi_state_list both clean up futex_pi_state's.
exit_pi_state_list takes the hb lock first, and most callers of
pi_state_free do too. requeue_pi didn't, which causes lots of
On Sun, 2014-10-26 at 15:11 +0100, Steinar H. Gunderson wrote:
On Sun, Oct 26, 2014 at 02:58:36PM +0100, Mike Galbraith wrote:
Can you try the below?
I can bake it into the kernel the next time I boot, but that is unlikely to
be anytime soon, I'm afraid. I'm maybe a bit surprised nobody
On Sat, 25 Oct 2014, Brian Silverman wrote:
@@ -1558,6 +1558,12 @@ retry_private:
ret = get_futex_value_locked(curval, uaddr1);
if (unlikely(ret)) {
+ /*
+ * We will have to lookup the pi_state again, so
+
Johan,
You convinced me. I will add an helper function
of_is_system_power_controller(node) which is compatible with both
properties: with or without the vendor prefix (until everything switch
to the new one).
In this case , we can adapt all drivers without break compatibility
and in few months if
Hi,
Am 17.10.2014 um 16:51 schrieb Bjorn Andersson:
On Wed 08 Oct 14:33 PDT 2014, Jeffrey Hugo wrote:
On 9/29/2014 6:34 PM, Bjorn Andersson wrote:
diff --git a/include/linux/soc/qcom/qcom_smem.h
b/include/linux/soc/qcom/qcom_smem.h
include/soc/ already exists, why add include/linux/soc?
On Sat, 25 Oct 2014, Brian Silverman wrote:
@@ -64,6 +64,7 @@
#include linux/hugetlb.h
#include linux/freezer.h
#include linux/bootmem.h
+#include linux/lockdep.h
Already included.
* PI futexes can not be requeued and must remove themself from the
* hash bucket. The hash bucket
ERROR: that open brace { should be on the previous line
Signed-off-by: Paul McQuade paulmcq...@gmail.com
---
drivers/staging/rtl8723au/core/rtw_ap.c | 130 ++--
1 file changed, 40 insertions(+), 90 deletions(-)
diff --git a/drivers/staging/rtl8723au/core/rtw_ap.c
Rewrite TURBOchannel error handling to use a common failure path, making
sure put_device is called for devices that failed initialization. While
at it update printk calls to use pr_err rather than KERN_ERR. Finally
avoid printk format warnings on resource_size_t type variables.
Commit-ID: 30a6b8031fe14031ab27c1fa3483cb9780e7f63c
Gitweb: http://git.kernel.org/tip/30a6b8031fe14031ab27c1fa3483cb9780e7f63c
Author: Brian Silverman bsilver16...@gmail.com
AuthorDate: Sat, 25 Oct 2014 20:20:37 -0400
Committer: Thomas Gleixner t...@linutronix.de
CommitDate: Sun, 26 Oct
Commit-ID: 993b2ff221999066fcff231590593d0b98f45d32
Gitweb: http://git.kernel.org/tip/993b2ff221999066fcff231590593d0b98f45d32
Author: Davidlohr Bueso d...@stgolabs.net
AuthorDate: Thu, 23 Oct 2014 20:27:00 -0700
Committer: Thomas Gleixner t...@linutronix.de
CommitDate: Sun, 26 Oct 2014
On Fri, Oct 24, 2014 at 2:18 PM, Kweh Hock Leong
hock.leong.k...@intel.com wrote:
From: Kweh, Hock Leong hock.leong.k...@intel.com
When using request_firmware_nowait() with FW_ACTION_NOHOTPLUG param to
expose user helper interface, if the user do not react immediately, after
120 seconds there
On 10/25/2014 11:00 AM, Andrew Lunn wrote:
On Sat, Oct 25, 2014 at 10:23:27AM -0700, Florian Fainelli wrote:
On 10/25/14 07:01, Andrew Lunn wrote:
Here is another naming option:
em1dsa0-virtual-0
I prefer this over isa.
However, i think there should be some sort of separator between the
On Fri, Oct 24, 2014 at 2:18 PM, Kweh Hock Leong
hock.leong.k...@intel.com wrote:
From: Kweh, Hock Leong hock.leong.k...@intel.com
Besides aborting through user helper interface, a new API
request_firmware_abort() allows kernel driver module to abort the
request_firmware() /
ERROR: foo*bar should be foo *bar
Signed-off-by: Paul McQuade paulmcq...@gmail.com
---
drivers/staging/rtl8723au/core/rtw_cmd.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/rtl8723au/core/rtw_cmd.c
b/drivers/staging/rtl8723au/core/rtw_cmd.c
Fix duplicate XT-PIC seen in /proc/interrupts on x86 systems that make
use of 8259A Programmable Interrupt Controllers. Specifically convert
output like this:
CPU0
0: 76573XT-PIC-XT-PICtimer
1: 11XT-PIC-XT-PICi8042
2: 0XT-PIC-XT-PIC
ERROR: foo * bar should be foo *bar
Signed-off-by: Paul McQuade paulmcq...@gmail.com
---
drivers/staging/rtl8723au/core/rtw_efuse.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/rtl8723au/core/rtw_efuse.c
ERROR: spaces required around that ':' (ctx:VxE)
Signed-off-by: Paul McQuade paulmcq...@gmail.com
---
drivers/staging/rtl8723au/core/rtw_ieee80211.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/staging/rtl8723au/core/rtw_ieee80211.c
Hi Maxime,
Thank you for the patch.
On Thursday 16 October 2014 11:01:01 Maxime Ripard wrote:
chanctnt is already filled by dma_async_device_register, which uses the
channel list to know how much channels there is.
Since it's already filled, we can safely remove it from the drivers' probe
On Fri, 2014-10-24 at 19:38 -0700, H. Peter Anvin wrote:
On 10/24/2014 05:22 PM, Andy Lutomirski wrote:
Is there any good reason not to use vmalloc for x86_64 stacks?
Additional TLB pressure if anything else.
It seems TLB pressure gets less and less interest these days...
Is it still worth
Add support for reading switch registers with 'ethtool -d'.
Signed-off-by: Guenter Roeck li...@roeck-us.net
---
v2:
- Do not compare new function pointers against NULL
- Check if get_regs is set before calling it
include/net/dsa.h | 7 +++
net/dsa/slave.c | 23 +++
2
Display sw_in_discards, sw_in_filtered, and sw_out_filtered for chips
supported by mv88e6123_61_65 and mv88e6352 drivers.
The variables are provided in port registers, not the normal status registers.
Mark by adding 0x100 to the register offset and add special handling code
to
Report switch register values to ethtool.
Signed-off-by: Guenter Roeck li...@roeck-us.net
---
v2:
- No change
drivers/net/dsa/mv88e6352.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/net/dsa/mv88e6352.c b/drivers/net/dsa/mv88e6352.c
index 8a956f9..d5bbe49 100644
---
The infrastructure can now report switch registers to ethtool.
Add support for it to the mv88e6123_61_65 driver.
Signed-off-by: Guenter Roeck li...@roeck-us.net
---
v2:
- No change
drivers/net/dsa/mv88e6123_61_65.c | 2 ++
drivers/net/dsa/mv88e6xxx.c | 24
The dsa core now supports reading from and writing to a switch EEPROM
if connected. Describe optional devicetree property indicating that
an EEPROM is present and its size.
Signed-off-by: Guenter Roeck li...@roeck-us.net
---
v2:
- Added patch
Documentation/devicetree/bindings/net/dsa/dsa.txt |
MV88E6352 supports read and write access to its configuration eeprom.
There is no means to detect if an EEPROM is connected to the switch.
Also, the switch supports EEPROMs with different sizes, but can not detect
or report the type or size of connected EEPROMs. Therefore, do not implement
the
On some chips it is possible to access the switch eeprom.
Add infrastructure support for it.
Signed-off-by: Guenter Roeck li...@roeck-us.net
---
v2:
- Add support for configuring switch EEPROM size through platform data
or devicetree data
- Do not compare new pointers against NULL
- Check if
MV88E6352 supports reading the chip temperature from two PHY registers,
6:26 and 6:27. Report it using the more accurate register 6:27.
Also report temperature limit and alarm.
Signed-off-by: Guenter Roeck li...@roeck-us.net
---
v2:
- Make new functionality optional, depending on
MV88E6123 and compatible chips support reading the chip temperature
from PHY register 6:26.
Signed-off-by: Guenter Roeck li...@roeck-us.net
---
v2:
- Make new functionality optional, depending on CONFIG_NET_DSA_HWMON
drivers/net/dsa/mv88e6123_61_65.c | 68 +--
Marvell 88E6352 is mostly compatible to MV88E6123/61/65,
but requires indirect phy access. Also, its configuration
registers are a bit different.
Signed-off-by: Guenter Roeck li...@roeck-us.net
---
v2:
- No change
MAINTAINERS | 5 +
drivers/net/dsa/Kconfig | 8 +
MV88E6176 is mostly compatible to MV88E6352 and is documented
in the same functional specification. Add support for it.
Signed-off-by: Guenter Roeck li...@roeck-us.net
---
v2:
- No change
drivers/net/dsa/Kconfig | 5 +++--
drivers/net/dsa/mv88e6352.c | 2 ++
2 files changed, 5
Setting skb-protocol to a private protocol type may result in warning
messages such as
e1000e :00:19.0 em1: checksum_partial proto=dada!
This happens if the L3 protocol is IP or IPv6 and skb-ip_summed is set
to CHECKSUM_PARTIAL. Looking through the code, it appears that changing
Report known silicon revisions when probing Marvell 88E6131 switches.
Signed-off-by: Guenter Roeck li...@roeck-us.net
---
v2:
- No change
drivers/net/dsa/mv88e6131.c | 12
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/drivers/net/dsa/mv88e6131.c
Some switches provide chip temperature data.
Add support for reporting it through the hwmon subsystem.
Signed-off-by: Guenter Roeck li...@roeck-us.net
---
v2:
- Updated headline to reflect what is reported, not how.
- Make added functionality optional with new Kconfig flag
- Register with hwmon
Patch 01/15 addresses an annoying and unhelpful log message.
Patches 02/15 and 03/15 are minor enhancements, adding support for
known switch revisions.
Patches 04/15 and 05/15 add support for MV88E6352 and MV88E6176.
Patch 06/15 adds support for hardware monitoring, specifically for
reporting
Report known silicon revisions when probing Marvell 88E6060 switches.
Signed-off-by: Guenter Roeck li...@roeck-us.net
---
v2:
- No change
drivers/net/dsa/mv88e6060.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/net/dsa/mv88e6060.c b/drivers/net/dsa/mv88e6060.c
If an attacker can cause a controlled kernel stack overflow,
overwriting the restart block is a very juicy exploit target.
Moving the restart block to struct task_struct prevents this type of
exploit.
It's also a decent simplification, since the restart code is more or
less identical on all
Hi Linus,
The following changes since commit f114040e3ea6e07372334ade75d1ee0775c355e1:
Linux 3.18-rc1 (2014-10-19 18:08:38 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
tags/armsoc-for-rc2
for you to fetch changes up to
On Sun, Oct 26, 2014 at 10:02:16AM -0700, Andy Lutomirski wrote:
If an attacker can cause a controlled kernel stack overflow,
overwriting the restart block is a very juicy exploit target.
Moving the restart block to struct task_struct prevents this type of
exploit.
The hell it does. In a
On Mon, Oct 13, 2014 at 12:11 PM, Bjorn Helgaas bhelg...@google.com wrote:
[+cc Alex, Christian, dri-devel]
On Sat, Oct 11, 2014 at 1:37 PM, Shawn Starr shawn.st...@rogers.com wrote:
On September 11, 2014 04:26:21 PM Bjorn Helgaas wrote:
[+cc linux-pci]
On Sat, Aug 2, 2014 at 10:02 AM,
On Sun, Oct 26, 2014 at 10:18 AM, Al Viro v...@zeniv.linux.org.uk wrote:
On Sun, Oct 26, 2014 at 10:02:16AM -0700, Andy Lutomirski wrote:
If an attacker can cause a controlled kernel stack overflow,
overwriting the restart block is a very juicy exploit target.
Moving the restart block to
On Sun, Oct 26, 2014 at 10:36:45AM -0700, Andy Lutomirski wrote:
I never said it was the *only* juicy target, but we can fix the rest,
too. Also, I suspect that overwriting task could be harder to
exploit. First, you need to avoid crashing, and second, on systems
with SMAP or similar
On x86 we have discussed to combine thread_info and task_struct into a single
allocation with a percpu variable lining pointng at it.
On October 26, 2014 11:09:39 AM PDT, Al Viro v...@zeniv.linux.org.uk wrote:
On Sun, Oct 26, 2014 at 10:36:45AM -0700, Andy Lutomirski wrote:
I never said it was
On Sat, Oct 25, 2014 at 4:16 PM, Andy Lutomirski l...@amacapital.net wrote:
On brief inspection, grsecurity isn't actually vmallocing the stack.
It seems to be allocating it the normal way and then vmapping it.
That allows it to modify sg_set_buf to work on stack addresses (sigh).
Perhaps
On Fri, Oct 24, 2014 at 01:53:28PM +0200, Linus Walleij wrote:
On Tue, Oct 7, 2014 at 11:32 PM, Beniamino Galvani b.galv...@gmail.com
wrote:
Add device tree bindings documentation for Amlogic Meson pinmux and
GPIO controller.
Signed-off-by: Beniamino Galvani b.galv...@gmail.com
(...)
sparc/include/asm/thread_info_32.h b/arch/sparc/include/asm/thread_info_32.h
index 025c98446b1e..88719dbb12f5 100644
--- a/arch/sparc/include/asm/thread_info_32.h
+++ b/arch/sparc/include/asm/thread_info_32.h
@@ -62,9 +62,6 @@ struct thread_info {
.flags = 0,
Hi!
+
+ /*
+ * There might have been an OOM kill while we were
+ * freezing tasks and the killed task might be still
+ * on the way out so we have to double check for race.
+ */
, so
/*
+ * PM-freezer should be
Hi!
+/*
+ * Number of OOM killer invocations (including memcg OOM killer).
+ * Primarily used by PM freezer to check for potential races with
+ * OOM killed frozen task.
+ */
+static atomic_t oom_kills = ATOMIC_INIT(0);
+
+int oom_kills_count(void)
+{
+ return
On Sat, Oct 25, 2014 at 8:57 PM, Al Viro v...@zeniv.linux.org.uk wrote:
[context for Linus]
Fuzzer has triggered deadlock in d_walk() with rename_lock taken twice.
AFAICS, the plausible scenario is
(child-d_flags DCACHE_DENTRY_KILLED) ||
triggering while ascending
On Sun, 2014-10-26 at 16:18 +, Paul McQuade wrote:
ERROR: spaces required around that ':' (ctx:VxE)
Signed-off-by: Paul McQuade paulmcq...@gmail.com
---
drivers/staging/rtl8723au/core/rtw_ieee80211.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git
On Sun, Oct 26, 2014 at 11:56:08AM -0700, Linus Torvalds wrote:
On Sat, Oct 25, 2014 at 8:57 PM, Al Viro v...@zeniv.linux.org.uk wrote:
Your patch looks fine, and I don't think we can livelock - because we
always set 'seq' to 1 if we retry, and that causes us to get the
exclusive lock, so we'd
On Sat, Oct 25, 2014 at 12:03 PM, David Härdeman da...@hardeman.nu wrote:
Wouldn't something like this be a simpler way of achieving the same
result? (untested):
The idea was to remove the empty change_protocol function that had
been added in the breaking commit.
IMHO, it would be better to not
create marco for max_rate values
Signed-off-by: Paul McQuade paulmcq...@gmail.com
---
drivers/staging/rtl8723au/core/rtw_ieee80211.c | 75 --
1 file changed, 34 insertions(+), 41 deletions(-)
diff --git a/drivers/staging/rtl8723au/core/rtw_ieee80211.c
Fix checkpatch.pl space prohibited after that open parenthesis '(' errors
Signed-off-by: Greg Donald gdon...@gmail.com
---
drivers/staging/rtl8192u/ieee80211/ieee80211_rx.c | 22 +-
.../staging/rtl8192u/ieee80211/ieee80211_softmac.c | 11 ---
1 - 100 of 532 matches
Mail list logo
