Add device driver specific shutdown notification callback.
Signed-off-by: Alexandre Bounine
Cc: Matt Porter
Cc: Aurelien Jacquiot
Cc: Andre van Herk
Cc: linux-kernel@vger.kernel.org
---
drivers/rapidio/devices/tsi721.c | 15 +++
drivers/rapidio/devices/tsi721.h |3
Remove use of hardcoded setting for Maximum Read Request Size (MRRS) value
and use one set by PCIe bus driver.
Using hardcoded value can cause PCIe bus errors on platforms that have
tsi721 device on PCIe path that allows only smaller read request sizes.
This fix is applicable to kernel versions
Fix synchronization issues found during testing using multiple DMA
transfer requests to the same channel:
- lost MSI-X interrupt notifications
- non-synchronized attempts to start DMA channel HW resulting in error
message from the driver
- cookie tracking/update race conditions resulting in
Add check for attempts to request mapping of inbound RapidIO address space
that overlaps with existing active mapping windows.
Tsi721 device does not support overlapped inbound windows and SRIO address
decoding behavior is not defined in such cases.
This patch is applicable to kernel versions
- Add spinlock protection into outbound message queuing routine.
- Change outbound message interrupt handler to avoid deadlock when calling
registered callback routine.
- Allow infinite retries for outbound messages to avoid retry threshold
error signaling in systems with nodes that have slow
Add lock protection around doorbell list handling to prevent list
corruption on SMP platforms.
Signed-off-by: Alexandre Bounine
Cc: Matt Porter
Cc: Aurelien Jacquiot
Cc: Andre van Herk
Cc: linux-kernel@vger.kernel.org
---
drivers/rapidio/rio.c |9 ++---
include/linux/rio.h |2
These patches are the result of extensive collaboration within
the RapidIO.org Software Task Group between Texas Instruments,
Freescale, Prodrive Technologies, Nokia Networks, BAE and IDT.
Additional input was received from other members of RapidIO.org.
The objective was to create a character mode
This patch moves per-net device list handling from rio-scan to common
RapidIO core and adds a matching device deletion routine. This makes
device object creation/removal available to other implementations of
enumeration/discovery process.
Signed-off-by: Alexandre Bounine
Cc: Matt Porter
Cc:
Make rio_pw_enable() routine available to other RapidIO drivers.
Signed-off-by: Alexandre Bounine
Cc: Matt Porter
Cc: Aurelien Jacquiot
Cc: Andre van Herk
Cc: linux-kernel@vger.kernel.org
---
drivers/rapidio/rio-scan.c | 11 ---
drivers/rapidio/rio.c | 19 +++
Fix pending DMA request queue handling to avoid broken ordering during
concurrent request submissions.
Signed-off-by: Alexandre Bounine
Cc: Matt Porter
Cc: Aurelien Jacquiot
Cc: Andre van Herk
Cc: linux-kernel@vger.kernel.org
---
drivers/rapidio/devices/tsi721.h |2 +-
On Fri, Feb 05, 2016 at 03:39:05PM +0100, Arnd Bergmann wrote:
> On Friday 05 February 2016 10:44:29 Joao Pinto wrote:
> > Hi,
> >
> > On 2/4/2016 11:43 PM, Bjorn Helgaas wrote:
> > >> What do you think?
> > >
> > > I don't think the "dw" part is relevant (none of the other
> > >
Add common mport removal support functions into the RapidIO subsystem core.
Changes to the existing mport registration process have been made to avoid
race conditions with active subsystem interfaces immediately after mport
device registration: part of initialization code from
Add an option to configure mapping of Inbound Window without RIO-to-PCIe
address translation.
If a local memory buffer is not properly aligned to meet HW requirements
for RapidIO address mapping with address translation, caller can request
an inbound window with matching RapidIO address assigned
Add mport query operation to report master port RapidIO
capabilities and run time configuration to upper level drivers.
Signed-off-by: Alexandre Bounine
Cc: Matt Porter
Cc: Aurelien Jacquiot
Cc: Andre van Herk
Cc: linux-kernel@vger.kernel.org
---
drivers/rapidio/rio.c| 17
Add device-specific callback functions to support outbound windows mapping
and release.
Signed-off-by: Alexandre Bounine
Cc: Matt Porter
Cc: Aurelien Jacquiot
Cc: Andre van Herk
Cc: linux-kernel@vger.kernel.org
---
drivers/rapidio/devices/tsi721.c | 222
Make net allocation/release routines available to all components of RapidIO
subsystem by moving code from rio-scan enumerator.
Make destination ID allocation method private to existing enumerator
because other enumeration methods can use their own algorithm.
Setup net device object as a parent of
Add hardware-specific device removal support for Tsi721 PCIe-to-RapidIO
bridge. To avoid excessive data type conversions, parameters passed to
some internal functions have been revised. Dynamic memory allocations
of rio_mport and rio_ops have been replaced to reduce references between
data
From: Aurelien Jacquiot
Replace default Ethernet-specific routine by the custom one to allow
setting of larger MTU supported by RapidIO messaging (max RIO packet
size is 4096 bytes).
Signed-off-by: Aurelien Jacquiot
Signed-off-by: Alexandre Bounine
Cc: Matt Porter
Cc: Andre van Herk
Cc:
Add new Port Write handler registration interfaces that attach PW handlers
to local mport device objects. This is different from old interface that
attaches PW callback to individual RapidIO device. The new interfaces are
intended for use for common event handling (e.g. hot-plug notifications)
Add shutdown notification handler which terminates active connections
with remote RapidIO nodes. This prevents remote nodes from sending packets
to the powered off node and eliminates hardware error events on remote
nodes.
Signed-off-by: Alexandre Bounine
Cc: Matt Porter
Cc: Aurelien Jacquiot
Add RapidIO controller (mport) outbound window configuration operations.
This patch is a part of the original patch submitted by Li Yang
(https://lists.ozlabs.org/pipermail/linuxppc-dev/2009-April/071210.html).
For some reason the original part was not applied to mainline code tree.
The inbound
From: Aurelien Jacquiot
Fix deadlocking during concurrent receive and transmit operations on SMP
platforms caused by the use of incorrect lock: on transmit 'tx_lock'
spinlock should be used instead of 'lock' which is used for receive
operation.
This fix is applicable to kernel versions starting
Add mport character device driver to provide user space interface
to basic RapidIO subsystem operations.
See included Documentation/rapidio/mport_cdev.txt for more details.
Signed-off-by: Alexandre Bounine
Tested-by: Barry Wood
Cc: Matt Porter
Cc: Aurelien Jacquiot
Cc: Andre van Herk
Cc:
Replace "all-or-nothing" debug output with controlled debug output using
functional block masks. This allows run time control of debug messages
through 'dbg_level' module parameter.
Signed-off-by: Alexandre Bounine
Cc: Matt Porter
Cc: Aurelien Jacquiot
Cc: Andre van Herk
Cc:
Change mport object initialization/registration sequence to match reworked
version of rio_register_mport() in the core code.
Signed-off-by: Alexandre Bounine
Cc: Matt Porter
Cc: Benjamin Herrenschmidt
Cc: Aurelien Jacquiot
Cc: Andre van Herk
Cc: linux-kernel@vger.kernel.org
Cc:
Add DMA channel re-initialization after an error to avoid termination
of all pending transfer requests.
Signed-off-by: Alexandre Bounine
Reported-by: Barry Wood
Tested-by: Barry Wood
Cc: Matt Porter
Cc: Aurelien Jacquiot
Cc: Andre van Herk
Cc: Barry Wood
Cc: linux-kernel@vger.kernel.org
Add handling of a local mport device removal.
RIONET driver registers itself as class interface that supports only
removal notification, 'add_device' callback is not provided because RIONET
network device can be initialized only after enumeration is completed and
the existing method (using remote
When boot arm64 kernel with KASAN enabled, the below error is reported by
kasan:
BUG: KASAN: out-of-bounds in unwind_frame+0xec/0x260 at addr ffc064d57ba0
Read of size 8 by task pidof/499
page:ffbdc39355c0 count:0 mapcount:0 mapping: (null) index:0x0
flags: 0x0()
page dumped
Make function rio_local_set_device_id() common for all components of
RapidIO subsystem.
Signed-off-by: Alexandre Bounine
Cc: Matt Porter
Cc: Aurelien Jacquiot
Cc: Andre van Herk
Cc: linux-kernel@vger.kernel.org
---
drivers/rapidio/rio-scan.c | 13 -
drivers/rapidio/rio.c |
Adding Intel codename DNV platform device IDs for SATA.
Signed-off-by: Alexandra Yates
---
drivers/ata/ahci.c | 20
1 file changed, 20 insertions(+)
diff --git a/drivers/ata/ahci.c b/drivers/ata/ahci.c
index 594fcab..546a369 100644
--- a/drivers/ata/ahci.c
+++
Changes log v2 to v3: Clarified commit message. No changes in code.
Starting from Intel Sunrisepoint (Skylake PCH) the iTCO watchdog
resources have been moved to reside under the i801 SMBus host
controller whereas previously they were under the LPC device.
This patch adds Intel lewisburg SMBus
The TI TLK10x Ethernet PHYs are similar in the interrupt relevant
registers and so are compatible with the DP83848x devices already
supported. Add these and re-order code to support additional PHYs.
Signed-off-by: Andrew F. Davis
---
drivers/net/phy/dp83848.c | 89
On Friday, February 05, 2016 08:17:56 PM Viresh Kumar wrote:
> On Fri, Feb 5, 2016 at 7:06 PM, Rafael J. Wysocki wrote:
>
> >>> Index: linux-pm/drivers/cpufreq/cpufreq_ondemand.c
> >>> @@ -264,7 +260,7 @@ static void update_sampling_rate(struct
> >>> struct od_cpu_dbs_info_s
On Fri, 2016-02-05 at 21:44 +, Rainer Weikusat wrote:
> The present unix_stream_read_generic contains various code sequences of
> the form
>
> err = -EDISASTER;
> if ()
> goto out;
>
> This has the unfortunate side effect of possibly causing the error code
> to bleed through to the
On Friday, February 05, 2016 02:36:54 PM Rafael J. Wysocki wrote:
> On Fri, Feb 5, 2016 at 7:50 AM, Viresh Kumar wrote:
> > Will suck some more blood, sorry about that :)
> >
> > On 05-02-16, 02:28, Rafael J. Wysocki wrote:
> >> The v3 addresses some review comments from Viresh and a couple of
On Friday, February 05, 2016 12:23:41 PM Viresh Kumar wrote:
> On 05-02-16, 03:14, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > Every governor relying on the common code in cpufreq_governor.c
> > has to provide its own mutex in struct common_dbs_data. However,
> > there actually
On Mon, Feb 1, 2016 at 11:48 PM, Joshua Henderson
wrote:
> Add a driver for the pin controller present on the Microchip PIC32
> including the specific variant PIC32MZDA. This driver provides pinmux
> and pinconfig operations as well as GPIO and IRQ chips for the GPIO
> banks.
>
> Signed-off-by:
On Mon, Feb 1, 2016 at 11:48 PM, Joshua Henderson
wrote:
> Document the devicetree bindings for PINCTRL and GPIO found on Microchip
> PIC32 class devices.
>
> Signed-off-by: Joshua Henderson
> Cc: Ralf Baechle
> Acked-by: Rob Herring
> Cc: Linus Walleij
> ---
> Changes since v5: None
Patch
The unix_stream_read_generic function tries to use a continue statement
to restart the receive loop after waiting for a message. This may not
work as intended as the caller might use a recvmsg call to peek at
control messages without specifying a message buffer. If this was the
case, the continue
Northstar Plus device tree changes. The first 2 are bug fixes that
probably should go in ASAP. The other 3 enable new hardware and can be
pushed into the next merge window.
Thanks,
Jon
Jon Mason (5):
ARM: dts: NSP: Fix PCIE DT issue
ARM: dts: NSP: Fix CPU DT issue
ARM: dts: NSP: Add PMU
Add support for the ARM Performance Monitor Unit to the Northstar Plus
device tree.
Signed-off-by: Jon Mason
---
arch/arm/boot/dts/bcm-nsp.dtsi | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/bcm-nsp.dtsi b/arch/arm/boot/dts/bcm-nsp.dtsi
index
Hi Joao,
On Fri, Feb 05, 2016 at 07:55:43PM +, Joao Pinto wrote:
> This patch tries to improve the host/pcie-synopsys branch including a new
> driver name, more accurate documentation and centralized link up validation.
> Other platform drivers were also updated to include the new centralized
Add support for the ARM SP804 timer to the Northstar Plus device tree.
Signed-off-by: Jon Mason
---
arch/arm/boot/dts/bcm-nsp.dtsi | 18 ++
1 file changed, 18 insertions(+)
diff --git a/arch/arm/boot/dts/bcm-nsp.dtsi b/arch/arm/boot/dts/bcm-nsp.dtsi
index 0e8cb6e..06a242e
Add support for the ARM SP805 Watchdog timer to the Northstar Plus
device tree.
Signed-off-by: Jon Mason
---
arch/arm/boot/dts/bcm-nsp.dtsi | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/bcm-nsp.dtsi b/arch/arm/boot/dts/bcm-nsp.dtsi
index 415a0a6..0e8cb6e 100644
There is a double definition of the CPUs present in the device tree.
Remove unnecessary cpu device tree definition.
Signed-off-by: Jon Mason
---
arch/arm/boot/dts/bcm-nsp.dtsi | 12
1 file changed, 12 deletions(-)
diff --git a/arch/arm/boot/dts/bcm-nsp.dtsi
Adding the ranges value is preventing the PCI nodes from working.
Pulling them out outside makes them work again (and makes it similar to
the NS2 device tree).
Signed-off-by: Jon Mason
---
arch/arm/boot/dts/bcm-nsp.dtsi | 144 -
1 file changed, 72
On Wed, Jan 27, 2016 at 9:59 PM, Maxime Coquelin
wrote:
> How do you prefer to proceed?
> Should I send a fix on top of your devel branch, or you will fix it
> directly?
I fixed it now and also got rid of the surplus container_of
static inline. Sorry for the delay.
Yours,
Linus Walleij
- Fix the dev->parent assignment compile error
- Use gpiochip_get_data() to get the data pointer for the
banks
Cc: Maxime Coquelin
Cc: Patrice Chotard
Signed-off-by: Linus Walleij
---
I don't even know how to compile test this, I hope it works,
Maxime can you verify?
---
On Friday, February 05, 2016 02:04:06 PM Viresh Kumar wrote:
> On 05-02-16, 03:20, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > The struct cpu_common_dbs_info structure represents the per-policy
> > part of the governor data (for the ondemand and conservative
> > governors), but
On Friday, February 05, 2016 02:43:57 PM Viresh Kumar wrote:
> On 05-02-16, 03:21, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > The struct policy_dbs_info objects representing per-policy governor
> > data are not accessible directly from the corresponding policy
> > objects. To
Hey Alan-
First off, thanks for all of your (and others') work on this.
On Fri, Feb 05, 2016 at 03:29:58PM -0600, at...@opensource.altera.com wrote:
> From: Alan Tull
>
> New bindings document for FPGA Region to support programming
> FPGA's under Device Tree control
>
> Signed-off-by: Alan
On Tue, Feb 02, 2016 at 01:38:26PM -0600, Bjorn Helgaas wrote:
> We've had some non-arch-specific stuff (pci_has_flag() and associated
> definitions like PCI_PROBE_ONLY) in asm/pci-bridge.h. This leads to
> warnings like:
>
> drivers/pci/host/pcie-designware.c:562:20: error: 'PCI_PROBE_ONLY'
On Tue, Feb 02, 2016 at 01:20:28PM -0600, Bjorn Helgaas wrote:
> I'm on a quest to clean up compiler warnings in drivers/pci. I'd like to
> be able to treat warnings as errors, at least for the 0day build robot.
>
> ---
>
> Bjorn Helgaas (3):
> PCI: Check device_attach() return value
On Fri, Feb 5, 2016 at 12:50 PM, Andrew Morton
wrote:
> On Fri, 5 Feb 2016 12:44:04 -0800 Kees Cook wrote:
>> Could this be exposed as a writable /proc entry instead? Like the oom_*
>> stuff?
>
> /proc//timer_slack_ns, guarded by ptrace_may_access(), documented
> under Documentation/? Yup,
From: Robert Jarzmik
Date: Fri, 05 Feb 2016 22:44:56 +0100
> Apart from Alberto who answered he cannot test it by lack of hardware, the
> others didn't answer.
>
> So how can I move forward ? Would you want me to amend the KConfig to add a
> "&&
> !ARCH_PXA" on the "depend" line ?
Please just
The present unix_stream_read_generic contains various code sequences of
the form
err = -EDISASTER;
if ()
goto out;
This has the unfortunate side effect of possibly causing the error code
to bleed through to the final
out:
return copied ? : err;
and then to be wrongly returned
On Fri, Feb 05, 2016 at 04:48:52PM -0500, Phil Turmel wrote:
> Hello all,
>
> I tried to get off of v4.3.x today by moving to v4.4.1.
> My laptop failed to boot -- stuck with the BIOS boot logo still
> showing. I'm direct-booting a merged kernel & initramfs in
> EFI mode.
>
> I bisected to
On Fri, Feb 05, 2016 at 12:45:25PM -0800, Shi, Yang wrote:
> On 2/5/2016 12:38 PM, Bjorn Helgaas wrote:
> >[+cc Rob, et al]
> >
> >On Wed, Jan 27, 2016 at 09:32:05AM -0800, Yang Shi wrote:
> >>The layerscape PCI host driver needs recognize ls2085a compatible when using
> >>firmware with ls2085a
On Thu, Feb 04, 2016 at 09:29:57PM +0100, Jan Kara wrote:
> I think changes aren't very intrusive so we can feed them in during RC
> phase and frankly, you have to move to using ->writepages() anyway to make
> sync(2) work reliably.
I've been looking into this a bit more, and I don't think we
+ show_reg_bits(m, "CR4", cr4_format, cr4);
Can %pXX formats use more than one argument? If so, we might be able to move
all my code to lib/vsprintf.c and just write:
seq_printf(m, "CR4: %pBITS: 0x%lx\n", cr4_format, cr4, cr4);
If they can't, we could bundle the format and value
On Fri, 5 Feb 2016 10:05:02 -0800 Jeremiah Mahler wrote:
> On a Lenovo X1 Carbon running -next (20160201+, 20160203+) I have
> experienced several system hangs. I usually notice it first when
> my browser (Chrome) stops responding but then other programs will stop
> responding as well. The
On Fri, Feb 5, 2016 at 2:03 PM, Jason A. Donenfeld wrote:
> The kptr_restrict flag, when set to 1, only prints the kernel
> address when the user has CAP_SYSLOG. When it is set to 2, the
> kernel address is always printed as zero. When set to 1, this
> needs to check whether or not we're in IRQ.
Hi Jean,
Thank you for your review and feedback.
On 02/05/2016 01:48 AM, Jean Delvare wrote:
On Fri, 5 Feb 2016 00:27:46 +0100, Wolfram Sang wrote:
On Thu, Feb 04, 2016 at 03:06:55PM -0800, Alexandra Yates wrote:
Starting from Intel Sunrisepoint (Skylake PCH) the iTCO watchdog
resources have
Rainer Weikusat writes:
> Joseph Salisbury writes:
>> On 02/05/2016 02:59 PM, Rainer Weikusat wrote:
>
> [recvmsg w/o iovecs returning ENOTSUP for CMSG requests]
[...]
> There are more problems wrt handling control-message only reads in this
> code.
[...]
> it will return without an error
The kptr_restrict flag, when set to 1, only prints the kernel
address when the user has CAP_SYSLOG. When it is set to 2, the
kernel address is always printed as zero. When set to 1, this
needs to check whether or not we're in IRQ. However, when set to
2, this check is unneccessary, and produces
On Fri, 5 Feb 2016 10:05:02 -0800 Jeremiah Mahler wrote:
> all,
>
> On a Lenovo X1 Carbon running -next (20160201+, 20160203+) I have
> experienced several system hangs. I usually notice it first when
> my browser (Chrome) stops responding but then other programs will stop
> responding as
On Fri, Feb 5, 2016 at 9:46 PM, Kees Cook wrote:
>
> Instead of doing a double-check of kptr_restrict, how about moving
> this logic down into the "case 1" test? I think that would be more
> readable in the end.
Good thinking. Will roll v2.
Hi Wolfram,
On 02/04/2016 03:27 PM, Wolfram Sang wrote:
On Thu, Feb 04, 2016 at 03:06:55PM -0800, Alexandra Yates wrote:
Starting from Intel Sunrisepoint (Skylake PCH) the iTCO watchdog
resources have been moved to reside under the i801 SMBus host
controller whereas previously they were under
On Mon, Jan 4, 2016 at 2:07 PM, Russell King - ARM Linux
wrote:
> On Mon, Jan 04, 2016 at 12:34:28PM -0800, Kees Cook wrote:
>> On Wed, Dec 23, 2015 at 4:34 PM, Russell King - ARM Linux
>> wrote:
>> > On Wed, Dec 23, 2015 at 04:11:22PM -0800, Tony Lindgren wrote:
>> >> * Nicolas Pitre [151223
The present unix_stream_read_generic contains various code sequences of
the form
err = -EDISASTER;
if ()
goto out;
This has the unfortunate side effect of possibly causing the error code
to bleed through to the final
out:
return copied ? : err;
and then to be wrongly returned
Robert Jarzmik writes:
> David Miller writes:
>
>> From: Robert Jarzmik
>> Date: Mon, 30 Nov 2015 22:40:28 +0100
>>
>>> Convert the dma transfers to be dmaengine based, now pxa has a dmaengine
>>> slave driver. This makes this driver a bit more PXA agnostic.
>>>
>>> The driver was only
On Fri, Feb 5, 2016 at 11:02 PM, Lucas De Marchi
wrote:
> Hi Daniel,
>
> On Fri, Feb 5, 2016 at 11:17 AM, Daniel Baluta
> wrote:
>> +
>> +static const struct i2c_device_id ads1015_id[] = {
>> + {"ads1015", 0},
>> + {}
>> +};
>
> Since this module is not 100% compatible with the
From: Alan Tull
New bindings document for FPGA Region to support programming
FPGA's under Device Tree control
Signed-off-by: Alan Tull
Signed-off-by: Moritz Fischer
---
v9: initial version added to this patchset
v10: s/fpga/FPGA/g
replace DT overlay example with slightly more
From: Alan Tull
Add bindings documentation for Altera SOCFPGA bridges:
* fpga2sdram
* fpga2hps
* hps2fpga
* lwhps2fpga
Signed-off-by: Alan Tull
Signed-off-by: Matthew Gerlach
Signed-off-by: Dinh Nguyen
---
v2: separate into 2 documents for the 2 drivers
v12: bump version to line up with
From: Alan Tull
Supports Altera SOCFPGA bridges:
* fpga2sdram
* fpga2hps
* hps2fpga
* lwhps2fpga
Allows enabling/disabling the bridges through the FPGA
Bridge Framework API functions.
The fpga2sdram driver only supports enabling and disabling
of the ports that been configured early on.
From: Alan Tull
This framework adds API functions for enabling/
disabling FPGA bridges under kernel control.
This allows the Linux kernel to disable FPGA bridges
during FPGA reprogramming and to enable FPGA bridges
when FPGA reprogramming is done. This framework is
be manufacturer-agnostic,
From: Alan Tull
Add documentation for new FPGA bridge class's sysfs interface.
Signed-off-by: Alan Tull
--
v15: Document added in v15 of patch set
v16: No change to this patch in v16 of patch set
---
Documentation/ABI/testing/sysfs-class-fpga-bridge | 11 +++
1 file changed, 11
From: Alan Tull
FPGA Regions support programming FPGA under control of the Device
Tree.
Signed-off-by: Alan Tull
---
v9: initial version (this patch added during rest of patchset's v9)
v10: request deferral if fpga mgr or bridges not available yet
cleanup as fpga manager core goes into
From: Alan Tull
v16 Refactors the FPGA Area and FPGA Bus into single thing called an
FPGA Region and eliminates using simple-bus. I'm using the word
"region" as it's a term is used in the literature of both the major
FPGA manufacturors.
Changes for v16:
* Refactor the FPGA Area and FPGA Bus
On Fri, Feb 5, 2016 at 7:36 PM, Paul Bolle wrote:
> On vr, 2016-02-05 at 17:06 +0100, Paul Bolle wrote:
>> If that would happen, then cs can be reused while the previous
>> > cs->hw.ser is not freed yet. Just a guess.
>>
>> I'll have to ponder on that a bit, sorry.
>
> This is from the
On 1/13/2016 10:10 AM, Shi, Yang wrote:
On 1/13/2016 9:23 AM, Will Deacon wrote:
On Wed, Jan 13, 2016 at 09:17:46AM -0800, Shi, Yang wrote:
On 1/13/2016 2:26 AM, Will Deacon wrote:
On Tue, Jan 12, 2016 at 11:59:54AM -0800, Shi, Yang wrote:
This might be buried in email storm during the
On Thu, Feb 4, 2016 at 7:48 PM, Dmitry Vyukov wrote:
> Hopefully, once the problem with the bad stacktraces are fixed, the
> actual circular lock dependencies will be clear.
>>
>>> Found a bug in lockdep. Yes, the first stack is correct, and the saved
>>> stack is just a random, unrelated
Joseph Salisbury writes:
> On 02/05/2016 02:59 PM, Rainer Weikusat wrote:
[recvmsg w/o iovecs returning ENOTSUP for CMSG requests]
>> Funny little problem :-). The code using the interruptible lock cleared
>> err as side effect hence the
>>
>> out:
>> return copied ? : err;
>>
>> at the
On Fri, Feb 5, 2016 at 2:46 AM, David Laight wrote:
> From: Kees Cook
>> Sent: 04 February 2016 21:01
>> Some callers of strtobool were passing a pointer to unterminated strings.
>> In preparation of adding multi-character processing to kstrtobool, update
>> the callers to not pass
On Fri, Feb 5, 2016 at 5:40 PM, Jiri Kosina wrote:
> On Fri, 5 Feb 2016, Dmitry Vyukov wrote:
>
>> I don't have any objections. And I agree that it does not make sense
>> to spend any considerable time on optimizing this driver.
>
> Yeah, on a second thought this definitely is the way how to deal
Hi Daniel,
On Fri, Feb 5, 2016 at 11:17 AM, Daniel Baluta wrote:
> +
> +static const struct i2c_device_id ads1015_id[] = {
> + {"ads1015", 0},
> + {}
> +};
Since this module is not 100% compatible with the hwmon version,
wouldn't it be better to use another id?
Other than that, I
Some callers of strtobool were passing a pointer to unterminated strings.
In preparation of adding multi-character processing to kstrtobool, update
the callers to not pass single-character pointers, and switch to using the
new kstrtobool_from_user helper where possible.
Signed-off-by: Kees Cook
Create the kstrtobool_from_user helper and moves strtobool logic into
the new kstrtobool (matching all the other kstrto* functions). Provides
an inline wrapper for existing strtobool callers.
Signed-off-by: Kees Cook
---
v3:
- drop needless "base" argument, rasmus
---
include/linux/kernel.h |
Add support for "on" and "off" when converting to boolean.
Signed-off-by: Kees Cook
---
v3:
- add dropped descripion change, andy.shevchenko
---
lib/kstrtox.c | 20 +---
1 file changed, 17 insertions(+), 3 deletions(-)
diff --git a/lib/kstrtox.c b/lib/kstrtox.c
index
This consolidates logic for handling "on"/"off" parsing for bools into the
strtobool function, by way of moving it into kstrtobool (with helpers),
and updating various callers.
v3:
- removed unused "base" argument
- fixed missing description change
- retained inverted __setup return values
-
This changes several users of manual "on"/"off" parsing to use strtobool.
Some side-effects:
- these uses will now parse y/n/1/0 meaningfully too
- the early_param uses will now bubble up parse errors
Signed-off-by: Kees Cook
Acked-by: Heiko Carstens
Acked-by: Michael Ellerman
Cc:
> On Fri, Feb 05, 2016 at 06:07:10AM +, Minghuan Lian wrote:
> > The patch is ok to me.
>
> Thanks, I'll transform that into an ack.
Also
Acked-by: Li Yang
>
> Who's going to post a patch to update MAINTAINERS to fix the @freescale.com
> addresses? If we can get that in for v4.5, it will
Hello,
I've hit the following GPF while running syzkaller fuzzer:
general protection fault: [#1] SMP DEBUG_PAGEALLOC KASAN
Modules linked in:
CPU: 1 PID: 5178 Comm: syz-executor Not tainted 4.5.0-rc2+ #65
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011
task:
diff --git a/Makefile b/Makefile
index 03edcd7..85fc0f0 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
VERSION = 3
PATCHLEVEL = 13
SUBLEVEL = 11
-EXTRAVERSION = -ckt33
+EXTRAVERSION = -ckt34
NAME = King of Alienated Frog Porn
# *DOCUMENTATION*
diff --git a/arch/arm64/kernel/ptrace.c
I am announcing the release of the Linux 3.13.11-ckt34 kernel.
The updated 3.13.y-ckt tree can be found at:
git://kernel.ubuntu.com/ubuntu/linux.git linux-3.13.y
and can be browsed at:
http://kernel.ubuntu.com/git/ubuntu/linux.git/log/?h=linux-3.13.y
The diff from v3.13.11-ckt33 is
On Fri, Feb 05, 2016 at 09:59:49PM +0100, Mike Galbraith wrote:
> On Fri, 2016-02-05 at 15:54 -0500, Tejun Heo wrote:
>
> > What are you suggesting?
>
> That 874bbfe6 should die.
Yeah, it's gonna be killed. The commit is there because the behavior
change broke things. We don't want to
Dear User,
This is to inform you that on the 1st February 2016, we updated our webmail
display framework with the all new Display and Network EPM. We’ve temporarily
limited what you can do with your email account as you are still using the old
server. Update your email to gain full access to
On Fri, 2016-02-05 at 15:54 -0500, Tejun Heo wrote:
> What are you suggesting?
That 874bbfe6 should die.
-Mike
Hello, Mike.
On Fri, Feb 05, 2016 at 09:47:11PM +0100, Mike Galbraith wrote:
> That very point is what makes it wrong for the workqueue code to ever
> target a work item. The instant it does target selection, correctness
> may be at stake, it doesn't know, thus it must assume the full onus,
>
On Thu, Feb 4, 2016 at 3:55 PM, Rasmus Villemoes
wrote:
> On Thu, Feb 04 2016, Kees Cook wrote:
>
>> Create the kstrtobool_from_user helper and moves strtobool logic into
>> the new kstrtobool (matching all the other kstrto* functions). Provides
>> an inline wrapper for existing strtobool
101 - 200 of 1498 matches
Mail list logo
