Le 23/07/2015 12:14, Harini Katakam a écrit :
> JUMBO and NO_GIGABIT_HALF have the same capability masks.
> Change one of them.
>
> Signed-off-by: Harini Katakam
Yes, indeed:
Acked-by: Nicolas Ferre
> ---
> drivers/net/ethernet/cadence/macb.h |2 +-
> 1 file changed, 1 insertion(+), 1 del
>From 0a8e0d63a9887735c6782d7b0c15c2c1fdf1952a Mon Sep 17 00:00:00 2001
From: "Du, Changbin"
Date: Thu, 23 Jul 2015 20:08:04 +0800
Subject: [PATCH] usb/gadget: make composite gadget meet usb compliance for
vbus draw
USB-IF compliance requirement limits the vbus current according to
current state
From: Xunlei Pang
cpuidle_device::safe_state_index need to be initialized before use,
so assign the driver's safe_state_index to it.
Signed-off-by: Xunlei Pang
---
drivers/cpuidle/cpuidle.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/cpuidle/cpuidle.c b/drivers/cpuidle/cpuidl
On Tue, Jul 21, 2015 at 05:08:42PM -0700, David Rientjes wrote:
> On Mon, 20 Jul 2015, Mel Gorman wrote:
>
> > From: Mel Gorman
> >
> > File-backed pages that will be immediately dirtied are balanced between
> > zones but it's unnecessarily expensive. Move consider_zone_balanced into
> > the all
The debug_read_tlb() uses the sprintf() functions directly on the buffer
allocated by buf = kmalloc(count), without taking into account the size
of the buffer, with the consequence corrupting the heap, depending on
the count requested by the user.
The patch fixes the issue replacing sprintf() by s
On Thu, Jul 23, 2015 at 01:59:33PM +0300, Ioan-Adrian Ratiu wrote:
> Enclose defined macro in paranthesis to avoid checkpatch complaint
> "ERROR: Macros with complex values should be enclosed in parentheses"
>
> Signed-off-by: Ioan-Adrian Ratiu
> ---
> drivers/staging/rtl8192e/rtllib_rx.c | 2 +-
Den 15.07.2015 11:36, skrev Paul Bolle:
On di, 2015-07-14 at 14:59 +0200, Henri Chain wrote:
--- /dev/null
+++ b/drivers/staging/fbtft/fb_uc1611.c
+#define DRVNAME"fb_uc1611"
+MODULE_ALIAS("spi:" DRVNAME);
+MODULE_ALIAS("platform:" DRVNAME);
+MODULE_ALIAS("spi:uc1611");
+MODULE_
To make the file more organize move mei client driver api
to the start of the file and add Kdoc.
There are no functional changes in this patch.
Signed-off-by: Tomas Winkler
---
V2: resend
V3: rebase
drivers/misc/mei/bus.c | 799 +++--
1 file changed,
Do not enable events implicitly in mei_cl_enable_device, it should be
done explicitly using mei_cl_register_event_cb so the events
are enabled only when needed.
The NFC drivers has been already using it that way so no need for
further changes just remove the code from mei_cl_enable_device.
Signed-
Rename mei_cl_uevent to mei_cl_device_uevent to match
the naming convention of mei_cl_bus_type functions
Signed-off-by: Tomas Winkler
---
V2: a new patch in the 2nd series
V3: rebase
drivers/misc/mei/bus.c | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/drivers
Instead of holding the list of host clients (me_cl)
we want to keep the list me client devices (mei_cl_device)
This way we can create host to me client connection only when needed.
Add list head to mei_cl_device and cl_bus_lock
Add bus_added flag to the me client (mei_me_client) to track if
the app
If event registeration has failed, the caller should know
about it.
Signed-off-by: Tomas Winkler
---
V2: fix the commit message
V3: rebase
drivers/misc/mei/bus.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/misc/mei/bus.c b/drivers/misc/mei/bus.c
index 257e20
MEI bus was designed around nfc and was hard to extend.
Instead of the hard coded way of adding the devices on the mei bus
we scan the whole me client list and create a device for each
eligible me client (mei_cl_bus_rescan); currently we support
only clients with single connection and fixed address
mei_cl_device_match now calls mei_cl_device_find that returns
the matching device id in the device id table.
We will utilize the mei_cl_device_find during probing
to locate the matching entry.
Signed-off-by: Tomas Winkler
---
V2: fix the commit message
V3: rebase
drivers/misc/mei/bus.c | 63
Add reference to the bus device (mei_device) for easier access.
To ensures that referencing cldev->bus is valid during cldev life time
we increase the bus ref counter on a client device creation and drop it
on the device release.
Signed-off-by: Tomas Winkler
---
V2: resend
V3: rebase
drivers/mis
Currently we support only clients with single connection
and fixed address clients so all other clients are blacklisted
Signed-off-by: Tomas Winkler
---
V2: a new patch in the 2nd series
V3: rebase
drivers/misc/mei/bus-fixup.c | 19 +++
1 file changed, 19 insertions(+)
diff --gi
Split the device registration into allocation and device struct
initialization, device setup, and the final device registration.
This why it is possible to run fixups and quirks during the setup stage
on an initialized device. Each fixup routine effects do_match flag.
If the flag is set to false at
Instead of generating device id on the fly during probing we
find the matching id entry on the device id table.
Get bus the module reference counter so it cannot
be unloaded after the driver has bounded to the client
device
Signed-off-by: Tomas Winkler
---
V2: resend
V3: rebase
drivers/misc/mei/
Blacklist nfc info client which is only used for retrieval
of the NFC radio version
Signed-off-by: Tomas Winkler
---
V2: a new patch in the 2nd series
V3: rebase
drivers/misc/mei/bus-fixup.c | 23 +++
1 file changed, 19 insertions(+), 4 deletions(-)
diff --git a/drivers/misc
In the mei bus layer there is use of different variables
of driver and device types with no clear naming convention.
There are generic struct device and struct driver,
then mei_cl_{device, driver}, and finally mei_device which
in this context serves as a bus device.
The patch sets following naming
Remove the dependency on struct ndev from the nfc device
name creation function so it is possible to use it
in a fixup routine
Signed-off-by: Tomas Winkler
---
V2: fix the commit message
V3: rebase
drivers/misc/mei/bus-fixup.c | 115 ---
drivers/misc/mei/b
The bus-fixup.c will be a place for fixups and quirks
for all types of me client devices.
As for now it contians only the fixup for setting
the nfc device name on the me client bus.
Signed-off-by: Tomas Winkler
---
V2: resend
V3: rebase
drivers/misc/mei/Makefile | 2 +-
drivers/mis
MEI bus was designed around nfc and was hard to extend.
Instead of hard coded way of adding the devices on the mei bus
we scan whole me client list and create a device for each
eligible me client
V2: Rephrase the commit message of most of the patches
Remove few patches that didn't bring substa
On Tue 2015-07-21 09:21:32, Sascha Hauer wrote:
> The thermal code uses int, long and unsigned long for temperatures
> in different places.
>
> Using an unsigned type limits the thermal framework to positive
> temperatures without need. Also several drivers currently will report
> temperatures nea
On Thu, Jul 23, 2015 at 11:51:49AM +0100, Suneel Garapati wrote:
> adds file for description on device node bindings for RTC
> found on Xilinx Zynq Ultrascale+ MPSoC.
>
> Signed-off-by: Suneel Garapati
> ---
> Documentation/devicetree/bindings/rtc/xlnx-rtc.txt | 25
> ++
> 1
Hi, Alexi
Thank you for your guidence, and by referencing your last mail
and other llvm backends, I found setting
BPFMCAsmInfo::SupportsDebugInformation = true in BPFMCAsmInfo.h
and fix some unhandeled switch can make llc output debug_info,
but important information is missing in the result:
bpf
A little change to patch_map() function,
use set_fixmap_offset() to make code more clear.
Signed-off-by: yalin wang
---
arch/arm64/kernel/insn.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/arch/arm64/kernel/insn.c b/arch/arm64/kernel/insn.c
index dd9671c..7dafd5a 100
On Mon, 2015-07-06 at 15:22 +0300, Andy Shevchenko wrote:
> The new coming Intel platforms such as Skylake will contain
> Sunrisepoint PCH.
>
> The driver is based on MFD framework since the main device, i.e.
> serial bus
> controller, contains register space for itself, DMA part, and an
> addi
Am 23.07.2015 um 07:09 schrieb Maxime Coquelin:
> This patch replaces use of linux,stdout-path by stdout-path as per
s/by/with/
> "chosen" DT bindings documentation.
>
> Doing that, the "console" argument is no more needed in kernel command
> line.
>
> Reported-by: Olof Johansson
> Signed-off-
23.07.2015 12:43, Oliver Neukum пишет:
On Mon, 2015-07-20 at 21:13 +0300, Eugene Shatokhin wrote:
[Race #5]
Race on dev->rx_urb_size. I reproduced it a similar way as the races
#2
and #3 (changing MTU while downloading files).
dev->rx_urb_size is written to here:
#0 usbnet_change_mtu (usbnet.
Oliver Neukum [mailto:oneu...@suse.com]
[...]
> If the device does not support remote wakeup and the driver enables it,
> runtime
> power management will be switched off.
> That is the current state and it means that devices which don't support remote
> wakeup cannot do runtime power management at
> -Original Message-
> From: Alexander Stein [mailto:alexander.st...@systec-electronic.com]
> Sent: Thursday, July 23, 2015 3:41 PM
> To: Badola Nikhil-B46172
> Cc: linux-kernel@vger.kernel.org; linux-arm-ker...@lists.infradead.org;
> devicet...@vger.kernel.org
> Subject: Re: [PATCH 3/3] ar
On Thu 23-07-15 19:11:03, Hidehiro Kawai wrote:
> Hi,
>
> Thanks for the feedback.
>
> (2015/07/23 17:25), Michal Hocko wrote:
> > Hi,
> >
> > On Wed 22-07-15 11:14:21, Hidehiro Kawai wrote:
> >> When an HA cluster software or administrator detects non-response
> >> of a host, they issue an NMI
Hi Daniel,
On 07/23/2015 11:31 AM, Daniel Borkmann wrote:
> Hi Michael,
>
> looks good already, a couple of comments inline, on top of Alexei's feedback:
>
> On 07/22/2015 10:10 PM, Michael Kerrisk (man-pages) wrote:
> ...
>> NAME
>> bpf - perform a command on an extended eBPF map or pro
> -Original Message-
> From: Mark Rutland [mailto:mark.rutl...@arm.com]
> Sent: Thursday, July 23, 2015 4:27 PM
> To: Badola Nikhil-B46172
> Cc: linux-kernel@vger.kernel.org; devicet...@vger.kernel.org; ba...@ti.com
> Subject: Re: [PATCH 1/3] Documentation: dt: dwc3: Add snps,configure-flad
Den 15.07.2015 04:14, skrev Greg KH:
On Tue, Jun 30, 2015 at 08:43:13AM +0200, Fabio Falzoi wrote:
Use a helper function to choose which set_addr_win implementation to
use, based on the value of the setaddrwin module parameter.
Signed-off-by: Fabio Falzoi
---
drivers/staging/fbtft/flexfb.c
commit 106542e7987c ("fs: Remove ext3 filesystem driver") removed ext3
and JBD, hence remove the superfluous condition.
Signed-off-by: Valentin Rothberg
---
I detected the issue with undertaker-checkpatch
(https://undertaker.cs.fau.de)
mm/Kconfig | 8 +---
1 file changed, 1 insertion(+), 7
This patch adds the CPU clocks so that the CPU DVFS can be enabled.
Signed-off-by: Sudeep Holla
Acked-by: Liviu Dudau
Cc: Jon Medhurst (Tixy)
---
arch/arm64/boot/dts/arm/juno-r1.dts | 6 ++
arch/arm64/boot/dts/arm/juno.dts| 6 ++
2 files changed, 12 insertions(+)
diff --git a/arch
Nize kontaktujte me pro zakladni dohodu.
E-mail: jjg.ch...@gmail.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http:
This patch adds CPU topology on Juno. It will be useful for ther other
IP blocks depending on this topology.
Signed-off-by: Sudeep Holla
Acked-by: Liviu Dudau
Cc: Jon Medhurst (Tixy)
---
arch/arm64/boot/dts/arm/juno-r1.dts | 26 ++
arch/arm64/boot/dts/arm/juno.dts|
On Thu, 23 Jul 2015, Viresh Kumar wrote:
> Cc'ing few more people who were involved in opp-v2 discussions.
>
> Guys, please take a closer look as this is the first user platform
> that wants to extend opp-v2 bindings with platform specific stuff.
>
> On 21-07-15, 12:33, Lee Jones wrote:
> > Cc:
This patch adds support for the MHU mailbox peripheral used on Juno by
application processors to communicate with remote SCP handling most of
the CPU/system power management. It also adds the SRAM reserving the
shared memory and SCPI message protocol using that shared memory.
Signed-off-by: Sudeep
On some ARM based systems, a separate Cortex-M based System Control
Processor(SCP) provides the overall power, clock, reset and system
control including CPU DVFS. SCPI Message Protocol is used to
communicate with the SCPI.
This patch adds a interface driver for adding OPPs and registering
the arm_
The clocks for the CPUs are provided by SCP and are managed by this
clock driver. So the cpufreq device needs to be added only after the
clock get registered and removed when this driver is unloaded.
This patch manages the cpufreq virtual device based on the clock
availability.
Signed-off-by: Sud
On some ARM based systems, a separate Cortex-M based System Control
Processor(SCP) provides the overall power, clock, reset and system
control. System Control and Power Interface(SCPI) Message Protocol
is defined for the communication between the Application Cores(AP)
and the SCP.
This patch adds
This patch adds devicetree binding for System Control and Power
Interface (SCPI) Message Protocol used between the Application Cores(AP)
and the System Control Processor(SCP). The MHU peripheral provides a
mechanism for inter-processor communication between SCP's M3 processor
and AP.
SCP offers co
This patch adds support for System Control and Power Interface (SCPI)
Message Protocol used between the Application Cores(AP) and the System
Control Processor(SCP). The MHU peripheral provides a mechanism for
inter-processor communication between SCP's M3 processor and AP.
SCP offers control and m
Hi,
This patch series adds support for:
1. SCPI(System Control and Power Interface) mailbox protocol driver.
It uses ARM MHU mailbox controller driver on Juno but can work with
any mailbox controllers using standard mailbox APIs
2. Add support for clocks provided by SCP firmware thro
Den 30.06.2015 08:43, skrev Fabio Falzoi:
Use a struct flexfb_lcd_controller to holds chip properties, instead of
relying on a long 'if - else if' chain.
This allows to:
- use a simple linear search to verify if a certain LCD controller
model is supported or not.
- add support for a new LCD chip
> -Original Message-
> From: Mark Rutland [mailto:mark.rutl...@arm.com]
> Sent: Thursday, July 23, 2015 3:27 PM
> To: Badola Nikhil-B46172
> Cc: linux-kernel@vger.kernel.org; devicet...@vger.kernel.org; ba...@ti.com
> Subject: Re: [PATCH 1/3] Documentation: dt: dwc3: Add snps,configure-flad
adds file for description on device node bindings for RTC
found on Xilinx Zynq Ultrascale+ MPSoC.
Signed-off-by: Suneel Garapati
---
Documentation/devicetree/bindings/rtc/xlnx-rtc.txt | 25 ++
1 file changed, 25 insertions(+)
create mode 100644 Documentation/devicetree/bindi
> From: Dan Carpenter
> Sent: Thursday, July 23, 2015 18:25
> On Thu, Jul 23, 2015 at 01:10:57PM +0300, Dan Carpenter wrote:
> > In this specific case, writing it as "if (ret != 0)" caused the bug. If
> > we had written it as "if (ret) return ret;" then there are no zeroes so
> > wouldn't have bee
On Tue, Jul 21, 2015 at 04:47:35PM -0700, David Rientjes wrote:
> On Mon, 20 Jul 2015, Mel Gorman wrote:
>
> > From: Mel Gorman
> >
> > The zonelist cache (zlc) was introduced to skip over zones that were
> > recently known to be full. At the time the paths it bypassed were the
> > cpuset checks
On Thu, 2015-07-23 at 11:07 +0200, Javier Martinez Canillas wrote:
> > +
> > + if (ret < 0)
> > + dev_err(&i2c->dev, "Failed to initialize regulator: %d\n",
> > ret);
> > +
>
> I don't think this is necessary, you are already adding logs for all
> the error conditions.
Yes,
On Wed, Jul 22, 2015 at 10:59:04PM +0800, Leo Yan wrote:
> On Wed, Jul 22, 2015 at 02:31:04PM +0100, Morten Rasmussen wrote:
> > On Tue, Jul 21, 2015 at 11:41:45PM +0800, Leo Yan wrote:
> > > Hi Morten,
> > >
> > > On Tue, Jul 07, 2015 at 07:23:44PM +0100, Morten Rasmussen wrote:
> > > > From: Mor
Enclose defined macro in paranthesis to avoid checkpatch complaint
"ERROR: Macros with complex values should be enclosed in parentheses"
Signed-off-by: Ioan-Adrian Ratiu
---
drivers/staging/rtl8192e/rtllib_rx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/r
On Fri, Jun 5, 2015 at 4:59 PM, Octavian Purdila
wrote:
> Since patch "i2c / ACPI: Use 0 to indicate that device does not have
> interrupt assigned" [1], 0 is not a valid i2c client irq anymore, so
> change all driver's checks accordingly.
>
> The same issue occurs when the device is instantiated
On Thu, Jul 23, 2015 at 11:52:19AM +0100, Badola Nikhil wrote:
> > -Original Message-
> > From: Mark Rutland [mailto:mark.rutl...@arm.com]
> > Sent: Thursday, July 23, 2015 3:27 PM
> > To: Badola Nikhil-B46172
> > Cc: linux-kernel@vger.kernel.org; devicet...@vger.kernel.org; ba...@ti.com
>
On Thu, Jul 23, 2015 at 12:42:15PM +0200, Peter Zijlstra wrote:
> > static_likely_init_true_branch(struct static_likely_init_true_key *key)
> > static_likely_init_false_branch(struct static_likely_init_false_key *key)
> > static_unlikely_init_false_branch(struct static_unlikely_init_false_key
> >
adds support for RTC controller found on
Xilinx Zynq Ultrascale+ MPSoC platform.
Signed-off-by: Suneel Garapati
---
drivers/rtc/Kconfig | 7 ++
drivers/rtc/Makefile | 1 +
drivers/rtc/rtc-zynqmp.c | 278 +++
3 files changed, 286 insertions
adds rtc controller node to zynqmp devicetree.
Signed-off-by: Suneel Garapati
---
arch/arm64/boot/dts/xilinx/zynqmp-ep108.dts | 4
arch/arm64/boot/dts/xilinx/zynqmp.dtsi | 9 +
2 files changed, 13 insertions(+)
diff --git a/arch/arm64/boot/dts/xilinx/zynqmp-ep108.dts
b/arch/a
Hello,
On Thu, Jul 23, 2015 at 03:51:47AM -0500, a.af...@hybridware.co wrote:
> Dears
> i have the following bug on reiserfs on gentoo linux kernel 3.4.9 how
> can i solve it
First, your kernel is totally outdated, you've been skipping 3 years of
fixes in 100 updates roughly covering 4600 bugs
On Thu, Jul 23, 2015 at 12:05:21AM +0100, Dave Hansen wrote:
> On 07/22/2015 03:48 PM, Catalin Marinas wrote:
> > You are right, on x86 the tlb_single_page_flush_ceiling seems to be
> > 33, so for an HPAGE_SIZE range the code does a local_flush_tlb()
> > always. I would say a single page TLB flush
On 07/23/2015 11:53 AM, Christoph Hellwig wrote:
> Any reason you're adding this to null_blk instead of having a separate
> null_nvm driver?
>
Only reason was to not duplicate the I/O submission/completion flow.
With the simple code at the moment, it is little to add. However, if
someone decides
Dears
i have the following bug on reiserfs on gentoo linux kernel 3.4.9 how
can i solve it
NOTE am not using NFS
[2292727.857807] kernel BUG at fs/reiserfs/stree.c:1474!
[2292727.857822] invalid opcode: [#1] SMP DEBUG_PAGEALLOC
[2292727.857856] CPU 0
[2292727.857863] Modules linked in: e1
On Wed, Jul 22, 2015 at 01:06:44PM -0400, Jason Baron wrote:
> Ok,
>
> So we could add all 4 possible initial states, where the
> branches would be:
>
> static_likely_init_true_branch(struct static_likely_init_true_key *key)
> static_likely_init_false_branch(struct static_likely_init_false_key *k
From: Peter Hurley [mailto:pe...@hurleysoftware.com]
Sent: Wednesday, July 22, 2015 3:52 PM
> Subject: Re: [PATCH 4/4] serial: 8250_dw: use serial_in() and not readl()
> From: Noam Camus
>
> This is now matches device endianness.
> I'm not seeing where serial_in() is used here, as claimed by
On Fri, Jul 17, 2015 at 12:10:09PM +0200, Florian Westphal wrote:
> Toralf Förster wrote:
> > I do run a server with a 64 bit hardened Gentoo Linux (kernel currently
> > 4.0.8).
> > Around 12th of July it started to spew those messages into kern.log :
> >
> > /var/log/kern.log:Jul 12 15:26:07 to
Hi Zhang,
On Tue, Jul 21, 2015 at 01:35:31PM +, Zhang, Rui wrote:
> > >
> Patch applied.
Thanks for applying. I missed to convert another place, so we get a new
compiler warning. The attached patch fixes this (suitable for git rebase
--autosquash). Please let me know if you can handle this or
From: Peter Hurley [mailto:pe...@hurleysoftware.com]
Sent: Wednesday, July 22, 2015 3:39 PM
>> +/* Writing to LCR may cause BUSY interrupt before we
>> + * register the IRQ line.
>> + * Currently autoconf() uses several writes to LCR.
>> + * In order to avoid calling to autoconf()
On 07/23/2015 11:53 AM, Christoph Hellwig wrote:
> Hi Matias,
>
> I like this new architecture.
Thanks, great to hear. :)
I will get the nitpicks fixed.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo
Capability mask for jumbo and no gigabit half duplex is the same.
Change one of them.
Signed-off-by: Harini Katakam
---
drivers/net/ethernet/cadence/macb.h |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/cadence/macb.h
b/drivers/net/ethernet/cadence/m
JUMBO and NO_GIGABIT_HALF have the same capability masks.
Change one of them.
Signed-off-by: Harini Katakam
---
drivers/net/ethernet/cadence/macb.h |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/cadence/macb.h
b/drivers/net/ethernet/cadence/macb.h
in
On Thu, 2015-07-23 at 09:55 +, Hayes Wang wrote:
> > Hi,
> >
> > this is most likely wrong. Usbcore does check for a device's ability to
> > do remote wakeup and will block a runtime suspend if it detects that
> > a remote wakeup would be required but the device cannot deliver.
> > (static int
Hi Andy,
On Wed, Jul 22, 2015 at 12:23:47PM -0700, Andy Lutomirski wrote:
> The modify_ldt syscall exposes a large attack surface and is
> unnecessary for modern userspace. Make it optional.
Wouldn't you prefer something like this which makes it possible to re-enable
it at runtime so that we can
On Thu, Jul 23, 2015 at 01:10:57PM +0300, Dan Carpenter wrote:
> In this specific case, writing it as "if (ret != 0)" caused the bug. If
> we had written it as "if (ret) return ret;" then there are no zeroes so
> wouldn't have been any temptation to return the zero instead of the ret.
I did a sea
SIG_SYS was added in commit a0727e8ce513 "signal, x86: add SIGSYS info
and make it synchronous."
Because we use the asm-generic struct siginfo, we got support for
SIG_SYS for free as part of that commit.
However there was no compat handling added for powerpc. That means we've
been advertising the
This commit enables seccomp filter on powerpc, now that we have all the
necessary pieces in place.
To support seccomp's desire to modify the syscall return value under
some circumstances, we use a different ABI to the ptrace ABI. That is we
use r3 as the syscall return value, and orig_gpr3 is the
Currently syscall_get_arguments() has two loops, one for compat and one
for regular tasks. In prepartion for the next patch, which changes which
registers we use, switch it to only have one loop, so we only have one
place to update.
Signed-off-by: Michael Ellerman
---
arch/powerpc/include/asm/sy
Currently syscall_get_arguments() is used by syscall tracepoints, and
collect_syscall() which is used in some debugging as well as
/proc/pid/syscall.
The current implementation just copies regs->gpr[3 .. 5] out, which is
fine for all the current use cases.
When we enable seccomp filter, that will
Wire up the syscall number and regs so the tests work on powerpc.
Acked-by: Kees Cook
Signed-off-by: Michael Ellerman
---
tools/testing/selftests/seccomp/seccomp_bpf.c | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/tools/testing/selftests/seccomp/seccomp_bpf.c
b/to
The seccomp_bpf test uses BPF_LD|BPF_W|BPF_ABS to load 32-bit values
from seccomp_data->args. On big endian machines this will load the high
word of the argument, which is not what the test wants.
Borrow a hack from samples/seccomp/bpf-helper.h which changes the offset
on big endian to account for
The API for calling do_syscall_trace_enter() is currently sensible
enough, it just returns the (modified) syscall number.
However once we enable seccomp filter it will get more complicated. When
seccomp filter runs, the seccomp kernel code (via SECCOMP_RET_ERRNO), or
a ptracer (via SECCOMP_RET_TRA
syscall_get_error() is unused, and never has been.
It's also probably wrong, as it negates r3 before returning it, but that
depends on what the caller is expecting.
It also doesn't deal with compat, and doesn't deal with TIF_NOERROR.
Although we could fix those, until it has a caller and it's cl
The documentation for syscall_get_nr() in asm-generic says:
Note this returns int even on 64-bit machines. Only 32 bits of
system call number can be meaningful. If the actual arch value
is 64 bits, this truncates to 32 bits so 0x means -1.
However our implementation was never updated t
Currently the only caller of syscall_set_return_value() is seccomp
filter, which is not enabled on powerpc.
This means we have not noticed that our implementation of
syscall_set_return_value() negates error, even though the value passed
in is already negative.
So remove the negation in syscall_se
Currently on powerpc we have our own #define for the highest (negative)
errno value, called _LAST_ERRNO. This is defined to be 516, for reasons
which are not clear.
The generic code, and x86, use MAX_ERRNO, which is defined to be 4095.
In particular seccomp uses MAX_ERRNO to restrict the value th
On Wed, Jul 22, 2015 at 02:26:30PM -0400, Dan Streetman wrote:
> The shared 'platform' driver module isn't needed, the platform drivers
> can directly register with crypto instead. It only adds unneeded
> complexity and problems.
>
> The first 4 patches are minor updates/bugfixes to the pSeries d
On Mon, 2015-20-07 at 19:01:42 UTC, Tim Gardner wrote:
> From: Tim Gardner
>
> drivers/macintosh/ans-lcd.c:201:1: warning: data definition has no type or
> storage class
> module_init(anslcd_init);
> ^
> drivers/macintosh/ans-lcd.c:201:1: error: type defaults to 'int' in
> declaration of 'mod
On Thu, Jul 23, 2015 at 03:05:16AM +, Dexuan Cui wrote:
> The kind of usage is not rare in the kernel code:
Yeah. But it's used 5% of the time. If it's under 15% then there is a
risk that we'll write a checkpatch rule to enforce the standard way...
There are some places where != 0 is idiomat
On Thursday 23 July 2015 15:42:58, Nikhil Badola wrote:
> Add "snps,configure-gfladj" boolean property to USB3 node. This property
^^
This does not match...
> is used to determine if frame length adjustment is required
>
> Signed-off-by: Nikhil Badola
> ---
> arch/arm/
Hi,
Thanks for the feedback.
(2015/07/23 17:25), Michal Hocko wrote:
> Hi,
>
> On Wed 22-07-15 11:14:21, Hidehiro Kawai wrote:
>> When an HA cluster software or administrator detects non-response
>> of a host, they issue an NMI to the host to completely stop current
>> works and take a crash dum
Please ignore this patch. This is not on the right base, i'll resend it.
Regards,
Harini
On Thu, Jul 23, 2015 at 3:31 PM, Harini Katakam
wrote:
> Capability mask for jumbo and no gigabit half duplex is the same.
> Change one of them.
>
> Signed-off-by: Harini Katakam
> ---
> drivers/net/ethern
On 07/22/2015 08:43 PM, Eric B Munson wrote:
> On Wed, 22 Jul 2015, Vlastimil Babka wrote:
>
>>
>> Hi,
>>
>> I think you should include a complete description of which
>> transitions for vma states and mlock2/munlock2 flags applied on them
>> are valid and what they do. It will also help with th
Add adjust_frame_length_quirk for writing to fladj register
which adjusts (micro)frame length to value provided by
"snps,configure-fladj" property thus avoiding USB 2.0 devices
to time-out over a longer run
Signed-off-by: Nikhil Badola
---
drivers/usb/dwc3/core.c | 12
drivers/usb/d
On 7/23/2015 1:01 AM, Spencer Baugh wrote:
From: Joern Engel
Make the warning about unsupported SCSI opcode more useful:
- Add in the initiator name so we know who's sending it.
- Print the warning even for opcodes that spc_parse_cdb() knows about
but that we don't handle.
Signed-off-
On 07/23/2015 12:12 AM, Alexei Starovoitov wrote:
> On 7/22/15 1:10 PM, Michael Kerrisk (man-pages) wrote:
>> BPF maps are a generic data structure for storage of different
>> data types. A user process can create multiple maps (with
>> key/value-pairs being opa
On Thu, Jul 23, 2015 at 11:09:21AM +0100, Nikhil Badola wrote:
> Add property snps,configure-fladj for enabling post silicon
> frame length adjustment
>
> Signed-off-by: Nikhil Badola
> ---
> Documentation/devicetree/bindings/usb/dwc3.txt | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a
From: Pan Xinhui
There are many nodes in the PAT memtype rb-tree. When we dump this tree
we call kzalloc every time to copy nodes. Actually these kzalloc are not
necessary. Lets do a optimization now.
Create an *entry* in memtype_seq_start(), and free it in
memtype_seq_stop(). These two callback
> Hi,
>
> this is most likely wrong. Usbcore does check for a device's ability to
> do remote wakeup and will block a runtime suspend if it detects that
> a remote wakeup would be required but the device cannot deliver.
> (static int autosuspend_check())
>
> So by removing the flag in the probe()
701 - 800 of 920 matches
Mail list logo
