Remove the regulators node and define fixed regulators directly under
the root node. This makes Exynos5250 Arndale board consistent with
other Exynos boards.
Suggested-by: Marek Szyprowski
Signed-off-by: Krzysztof Kozlowski
---
Changes since v1:
1. New patch
---
arch/arm/boot/dts/exynos5250-
There is no need to keep DMA controller nodes under AMBA bus node.
Remove the "amba" node to fix dtschema warnings like:
amba: $nodename:0: 'amba' does not match
'^(bus|soc|axi|ahb|apb)(@[0-9a-f]+)?$'
Signed-off-by: Krzysztof Kozlowski
---
Changes since v1:
1. Remove the bus, as suggested
o bio_list[1] in a totally
> undocumented way. But even with that the problem should only show
> up with "block: shortcut __submit_bio_noacct for blk-mq drivers".
>
> Can you try this patch?
Applied your patch on top of linux-next 20200702 and tested on
arm64 and x86_64 devices an
On Thu, Jul 02, 2020 at 01:54:00AM -0700, Danny Lin wrote:
> A recent LLVM 11 commit [1] made LLD stop implicitly coalescing some
> temporary LLVM sections, namely .{data,bss}..compoundliteral.XXX:
>
> [30] .data..compoundli PROGBITS 9ac9a000 19e9a000
>cea0
On Thu, 2 Jul 2020 at 21:19, Roman Gushchin wrote:
>
> On Thu, Jul 02, 2020 at 12:22:03PM +0530, Naresh Kamboju wrote:
> > On Thu, 2 Jul 2020 at 00:16, Roman Gushchin wrote:
> > >
> > > On Wed, Jul 01, 2020 at 10:29:04AM +0200, Michal Hocko wrote:
> > > > Smells like a different observable proble
Allow padata_do_multithreaded function to be called after bootstrap.
v2: removed __init from padata_work_alloc_mt and padata_works_free
Signed-off-by: Nico Pache
---
include/linux/padata.h | 2 +-
kernel/padata.c| 10 +-
2 files changed, 6 insertions(+), 6 deletions(-)
diff --
On Wed, Jul 01, 2020 at 09:29:38PM -0700, Florian Fainelli wrote:
> Hi all,
>
> This patch series untangles the ethtool netlink dependency with PHYLIB
> which exists because the cable test feature calls directly into PHY
> library functions. The approach taken here is to utilize a new set of
> net
On Thu, Jul 02, 2020 at 10:19:40AM +0200, Arnd Bergmann wrote:
> On Wed, Jul 1, 2020 at 11:54 PM 'Nick Desaulniers' via Clang Built
> Linux wrote:
> >
> > Hi Arnd,
> > I usually wait longer to bump threads for review, but we have a
> > holiday in the US so we're off tomorrow and Friday.
> > script
On 02/07/20 16:32, Frederic Weisbecker wrote:
> On Thu, Jul 02, 2020 at 11:59:59AM +0200, Juri Lelli wrote:
> > On 02/07/20 01:20, Frederic Weisbecker wrote:
> > > On Wed, Jul 01, 2020 at 06:35:04PM +0200, Juri Lelli wrote:
> > > > Guess you might be faster to understand what I'm missing. :-)
> > >
On Wed, 1 Jul 2020 at 13:49, Michal Hocko wrote:
>
> On Wed 01-07-20 13:24:54, Naresh Kamboju wrote:
> > While running LTP mm test suite on arm64 Juno device the kernel panic
> > noticed on linux-next 20200630 tag.
>
> Can you try to bisect? The new memcg slab allocator series sounds like a
> pote
On Thu, Jul 02, 2020 at 09:25:08PM +0530, Naresh Kamboju wrote:
> On Thu, 2 Jul 2020 at 21:19, Roman Gushchin wrote:
> >
> > On Thu, Jul 02, 2020 at 12:22:03PM +0530, Naresh Kamboju wrote:
> > > On Thu, 2 Jul 2020 at 00:16, Roman Gushchin wrote:
> > > >
> > > > On Wed, Jul 01, 2020 at 10:29:04AM
On 7/2/20 6:18 AM, Mark Brown wrote:
On Wed, Jul 01, 2020 at 09:21:24PM -0400, Sasha Levin wrote:
From: Pierre-Louis Bossart
[ Upstream commit c8d2e2bfaeffa0f914330e8b4e45b986c8d30b58 ]
Usually the DSP is not traditionally enabled on H skews but this might
be used moving forward.
"This m
On Wed, Jul 1, 2020 at 11:46 AM Roman Gushchin wrote:
...
> --
>
> From c97afecd32c0db5e024be9ba72f43d22974f5bcd Mon Sep 17 00:00:00 2001
> From: Roman Gushchin
> Date: Wed, 1 Jul 2020 11:05:32 -0700
> Subject: [PATCH] mm: kmem: make memcg_kmem_enabled() irreversible
>
> Historically the kernel m
Hi Geert,
On 02.07.20 16:57, Geert Uytterhoeven wrote:
Hi Frieder,
On Thu, Jul 2, 2020 at 4:46 PM Frieder Schrempf
wrote:
On 02.07.20 16:25, Mark Brown wrote:
On Thu, Jul 02, 2020 at 04:18:46PM +0200, Schrempf Frieder wrote:
From: Frieder Schrempf
Allow external SPI ports on Kontron board
On Thu, Jul 02, 2020 at 08:54:53AM -0700, Kees Cook wrote:
> On Thu, Jul 02, 2020 at 01:54:00AM -0700, Danny Lin wrote:
> > A recent LLVM 11 commit [1] made LLD stop implicitly coalescing some
> > temporary LLVM sections, namely .{data,bss}..compoundliteral.XXX:
> >
> > [30] .data..compoundli PR
* Sergey Senozhatsky [200702 05:13]:
> On (20/06/30 11:02), Tony Lindgren wrote:
> > This conditional disable for irq_shared does not look nice to me
> > from the other device point of view :)
> >
> > Would it be possible to just set up te dummy interrupt handler
> > for the startup, then change
On 2020-07-01 20:39, Krishna Reddy wrote:
On 01/07/2020 20:00, Krishna Reddy wrote:
+items:
+ - enum:
+ - nvdia,tegra194-smmu
+ - const: arm,mmu-500
Is the fallback compatible appropriate here? If software treats this as a
standard MMU-500 it will only
fb_probe() can successfully allocate a new frame buffer, but then fail
to perform some operations with regulator. In these cases fb_probe()
goes to label err_pm_runtime_disable where the frame buffer is not
released. The patch makes fb_probe() to go to label err_release_fb on
corresponding error ha
On Thu, Jul 02, 2020 at 10:42:21AM -0500, Pierre-Louis Bossart wrote:
> On 7/2/20 6:18 AM, Mark Brown wrote:
> > On Wed, Jul 01, 2020 at 09:21:24PM -0400, Sasha Levin wrote:
> > > From: Pierre-Louis Bossart
> > > [ Upstream commit c8d2e2bfaeffa0f914330e8b4e45b986c8d30b58 ]
> > > Usually the DSP
Tetsuo Handa writes:
> On 2020/07/02 22:08, Eric W. Biederman wrote:
>> Tetsuo Handa writes:
>>
>>> On 2020/06/30 21:29, Eric W. Biederman wrote:
Hmm. The wake up happens just of tgid->wait_pidfd happens just before
release_task is called so there is a race. As it is possible to wak
ср, 1 июл. 2020 г. в 18:35, Sasha Levin :
>
> From: Zhang Xiaoxu
>
> [ Upstream commit 95a3d8f3af9b0d63b43f221b630beaab9739d13a ]
>
> When xfstests generic/451, there is an BUG at mm/memcontrol.c:
> page:ea000560f2c0 refcount:2 mapcount:0 mapping:8544e0ea
>index:0xf
> mappi
Hi,
On Thu, Jul 02, 2020 at 03:39:09PM +0100, Mark Brown wrote:
> On Thu, Jul 02, 2020 at 03:42:24PM +0200, nicolas.fe...@microchip.com wrote:
>
> > I kept these entries together as it may generate conflicts if handled
> > separately. I suggest that Mark take the chunk as maintainer of SPI and
>
On 02/07/20 15:42, Vincent Guittot wrote:
> task_h_load() can return 0 in some situations like running stress-ng
> mmapfork, which forks thousands of threads, in a sched group on a 224 cores
> system. The load balance doesn't handle this correctly because
> env->imbalance never decreases and it w
On 6/26/20 6:02 AM, Joonsoo Kim wrote:
> 2020년 6월 25일 (목) 오후 8:26, Michal Hocko 님이 작성:
>>
>> On Tue 23-06-20 15:13:43, Joonsoo Kim wrote:
>> > From: Joonsoo Kim
>> >
>> > There is no difference between two migration callback functions,
>> > alloc_huge_page_node() and alloc_huge_page_nodemask(), ex
Hi Nicholas,
I love your patch! Yet something to improve:
[auto build test ERROR on powerpc/next]
[also build test ERROR on tip/locking/core v5.8-rc3 next-20200702]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use as documented
This change adds a new kernel configuration that sets the l1d cache
flush setting at compile time rather than at run time.
Signed-off-by: Abhishek Bhardwaj
---
arch/x86/kernel/cpu/bugs.c | 8
arch/x86/kvm/Kconfig | 17 +
2 files changed, 25 insertions(+)
diff --
On Wed 01-07-20 11:45:52, Roman Gushchin wrote:
[...]
> >From c97afecd32c0db5e024be9ba72f43d22974f5bcd Mon Sep 17 00:00:00 2001
> From: Roman Gushchin
> Date: Wed, 1 Jul 2020 11:05:32 -0700
> Subject: [PATCH] mm: kmem: make memcg_kmem_enabled() irreversible
>
> Historically the kernel memory acco
On Thu, 2020-07-02 at 08:42 -0700, Kees Cook wrote:
> On Thu, Jul 02, 2020 at 04:23:35PM +0100, Mark Brown wrote:
> > On Thu, Jul 02, 2020 at 08:21:40AM -0700, Kees Cook wrote:
> > > On Wed, Jul 01, 2020 at 09:39:20PM +0100, Mark Brown wrote:
> > > > Please copy maintainers on patches :(
> > > Hi!
On 02.07.20 17:07, Mark Brown wrote:
On Thu, Jul 02, 2020 at 04:46:09PM +0200, Frieder Schrempf wrote:
My intention is to use the spidev driver in the default board DT for an
interface that is routed to an extension connector and has no dedicated
slave device attached onboard. So users can atta
On 02/07/20 16:45, Quentin Perret wrote:
> On Thursday 02 Jul 2020 at 15:31:07 (+0100), Valentin Schneider wrote:
>> There an "interesting" quirk of asym_cpu_capacity_level() in that it does
>> something slightly different than what it says on the tin: it detects
>> the lowest topology level wher
From: Bartosz Golaszewski
Use the managed variant of krealloc() and shrink the code a bit.
Signed-off-by: Bartosz Golaszewski
---
NOTE: this patch depends on the series adding devm_krealloc() which is
not yet accepted.
Greg,
here's just a quick example of a second user of devm_krealloc(). Thi
Hi Greg,
On 7/2/20 9:17 AM, Grzegorz Jaszczyk wrote:
The PRUSS INTC receives a number of system input interrupt source events
and supports individual control configuration and hardware prioritization.
These input events can be mapped to some output host interrupts through 2
levels of many-to-one
Hi Linus,
Please pull the following Kselftest fixes update for Linux 5.8-rc4.
This kselftest fixes update for Linux 5.8-rc4 consists of tpm test
fixes from Jarkko Sakkinen.
diff is attached.
thanks,
-- Shuah
The following change
The definition of pci_channel_io_normal and friends is relatively
complicated and ugly:
typedef unsigned int __bitwise pci_channel_state_t;
enum pci_channel_state {
pci_channel_io_normal = (__force pci_channel_state_t) 1,
...
};
This is clear
The type used to describe the PCI channel state is a combination
of a bitwise typedef 'pci_channel_state_t' and an enumeration
of constant __force casted to this typedef: enum pci_channel_state.
It's a bit complex and quite ugly because:
* in C enums are weakly typed (they're essentially the same
On 01.07.20 13:54, Wei Yang wrote:
> On Wed, Jul 01, 2020 at 10:29:08AM +0200, David Hildenbrand wrote:
>> On 01.07.20 04:11, Wei Yang wrote:
>>> On Tue, Jun 30, 2020 at 02:44:00PM +0200, David Hildenbrand wrote:
On 30.06.20 05:18, Wei Yang wrote:
> When walking page tables, we define seve
The method struct pci_error_handlers::error_detected() is defined and
documented as taking an 'enum pci_channel_state' for the second
argument but most drivers use 'pci_channel_state_t' instead.
This 'pci_channel_state_t' is not a typedef for the enum but a typedef
for a bitwise type in order to ha
For typechecking reasons, the typedef 'pci_channel_state_t'
should be used instead of the 'enum pci_channel_state'.
One simple way to enforce this is to remove the definition of
'enum pci_channel_state' and replace it by an anonymous 'enum'.
Signed-off-by: Luc Van Oostenryck
---
include/linux/p
* Внимание: бенефициар *
* Сообщите, что мы получили утвержденный файл оплаты от FEDERAL
МИНИСТЕРСТВО ФИНАНСОВ совместно с Международным валютным фондом (МВФ)
компенсация жертвам мошенничества и ваш адрес электронной почты входит в список
жертвы. *
* Я пишу, чтобы сообщить вам, что мы будем отпра
On Thu, 2 Jul 2020 at 18:11, Valentin Schneider
wrote:
>
>
> On 02/07/20 15:42, Vincent Guittot wrote:
> > task_h_load() can return 0 in some situations like running stress-ng
> > mmapfork, which forks thousands of threads, in a sched group on a 224 cores
> > system. The load balance doesn't handl
[AMD Public Use]
> -Original Message-
> From: Kai-Heng Feng
> Sent: Thursday, July 2, 2020 8:04 AM
> To: Joerg Roedel
> Cc: Deucher, Alexander ;
> io...@lists.linux-foundation.org; open list
> Subject: [BUG] "Pre-boot DMA Protection" makes AMDGPU stop working
>
> Hi,
>
> A more detail
Hi Vinay,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v5.8-rc3 next-20200702]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use as documented in
* Lee Jones [200701 03:24]:
> When building the kernel with W=1 the build system complains of:
>
> drivers/mmc/host/omap.c:854:6: warning: no previous prototype for
> ‘omap_mmc_notify_cover_event’ [-Wmissing-prototypes]
> 854 | void omap_mmc_notify_cover_event(struct device *dev, int num, int
On Thu, Jul 02, 2020 at 05:56:52PM +0200, Michal Kubecek wrote:
> On Wed, Jul 01, 2020 at 09:29:38PM -0700, Florian Fainelli wrote:
> > Hi all,
> >
> > This patch series untangles the ethtool netlink dependency with PHYLIB
> > which exists because the cable test feature calls directly into PHY
> >
On Thu, 2 Jul 2020 18:34:24 +0200 Andrew Lunn wrote:
> On Thu, Jul 02, 2020 at 05:56:52PM +0200, Michal Kubecek wrote:
> > On Wed, Jul 01, 2020 at 09:29:38PM -0700, Florian Fainelli wrote:
> > > Hi all,
> > >
> > > This patch series untangles the ethtool netlink dependency with PHYLIB
> > > whic
On 7/2/20 6:22 PM, Michal Hocko wrote:
> On Wed 01-07-20 11:45:52, Roman Gushchin wrote:
> [...]
>> >From c97afecd32c0db5e024be9ba72f43d22974f5bcd Mon Sep 17 00:00:00 2001
>> From: Roman Gushchin
>> Date: Wed, 1 Jul 2020 11:05:32 -0700
>> Subject: [PATCH] mm: kmem: make memcg_kmem_enabled() irreve
On Thu, 2 Jul 2020 12:06:32 +0530 Vaibhav Gupta wrote:
> With legacy PM, drivers themselves were responsible for managing the
> device's power states and takes care of register states. And they use PCI
> helper functions to do it.
>
> After upgrading to the generic structure, PCI core will take c
On Thursday 02 Jul 2020 at 17:25:41 (+0100), Valentin Schneider wrote:
> It's actually pretty close to what happens with the LLC domain on SMP -
> select_idle_sibling() doesn't look outside of it. The wake_affine() stuff
> might steer the task towards a different LLC, but that's about it for
> wake
This patchset adds interconnect API support for the Exynos SoC "samsung,
exynos-bus" compatible devices, which already have their corresponding
exynos-bus driver in the devfreq subsystem. Complementing the devfreq
driver with an interconnect functionality allows to ensure the QoS
requirements of d
Add documentation for new optional properties in the exynos bus nodes:
samsung,interconnect-parent, #interconnect-cells, bus-width.
These properties allow to specify the SoC interconnect structure which
then allows the interconnect consumer devices to request specific
bandwidth requirements.
Signe
This patch adds the following properties for Exynos4412 interconnect
bus nodes:
- samsung,interconnect-parent: to declare connections between
nodes in order to guarantee PM QoS requirements between nodes,
- #interconnect-cells: required by the interconnect framework,
- bus-width: the bus widt
This patch adds interconnect support to exynos-mixer. The mixer works
the same as before when CONFIG_INTERCONNECT is 'n'.
For proper operation of the video mixer block we need to ensure the
interconnect busses like DMC or LEFTBUS provide enough bandwidth so
as to avoid DMA buffer underruns in the
This patch adds a generic interconnect driver for Exynos SoCs in order
to provide interconnect functionality for each "samsung,exynos-bus"
compatible device.
The SoC topology is a graph (or more specifically, a tree) and its
edges are specified using the 'samsung,interconnect-parent' in the
DT. Du
This patch adds registration of a child platform device for the exynos
interconnect driver. It is assumed that the interconnect provider will
only be needed when #interconnect-cells property is present in the bus
DT node, hence the child device will be created only when such a property
is present.
On Wed, Jul 1, 2020 at 10:14 PM Guenter Roeck wrote:
>
> On Thu, Jul 02, 2020 at 01:42:23AM +, Chu Lin wrote:
> > Per max6581, reg 4d and reg 4e is used for temperature read offset.
> > This patch will let the user specify the temperature read offset for
> > max6581. This patch is tested on ma
On Thu, Jul 02, 2020 at 06:22:02PM +0200, Michal Hocko wrote:
> On Wed 01-07-20 11:45:52, Roman Gushchin wrote:
> [...]
> > >From c97afecd32c0db5e024be9ba72f43d22974f5bcd Mon Sep 17 00:00:00 2001
> > From: Roman Gushchin
> > Date: Wed, 1 Jul 2020 11:05:32 -0700
> > Subject: [PATCH] mm: kmem: make
From: Artur Świgoń
This patch adds an 'interconnects' property to Exynos4412 DTS in order to
declare the interconnect path used by the mixer. Please note that the
'interconnect-names' property is not needed when there is only one path in
'interconnects', in which case calling of_icc_get() with a
On Thu, 2 Jul 2020 18:08:11 +0300 Moshe Shemesh wrote:
> From: Vladyslav Tarasiuk
>
> In order to use new devlink port health reporters infrastructure, add
> corresponding constructor and destructor functions.
>
> Signed-off-by: Vladyslav Tarasiuk
> Reviewed-by: Moshe Shemesh
> Reviewed-by: J
On 7/2/2020 9:35 AM, Jakub Kicinski wrote:
> On Thu, 2 Jul 2020 18:34:24 +0200 Andrew Lunn wrote:
>> On Thu, Jul 02, 2020 at 05:56:52PM +0200, Michal Kubecek wrote:
>>> On Wed, Jul 01, 2020 at 09:29:38PM -0700, Florian Fainelli wrote:
Hi all,
This patch series untangles the etht
Fix W=1 warning
Signed-off-by: Pierre-Louis Bossart
---
sound/soc/amd/acp-da7219-max98357a.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/sound/soc/amd/acp-da7219-max98357a.c
b/sound/soc/amd/acp-da7219-max98357a.c
index 9414d7269c4f..7d8986379d80 100644
--- a/sound/soc/amd/acp-da7219-m
Fix W=1 warning
Signed-off-by: Pierre-Louis Bossart
---
sound/soc/amd/acp-rt5645.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/sound/soc/amd/acp-rt5645.c b/sound/soc/amd/acp-rt5645.c
index 73b31f88a6b5..87f0060e771f 100644
--- a/sound/soc/amd/acp-rt5645.c
+++ b/sound/soc/amd/acp-rt5645
On 01/07/2020 21:06, Valentin Schneider wrote:
> This flag was introduced in 2014 by commit
>
> d77b3ed5c9f8 ("sched: Add a new SD_SHARE_POWERDOMAIN for sched_domain")
>
> but AFAIA it was never leveraged by the scheduler. The closest thing I can
> think of is EAS caring about frequency domains
Fix W=1 warning. the card variable is useless here.
Signed-off-by: Pierre-Louis Bossart
---
sound/soc/amd/raven/acp3x-pcm-dma.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/sound/soc/amd/raven/acp3x-pcm-dma.c
b/sound/soc/amd/raven/acp3x-pcm-dma.c
index 5bd458e0fe31..1f0fe5aaab1d 100644
Fix W=1 warning. The variable prtd is set but not used.
Signed-off-by: Pierre-Louis Bossart
---
sound/soc/amd/raven/acp3x-i2s.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/sound/soc/amd/raven/acp3x-i2s.c b/sound/soc/amd/raven/acp3x-i2s.c
index a0e14cc91d95..c3eb9b347eaa 100644
--- a/sou
This is the third round of my changeset to split the user mode driver
code from the user mode helper code, and to make the code use common
facilities to get things done instead of recreating them just
for the user mode driver code.
I have split the changes into small enough pieces so they should
Fix W=1 warning. The variable prtd is not used, remove.
Signed-off-by: Pierre-Louis Bossart
---
sound/soc/amd/raven/acp3x-pcm-dma.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/sound/soc/amd/raven/acp3x-pcm-dma.c
b/sound/soc/amd/raven/acp3x-pcm-dma.c
index 1f0fe5aaab1d..17290c829c4b 100
Fix W=1 warning. the card variable is useless here
Signed-off-by: Pierre-Louis Bossart
---
sound/soc/amd/raven/acp3x-i2s.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/sound/soc/amd/raven/acp3x-i2s.c b/sound/soc/amd/raven/acp3x-i2s.c
index 14607563abd2..a0e14cc91d95 100644
--- a/sound/so
Now that the functionality of umh_setup_pipe and
umh_clean_and_save_pid has changed their names are too specific and
don't make much sense. Instead name them umd_setup and umd_cleanup
for the functional role in setting up user mode drivers.
v1: https://lkml.kernel.org/r/875zbegf82.fsf...@x220.in
The only caller of call_usermodehelper_setup_file is fork_usermode_blob.
In fork_usermode_blob replace call_usermodehelper_setup_file with
call_usermodehelper_setup and delete fork_usermodehelper_setup_file.
For this to work the argv_free is moved from umh_clean_and_save_pid
to fork_usermode_blob.
I am separating the code specific to user mode drivers from the code
for ordinary user space helpers. Move setting of PF_UMH from
call_usermodehelper_exec_async which is core user mode helper code
into umh_pipe_setup which is user mode driver code.
The code is equally as easy to write in one loca
This structure is only used for user mode drivers so change
the prefix from umh to umd to make that clear.
v1: https://lkml.kernel.org/r/87o8p6f0kw.fsf...@x220.int.ebiederm.org
v2: https://lkml.kernel.org/r/878sg563po.fsf...@x220.int.ebiederm.org
Reviewed-by: Greg Kroah-Hartman
Signed-off-by: "Er
This makes it clear which code is part of the core user mode
helper support and which code is needed to implement user mode
drivers.
This makes the kernel smaller for everyone who does not use a usermode
driver.
v1: https://lkml.kernel.org/r/87tuyyf0ln.fsf...@x220.int.ebiederm.org
v2: https://lkm
The pid in struct subprocess_info is only used by umh_clean_and_save_pid to
write the pid into umh_info.
Instead always capture the pid on struct umh_info in umh_pipe_setup, removing
code that is specific to user mode drivers from the common user path of
user mode helpers.
v1: https://lkml.kernel
Create an independent helper thread_group_exited report return true
when all threads have passed exit_notify in do_exit. AKA all of the
threads are at least zombies and might be dead or completely gone.
Create this helper by taking the logic out of pidfd_poll where
it is already tested, and addin
Instead of relying on the exit_umh cleanup callback use the fact a
struct pid can be tested to see if a process still exists, and that
struct pid has a wait queue that notifies when the process dies.
v1: https://lkml.kernel.org/r/87h7uydlu9.fsf...@x220.int.ebiederm.org
v2: https://lkml.kernel.org/
There is exactly one argument so there is nothing to split. All
split_argv does now is cause confusion and avoid the need for a cast
when passing a "const char *" string to call_usermodehelper_setup.
So avoid confusion and the possibility of an odd driver name causing
problems by just using a fix
The only thing supplied in the cmdline today is the driver name so
rename the field to clarify the code.
As this value is always supplied stop trying to handle the case of
a NULL cmdline.
Additionally since we now have a name we can count on use the
driver_name any place where the code is looking
Now that the last callser has been removed remove this code from exec.
For anyone thinking of resurrecing do_execve_file please note that
the code was buggy in several fundamental ways.
- It did not ensure the file it was passed was read-only and that
deny_write_access had been called on it. W
The bpfilter code no longer uses the umd_info.cleanup callback. This
callback is what exit_umh exists to call. So remove exit_umh and all
of it's associated booking.
v1: https://lkml.kernel.org/r/87bll6dlte.fsf...@x220.int.ebiederm.org
v2: https://lkml.kernel.org/r/87y2o53abg.fsf...@x220.int.ebi
With the user mode driver code changed to not set subprocess_info.file
there are no more users of subproces_info.file. Remove this field
from struct subprocess_info and remove the only user in
call_usermodehelper_exec_async that would call do_execve_file instead
of do_execve if file was set.
v1:
To allow for restarts 61fbf5933d42 ("net: bpfilter: restart
bpfilter_umh when error occurred") moved the blob holding the
userspace binary out of the init sections.
Now that loading the blob into a filesystem is separate from executing
the blob the blob no longer needs to live .rodata to allow for
Instead of loading a binary blob into a temporary file with
shmem_kernel_file_setup load a binary blob into a temporary tmpfs
filesystem. This means that the blob can be stored in an init section
and discared, and it means the binary blob will have a filename so can
be executed normally.
The only
On Thu, Jul 02, 2020 at 04:12:16PM +0200, Sebastian Andrzej Siewior wrote:
> On 2020-06-30 11:35:34 [-0700], Paul E. McKenney wrote:
> > > This is not going to work together with the "wait context validator"
> > > (CONFIG_PROVE_RAW_LOCK_NESTING). As of -rc3 it should complain about
> > > printk() w
Use struct pid instead of user space pid values that are prone to wrap
araound.
In addition track the entire thread group instead of just the first
thread that is started by exec. There are no multi-threaded user mode
drivers today but there is nothing preclucing user drivers from being
multi-thr
On 02/07/20 17:37, Quentin Perret wrote:
> On Thursday 02 Jul 2020 at 17:25:41 (+0100), Valentin Schneider wrote:
>> It's actually pretty close to what happens with the LLC domain on SMP -
>> select_idle_sibling() doesn't look outside of it. The wake_affine() stuff
>> might steer the task towards
On 2020-07-02 17:25, Bartosz Golaszewski wrote:
From: Bartosz Golaszewski
Use the managed variant of krealloc() and shrink the code a bit.
Signed-off-by: Bartosz Golaszewski
---
NOTE: this patch depends on the series adding devm_krealloc() which is
not yet accepted.
Greg,
here's just a quic
Add an IOCB_NOIO flag that indicates to generic_file_read_iter that it
shouldn't trigger any filesystem I/O for the actual request or for
readahead. This allows to do tentative reads out of the page cache as
some filesystems allow, and to take the appropriate locks and retry the
reads only if the
Now that the locking order in gfs2 is fixed, switch back to using the
->readahead address space operation. With that, mpage_readpages is
unused and can be removed.
Signed-off-by: Andreas Gruenbacher
---
fs/gfs2/aops.c| 19 +--
fs/mpage.c| 75 -
Commit d4388340ae0b ("fs: convert mpage_readpages to mpage_readahead")
converted gfs2 and other filesystems from the ->readpages to the
->readahead address space operation. Other than ->readpages,
->readahead is passed the pages to readahead locked. Due to problems in
the current page locking str
Hi all,
commit d4388340ae0b ("fs: convert mpage_readpages to mpage_readahead")
converted gfs2 and other filesystems from the ->readpages to the
->readahead address space operation. Due to gfs2 doing its locking in
the ->readpage and ->readahead address space operations rather than at a
higher lev
So far, gfs2 has taken the filesystem locks inside the ->readpage and
->readahead address space operations. These operations are too
low-level, causing lock ordering problems and workarounds. To get rid
of those, move the locking to the ->read_iter file and ->fault vm
operations.
The cache consi
On Thu, Jul 02, 2020 at 08:58:49AM -0400, Steven Rostedt wrote:
> On Thu, 2 Jul 2020 14:34:02 +0200
> Greg KH wrote:
>
> > > I can add an option to do that if you want. My full logs end up being a
> > > few hundred megabytes. Perhaps I could add a compress option too.
> >
> > It's fine, the de
Move the bindings out of drivers/staging and place them in
Documentation/devicetree/bindings instead.
Also, add DT nodes for RK3399 and verify with make ARCH=arm64 dtbs_check
and make ARCH=arm64 dt_binding_check.
Tested by verifying images streamed from Scarlet Chromebook
Changes in v3:
- droppe
Add missing required items in Rockchip ISP1 dt-bindings example for
a complete i2c node.
Signed-off-by: Helen Koike
---
Changes in v3: None
Changes in v2:
- new patch in the series
---
.../devicetree/bindings/media/rockchip-isp1.yaml | 5 +
1 file changed, 5 insertions(+)
diff
Organize properties order in dt-binbings to move it out of staging.
On top: compatible, reg and interrupts.
Then alphabetical order, then properties starting with '#'.
Signed-off-by: Helen Koike
---
V3: none
V2:
- this is a new patch in the series
---
.../bindings/media/rockchip-isp1.yaml
The Rockchip ISP bindings was moved out of staging.
Update MAINTAINERS file with the new path.
Fields sorted according to output of
./scripts/parse-maintainers.pl --input=MAINTAINERS --output=MAINTAINERS
--order
Signed-off-by: Helen Koike
---
V3:
- Add line:
L: linux-rockc...@lists.infrade
aclk_isp_wrap is a child of aclk_isp, and hclk_isp_wrap is a child of
hclk_isp, thus we can remove parents from the list, with the goal to
cleanup the dt-bindings and remove it from staging.
For reference, this is the isp clock topology:
xin24m
pll_npll
npll
clk_isp1
Fix the following error found with make ARCH=arm64 dt_binding_check:
Documentation/devicetree/bindings/media/rockchip-isp1.example.dts:24.27-101.11:
Warning (unit_address_vs_reg): /example-0/parent@0: node has a unit name, but
no reg or ranges property
Reported-by: Johan Jonker
Signed-off-by: H
Move rkisp1 bindings to Documentation/devicetree/bindings/media
Verified with:
make ARCH=arm64 dt_binding_check
DT_SCHEMA_FILES=Documentation/devicetree/bindings/media/rockchip-isp1.yaml
Signed-off-by: Helen Koike
Acked-by: Rob Herring
---
.../devicetree/bindings/media/rockchip-isp1.yaml
Add missing required nodes in json-schema yaml file for
Rockchip ISP1 dt-bindings.
Signed-off-by: Helen Koike
---
Changes in v3: None
Changes in v2:
- New patch in the series
---
.../devicetree/bindings/media/rockchip-isp1.yaml | 8
1 file changed, 8 insertions(+)
diff --git
701 - 800 of 1488 matches
Mail list logo
