Hello,
On Sun, Nov 05, 2017 at 11:01:05AM +0800, huang ying wrote:
> On Fri, Nov 3, 2017 at 11:00 PM, Zi Yan wrote:
> > On 3 Nov 2017, at 3:52, Huang, Ying wrote:
> >
> >> From: Huang Ying
> >>
> >> If THP migration is enabled, the following situation is possible,
> >>
> >> - A THP is mapped at
On Mon, Nov 06, 2017 at 04:46:54PM +0100, Greg Kroah-Hartman wrote:
> On Mon, Nov 06, 2017 at 10:59:47AM +0200, Gilad Ben-Yossef wrote:
> > On Mon, Nov 6, 2017 at 10:37 AM, Tobin C. Harding wrote:
> > > On Mon, Nov 06, 2017 at 06:55:52AM +, Gilad Ben-Yossef wrote:
> > >> Registers ioread/iowri
On 11/6/2017 2:17 PM, Tom Lendacky wrote:
> When crosvm is used to boot a kernel as a VM, the SMP MP-table is found
> at physical address 0x0. This causes mpf_base to be set to 0 and a
> subsequent "if (!mpf_base)" check in default_get_smp_config() results in
> the MP-table not being parsed. Furth
> -Original Message-
> From: linux-cifs-ow...@vger.kernel.org [mailto:linux-cifs-
> ow...@vger.kernel.org] On Behalf Of Long Li
> Sent: Monday, November 6, 2017 2:00 PM
> To: Matthew Wilcox ; Pavel Shilovsky
>
> Cc: linux-cifs ; Stephen Hemminger
> ; linux-r...@vger.kernel.org; Kernel Mail
On Wed, Nov 01, 2017 at 09:44:03AM -0400, Sven Van Asbroeck wrote:
> Some eeproms in the at24 family do not roll over page reads,
> e.g. the Microchip 24AA16/24LC16B. On those eeproms, reads
> that straddle block boundaries will not work correctly.
>
> Solution:
> Implement read rollover in the dr
On Wed, Nov 01, 2017 at 04:20:05PM -0700, Florian Fainelli wrote:
> BCM7278 includes a RGN200 hardware random number generator, document the
> compatible string for that version of the IP.
>
> Signed-off-by: Florian Fainelli
> ---
> Documentation/devicetree/bindings/rng/brcm,iproc-rng200.txt | 4
Currently, the existing qspinlock implementation will fallback to
test-and-set if the hypervisor has not set the PV_UNHALT flag.
This patch gives the opportunity to guest kernels to select
between test-and-set and the regular queueu fair lock implementation
based on the PV_DEDICATED KVM feature fl
The GMII groups need to be split across GMAC0 and GMAC1 since
GMAC0 is always available but GMAC1 masks GPIO2 lines 0-7
so we might want just one interface out.
Signed-off-by: Linus Walleij
---
drivers/pinctrl/pinctrl-gemini.c | 79 +++-
1 file changed, 54 ins
On Mon, Nov 06, 2017 at 10:53:48AM -0500, Zi Yan wrote:
> Thanks for clarifying it. We both agree that !pmd_present(), which means
> PMD migration entry, does not get into userfaultfd_must_wait(),
> then there seems to be no issue with current code yet.
>
> However, the if (!pmd_present(_pmd)) in
On Mon, 06 Nov 2017 10:05:34 +0100
Gerd Hoffmann wrote:
> Hi,
>
> > > I thought we had agreed to make this behave similar to
> > > VFIO_GROUP_GET_DEVICE_FD, the ioctl would take a __u32 dmabuf_id
> > > and
> > > return the file descriptor as the ioctl return value. Thanks,
> >
> > If we fo
On Mon, Nov 6, 2017 at 6:41 PM, Dave Martin wrote:
> On Mon, Nov 06, 2017 at 05:12:03PM +, Arnd Bergmann wrote:
>> On Mon, Nov 6, 2017 at 5:50 PM, Dave Martin wrote:
>> > On Mon, Nov 06, 2017 at 01:36:40PM +, Arnd Bergmann wrote:
>> >> The register_sysctl() function has been around for fi
On 11/03/2017 05:14 PM, Kees Cook wrote:
> On Fri, Nov 3, 2017 at 4:04 PM, Laura Abbott wrote:
>> __{get,put}_user calls are designed to be fast and have no checks,
>> relying on the caller to have made the appropriate calls previously.
>> It's very easy to forget a check though, leaving the kerne
I forgot to add Boris's Reviewed-by Tag. If the patchset is acceptable,
please let me know if I should send another version with the Tag or if
the Tag can be added when it is merged.
On 11/06/2017 11:44 AM, Janakarajan Natarajan wrote:
The function for CPUID 8001 ECX is set to 0xc001. Se
On 11/02/2017 05:19 AM, Juergen Gross wrote:
> In order to support Linux to run as a pv guest on machines with huge
> memory (>16TB) or as a hvm guest with more than 16TB of memory the
> kernel has to support grant table interface v2, as v1 is limited to
> 32 bit frame numbers.
>
> This series re-a
> -Original Message-
> From: Tom Talpey
> Sent: Monday, November 6, 2017 12:26 PM
> To: Long Li ; Matthew Wilcox
> ; Pavel Shilovsky
> Cc: linux-cifs ; Stephen Hemminger
> ; linux-r...@vger.kernel.org; Kernel Mailing
> List ; Steve French
> Subject: RE: [Patch v5 08/21] CIFS: SMBD: Upper
Thanks! I noticed the report just before I saw your email. :) This
should be fixed in tip soon.
-Kees
On Mon, Nov 6, 2017 at 5:34 AM, Arnd Bergmann wrote:
> The timer_setup() conversion included a small typo that breaks the
> build:
>
> arch/arm/mach-footbridge/dc21285.c: In function 'dc21285_en
On Mon, Nov 06, 2017 at 07:29:18AM -0800, Joe Perches wrote:
> On Mon, 2017-11-06 at 08:33 +, Andy Whitcroft wrote:
> > On Mon, Nov 06, 2017 at 03:19:14PM +1100, Tobin C. Harding wrote:
> > > Hi,
>
> Hello.
>
> > > When parsing drivers/staging/unisys/visorbus/visorchipset.c in Greg's
> > > st
From: Boqun Feng
Call the rseq_handle_notify_resume() function on return to userspace if
TIF_NOTIFY_RESUME thread flag is set.
Increment the event counter and perform fixup on the pre-signal when a
signal is delivered on top of a restartable sequence critical section.
Signed-off-by: Boqun Feng
Here is an updated rseq patchset taking into account the feedback
received at kernel summit and afterwards.
Use-cases explanation and benchmarks can be found in patch 01
"Restartable sequences system call".
This is still submitted as RFC. I'm keeping a linux-rseq
tree with this patchset at:
http
Signed-off-by: Mathieu Desnoyers
CC: "Paul E. McKenney"
CC: Peter Zijlstra
CC: Paul Turner
CC: Thomas Gleixner
CC: Andrew Hunter
CC: Andy Lutomirski
CC: Andi Kleen
CC: Dave Watson
CC: Chris Lameter
CC: Ingo Molnar
CC: "H. Peter Anvin"
CC: Ben Maurer
CC: Steven Rostedt
CC: Josh Triplet
This new cpu_opv system call executes a vector of operations on behalf
of user-space on a specific CPU with preemption disabled. It is inspired
from readv() and writev() system calls which take a "struct iovec" array
as argument.
The operations available are: comparison, memcpy, add, or, and, xor,
Implements two basic tests of RSEQ functionality, and one more
exhaustive parameterizable test.
The first, "basic_test" only asserts that RSEQ works moderately
correctly. E.g. that the CPUID pointer works.
"basic_percpu_ops_test" is a slightly more "realistic" variant,
implementing a few simple p
Signed-off-by: Mathieu Desnoyers
CC: Russell King
CC: Catalin Marinas
CC: Will Deacon
CC: Thomas Gleixner
CC: Paul Turner
CC: Andrew Hunter
CC: Peter Zijlstra
CC: Andy Lutomirski
CC: Andi Kleen
CC: Dave Watson
CC: Chris Lameter
CC: Ingo Molnar
CC: Ben Maurer
CC: Steven Rostedt
CC: "P
Signed-off-by: Mathieu Desnoyers
CC: Russell King
CC: Catalin Marinas
CC: Will Deacon
CC: Thomas Gleixner
CC: Paul Turner
CC: Andrew Hunter
CC: Peter Zijlstra
CC: Andy Lutomirski
CC: Andi Kleen
CC: Dave Watson
CC: Chris Lameter
CC: Ingo Molnar
CC: "H. Peter Anvin"
CC: Ben Maurer
CC:
The A13 Olinuxino have an headphone jack and audio is supported
so enable it.
Signed-off-by: Emmanuel Vadot
---
arch/arm/boot/dts/sun5i-a13-olinuxino.dts | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/sun5i-a13-olinuxino.dts
b/arch/arm/boot/dts/sun5i-a13-olinuxino.dts
Expose a new system call allowing each thread to register one userspace
memory area to be used as an ABI between kernel and user-space for two
purposes: user-space restartable sequences and quick access to read the
current CPU number value from user-space.
* Restartable sequences (per-cpu atomics)
Fixes assembler errors:
/tmp/cceKwI9a.s: Assembler messages:
/tmp/cceKwI9a.s:849: Error: co-processor offset out of range
with gcc prior to gcc-7. This can trigger if multiple rseq inline asm
are used within the same function.
My best guess on the cause of this issue is that gcc has a hard
time f
Wire up the rseq system call on 32-bit ARM.
This provides an ABI improving the speed of a user-space getcpu
operation on ARM by skipping the getcpu system call on the fast path, as
well as improving the speed of user-space operations on per-cpu data
compared to using load-linked/store-conditional.
Call the rseq_handle_notify_resume() function on return to userspace if
TIF_NOTIFY_RESUME thread flag is set.
Increment the event counter and perform fixup on the pre-signal frame
when a signal is delivered on top of a restartable sequence critical
section.
Signed-off-by: Mathieu Desnoyers
CC: R
Signed-off-by: Mathieu Desnoyers
CC: Benjamin Herrenschmidt
CC: Paul Mackerras
CC: Michael Ellerman
CC: Boqun Feng
CC: Peter Zijlstra
CC: "Paul E. McKenney"
CC: linuxppc-...@lists.ozlabs.org
---
arch/powerpc/include/asm/systbl.h | 1 +
arch/powerpc/include/asm/unistd.h | 2 +-
arc
From: Boqun Feng
Wire up the rseq system call on powerpc.
This provides an ABI improving the speed of a user-space getcpu
operation on powerpc by skipping the getcpu system call on the fast
path, as well as improving the speed of user-space operations on per-cpu
data compared to using load-reser
Wire up the rseq system call on x86 32/64.
This provides an ABI improving the speed of a user-space getcpu
operation on x86 by removing the need to perform a function call, "lsl"
instruction, or system call on the fast path, as well as improving the
speed of user-space operations on per-cpu data.
Take an effort to recode the arm64 vdso code from assembler to C
previously submitted by Andrew Pinski , rework
it for use in both arm and arm64, overlapping any optimizations
for each architecture. But instead of landing it in arm64, land the
result into lib/vdso and unify both implementations to
Take an effort to recode the arm64 vdso code from assembler to C
previously submitted by Andrew Pinski , rework
it for use in both arm and arm64, overlapping any optimizations
for each architecture. But instead of landing it in arm64, land the
result into lib/vdso and unify both implementations to
Take an effort to recode the arm64 vdso code from assembler to C
previously submitted by Andrew Pinski , rework
it for use in both arm and arm64, overlapping any optimizations
for each architecture. But instead of landing it in arm64, land the
result into lib/vdso and unify both implementations to
Take an effort to recode the arm64 vdso code from assembler to C
previously submitted by Andrew Pinski , rework
it for use in both arm and arm64, overlapping any optimizations
for each architecture. But instead of landing it in arm64, land the
result into lib/vdso and unify both implementations to
Call the rseq_handle_notify_resume() function on return to
userspace if TIF_NOTIFY_RESUME thread flag is set.
Increment the event counter and perform fixup on the pre-signal frame
when a signal is delivered on top of a restartable sequence critical
section.
Signed-off-by: Mathieu Desnoyers
CC: R
Take an effort to recode the arm64 vdso code from assembler to C
previously submitted by Andrew Pinski , rework
it for use in both arm and arm64, overlapping any optimizations
for each architecture. But instead of landing it in arm64, land the
result into lib/vdso and unify both implementations to
Take an effort to recode the arm64 vdso code from assembler to C
previously submitted by Andrew Pinski , rework
it for use in both arm and arm64, overlapping any optimizations
for each architecture. But instead of landing it in arm64, land the
result into lib/vdso and unify both implementations to
Take an effort to recode the arm64 vdso code from assembler to C
previously submitted by Andrew Pinski , rework
it for use in both arm and arm64, overlapping any optimizations
for each architecture. But instead of landing it in arm64, land the
result into lib/vdso and unify both implementations to
Take an effort to recode the arm64 vdso code from assembler to C
previously submitted by Andrew Pinski , rework
it for use in both arm and arm64, overlapping any optimizations
for each architecture. But instead of landing it in arm64, land the
result into lib/vdso and unify both implementations to
On Mon, Nov 06, 2017 at 09:25:33PM +0300, Pavel Vasilyev wrote:
> ./leaking_addresses.pl --dont_walk_abs /proc --dont_walk_abs /sys
> Unknown option: dont_walk_abs
> Unknown option: dont_walk_abs
Oh thanks. Documentation is out of sync with the code, what are the odds.
v4 to come.
thanks,
Tobin
Take an effort to recode the arm64 vdso code from assembler to C
previously submitted by Andrew Pinski , rework
it for use in both arm and arm64, overlapping any optimizations
for each architecture. But instead of landing it in arm64, land the
result into lib/vdso and unify both implementations to
Take an effort from the previous 9 patches to recode the arm64 vdso
code from assembler to C previously submitted by
Andrew Pinski , rework it for use in both arm and
arm64, overlapping any optimizations for each architecture. But
instead of landing it in arm64, land the result into lib/vdso and
un
Take an effort to recode the arm64 vdso code from assembler to C
previously submitted by Andrew Pinski , rework
it for use in both arm and arm64, overlapping any optimizations
for each architecture. But instead of landing it in arm64, land the
result into lib/vdso and unify both implementations to
Take an effort to recode the arm64 vdso code from assembler to C
previously submitted by Andrew Pinski , rework
it for use in both arm and arm64, overlapping any optimizations
for each architecture. But instead of landing it in arm64, land the
result into lib/vdso and unify both implementations to
On Tue, Oct 24, 2017 at 10:49 PM, John Stultz wrote:
> On Thu, Oct 19, 2017 at 4:14 AM, Arnd Bergmann wrote:
>
> This one doesn't seem to build for me... In the meantime, I'm going
> to go ahead testing with patches 1-6.
>
> jstultz@buildbox:~/projects/linux/time$ make -j24 bzImage > /dev/null
Take an effort to recode the arm64 vdso code from assembler to C
previously submitted by Andrew Pinski , rework
it for use in both arm and arm64, overlapping any optimizations
for each architecture. But instead of landing it in arm64, land the
result into lib/vdso and unify both implementations to
On Mon, Nov 06, 2017 at 06:51:35PM +, James Morse wrote:
> > If you look at percpu_down_read(), you'll note it'll disable preemption
> > before calling __percpu_down_read().
>
> Yes, this is how __percpu_down_read() protects the combination of it's
> fast/slow
> paths.
>
> But next percpu_do
On Thu, Oct 19, 2017 at 06:15:52PM +0100, Suzuki K Poulose wrote:
> Right now we issue an update_buffer() and reset_buffer() call backs
> in succession when we stop tracing an event. The update_buffer is
> supposed to check the status of the buffer and make sure the ring buffer
> is updated with th
>> Add a jump target so that a bit of exception handling can be better reused
>> at the end of this function.
>
> Why not look at what the C compiler generates before making the code
> less readable ?
* Does the adjusted source code layout fit to information from the section
“7) Centralized exi
A DSA port has a dedicated CPU port assigned to it, stored in the cpu_dp
member. It is not meant to be modified by a port, thus make it const.
Signed-off-by: Vivien Didelot
---
include/net/dsa.h | 2 +-
net/dsa/slave.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/incl
When probing a DSA switch, there is basically two stages.
The first stage is the parsing of the switch device, from either device
tree or platform data. It fetches the DSA tree to which it belongs, and
validates its ports. The switch device is then added to the tree, and
the second stage is called
Instead of having two dsa_ds_find_port_dn (which returns a bool) and
dsa_dst_find_port_dn (which returns a switch) functions, provide a more
explicit dsa_tree_find_port_by_node function which returns a matching
port.
Signed-off-by: Vivien Didelot
---
net/dsa/dsa2.c | 37 +
The *_complete() functions take too much arguments to do only one thing:
they try to fetch the dsa_port structures corresponding to device nodes
under the "link" list property of DSA ports, and use them to setup the
routing table of switches.
This patch simplifies them by providing instead simpler
Now that the tree setup is centralized, we can simplify the code a bit
more by setting up or tearing down the tree directly when adding or
removing a switch to/from it.
Signed-off-by: Vivien Didelot
---
net/dsa/dsa2.c | 35 ---
1 file changed, 16 insertions(+), 19
This commit brings no functional changes. It gets rid of the underscore
prefixed _dsa_register_switch and _dsa_unregister_switch functions in
favor of dsa_switch_probe() which parses and adds a switch to a tree and
dsa_switch_remove() which removes a switch from a tree.
Signed-off-by: Vivien Didel
The dsa_dst_parse function called just before dsa_dst_apply does not
parse the tree but does only one thing: it assigns the default CPU port
to dst->cpu_dp and to each user ports.
This patch simplifies this by calling a dsa_tree_setup_default_cpu
function at the beginning of dsa_dst_apply directly
The OF code provides a of_for_each_phandle() helper to iterate over
phandles. Use it instead of arbitrary iterating ourselves over the list
of phandles hanging to the "link" property of the port's device node.
The of_phandle_iterator_next() helper calls of_node_put() itself on
it.node. Thus We mus
The dsa_dsa_port_apply and dsa_cpu_port_apply functions do exactly the
same. The dsa_user_port_apply function does not try to register a fixed
link but try to create a slave.
This commit factorizes and scopes all that in two convenient
dsa_port_setup and dsa_port_teardown functions.
It won't hurt
This commit provides better scope for the DSA tree setup and teardown
functions. It renames the "applied" bool to "setup" and print a message
when the tree is setup, as it is done during teardown.
At the same time, check dst->setup in dsa_tree_setup, where it is set to
true.
Signed-off-by: Vivien
Add DSA helpers to setup and teardown a master net device wired to its
CPU port. This centralizes the dsa_ptr assignment.
This also makes the master ethtool helpers static at the same time.
Signed-off-by: Vivien Didelot
---
net/dsa/dsa2.c | 36 +++-
net/dsa/d
On Mon, Nov 06, 2017 at 09:41:09AM -0800, Linus Torvalds wrote:
> On Mon, Nov 6, 2017 at 9:27 AM, Linus Torvalds
> wrote:
> >
> > Lovely. This is great. It shows just how much totally pointless stuff
> > we leak, and to normal users that really shouldn't need it.
>
> Side note: it would be good t
This patches brings no functional changes. It removes the unused dst
argument from the dsa_ds_apply and dsa_ds_unapply functions, rename them
to dsa_switch_setup and dsa_switch_teardown for a more explicit scope.
This clarifies the steps of the setup or teardown of a switch fabric.
Signed-off-by:
On Mon, Nov 06, 2017 at 12:27:45PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.18.80 release.
> There are 27 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know
On Mon, Nov 06, 2017 at 10:43:23AM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.61 release.
> There are 67 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
On Mon, Nov 06, 2017 at 10:44:35AM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.97 release.
> There are 40 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
On Mon, Nov 06, 2017 at 10:12:13AM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.13.12 release.
> There are 36 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know
On Thu, Nov 02, 2017 at 11:15:58AM -0700, Stephane Eranian wrote:
> This patch adds a new --skid-ip option to perf record
> to capture the unmodified interrupted instruction pointer in
> each sample. With this option, the kernel captures both the
> ip and skid ip. Unless precise mode is enabled bot
* Ram Pai:
> Testing:
> ---
> This patch series has passed all the protection key
> tests available in the selftest directory.The
> tests are updated to work on both x86 and powerpc.
> The selftests have passed on x86 and powerpc hardware.
How do you deal with the key reuse problem? Is it th
Substantial added attack surface will never go away as a problem. There
aren't a finite number of vulnerabilities to be found.
On Mon, Nov 6, 2017 at 6:59 AM, Christian König
wrote:
> Am 06.11.2017 um 12:44 schrieb Dan Carpenter:
>>
>> We assign "v_init = asic_blank_start;" a few lines earlier so there is
>> no need to do it again inside the if statements. Also "v_init" is
>> unsigned so it can't be less than zero.
>>
>>
>
> And this is getting a bit nutty:
>
> support-resetting-warn_once.patch
> support-resetting-warn_once-checkpatch-fixes.patch
> support-resetting-warn_once-for-all-architectures.patch
> support-resetting-warn_once-for-all-architectures-v2.patch
> support-resetting-warn_once-for-all-architecture
On Wed, Nov 01, 2017 at 06:04:06PM -0700, Florian Fainelli wrote:
> Since the same block is used on BCM2835 and BCM6368, merge the bindings
> and remove the brcm,bcm6368.txt binding document.
>
> Signed-off-by: Florian Fainelli
> ---
> .../devicetree/bindings/rng/brcm,bcm2835.txt | 22
> +
(-)
After that, all 1118 timer_setup() callsites will be finished. My
tree, based on next-20171106, is here:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/log/?h=kspp/timer/next/20171106/conversions
Notes and break-down of patch statuses:
# in-flight (tip/timers/core)
ARM: foot
On Thu, Nov 02, 2017 at 02:53:49PM +1100, Joel Stanley wrote:
> The device tree bindings are updated to document the resets phandle, and
> the example is updated to match what is expected for both the reset and
> clock phandle.
>
> Note that the bindings should have always had the reset controller
On Thu, Nov 02, 2017 at 02:56:24PM +0800, Chunyan Zhang wrote:
> This patch added the list of clocks for Spreadtrum's SC9860 SoC,
> together with clock initialization code.
>
> Signed-off-by: Chunyan Zhang
> ---
> drivers/clk/sprd/Kconfig| 10 +
> drivers/clk/sprd/Makefile
On Sat, Nov 4, 2017 at 8:21 AM, Nicolas Iooss
wrote:
> On Sun, Sep 3, 2017 at 2:00 PM, Nicolas Iooss
> wrote:
>>
>> Function vega10_apply_state_adjust_rules() only initializes
>> stable_pstate_sclk_dpm_percentage when
>> data->registry_data.stable_pstate_sclk_dpm_percentage is not between 1
>> an
On 11/06/17 12:17, Tom Lendacky wrote:
> When crosvm is used to boot a kernel as a VM, the SMP MP-table is found
> at physical address 0x0. This causes mpf_base to be set to 0 and a
> subsequent "if (!mpf_base)" check in default_get_smp_config() results in
> the MP-table not being parsed. Further
On Fri, Nov 03, 2017 at 03:53:01PM +1100, Andrew Jeffery wrote:
> Signed-off-by: Andrew Jeffery
> ---
> .../devicetree/bindings/hwmon/max31785.txt | 22
> ++
> 1 file changed, 22 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/hwmon/max31785.txt
"INVALID_STATE" is already being returned in the default case and this
code cannot be reached.
Addresses-Coverity-ID: 1398384
Signed-off-by: Gustavo A. R. Silva
---
drivers/net/wireless/rsi/rsi_91x_ps.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/net/wireless/rsi/rsi_91x_ps.c
b/d
Commit c6e26ea8c893 ("dpaa_eth: change device used") generated some
conflicts in my patches waiting for submission. So I took a closer look at
it.
So here is a serie of 4 patches.
The 1st one is just about a spurious call to 'dev_set_drvdata()', which is
done in only 1 error handling path in the
There is no need to release explicitly some devm_ allocated resources.
If the 'mac_probe()' probe function fails, they will be released
automatically, as already done in the other error handling paths of
this function.
Also goto '_return_of_get_parent' as in the other error handling paths.
This is
Memory allocation functions already display some informaton in case of
memory allocation failure. There is no need to add an extra 'dev_err' here.
Signed-off-by: Christophe JAILLET
---
drivers/net/ethernet/freescale/fman/mac.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/net/ethern
If 'of_phy_find_device()' fails, we must undo the previous 'of_node_get()'
call, as done the the following error handling code.
Signed-off-by: Christophe JAILLET
---
drivers/net/ethernet/freescale/fman/mac.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/ethernet/freescale/fman/
Commit c6e26ea8c893 ("dpaa_eth: change device used") has removed usage of
'dev_set_drvdata()' in the 'mac_probe() function.
This call should also be axed.
Signed-off-by: Christophe JAILLET
---
drivers/net/ethernet/freescale/fman/mac.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/n
I've hit this 6 times now, across 3 boots:
Nov 3 11:04:54 turing-police kernel: [ 547.814748] BUG: sleeping function
called from invalid context at mm/slab.h:422
Nov 3 20:24:11 turing-police kernel: [ 60.093793] BUG: sleeping function
called from invalid context at mm/slab.h:422
Nov 4 20:
On 11/06/2017 04:27 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.18.80 release.
> There are 27 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses s
On Mon, Nov 06, 2017 at 03:56:54PM -0500, valdis.kletni...@vt.edu wrote:
> I've hit this 6 times now, across 3 boots:
>
> Nov 3 11:04:54 turing-police kernel: [ 547.814748] BUG: sleeping function
> called from invalid context at mm/slab.h:422
>
> Nov 3 20:24:11 turing-police kernel: [ 60.09
On 11/6/2017 3:41 PM, H. Peter Anvin wrote:
On 11/06/17 12:17, Tom Lendacky wrote:
When crosvm is used to boot a kernel as a VM, the SMP MP-table is found
at physical address 0x0. This causes mpf_base to be set to 0 and a
subsequent "if (!mpf_base)" check in default_get_smp_config() results in
t
Hi Thomas,
Please pull these timer conversions for tip/timers/core. These are a couple
fixes and more conversions that have either been reviewed or have been
pending on the list long enough.
I expect at least one more pull that will have the last scsi fix and one
netfilter conversion. After that,
Hi Yixun,
On Mon, Nov 6, 2017 at 10:31 AM, Yixun Lan wrote:
> Hi Neil:
>
>
> On 11/06/17 16:57, Neil Armstrong wrote:
>> On 06/11/2017 08:52, Yixun Lan wrote:
>>> According to the datasheet, in Meson-GXBB/GXL series,
>>> The clock gate bit for SARADC is HHI_GCLK_MPEG2 bit[22],
>>> while clock gat
On Mon, Nov 6, 2017 at 2:01 PM, Ido Schimmel wrote:
> On Mon, Nov 06, 2017 at 03:56:54PM -0500, valdis.kletni...@vt.edu wrote:
>> I've hit this 6 times now, across 3 boots:
>>
>> Nov 3 11:04:54 turing-police kernel: [ 547.814748] BUG: sleeping function
>> called from invalid context at mm/slab.
syzbot
wrote:
> syzkaller hit the following crash on 5a3517e009e979f21977d362212b7729c5165d92
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached
> Raw console output is attached.
> C reproducer is attached
> syzka
On 11/6/2017 1:15 PM, Sinan Kaya wrote:
> On 11/6/2017 1:03 PM, Robin Murphy wrote:
>>> #ifdef CONFIG_ACPI
>>> ret = strcmp(acpi_device_hid(adev), "QCOM8062");
>>> + if (ret)
>>> + ret = strcmp(acpi_device_hid(adev), "QCOM8063");
>> This string-juggling look
Problem and motivation: Once a breakpoint perf event (PERF_TYPE_BREAKPOINT)
is created, there is no flexibility to change the breakpoint type
(bp_type), breakpoint address (bp_addr), or breakpoint length (bp_len). The
only option is to close the perf event and configure a new breakpoint
event. This
On Fri, Nov 03, 2017 at 03:25:05PM +0800, Kaihua Zhong wrote:
> From: Leo Yan
>
> Document the DT binding for stub clock which is used for CPU,
> GPU and DDR frequency scaling.
>
> Signed-off-by: Leo Yan
> ---
> Documentation/devicetree/bindings/clock/hi3660-clock.txt | 6 ++
> 1 file chan
Quoting Daniel Micay (danielmi...@gmail.com):
> Substantial added attack surface will never go away as a problem. There
> aren't a finite number of vulnerabilities to be found.
There's varying levels of usefulness and quality. There is code which I
want to be able to use in a container, and code
From: Dave Hansen
Intel's Skylake Server CPUs have a different LLC topology than previous
generations. When in Sub-NUMA-Clustering (SNC) mode, the package is
divided into two "slices", each containing half the cores, half the LLC,
and one memory controller and each slice is enumerated to Linux
On Mon, Nov 6, 2017 at 2:04 PM, Eric Dumazet wrote:
> I have a patch, will send in a couple of minutes. Thanks.
https://patchwork.ozlabs.org/patch/834983/ ipv6: addrconf: fix a lockdep splat
801 - 900 of 1588 matches
Mail list logo
