Use straightline code with failure handling gotos instead of a lot
of nested conditionals.
Signed-off-by: Christoph Hellwig
Reviewed-by: Greg Kroah-Hartman
Reviewed-by: Darrick J. Wong
---
fs/select.c | 48
From: Haridhar Kalvala
hammer LED backlight brightness is not getting set when USB
device is in suspend state.
This patch fixes the issue by requesting USB HID device to be
in FULLON mode, so that sending hardware output report and
hardware raw request won't fail to
On Wed, Mar 28 2018, Herbert Xu wrote:
> On Wed, Mar 28, 2018 at 08:54:41AM +1100, NeilBrown wrote:
>>
>> Possibly.
>> I particularly want the interface to require that you pass the
>> previously returned object to _continue. That makes it easy to see that
>> the object is still being used. If
On Wed, Mar 28, 2018 at 4:42 AM, Minchan Kim wrote:
> binder_update_page_range needs down_write of mmap_sem because
> vm_insert_page need to change vma->vm_flags to VM_MIXEDMAP unless
> it is set. However, when I profile binder working, it seems
> every binder buffers should
Hi,
On 3/28/2018 1:44 AM, Doug Anderson wrote:
> Hi,
>
> On Tue, Mar 27, 2018 at 12:50 AM, Manu Gautam wrote:
>> Hi,
>>
>>
>> On 3/27/2018 12:26 PM, Vivek Gautam wrote:
>>>
>>> On 3/27/2018 10:37 AM, Manu Gautam wrote:
Hi Doug,
On 3/27/2018 9:56 AM,
Signed-off-by: Christoph Hellwig
---
net/phonet/socket.c | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/net/phonet/socket.c b/net/phonet/socket.c
index 28d981512f5f..70ac4539d5b7 100644
--- a/net/phonet/socket.c
+++ b/net/phonet/socket.c
@@ -341,15
Signed-off-by: Christoph Hellwig
---
net/nfc/llcp_sock.c | 9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/net/nfc/llcp_sock.c b/net/nfc/llcp_sock.c
index 376040092142..b6010750e634 100644
--- a/net/nfc/llcp_sock.c
+++ b/net/nfc/llcp_sock.c
@@ -549,16
Signed-off-by: Christoph Hellwig
---
net/caif/caif_socket.c | 12
1 file changed, 4 insertions(+), 8 deletions(-)
diff --git a/net/caif/caif_socket.c b/net/caif/caif_socket.c
index a6fb1b3bcad9..c7991867d622 100644
--- a/net/caif/caif_socket.c
+++
With the current aio code there is no need for the magic KIOCB_CANCELLED
value, as a cancelation just kicks the driver to queue the completion
ASAP, with all actual completion handling done in another thread. Given
that both the completion path and cancelation take the context lock there
is no
The upcoming aio poll support would like to be able to complete the
iocb inline from the cancellation context, but that would cause
a lock order reversal. Add support for optionally moving the cancelation
outside the context lock to avoid this reversal.
To make this safe aio_complete needs to
Now that sock_poll handles a NULL ->poll or ->poll_mask there is no need
for a stub.
Signed-off-by: Christoph Hellwig
---
crypto/af_alg.c | 1 -
crypto/algif_hash.c | 2 --
crypto/algif_rng.c | 1 -
drivers/isdn/mISDN/socket.c | 1 -
On Wed, Mar 28, 2018 at 5:49 AM, Guo Ren wrote:
> Hi Arnd,
>
> On Tue, Mar 27, 2018 at 09:38:56AM +0200, Arnd Bergmann wrote:
>> Usually the way gcc handles this, either each CPU is a strict superset
>> of another
>> one, so you just need to specify the one with the smallest
Factor out two busy poll related helpers for late reuse, and remove
a command that isn't very helpful, especially with the __poll_t
annotations in place.
Signed-off-by: Christoph Hellwig
---
include/net/busy_poll.h | 15 +++
net/socket.c| 21
These days we don't treat sync iocbs special in the aio completion code as
they never use it. Remove the old comment and BUG_ON given that the
current definition of is_sync_kiocb makes it impossible to hit.
iocb to the top of the function.
Signed-off-by: Christoph Hellwig
---
Replying to myself here, more or less to reflect further discussion on IRC
related to where the
bindings goes. Also, to publicly acknowledge and thank Geert for tons of advice
and comments
outside the email chain...
So, after further discussion on IRC, that's what I've been trying to do
[hope
On 27/03/2018 at 11:52, Mike Looijmans wrote:
Call of_get_nvmem_mac_address() to fetch the MAC address from an nvmem
cell, if one is provided in the device tree. This allows the address to
be stored in an I2C EEPROM device for example.
Signed-off-by: Mike Looijmans
On Tue, 27 Mar 2018, Eric Biggers wrote:
> Hi Michael,
>
> On Tue, Mar 27, 2018 at 11:06:14PM +0100, Michael Young wrote:
> > NFS mounts stopped working on one of my computers after a kernel update from
> > 4.15.3 to 4.15.4. I traced the problem to the commit
> >
On 2018-03-28 10:13, Rafael J. Wysocki wrote:
On Wed, Mar 28, 2018 at 12:10 AM, Rafael J. Wysocki wrote:
On Tuesday, March 27, 2018 11:50:02 PM CEST Thomas Ilsche wrote:
On 2018-03-20 16:45, Rafael J. Wysocki wrote:
From: Rafael J. Wysocki
In
Hi Huacai,
On Wed, Mar 28, 2018 at 04:38:16PM +0800, Huacai Chen wrote:
> Call __stack_chk_guard_setup() in decompress_kernel() is too late that
> stack checking always fails for decompress_kernel() itself. So remove
> __stack_chk_guard_setup() and initialize __stack_chk_guard before we
> call
Hi David,
Thanks for feedback.
On Tue, Mar 27, 2018 at 01:28:22PM -0400, David Miller wrote:
> From: Vadim Lomovtsev
> Date: Tue, 27 Mar 2018 08:07:29 -0700
>
> > From: Vadim Lomovtsev
> >
> > By default CN88XX BGX accepts all
The kernel documentation states that the locking of the irq-chip
registers should be handled by the irq-chip driver. In the irq-gic,
the accesses to the irqchip are seemingly not protected and multiple
writes to SPIs from different irq descriptors do RMW requests without
taking the irq-chip lock.
On 28/03/2018 at 11:53:17 +0800, Sean Wang wrote:
> On Tue, 2018-03-27 at 17:18 +0200, Alexandre Belloni wrote:
> > On 25/03/2018 at 03:36:28 +0800, Sean Wang wrote:
> > > just reply both replies in the same mail
> > >
> > > 1.) the power-off device is a part of rtc, use the same registers rtc
>
On Sun, Mar 25, 2018 at 08:02:16PM -0700, Jia He wrote:
>Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
>where possible") optimized the loop in memmap_init_zone(). But there is
>still some room for improvement. E.g. if pfn and pfn+1 are in the same
>memblock region, we can
On 3/28/2018 12:52 AM, Daniel Vacek Wrote:
On Sat, Mar 24, 2018 at 1:24 PM, Jia He wrote:
Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
where possible") optimized the loop in memmap_init_zone(). But it causes
possible panic bug. So Daniel Vacek
A resend of the "arch_spin_is_locked() patches" discussed in the last
days, together with a third patch/clean-up suggested by Will during
the review procees. The first two patches are unmodified, except for
the inclusion of Acked-by:'s.
Cheers,
Andrea
Andrea Parri (3):
arm64: Remove
On 3/28/2018 5:18 PM, Wei Yang Wrote:
Oops, I should reply this thread. Forget about the reply on another thread.
On Sun, Mar 25, 2018 at 08:02:15PM -0700, Jia He wrote:
Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
where possible") optimized the loop in
From: Colin Ian King
Trivial fix to spelling mistake in message text
Signed-off-by: Colin Ian King
---
drivers/scsi/fnic/fnic_trace.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/fnic/fnic_trace.c
On Wed, 28 Mar 2018, Thomas Gleixner wrote:
> On Tue, 27 Mar 2018, Kees Cook wrote:
>
> > > I guess if we put this storage into the rs_control (rather than on the
> > > stack) then we'd have to worry about concurrent uses of it. It looks
> > > like all the other fields are immutable once it's
On Wed, Mar 28, 2018 at 10:38 AM, Thomas Ilsche
wrote:
> On 2018-03-28 10:13, Rafael J. Wysocki wrote:
>>
>> On Wed, Mar 28, 2018 at 12:10 AM, Rafael J. Wysocki
>> wrote:
>>>
>>> On Tuesday, March 27, 2018 11:50:02 PM CEST Thomas Ilsche wrote:
Hi,
On 03/24/2018 01:47 PM, Heiner Kallweit wrote:
Am 24.03.2018 um 07:46 schrieb Vincent Guittot:
Hi Heiner,
Le Friday 23 Mar 2018 à 22:28:09 (+0100), Heiner Kallweit a écrit :
Recently I started to get the following problems with linux-next:
- When working via Putty/SSH on the system the
2018-03-27 1:16 GMT+02:00 Kees Cook :
> On Tue, Mar 13, 2018 at 12:51 PM, Salvatore Mesoraca
> wrote:
>> Avoid a VLA[1] by using a real constant expression instead of a variable.
>> The compiler should be able to optimize the original code and avoid
The tag control information (TCI) part of the VLAN header contains several
fields, including PCP (priority code point) and PVID (port VLAN id).
Current implementation uses function ethsw_port_set_tci() to set the PVID
value and mistakenly overwrites the rest of the TCI fields with 0,
including
On Mon, 12 Mar 2018, Charles Keepax wrote:
> Now GPIOD has support for both pdata systems and for non-standard DT
> bindings the Arizona reset GPIO can be converted to use it. Worth
> noting gpiod_set_raw_value_cansleep is used to match the behaviour
> of the old GPIOs. This is because the part
Fixes the following sparse warnings:
drivers/md/dm-verity-target.c:375:6: warning:
symbol 'verity_for_io_block' was not declared. Should it be static?
drivers/md/dm-verity-target.c:403:14: warning:
symbol 'verity_calc_buffs_for_bv' was not declared. Should it be static?
Signed-off-by: Wei
On 03/27/2018 07:01 PM, Eric W. Biederman wrote:
Stefan Berger writes:
From: Yuqiong Sun
Add new CONFIG_IMA_NS config option. Let clone() create a new IMA
namespace upon CLONE_NEWUSER flag. Attach the ima_ns data structure
to user_namespace.
On Mon, Mar 26, 2018 at 10:29 PM, Masahiro Yamada
wrote:
> CONFIG_GCOV_FORMAT_AUTODETECT compiles either gcc_3_4.c or gcc_4_7.c
> according to your GCC version.
>
> We can achieve the equivalent behavior by setting reasonable dependency
> with the knowledge of the
On Mon, Mar 26, 2018 at 10:29 PM, Masahiro Yamada
wrote:
> For PowerPC, GCC 5.2 is the requirement for GCC plugins. Move the
> version check to Kconfig so that the GCC plugin menus will be hidden
> if an older compiler is in use.
>
> Signed-off-by: Masahiro Yamada
Replace magic numbers by a well known define in order to make the code
human readable and also facilitate the code reusability.
Signed-off-by: Gustavo Pimentel
---
drivers/pci/dwc/pcie-designware-host.c | 34 --
The patch set was made against the Bjorn's next branch.
Adds support Designware EP support.
Increases the maximum number of interrupts allowed for Designware IP
controller.
Does a code cleanup on Designware driver:
- Replaces magic numbers without a easy meaning by a well known define
that
On Mon, Mar 26, 2018 at 06:16:29PM +0100, Colin King wrote:
> From: Colin Ian King
>
> Replace several allocation and memcpys with kmemdup and add in some
> missing memory allocation failure checks. Also fix an incorrect
> -EFAULT return with -ENOMEM.
>
>
Adds a callback that defines the maximum number of vectors that can be use
by the Root Complex.
Since this is a parameter associated to each SoC IP setting, makes sense to
be configurable and easily visible to future modifications.
The designware IP supports a maximum of 256 vectors.
Changes the IP registers size to accommodate the ATU unroll space.
Replaces "ctrlreg" reg-name by "dbi" to be coherent with similar drivers.
Replaces the pcie base address example by a real pcie base address in use.
Signed-off-by: Gustavo Pimentel
---
Signed-off-by: Gustavo Pimentel
---
Documentation/devicetree/bindings/pci/designware-pcie.txt | 13 +
1 file changed, 13 insertions(+)
diff --git a/Documentation/devicetree/bindings/pci/designware-pcie.txt
On Wed, 28 Mar 2018 10:36:38 +0800
Dong Jia Shi wrote:
> * Cornelia Huck [2018-03-27 12:01:27 +0200]:
>
> [...]
>
> > > >
> > > > So, basically everything is filled by pfn_array_alloc_pin()?
> > > Yes.
> > >
> > > > Should we expect a
Hi Arnd,
On Wed, Mar 28, 2018 at 09:40:49AM +0200, Arnd Bergmann wrote:
> Ok, thanks for the clarification. Obviously if they are mutually incompatible,
> there is no point in using a common kernel, so your current version is
> absolutely fine, and this is similar to how we cannot have a common
For PCIe devices the right policy is not a round robin but to use
the pcie device closer to the node. I did a prototype for that
long ago and the concept can work. Can you look into that and
also make that policy used automatically for PCIe devices?
On Mon, Mar 26, 2018 at 10:40:15AM +0200, Johannes Thumshirn wrote:
> nvme_start_keep_alive() isn't used outside core.c so unexport it and
> make it static.
>
> Signed-off-by: Johannes Thumshirn
Looks good:
Reviewed-by: Christoph Hellwig
I really don't want more lightnvm cruft in the core. We'll need
a proper abstraction.c
On Fri, Mar 23, 2018 at 12:00:08PM +0100, Matias Bjørling wrote:
> On 02/05/2018 01:15 PM, Matias Bjørling wrote:
> > The nvme driver sets up the size of the nvme namespace in two steps.
> > First it
On 27/03/2018 23:18, David Rientjes wrote:
> On Tue, 13 Mar 2018, Laurent Dufour wrote:
>
>> diff --git a/include/linux/mm.h b/include/linux/mm.h
>> index 2f3e98edc94a..b6432a261e63 100644
>> --- a/include/linux/mm.h
>> +++ b/include/linux/mm.h
>> @@ -1199,6 +1199,7 @@ static inline void
Call __stack_chk_guard_setup() in decompress_kernel() is too late that
stack checking always fails for decompress_kernel() itself. So remove
__stack_chk_guard_setup() and initialize __stack_chk_guard before we
call decompress_kernel().
Original code comes from ARM but also used for MIPS and SH,
There would be so many same lines printed by frequent prink if one
disk went wrong, like,
[ 546.185242] sd 0:1:0:0: rejecting I/O to offline device
[ 546.185258] sd 0:1:0:0: rejecting I/O to offline device
[ 546.185280] sd 0:1:0:0: rejecting I/O to offline device
[ 546.185307] sd 0:1:0:0:
This is an initial reduced version of the self tests that Google contributed,
with the harness reduced from 12000 to 6000 lines thanks to my trusty chainsaw
(model "d%").
Rather than including them in kvm-unit-tests, I chose to place these tests
into linux.git, which of course had the side effect
> -Original Message-
> From: Dongli Zhang [mailto:dongli.zh...@oracle.com]
> Sent: 28 March 2018 00:42
> To: xen-de...@lists.xenproject.org; linux-kernel@vger.kernel.org
> Cc: net...@vger.kernel.org; Wei Liu ; Paul Durrant
>
> Subject: [PATCH
On Sun, Mar 25, 2018 at 08:02:18PM -0700, Jia He wrote:
>This is the preparation for further optimizing in early_pfn_valid
>on arm64.
>
>Signed-off-by: Jia He
>---
> arch/arm64/include/asm/page.h | 3 ++-
> arch/arm64/mm/init.c | 25 -
> 2
Commit 38b850a73034f ("arm64: spinlock: order spin_{is_locked,unlock_wait}
against local locks") added an smp_mb() to arch_spin_is_locked(), in order
"to ensure that the lock value is always loaded after any other locks have
been taken by the current CPU", and reported one example (the "insane
On Tue, Mar 27, 2018 at 11:47:18PM -0700, Nathan Chancellor wrote:
> On Wed, Mar 28, 2018 at 08:32:02AM +0200, gre...@linuxfoundation.org wrote:
> > On Tue, Mar 27, 2018 at 01:47:55PM -0700, Nathan Chancellor wrote:
> > > On Tue, Mar 27, 2018 at 08:40:56PM +, Kani, Toshi wrote:
> > > > On Tue,
On Wed, Mar 28, 2018 at 05:33:32PM +0800, Ji.Zhang wrote:
> On Mon, 2018-03-26 at 12:39 +0100, Mark Rutland wrote:
> > I think that it would be preferable to try to avoid the inifinite loop
> > case. We could hit that by accident if we're tracing a live task.
> >
> > It's a little tricky to
This commit 15122ee2c515a ("arm64: Enforce BBM for huge
IO/VMAP mappings") is a temporary work-around until the
issues with CONFIG_HAVE_ARCH_HUGE_VMAP gets fixed.
Revert this change as we have fixes for the issue.
Signed-off-by: Chintan Pandya
---
From: V1-> V6:
- No
This patch ("mm/vmalloc: Add interfaces to free unmapped
page table") adds following 2 interfaces to free the page
table in case we implement huge mapping.
pud_free_pmd_page() and pmd_free_pte_page()
Some architectures (like arm64) needs to do proper TLB
maintanance after updating pagetable
From: Steve Twiss
Replace multi-line entries in the regmap_range arrays with single
line macros: regmap_reg_range(). This will leave the static structure
array entries for regmap_range unaltered. It will significantly reduce
the line count in the DA9062/61 core
On Wed, Mar 28, 2018 at 04:25:37PM +1100, Michael Ellerman wrote:
> That was tempting, but it leaves unfixed all the other potential
> callers, both in in-tree and out-of-tree and in code that's yet to be
> written.
So I myself don't care one teeny tiny bit about out of tree code, they
get to
On Fri, 23 Mar 2018, sean.w...@mediatek.com wrote:
> From: Sean Wang
>
> Add a description for MT6323 RTC and link it to the detailed binding
> documentation.
>
> Signed-off-by: Sean Wang
> ---
> Documentation/devicetree/bindings/mfd/mt6397.txt
On Wed, Mar 28, 2018 at 11:14:50AM +0200, Martijn Coenen wrote:
> This can't happen with normal nodes (because you can't get a ref
> to a node you own), but it could happen with the context manager;
> to make the behavior consistent with regular nodes, reject
> transactions into the context
On Mon, Mar 26, 2018 at 10:29 PM, Masahiro Yamada
wrote:
> If the target compiler is GCC 4.8 or newer, plugins are compiled with
> HOSTCXX. Otherwise, gcc-plugin.sh will select HOSTCC or HOSTCXX.
>
> To simplify things, drop the HOSTCC support for plugins. If you
On Wed, Mar 28, 2018 at 11:06:54AM +0200, Martijn Coenen wrote:
> On Wed, Mar 28, 2018 at 10:19 AM, Greg KH wrote:
> > Does this need to go to older kernels as well?
>
> Yes, this should apply cleanly to 4.14 as well. It won't apply to
> pre-4.14 kernels because of
On Wed, Mar 28, 2018 at 12:10 AM, Rafael J. Wysocki wrote:
> On Tuesday, March 27, 2018 11:50:02 PM CEST Thomas Ilsche wrote:
>> On 2018-03-20 16:45, Rafael J. Wysocki wrote:
>> > From: Rafael J. Wysocki
>> >
>> > In order to address the issue with
On Wed, Mar 28, 2018 at 03:31:31PM +0900, Ji-Hun Kim wrote:
> There are no null pointer checking on rd_info and td_info values which
> are allocated by kzalloc. It has potential null pointer dereferencing
> issues. Add return when allocation is failed.
>
> Signed-off-by: Ji-Hun Kim
The iowait boosting code has been recently updated to add a progressive
boosting behavior which allows to be less aggressive in boosting tasks
doing only sporadic IO operations, thus being more energy efficient for
example on mobile platforms.
The current code is now however a bit convoluted.
On Wed, Mar 28, 2018 at 10:19 AM, Greg KH wrote:
> Does this need to go to older kernels as well?
Yes, this should apply cleanly to 4.14 as well. It won't apply to
pre-4.14 kernels because of the fine-grained locking changes, but the
same issue exists there and I
On Wed, Mar 28, 2018 at 08:51:35AM +1100, Benjamin Herrenschmidt wrote:
> On Tue, 2018-03-27 at 15:13 +0200, Andrea Parri wrote:
> > >
> > > So unless it's very performance sensitive, I'd rather have things like
> > > spin_is_locked be conservative by default and provide simpler ordering
> > >
Oops, I should reply this thread. Forget about the reply on another thread.
On Sun, Mar 25, 2018 at 08:02:15PM -0700, Jia He wrote:
>Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
>where possible") optimized the loop in memmap_init_zone(). But it causes
>possible panic
Hi!
> > > I can talk to the modem and start a call.
> >
> > Doing an AT query is the easy part :)
> >
> > > Then something like this (untested!) is certainly needed.
> > > Probably more...
> >
> > I intentionally left this part out. The CPCAP codec has two DAIs
> > and not 3+. The code you
Removes "#ifndef queued_spin_is_locked" from the generic code: this is
not used _and_ it is reasonable to conclude that it'll never be.
Also removes the comment about spin_is_locked() from mutex_is_locked():
it remains valid, but not particularly useful.
Suggested-by: Will Deacon
Commit 51d7d5205d338 ("powerpc: Add smp_mb() to arch_spin_is_locked()")
added an smp_mb() to arch_spin_is_locked(), in order to ensure that
Thread 0Thread 1
spin_lock(A); spin_lock(B);
r0 = spin_is_locked(B) r1 =
On Tue, Mar 27, 2018 at 06:27:04PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.125 release.
> There are 43 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
On Wed, 28 Mar 2018, Laurent Dufour wrote:
> >> @@ -2913,7 +2921,8 @@ int do_swap_page(struct vm_fault *vmf)
> >>int exclusive = 0;
> >>int ret = 0;
> >
> > Initialization is now unneeded.
>
> I'm sorry, what "initialization" are you talking about here ?
>
The initialization of the
On 2018-03-23 16:40:57 [+0100], To linux-rt-us...@vger.kernel.org wrote:
while this seems to work I am not quite happy with it and looking into
alternatives…
Sebastian
On Tue, 20 Mar 2018, Enric Balletbo i Serra wrote:
> With this patch, the cros_ec_ctl driver will register the legacy
> accelerometer driver (named cros_ec_accel_legacy) if it fails to
> register sensors through the usual path cros_ec_sensors_register().
> This legacy device is present on
On Wed, Mar 28, 2018 at 01:30:20PM +0300, Kirill Tkhai wrote:
> On 27.03.2018 18:48, Vladimir Davydov wrote:
> > On Tue, Mar 27, 2018 at 06:09:20PM +0300, Kirill Tkhai wrote:
> >> diff --git a/mm/vmscan.c b/mm/vmscan.c
> >> index 8fcd9f8d7390..91b5120b924f 100644
> >> --- a/mm/vmscan.c
On Thu, 22 Mar 2018, Baolin Wang wrote:
> There are some global registers in Spreadtrum sc27xx PMICs, which will
> be accessed by other drivers. So this patch adds one syscon cell to
> help to access the PMIC's global registers.
>
> Signed-off-by: Baolin Wang
> ---
>
On Mon, Mar 26, 2018 at 10:29 PM, Masahiro Yamada
wrote:
> As Documentation/kbuild/kconfig-language.txt notes, 'select' should be
> used with care - it forces a lower limit of another symbol, ignoring
> the dependency. In this case, KCOV can select GCC_PLUGINS even
Adds the designware EP device ID entry to pci_endpoint_test driver table
to allow this device to be recognize and handle by the pci_endpoint_test
driver.
Signed-off-by: Gustavo Pimentel
---
drivers/misc/pci_endpoint_test.c | 1 +
1 file changed, 1 insertion(+)
Looks good,
Reviewed-by: Christoph Hellwig
On 25/03/2018 23:50, David Rientjes wrote:
> On Tue, 13 Mar 2018, Laurent Dufour wrote:
>
>> When handling page fault without holding the mmap_sem the fetch of the
>> pte lock pointer and the locking will have to be done while ensuring
>> that the VMA is not touched in our back.
>>
>> So move the
Commit-ID: 9b9a51354cae933f5640b5bb73bbcd32f989122f
Gitweb: https://git.kernel.org/tip/9b9a51354cae933f5640b5bb73bbcd32f989122f
Author: Eric Dumazet
AuthorDate: Tue, 27 Mar 2018 20:22:33 -0700
Committer: Thomas Gleixner
CommitDate: Wed, 28 Mar
Commit-ID: 07344b15a994acadbe439aa4e75127ed1ccca099
Gitweb: https://git.kernel.org/tip/07344b15a994acadbe439aa4e75127ed1ccca099
Author: Tom Lendacky
AuthorDate: Tue, 27 Mar 2018 17:07:11 -0500
Committer: Thomas Gleixner
CommitDate: Wed, 28
Commit-ID: 151ad17fbe5e56afa59709f41980508672c777ce
Gitweb: https://git.kernel.org/tip/151ad17fbe5e56afa59709f41980508672c777ce
Author: Andrew Banman
AuthorDate: Tue, 27 Mar 2018 17:09:06 -0500
Committer: Thomas Gleixner
CommitDate: Wed, 28 Mar 2018
Call __stack_chk_guard_setup() in decompress_kernel() is too late that
stack checking always fails for decompress_kernel() itself. So remove
__stack_chk_guard_setup() and initialize __stack_chk_guard before we
call decompress_kernel().
Original code comes from ARM but also used for MIPS and SH,
Hi all,
Changes since 20180327:
The asm-generic tree gained conflicts against the kbuild tree.
The arm64 tree gained a conflict against the arm64-fixes tree.
The vfs tree still had its build failure for which I reverted a commit.
The kvm-arm tree gained conflicts against the arm64 tree.
The
When multiple cpus are related in one cpufreq policy, the first online
cpu will be chosen by default to handle cpufreq operations. Let's take
cpu0 and cpu1 as an example.
When cpu0 is offline, policy->cpu will be shifted to cpu1. Cpu1's should
be initialized. Otherwise, perf capabilities are 0s
Add UFS Protocol Information Units(upiu) trace events for ufs driver,
used to trace various ufs transaction types- command, task-management
and device management.
The trace-point format is generic and can be easily adapted to trace
other upius if needed.
Currently tracing ufs transaction of type
Add a new serial node for the Qualcomm BT controller QCA6174. This
allows automatic probing and hci registration through the serdev
framework instead of relying on the userspace helpers.
Signed-off-by: Thierry Escande
---
v6
- Move gpio properties into pinconf
On Mon, Mar 5, 2018 at 5:22 PM, Thang Q. Nguyen wrote:
> On Mon, Jan 29, 2018 at 5:24 PM, Thang Q. Nguyen wrote:
>> From: Tung Nguyen
>>
>> Currently, hcd->shared_hcd always creates and registers to the usb-core.
>> If, for some reasons,
On Fri, Mar 16, 2018 at 11:05:31AM -0700, Nathan Chancellor wrote:
> On Fri, Mar 16, 2018 at 04:22:32PM +0100, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.4.122 release.
> > There are 63 patches in this series, all will be posted as a response
> > to this
On Tue, Mar 27, 2018 at 08:22:33PM -0700, Eric Dumazet wrote:
> When changing rdmsr_safe_on_cpu() to schedule, I missed that
> __rdmsr_safe_on_cpu() was also used by rdmsrl_safe_on_cpu()
>
> Lets make rdmsrl_safe_on_cpu() a wrapper instead of copy/pasting
> the code I added for the completion
On Wed, 28 Mar 2018, Laurent Dufour wrote:
> >> This configuration variable will be used to build the code needed to
> >> handle speculative page fault.
> >>
> >> By default it is turned off, and activated depending on architecture
> >> support.
> >>
> >> Suggested-by: Thomas Gleixner
://github.com/0day-ci/linux/commits/Razvan-Stefanescu/staging-fsl-dpaa2-ethsw-Fix-TCI-values-overwrite/20180328-154703
config: i386-allmodconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All
On 2018-03-26 11:13:59 [-0400], Steven Rostedt wrote:
> > diff --git a/drivers/target/target_core_tmr.c
> > b/drivers/target/target_core_tmr.c
> > index 9c7bc1ca341a..3d35dad1de2c 100644
> > --- a/drivers/target/target_core_tmr.c
> > +++ b/drivers/target/target_core_tmr.c
>
> Can you add a
On 25/03/2018 23:50, David Rientjes wrote:
> On Tue, 13 Mar 2018, Laurent Dufour wrote:
>
>> From: Peter Zijlstra
>>
>> When speculating faults (without holding mmap_sem) we need to validate
>> that the vma against which we loaded pages is still valid when we're
>> ready to
On Tue, 27 Mar 2018, Matthias Brugger wrote:
>
>
> On 03/27/2018 10:05 AM, Lee Jones wrote:
> > On Fri, 23 Mar 2018, Dmitry Torokhov wrote:
> >> On Thu, Mar 22, 2018 at 10:17:53AM +0800, Sean Wang wrote:
> >>> Hi, Dmitry and Lee
> >>>
> >>> The series seems not being got merged. Are they good
101 - 200 of 1952 matches
Mail list logo