Hi Abhishek,
On Mon, 23 Apr 2018 11:58:42 +0530, Abhishek Sahu
wrote:
> On 2018-04-22 21:49, Miquel Raynal wrote:
> > Hi Abhishek,
> > > On Thu, 12 Apr 2018 12:36:42 +0530, Abhishek Sahu
> > wrote:
> > >> On 2018-04-10 15:14, Miquel Raynal wrote:
> >> > Hi Abhishek,
> >> > > On Wed, 4
On Sun, Apr 22, 2018 at 01:44:07PM -0700, Nathan Chancellor wrote:
> On Sun, Apr 22, 2018 at 03:52:38PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.4.129 release.
> > There are 97 patches in this series, all will be posted as a response
> > to this on
On Mon, Apr 23, 2018 at 12:02:08AM +0200, Thomas Gleixner wrote:
> There are a few bogus SPDX identifiers in various files and SPDX
> Identifiers used in tree or about to be used which have no corresponding
> License Text file in the LICENSES directory or use the new variant of the
> GPL-2.0[+] lic
On Mon, Apr 23, 2018 at 9:02 AM, syzbot
wrote:
> Hello,
>
> syzbot hit the following crash on upstream commit
> 83beed7b2b26f232d782127792dd0cd4362fdc41 (Fri Apr 20 17:56:32 2018 +)
> Merge branch 'fixes' of
> git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal
> syzbot da
On Mon, Apr 23, 2018 at 12:02:17AM +0200, Thomas Gleixner wrote:
> The infiniband code uses a variant of the OpenIB license. This license is
> BSD-2-Clause with the MIT disclaimer. The linux kernel uses this license
> extensively throughout the driver subsystem since 2005. Note that the
> OpenIB.or
On Mon, Apr 23, 2018 at 12:02:16AM +0200, Thomas Gleixner wrote:
> Add the full text of the CC-BY-SA-4.0 license to the kernel tree. It was
> copied directly from:
>
>https://spdx.org/licenses/CC-BY-SA-4.0.html#licenseText
>
> Signed-off-by: Thomas Gleixner
As we only have 1 user of th
On Mon, Apr 23, 2018 at 12:02:12AM +0200, Thomas Gleixner wrote:
> Quite some files have been flagged with the new GPL-2.0-only and
> GPL-2.0-or-later identifiers which replace the original GPL-2.0 and
> GPL-2.0+ identifiers in the SPDX license identifier specification, but the
> identifiers are no
* valdis.kletni...@vt.edu wrote:
> Seeing these warnings. 'diff' tells me that the files
> are in fact significantly different.
>
> Warning: Kernel ABI header at 'tools/include/uapi/linux/kvm.h' differs from
> latest version at 'include/uapi/linux/kvm.h'
> Warning: Kernel ABI header at 'tools
On 2018-04-23 00:02, Thomas Gleixner wrote:
> GPL2.0 is not a valid SPDX identiier. Replace it with GPL-2.0.
>
> Fixes: 4a362601baa6 ("x86/jailhouse: Add infrastructure for running in
> non-root cell")
> Signed-off-by: Thomas Gleixner
> Cc: Jan Kiszka
> ---
> arch/x86/include/asm/jailhouse_par
On Mon, Apr 23, 2018 at 12:02:15AM +0200, Thomas Gleixner wrote:
> Add the full text of the Apache License version 2 to the kernel tree. It
> was copied directly from:
>
>https://spdx.org/licenses/Apache-2.0.html#licenseText
>
> Signed-off-by: Thomas Gleixner
Ugh, blame Android for thi
On Mon, Apr 23, 2018 at 12:02:14AM +0200, Thomas Gleixner wrote:
> Add the full text of the CDDL-1.0 to the kernel tree. It was copied directly
> from:
>
>https://spdx.org/licenses/CDDL-1.0.html#licenseText
>
> Signed-off-by: Thomas Gleixner
Reviewed-by: Greg Kroah-Hartman
On Mon, Apr 23, 2018 at 12:02:13AM +0200, Thomas Gleixner wrote:
> Add the full text of the X11 to the kernel tree. It was copied directly
> from:
>
>https://spdx.org/licenses/X11.html#licenseText
>
> Signed-off-by: Thomas Gleixner
Reviewed-by: Greg Kroah-Hartman
2018-04-20 16:03 GMT+08:00 Christoph Hellwig :
> Switch to the generic noncoherent direct mapping implementation.
>
> This makes sure kmap_atomic_pfn is consistently used for access to
> virtual addresses instead of either using the slower plain kmap
> or blindly expecting page_address() to work.
>
On 20 April 2018 at 17:53, Eugeniy Paltsev wrote:
> Hi Ulf,
>
> On Fri, 2018-04-20 at 09:35 +0200, Ulf Hansson wrote:
>> [...]
>>
>> >
>> > 2. Add missing stuff to support multislot mode in DesignWare MMC driver.
>> > * Add missing slot switch to __dw_mci_start_request() function.
>> > * Refacto
On Mon, Apr 23, 2018 at 1:07 AM, Linus Walleij wrote:
> Instead of passing a global GPIO number, pass a descriptor looked
> up from the device tree configuration node.
>
> Cc: Chanwoo Choi
> Cc: Krzysztof Kozlowski
> Cc: Bartlomiej Zolnierkiewicz
> Signed-off-by: Linus Walleij
> ---
> ChangeLo
On 2018-04-22 22:04, Miquel Raynal wrote:
Hi Abhishek,
On Thu, 12 Apr 2018 15:29:48 +0530, Abhishek Sahu
wrote:
On 2018-04-10 13:37, Boris Brezillon wrote:
> On Tue, 10 Apr 2018 09:55:58 +0200
> Miquel Raynal wrote:
> >> > Hi Abhishek,
>> >
>> > On Tue, 10 Apr 2018 11:39:35 +0530, Abhishek S
On Fri, 20 Apr 2018, Dan Carpenter wrote:
> The COMP1 and COMP2 elements are in 0 and 1 respectively so this code is
> accessing the wrong elements and one space beyond the end of the array.
> We should be using "id - 1" instead.
>
> The "id" variable is never COMP (0) so that code can be removed
On Monday 16 April 2018 09:49 PM, Sylwester Nawrocki wrote:
> There is no functional change, just replacing regmap_read()/modify/
> regmap_write() with regmap_update_bits() function calls.
merged, thanks!
-Kishon
>
> Signed-off-by: Sylwester Nawrocki
> ---
> drivers/phy/samsung/phy-exynos-m
On Tue, Apr 17, 2018 at 04:33:14PM +0200, Laurent Dufour wrote:
> From: Peter Zijlstra
>
> Wrap the VMA modifications (vma_adjust/unmap_page_range) with sequence
> counts such that we can easily test if a VMA is changed.
So, seqcount is to protect modifying all attributes of vma?
>
> The unmap
From: Sean Wang
Similar to the readx_poll_timeout() macro calling ktime_* and using
ktime_t type, which is declared in . So, make
include/linux/regmap.h explicitly include , like
include/linux/iopoll.h does. Otherwise, users of the macro will see
below errors.
error: implicit declaration of fun
On Sunday 25 March 2018 04:08 AM, Alban Bedel wrote:
> The ATH79 USB phy is very simple, it only have a reset. On some SoC a
> second reset is used to force the phy in suspend mode regardless of the
> USB controller status.
>
> This driver is added to the qualcom directory as atheros is now part
On Tuesday 20 March 2018 11:31 AM, Manu Gautam wrote:
> phy_init() and phy_exit() calls, and phy_power_on() and
> phy_power_off() already accept NULL as valid PHY reference
> and act as NOP. Extend same concept to phy runtime_pm APIs
> to keep drivers (e.g. dwc3) code simple while dealing with
>
From: Sean Wang
Reuse the common helpers regmap_read_poll_timeout provided by Linux core
instead of an open-coded handling.
v1 -> v2:
- use macro definitions MTK_POLL_DELAY_US and MTK_POLL_TIMEOUT for
arguments sleep_us and timeout_us passing in regmap_read_poll_timeout.
- remove unnecessar
On 04/18/2018 06:15 PM, Oleksandr Andrushchenko wrote:
On 04/16/2018 09:24 AM, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko
Please note: this patch series depends on [3].
The dependency is now merged into Xen kernel tree [4] for-linus-4.17
The dependency is now pulled into Li
Add usb otg support for bananapi-m64 board,
- USB-ID connected with PH9
- USB-DRVVBUS controlled by N_VBUSEN pin from PMIC
Signed-off-by: Jagan Teki
Reviewed-by: Chen-Yu Tsai
---
Changes for v6:
- Rebase on master
Changes for v5:
- Kept reg_drivevbus node in alphabetical order.
- Collect Chen-Y
Like axp221, axp223, axp813 the axp803 is also supporting external
regulator to drive the OTG VBus through N_VBUSEN PMIC pin.
Add support for it.
Signed-off-by: Jagan Teki
Reviewed-by: Rob Herring
Reviewed-by: Chen-Yu Tsai
---
Changes for v6:
- Rebase on master
Changes for v5:
- Collect Chen
Add reg_drivevbus regualtor for boards which are using
external regulator to drive the OTG VBus through N_VBUSEN
PMIC pin.
Signed-off-by: Jagan Teki
Reviewed-by: Chen-Yu Tsai
---
Changes for v6:
- Rebase on master
Changes for v5:
- Collect Chen-Yu reviewed-by tag
Changes for v4:
- rebase on mas
On Tue, Apr 17, 2018 at 04:33:12PM +0200, Laurent Dufour wrote:
> pte_unmap_same() is making the assumption that the page table are still
> around because the mmap_sem is held.
> This is no more the case when running a speculative page fault and
> additional check must be made to ensure that the fi
On 2018-04-22 21:55, Miquel Raynal wrote:
Hi Abhishek,
On Thu, 12 Apr 2018 12:24:16 +0530, Abhishek Sahu
wrote:
On 2018-04-10 14:42, Miquel Raynal wrote:
> Hi Abhishek,
> > On Wed, 4 Apr 2018 18:12:20 +0530, Abhishek Sahu
> wrote:
> >> parse_read_errors can be called with only oob buf also
On 2018-04-22 21:49, Miquel Raynal wrote:
Hi Abhishek,
On Thu, 12 Apr 2018 12:36:42 +0530, Abhishek Sahu
wrote:
On 2018-04-10 15:14, Miquel Raynal wrote:
> Hi Abhishek,
> > On Wed, 4 Apr 2018 18:12:24 +0530, Abhishek Sahu
> wrote:
> >> This patch does minor code reorganization for raw reads
On Fri, 20 Apr 2018, Dan Carpenter wrote:
> On Fri, Apr 20, 2018 at 09:39:09AM +0100, Lee Jones wrote:
> > On Fri, 20 Apr 2018, Dan Carpenter wrote:
> >
> > > On Fri, Apr 20, 2018 at 09:09:43AM +0100, Lee Jones wrote:
> > > > On Thu, 19 Apr 2018, Dan Carpenter wrote:
> > > >
> > > > > The tps_co
On Sat, 2018-04-21 at 11:54 +0300, Kalle Valo wrote:
> Joey Pabalinas writes:
>
> > On Sat, Apr 21, 2018 at 10:50:51AM +0300, Kalle Valo wrote:
> > > Is there any way to fix it? With ath10k I use sparse a lot and
> > > because
> > > of these warnings sparse is now very annoying to use.
> >
> > I
On 22.04.2018 17:37, Tony Krowiak wrote:
> Introduces a new function to reset the crypto attributes for all
> vcpus whether they are running or not. Each vcpu in KVM will
> be removed from SIE prior to resetting the crypto attributes in its
> SIE state description. After all vcpus have had their cr
[haaa, I finally found time to read more of these]
On Sat, Mar 10, 2018 at 10:17:47AM -0800, Andiry Xu wrote:
> From: Andiry Xu
>
> These routines are incomplete and currently only support reserved inodes,
> whose addresses are fixed. This is necessary for fill_super to work.
> File/dir operatio
On 4/12/2018 8:38 PM, Miklos Szeredi wrote:
Implement FS_IOC_GETFLAGS and FS_IOC_SETFLAGS.
Needs vfs_ioctl() exported to modules.
Do you think if it is better to separate out ovl implementation and
export of vfs_ioctl method ?
Probably there are other users which should be using vfs_ioctl met
On Sun, 22 Apr 2018 21:06:04 -0400 (EDT)
David Miller wrote:
> From: Ahmed Abdelsalam
> Date: Fri, 20 Apr 2018 15:58:05 +0200
>
> > In case of seg6 in encap mode, seg6_do_srh_encap() calls set_tun_src()
> > in order to set the src addr of outer IPv6 header.
> >
> > The net_device is required f
Hi Wolfram,
On 21.4.2018 18:23, Wolfram Sang wrote:
> Hi Michal,
>
> Thanks for the reviews!
>
>> There are two more occurences in this gpio-zynq driver.
>> zynq_gpio_resume, zynq_gpio_suspend. It wasn't detected because these
>> two lines are not together. But the same change can be applied for
Hi Lukasz,
On 04/23/2018 12:31 AM, Lukasz Majewski wrote:
> From: Stanislav Meduna
>
> On a TQMa53 module the mmc_sleep leaves the eMMC card in a state
> that the imx53 rom boot code is unable to probe, resulting in
> reboot hanging. Add a device tree property to disable sleeping
> on suspend.
>
On Sun, Apr 22, 2018 at 10:54:23PM +0100, Ben Hutchings wrote:
> > offset = blk - group_first_block;
> > - if (!ext4_test_bit(EXT4_B2C(sbi, offset), bh->b_data))
> > + if (offset < 0 || EXT4_B2C(sbi, offset) >= sb->s_blocksize ||
> > + !ext4_test_bit(EXT4_B2C(sbi, offset), bh->b_data)
This patch adds to check return value of calloc in write_superblock().
Signed-off-by: Chao Yu
---
fsck/mount.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fsck/mount.c b/fsck/mount.c
index 7e936dc056e5..badbe639742e 100644
--- a/fsck/mount.c
+++ b/fsck/mount.c
@@ -2155,6 +2155,7 @@ void
Hi Laurent,
I guess it's good timing to review. Guess LSF/MM goes so might change
a lot since then. :) Anyway, I grap a time to review.
On Tue, Apr 17, 2018 at 04:33:07PM +0200, Laurent Dufour wrote:
> This configuration variable will be used to build the code needed to
> handle speculative page
Seeing these warnings. 'diff' tells me that the files
are in fact significantly different.
Warning: Kernel ABI header at 'tools/include/uapi/linux/kvm.h' differs from
latest version at 'include/uapi/linux/kvm.h'
Warning: Kernel ABI header at 'tools/include/uapi/linux/prctl.h' differs from
lates
On Sun, Apr 22, 2018 at 11:14:10AM +0200, Wolfram Sang wrote:
> We should get drvdata from struct device directly. Going via
> platform_device is an unneeded step back and forth.
>
> Signed-off-by: Wolfram Sang
Acked-by: Ludovic Desroches
Thanks
> ---
>
> Build tested only. buildbot is happy.
On Sun, Apr 22, 2018 at 11:14:09AM +0200, Wolfram Sang wrote:
> We should get drvdata from struct device directly. Going via
> platform_device is an unneeded step back and forth.
>
> Signed-off-by: Wolfram Sang
Acked-by: Ludovic Desroches
Thanks
> ---
>
> Build tested only. buildbot is happy.
On Fri, 20 Apr 2018 09:38:04 -0500
"Eric W. Biederman" wrote:
> Filling in struct siginfo before calling force_sig_info a tedious and
> error prone process, where once in a great while the wrong fields
> are filled out, and siginfo has been inconsistently cleared.
>
> Simplify this process by us
On 2018年04月01日 22:12, Tiwei Bie wrote:
Hello everyone,
This RFC implements packed ring support for virtio driver.
The code was tested with DPDK vhost (testpmd/vhost-PMD) implemented
by Jens at http://dpdk.org/ml/archives/dev/2018-January/089417.html
Minor changes are needed for the vhost code
We assumes used ring update is the only user for vhost_put_user() in
the past. This may not be the case for the incoming packed ring which
may update the descriptor ring for used. So introduce a new type
parameter.
Signed-off-by: Jason Wang
---
drivers/vhost/vhost.c | 14 +++---
1 file c
We used to return descriptor head by vhost_get_vq_desc() to device and
pass it back to vhost_add_used() and its friends. This exposes the
internal used ring layout to device which makes it hard to be extended for
e.g packed ring layout.
So this patch tries to hide the used ring layout by
- lettin
Two helpers of setting/getting used len were introduced to avoid
explicitly manipulating vhost_used_elem in zerocopy code. This will be
used to hide used_elem internals and simplify packed ring
implementation.
Signed-off-by: Jason Wang
---
drivers/vhost/net.c | 11 +--
drivers/vhost/vh
Signed-off-by: Jason Wang
---
include/uapi/linux/virtio_config.h | 9 +
include/uapi/linux/virtio_ring.h | 13 +
2 files changed, 22 insertions(+)
diff --git a/include/uapi/linux/virtio_config.h
b/include/uapi/linux/virtio_config.h
index 308e209..5903d51 100644
--- a/incl
This patch introduces basic support for event suppression aka driver
and device area.
Signed-off-by: Jason Wang
---
drivers/vhost/vhost.c| 170 ---
drivers/vhost/vhost.h| 10 ++-
include/uapi/linux/virtio_ring.h | 19 +
3 files ch
Signed-off-by: Jason Wang
---
drivers/vhost/net.c | 3 +-
drivers/vhost/vhost.c | 535 ++
drivers/vhost/vhost.h | 8 +-
3 files changed, 509 insertions(+), 37 deletions(-)
diff --git a/drivers/vhost/net.c b/drivers/vhost/net.c
index 30273ad..
On (01/23/18 07:43), Tejun Heo wrote:
> >
> > We can have more. But if printk is causing printks, that's a major bug.
> > And work queues are not going to fix it, it will just spread out the
> > pain. Have it be 100 printks, it needs to be fixed if it is happening.
> > And having all printks just
Move get_rx_bufs() to vhost.c and rename it to
vhost_get_rx_bufs(). This helps to hide vring internal layout from
specific device implementation. Packed ring implementation will
benefit from this.
Signed-off-by: Jason Wang
---
drivers/vhost/net.c | 83 ++
Hi all:
This RFC implement packed ring layout. The code were tested with
Tiwei's RFC V2 a thttps://lkml.org/lkml/2018/4/1/48. Some fixups and
tweaks were needed on top of Tiwei's code to make it run. TCP stream
and pktgen does not show obvious difference compared with split ring.
Changes from V2:
Instead of depending on the exported vring_used_elem, this patch
switches to use a new internal structure vhost_used_elem which embed
vring_used_elem in itself. This could be used to let vhost to record
extra metadata for the incoming packed ring layout.
Signed-off-by: Jason Wang
---
drivers/vho
Hi Souptick,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.17-rc2 next-20180420]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
Hi Guenter,
Commit
bcafe0ea7e4f ("hwmon: MC13783: Add uid and die temperature sensor inputs")
is missing a Signed-off-by from its committer. It was rebased since
yesterday.
--
Cheers,
Stephen Rothwell
pgplr3KQaJ9HR.pgp
Description: OpenPGP digital signature
On (04/20/18 11:12), Petr Mladek wrote:
[..]
> Will 1000 lines within 1 hour be enough for you, please?
I'm afraid it won't.
> I am lost. In the mail
[..]
> My understanding of the older mail is that you called
> console_drivers() in printk_safe() context only because it was
> easier to disable p
Hi all,
Changes since 20180420:
The usb tree gained a conflict against the usb.current tree.
Non-merge commits (relative to Linus' tree): 1418
1459 files changed, 55564 insertions(+), 22829 deletions(-)
I have create
On Tue, Apr 17, 2018 at 12:28:52PM +, Radhey Shyam Pandey wrote:
> > > + if ((seg->hw.status & XILINX_DMA_COMP_MASK) ||
> > > + (!chan->xdev->has_axieth_connected)) {
> >
> > why the second case ? That is not expalined in log?
> In the current implementation, delay tim
Hi,
May I know when this patch would be taken for merging?
On Sat, Apr 7, 2018 at 9:58 AM, Chandan Vn wrote:
> On Fri, Apr 6, 2018 at 9:47 PM, Laura Abbott wrote:
>> Does this have an impact on anything besides accounting
>> in memblock?
>
> Yes, the impact is only on accounting or debugging.
On 2018-04-22 21:06, Mark Rutland wrote:
> On Sun, Apr 22, 2018 at 12:47:57PM +0200, Jan Kiszka wrote:
>> Hi,
>>
>> this can be triggered simply by running
>>
>> # echo 0 > /sys/devices/system/cpu/cpu3/online
>> # echo 1 > /sys/devices/system/cpu/cpu3/online
>>
>> [ 455.904854]
>> ===
Since tmpfs THP was supported in 4.8, hugetlbfs is not the only
filesystem with huge page support anymore. tmpfs can use huge page via
THP when mounting by "huge=" mount option.
When applications use huge page on hugetlbfs, it just need check the
filesystem magic number, but it is not enough for t
On 20-04-18, 09:50, Florian Fainelli wrote:
> On 04/20/2018 02:35 AM, Viresh Kumar wrote:
> > On 20-04-18, 10:15, Sudeep Holla wrote:
> >> It still doesn't give the flexibility to switch between the two
> >> implementations boot time based on some firmware config(e.g. DT status
> >> property).
> >
On 04/22/2018 05:09 PM, Michal Hocko wrote:
> On Mon 16-04-18 19:09:14, Mike Kravetz wrote:
> [...]
>> @@ -2010,9 +2011,13 @@ static __always_inline struct page
>> *__rmqueue_cma_fallback(struct zone *zone,
>> {
>> return __rmqueue_smallest(zone, order, MIGRATE_CMA);
>> }
>> +#define contig
On 22 April 2018 at 23:00, Dmitry Vyukov wrote:
> On Sun, Apr 22, 2018 at 2:51 PM, Michal Hocko wrote:
>> On Fri 20-04-18 18:50:24, Catalin Marinas wrote:
>>> On Sat, Apr 21, 2018 at 12:58:33AM +0800, Chunyu Hu wrote:
>>> > __GFP_NORETRY and __GFP_NOFAIL are combined in gfp_kmemleak_mask now.
>>
Add MAX7322 IO expander support.
Signed-off-by: Anson Huang
---
arch/arm/boot/dts/imx6sx-sabreauto.dts | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/imx6sx-sabreauto.dts
b/arch/arm/boot/dts/imx6sx-sabreauto.dts
index 2caca934..d59084f 100644
--- a/arch/arm/boot/dt
i.MX6SX Sabre Auto board has GPIO1_IO13 pin can be
MUXed as WDOG output to reset PMIC, add this function
support.
Signed-off-by: Anson Huang
---
arch/arm/boot/dts/imx6sx-sabreauto.dts | 12
1 file changed, 12 insertions(+)
diff --git a/arch/arm/boot/dts/imx6sx-sabreauto.dts
b/arch
Add FEC support on i.MX6SX Sabre Auto board.
Signed-off-by: Anson Huang
---
arch/arm/boot/dts/imx6sx-sabreauto.dts | 70 ++
1 file changed, 70 insertions(+)
diff --git a/arch/arm/boot/dts/imx6sx-sabreauto.dts
b/arch/arm/boot/dts/imx6sx-sabreauto.dts
index 812f40
i.MX6SX Sabre Auto board has two max7310 IO expander
on I2C3 bus, add support for them.
Signed-off-by: Anson Huang
---
arch/arm/boot/dts/imx6sx-sabreauto.dts | 28
1 file changed, 28 insertions(+)
diff --git a/arch/arm/boot/dts/imx6sx-sabreauto.dts
b/arch/arm/boot/
Add pfuze100 support on i.MX6SX Sabre Auto board.
Signed-off-by: Anson Huang
---
arch/arm/boot/dts/imx6sx-sabreauto.dts | 117 +
1 file changed, 117 insertions(+)
diff --git a/arch/arm/boot/dts/imx6sx-sabreauto.dts
b/arch/arm/boot/dts/imx6sx-sabreauto.dts
index
Hi David,
On 04/19/18 06:31, David Howells wrote:
> Introduce a filesystem context concept to be used during superblock
> creation for mount and superblock reconfiguration for remount. This is
> allocated at the beginning of the mount procedure and into it is placed:
>
> (1) Filesystem type.
>
On 21 April 2018 at 01:50, Catalin Marinas wrote:
> On Sat, Apr 21, 2018 at 12:58:33AM +0800, Chunyu Hu wrote:
>> __GFP_NORETRY and __GFP_NOFAIL are combined in gfp_kmemleak_mask now.
>> But it's a wrong combination. As __GFP_NOFAIL is blockable, but
>> __GFP_NORETY is not blockable, make it self
On 4/22/18 6:47 PM, Michal Hocko wrote:
On Sat 21-04-18 00:33:59, Yang Shi wrote:
Since tmpfs THP was supported in 4.8, hugetlbfs is not the only
filesystem with huge page support anymore. tmpfs can use huge page via
THP when mounting by "huge=" mount option.
When applications use huge page o
On Sun, Apr 22, 2018 at 06:14:18PM -0700, Joel Fernandes wrote:
> On Fri, Apr 20, 2018 at 12:07 AM, Joel Fernandes wrote:
> > Hi,
> >
> > Thanks Matsami and Namhyung for the suggestions!
> >
> > On Wed, Apr 18, 2018 at 10:43 PM, Namhyung Kim wrote:
> >> On Wed, Apr 18, 2018 at 06:02:50PM +0900, M
With the addition of the end-of-test state, it is not uncommon for the
kvm.sh summary lines to overflow 80 characters. This commit therefore
applies abbreviations in order to make the line fit into 80 characters
with high probability.
And yes, I did make heavy use of punched cards back in the day
Currently, kvm-find-errors.sh looks only for build errors ("error:"),
so this commit makes it also locate build warnings ("warning:").
Signed-off-by: Paul E. McKenney
---
tools/testing/selftests/rcutorture/bin/kvm-find-errors.sh | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --
This commit adds a script that allows viewing the build and/or
console output from failed rcutorture, locktorture, or rcuperf runs.
This replaces a time-honored but inefficient manual procedure that uses
cut and paste.
Signed-off-by: Paul E. McKenney
---
.../selftests/rcutorture/bin/kvm-find-err
This commit adds the end-of-test test, if present in the console output,
to the kvm.sh test summary that is printed by kvm-recheck.sh. Note that
this only applies to rcutorture console output.
Signed-off-by: Paul E. McKenney
---
tools/testing/selftests/rcutorture/bin/kvm-recheck-rcu.sh | 8
The rcutorture scripting scans the console output twice, once to look
for various sorts of hangs and again to find warnings and panics.
Unfortunately, only the output of the second scan gets written to the
console.log.diags file, which can cause hangs to be overlooked.
This commit therefore folds t
This commit adds end-of-test state printout to help check whether RCU
shut down nicely. Note that this printout only helps for flavors of
RCU that are not used much by the kernel. In particular, for normal
RCU having a grace period in progress is expected behavior.
Signed-off-by: Paul E. McKenne
Hello!
This series contains torture-test updates:
1. Add a script to edit output from failed runs. Running this
script takes your editor through the build errors and the various
problems in the console output, for each such file, first showing
a summary of the errors
The __rcu_process_callbacks() function currently checks to see if
the current CPU needs a grace period and also if there is any other
reason to kick off a new grace period. This is one of the fail-safe
checks that has been rendered unnecessary by the changes that increase
the accuracy of rcu_gp_cl
The rcu_start_future_gp() function uses a sloppy check for a grace
period being in progress, which works today because there are a number
of code sequences that resolve the resulting races. However, some of
these race-resolution code sequences must acquire the root rcu_node
structure's ->lock, and
Hi Greg,
Today's linux-next merge of the usb tree got a conflict in:
drivers/usb/core/hcd.c
between commit:
63cb03f5c11e ("usb: core: split usb_phy_roothub_{init,alloc}")
from the usb.current tree and commit:
bc40f5341741 ("USB: core: hcd: drop support for legacy phys")
from the usb tr
The rcu_migrate_callbacks() function invokes rcu_advance_cbs()
twice, ignoring the return value. This is OK at pressent because of
failsafe code that does the wakeup when needed. However, this failsafe
code acquires the root rcu_node structure's lock frequently, while
rcu_migrate_callbacks() does
There is no longer any need for ->need_future_gp[] to count the number of
requests for future grace periods, so this commit converts the additions
to assignments to "true" and reduces the size of each element to one byte.
While we are in the area, fix an obsolete comment.
Signed-off-by: Paul E. Mc
Accessors for the ->need_future_gp[] array are currently open-coded,
which makes them difficult to change. To improve maintainability, this
commit adds need_future_gp_mask() to compute the indexing mask from the
array size, need_future_gp_element() to access the element corresponding
to the specif
Currently, the rcu_future_needs_gp() function checks only the current
element of the ->need_future_gps[] array, which might miss elements that
were offset from the expected element, for example, due to races with
the start or the end of a grace period. This commit therefore makes
rcu_future_needs_
The rcu_start_gp_advanced() is invoked only from rcu_start_future_gp() and
much of its code is redundant when invoked from that context. This commit
therefore inlines rcu_start_gp_advanced() into rcu_start_future_gp(),
then removes rcu_start_gp_advanced().
Signed-off-by: Paul E. McKenney
---
ke
Currently, rcu_gp_cleanup() scans the rcu_node tree in order to reset
state to reflect the end of the grace period. It also checks to see
whether a new grace period is needed, but in a number of cases, rather
than directly cause the new grace period to be immediately started, it
instead leaves the
When rcu_cbs_completed() is invoked on a non-root rcu_node structure,
it unconditionally assumes that two grace periods must complete before
the callbacks at hand can be invoked. This is overly conservative because
if that non-root rcu_node structure believes that no grace period is in
progress, a
It is true that currently only the low-order two bits are used, so
there should be no problem given modern machines and compilers, but
good hygiene and maintainability dictates use of an unsigned long
instead of an int. This commit therefore makes this change.
Signed-off-by: Paul E. McKenney
---
Once the grace period has ended, any RCU_GP_FLAG_FQS requests are
irrelevant: The grace period has ended, so there is no longer any
point in forcing quiescent states in order to try to make it end sooner.
This commit therefore causes rcu_gp_cleanup() to clear any bits other
than RCU_GP_FLAG_INIT f
On Fri, Apr 06, 2018 at 03:07:11AM +, Naoya Horiguchi wrote:
> Subject: [PATCH] mm: enable thp migration for shmem thp
This patch is buggy, but not in a significant way:
> @@ -524,13 +524,26 @@ int migrate_page_move_mapping(struct address_space
> *mapping,
> }
>
> radix_tree_re
All of the cpu_needs_another_gp() function's checks (except for
newly arrived callbacks) have been subsumed into the rcu_gp_cleanup()
function's scan of the rcu_node tree. This commit therefore drops the
call to cpu_needs_another_gp(). The check for newly arrived callbacks
is supplied by rcu_acce
Now that grace-period requests use funnel locking and now that they
set ->gp_flags to RCU_GP_FLAG_INIT even when the RCU grace-period
kthread has not yet started, rcu_gp_kthread() no longer needs to check
need_any_future_gp() at startup time. This commit therefore removes
this check.
Signed-off-b
If rcu_start_this_gp() is invoked with a requested grace period more
than three in the future, then either the ->need_future_gp[] array
needs to be bigger or the caller needs to be repaired. This commit
therefore adds a WARN_ON_ONCE() checking for this condition.
Signed-off-by: Paul E. McKenney
The rcu_cbs_completed() function provides the value of ->completed
at which new callbacks can safely be invoked. This is recorded in
two-element ->need_future_gp[] arrays in the rcu_node structure, and
the elements of these arrays corresponding to the just-completed grace
period are zeroed at the
1 - 100 of 922 matches
Mail list logo