On 24/08/2020 12:05, pet...@infradead.org wrote:
> On Sun, Aug 23, 2020 at 04:09:42PM -0700, Andy Lutomirski wrote:
>> On Fri, Aug 21, 2020 at 3:21 AM Peter Zijlstra wrote:
>>> Get rid of the two variables, avoid computing si_code when not needed
>>> and be consistent about which dr6 value is used
On Fri, Aug 21, 2020 at 09:25:26AM -0700, Randy Dunlap wrote:
> On 8/21/20 8:28 AM, Tomer Samara wrote:
> > Remove BUG() from ion_sytem_heap.c
> >
> > this fix the following checkpatch issue:
> > Avoid crashing the kernel - try using WARN_ON &
> > recovery code ratherthan BUG() or BUG_ON().
> >
>
On Mon, Aug 24, 2020 at 02:24:57PM +0300, Dan Carpenter wrote:
> On Fri, Aug 21, 2020 at 09:25:26AM -0700, Randy Dunlap wrote:
> > On 8/21/20 8:28 AM, Tomer Samara wrote:
> > > Remove BUG() from ion_sytem_heap.c
> > >
> > > this fix the following checkpatch issue:
> > > Avoid crashing the kernel -
On 30-07-20, 10:01, Stephan Gerhold wrote:
> dev_pm_opp_attach_genpd() allows attaching an arbitrary number of
> power domains to an OPP table. In that case, the genpd core will
> create a virtual device for each of the power domains.
>
> At the moment, the OPP core only calls
> dev_pm_genpd_set_p
Upstream commits fdfe7cbd5880 ("KVM: Pass MMU notifier range flags to
kvm_unmap_hva_range()") and b5331379bc62 ("KVM: arm64: Only reschedule
if MMU_NOTIFIER_RANGE_BLOCKABLE is not set") fix a "sleeping from invalid
context" BUG caused by unmap_stage2_range() attempting to reschedule when
called on
Upstream commits fdfe7cbd5880 ("KVM: Pass MMU notifier range flags to
kvm_unmap_hva_range()") and b5331379bc62 ("KVM: arm64: Only reschedule
if MMU_NOTIFIER_RANGE_BLOCKABLE is not set") fix a "sleeping from invalid
context" BUG caused by unmap_stage2_range() attempting to reschedule when
called on
Upstream commits fdfe7cbd5880 ("KVM: Pass MMU notifier range flags to
kvm_unmap_hva_range()") and b5331379bc62 ("KVM: arm64: Only reschedule
if MMU_NOTIFIER_RANGE_BLOCKABLE is not set") fix a "sleeping from invalid
context" BUG caused by unmap_stage2_range() attempting to reschedule when
called on
commit b5331379bc62611d1026173a09c73573384201d9 upstream.
When an MMU notifier call results in unmapping a range that spans multiple
PGDs, we end up calling into cond_resched_lock() when crossing a PGD boundary,
since this avoids running into RCU stalls during VM teardown. Unfortunately,
if the VM
commit fdfe7cbd58806522e799e2a50a15aee7f2cbb7b6 upstream.
The 'blockable' flag passed to the 'invalidate_range_start()' call back
of 'struct mmu_notifier' is used to indicate whether the function is
permitted to block. In the case of
kvm_mmu_notifier_invalidate_range_start(), this field is not for
commit fdfe7cbd58806522e799e2a50a15aee7f2cbb7b6 upstream.
The 'flags' field of 'struct mmu_notifier_range' is used to indicate
whether invalidate_range_{start,end}() are permitted to block. In the
case of kvm_mmu_notifier_invalidate_range_start(), this field is not
forwarded on to the architecture
On 21-08-20, 18:31, Stephan Gerhold wrote:
> This patch does not apply anymore after the cleanup you pushed to
> opp/linux-next. I would be happy to send a v2 with that fixed.
>
> On my other OPP patch set you mentioned that you might apply these
> directly with some of your own changes - would yo
commit b5331379bc62611d1026173a09c73573384201d9 upstream.
When an MMU notifier call results in unmapping a range that spans multiple
PGDs, we end up calling into cond_resched_lock() when crossing a PGD boundary,
since this avoids running into RCU stalls during VM teardown. Unfortunately,
if the VM
commit b5331379bc62611d1026173a09c73573384201d9 upstream.
When an MMU notifier call results in unmapping a range that spans multiple
PGDs, we end up calling into cond_resched_lock() when crossing a PGD boundary,
since this avoids running into RCU stalls during VM teardown. Unfortunately,
if the VM
> Let me know your thoughts and looking forward to a good LPC MC discussion!
>
Nice write up Joel, thanks for taking time to compile this with great detail!
After going through the details of interface proposal using cgroup v2
controllers,
and based on our discussion offline, would like to note d
commit fdfe7cbd58806522e799e2a50a15aee7f2cbb7b6 upstream.
The 'flags' field of 'struct mmu_notifier_range' is used to indicate
whether invalidate_range_{start,end}() are permitted to block. In the
case of kvm_mmu_notifier_invalidate_range_start(), this field is not
forwarded on to the architecture
On Mon, Aug 24, 2020 at 04:48:20PM +0530, Viresh Kumar wrote:
> On 30-07-20, 10:01, Stephan Gerhold wrote:
> > Move call to dev_pm_genpd_set_performance_state() to a separate
> > function so we can avoid duplicating the code for the single and
> > multiple genpd case.
> >
> > Signed-off-by: Stepha
commit fdfe7cbd58806522e799e2a50a15aee7f2cbb7b6 upstream.
The 'flags' field of 'struct mmu_notifier_range' is used to indicate
whether invalidate_range_{start,end}() are permitted to block. In the
case of kvm_mmu_notifier_invalidate_range_start(), this field is not
forwarded on to the architecture
commit b5331379bc62611d1026173a09c73573384201d9 upstream.
When an MMU notifier call results in unmapping a range that spans multiple
PGDs, we end up calling into cond_resched_lock() when crossing a PGD boundary,
since this avoids running into RCU stalls during VM teardown. Unfortunately,
if the VM
On 8/21/20 7:32 AM, Krzysztof Kozlowski wrote:
On Fri, 21 Aug 2020 at 08:31, Krzysztof Kozlowski wrote:
On Mon, 17 Aug 2020 at 19:17, Lukasz Luba wrote:
Hi Krzysztof,
On 8/17/20 4:50 PM, Krzysztof Kozlowski wrote:
On Wed, Jul 08, 2020 at 04:34:20PM +0100, Lukasz Luba wrote:
The interr
When mtu is locked, we should not obtain ipv4 mtu as we return immediately
in this case and leave acquired ipv4 mtu unused.
Signed-off-by: Miaohe Lin
---
net/ipv4/route.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/net/ipv4/route.c b/net/ipv4/route.c
index 8ca6bcab7b03.
Hi Lad-san,
> From: Lad Prabhakar, Sent: Saturday, August 15, 2020 2:31 AM
>
> Document the support for R-Car PCIe EP on R8A774A1 and R8A774B1 SoC
> devices.
>
> Also constify "renesas,rcar-gen3-pcie-ep" so that it can be used as
> fallback compatible string for R-Car Gen3 and RZ/G2 devices as t
On Thu, 2020-08-20 at 14:00 -0700, Jim Mattson wrote:
> On Thu, Aug 20, 2020 at 6:33 AM Maxim Levitsky wrote:
> > No functional changes.
> >
> > Signed-off-by: Maxim Levitsky
> > ---
> > arch/x86/kvm/svm/nested.c | 10 +-
> > arch/x86/kvm/svm/svm.c| 13 +++--
> > arch/x86/kv
24.08.2020 01:30, Pavel Machek пишет:
>> +orange_led->cdev.name = "power-button-orange";
>
> "orange:power" -- or what is this LED usually used for?
The orange LED is supposed to indicate that battery is charging up.
Hi Robin,
On 20.08.2020 17:08, Robin Murphy wrote:
> Hi all,
>
> After 5 years or so of intending to get round to this, finally the
> time comes! The changes themselves actualy turn out to be relatively
> mechanical; the bigger concern appears to be how to get everything
> merged across about 5 di
On Wed, 19 Aug 2020 at 12:08, Maulik Shah wrote:
>
> This change was done based on an test results of unmerged series of
> adding RSC power domain and using .power_off callback of genpd to
> invoke rpmh_flush().
>
> Call trace:
> dump_backtrace+0x0/0x174
> show_stack+0x20/0x2c
>
On Mon, Aug 24, 2020 at 02:39:32PM +0530, Viresh Kumar wrote:
> From: Stephan Gerhold
>
> The OPP core manages various resources, e.g. clocks or interconnect paths.
> These resources are looked up when the OPP table is allocated once
> dev_pm_opp_get_opp_table() is called the first time (either d
On Mon, Aug 24, 2020 at 05:00:27PM +0530, Viresh Kumar wrote:
> On 21-08-20, 18:31, Stephan Gerhold wrote:
> > This patch does not apply anymore after the cleanup you pushed to
> > opp/linux-next. I would be happy to send a v2 with that fixed.
> >
> > On my other OPP patch set you mentioned that y
On Mon, Aug 24, 2020 at 02:27:08PM +0300, Dan Carpenter wrote:
> On Mon, Aug 24, 2020 at 02:24:57PM +0300, Dan Carpenter wrote:
> > On Fri, Aug 21, 2020 at 09:25:26AM -0700, Randy Dunlap wrote:
> > > On 8/21/20 8:28 AM, Tomer Samara wrote:
> > > > Remove BUG() from ion_sytem_heap.c
> > > >
> > > >
On Thu, 2020-08-20 at 14:26 -0700, Jim Mattson wrote:
> On Thu, Aug 20, 2020 at 6:34 AM Maxim Levitsky wrote:
> > Replace svm_vcpu_init_msrpm with svm_vcpu_alloc_msrpm, that also allocates
> > the msr bitmap and add svm_vcpu_free_msrpm to free it.
> >
> > This will be used later to move the neste
Hi Krzysztof,
On 8/22/20 5:32 PM, Krzysztof Kozlowski wrote:
The struct exynos5_dmc members bypass_rate, mx_mspll_ccore_phy,
mout_mx_mspll_ccore_phy and opp_bypass are not actually used.
Apparently there was a plan to store the OPP for the bypass mode in
opp_bypass member, but drivers fails to
On 8/22/20 11:35 PM, Jan Kiszka wrote:
> On 01.06.20 09:04, Vignesh Raghavendra wrote:
>> dma_request_chan_by_mask() can throw EPROBE_DEFER if DMA provider
>> is not yet probed. Currently driver just falls back to using PIO mode
>> (which is less efficient) in this case. Instead return probe def
Hi Jan,
On 8/24/20 11:25 AM, Jan Kiszka wrote:
[...]
>> +MODULE_AUTHOR("Vignesh Raghavendra ");
>>
> On the AM65x, this changes mtd->name (thus mtd-id for
> parser/cmdlinepart) from 4704.spi.0 to spi7.0. The besides having to
> deal with both names now, "spi7" sounds like it could easily chan
Use helper macro RT_TOS() to get tos in __icmp_send().
Signed-off-by: Miaohe Lin
---
net/ipv4/icmp.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/net/ipv4/icmp.c b/net/ipv4/icmp.c
index cf36f955bfe6..3b387dc3864f 100644
--- a/net/ipv4/icmp.c
+++ b/net/ipv4/icmp.c
@@ -6
On Mon, 24 Aug 2020 at 10:14, Walter Wu wrote:
>
> Generic KASAN support to record the last two timer and workqueue
> stacks and print them in KASAN report. So that need to update
> documentation.
>
> Signed-off-by: Walter Wu
> Cc: Andrey Ryabinin
> Cc: Dmitry Vyukov
> Cc: Alexander Potapenko
On Mon, 24 Aug 2020 at 10:14, Walter Wu wrote:
>
> Adds a test to verify workqueue stack recording and print it in
> KASAN report.
>
> The KASAN report was as follows(cleaned up slightly):
>
> BUG: KASAN: use-after-free in kasan_workqueue_uaf
>
> Freed by task 54:
> kasan_save_stack+0x24/0x50
On Mon, 24 Aug 2020 at 10:07, Walter Wu wrote:
>
> Syzbot reports many UAF issues for workqueue or timer, see [1] and [2].
> In some of these access/allocation happened in process_one_work(),
> we see the free stack is useless in KASAN report, it doesn't help
> programmers to solve UAF on workqueu
>> Yet, I have noticed that there is no checking of 'base' in these functions.
>> But I am not sure how to check is better.As we know that the result is
>> undefined when divisor is zero. It maybe good to print error and dump stack.
>> Let the process to know that the divisor is zero by sending S
Add else to split mutually exclusive case and avoid some unnecessary check.
Signed-off-by: Miaohe Lin
---
mm/mempool.c | 10 --
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/mm/mempool.c b/mm/mempool.c
index 79bff63ecf27..73fb2e548b43 100644
--- a/mm/mempool.c
+++ b/mm/me
On Mon, Aug 24, 2020 at 04:57:44PM +0530, Viresh Kumar wrote:
> On 30-07-20, 10:01, Stephan Gerhold wrote:
> > dev_pm_opp_attach_genpd() allows attaching an arbitrary number of
> > power domains to an OPP table. In that case, the genpd core will
> > create a virtual device for each of the power dom
friendly ping :)
>Miaohe Lin wrote:
>From: Miaohe Lin
>
>The need for padding 64bit is implicitly checked by nla_align_64bit(), so
>remove this explicit one.
>
>Signed-off-by: Miaohe Lin
>---
> lib/nlattr.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
>diff --git a/lib/nlattr.c b
On Wed, Aug 19, 2020 at 07:59:56PM +0200, David Hildenbrand wrote:
> On the memory onlining path, we want to start with MIGRATE_ISOLATE, to
> un-isolate the pages after memory onlining is complete. Let's allow
> passing in the migratetype.
>
> Acked-by: Michal Hocko
> Cc: Andrew Morton
> Cc: Mic
friendly ping :)
>Miaohe Lin wrote:
>From: Miaohe Lin
>
>Use wrapper function wake_up_worker() to wake up first idle worker.
>
>Signed-off-by: Miaohe Lin
>---
> kernel/workqueue.c | 10 --
> 1 file changed, 4 insertions(+), 6 deletions(-)
>
>diff --git a/kernel/workqueue.c b/kernel/workq
On Mon, Aug 24, 2020 at 12:26:01PM +0100, Andrew Cooper wrote:
> > INT1 is a trap,
> > instruction breakpoint is a fault
> >
> > So if you have:
> >
> > INT1
> > 1: some-instr
> >
> > and set an X breakpoint on 1, we'll loose the INT1, right?
>
> You should get two. First with a dr6 of 0 (I
On Mon, Aug 24, 2020 at 12:43:33PM +0100, Lukasz Luba wrote:
> Hi Krzysztof,
>
> On 8/22/20 5:32 PM, Krzysztof Kozlowski wrote:
> > The struct exynos5_dmc members bypass_rate, mx_mspll_ccore_phy,
> > mout_mx_mspll_ccore_phy and opp_bypass are not actually used.
> >
> > Apparently there was a plan
On Monday 24 August 2020 11:50:42 CEST Dan Carpenter wrote:
> On Thu, Aug 20, 2020 at 05:58:47PM +0200, Jerome Pouiller wrote:
> > From: Jérôme Pouiller
> >
> > The protection of the management frames is mainly done by mac80211.
> > However, frames for the management of the BlockAck sessions are d
On Mon, 24 Aug 2020 17:14:56 +0530
Vignesh Raghavendra wrote:
> Hi Jan,
>
> On 8/24/20 11:25 AM, Jan Kiszka wrote:
> [...]
>
> >> +MODULE_AUTHOR("Vignesh Raghavendra ");
> >>
> > On the AM65x, this changes mtd->name (thus mtd-id for
> > parser/cmdlinepart) from 4704.spi.0 to spi7.0. The b
On 24.08.20 13:44, Vignesh Raghavendra wrote:
> Hi Jan,
>
> On 8/24/20 11:25 AM, Jan Kiszka wrote:
> [...]
>
>>> +MODULE_AUTHOR("Vignesh Raghavendra ");
>>>
>> On the AM65x, this changes mtd->name (thus mtd-id for
>> parser/cmdlinepart) from 4704.spi.0 to spi7.0. The besides having to
>> deal
On Wed, Aug 19, 2020 at 07:59:57PM +0200, David Hildenbrand wrote:
> Currently, it can happen that pages are allocated (and freed) via the buddy
> before we finished basic memory onlining.
>
> For example, pages are exposed to the buddy and can be allocated before
> we actually mark the sections o
> + select RESET_CONTROLLER
Only needed for Gen3, so 'if ARCH_RCAR_GEN3'?
signature.asc
Description: PGP signature
On 24-08-20, 13:30, Stephan Gerhold wrote:
> You're right. Not sure why I removed it.
>
> I suspect I had it in _set_required_opp() at some point, but I moved
> code around several times until I was happy with the result.
>
> We should just add it back.
> Should I send a v2 with it fixed or would
On Thu, 2020-06-18 at 18:01 +0200, Roberto Sassu wrote:
> This patch checks the size for the EVM_IMA_XATTR_DIGSIG and
> EVM_XATTR_PORTABLE_DIGSIG types to ensure that the algorithm is read from
> the buffer returned by vfs_getxattr_alloc().
>
> Cc: sta...@vger.kernel.org # 4.19.x
> Fixes: 5feeb611
Hi Ritesh,
I love your patch! Perhaps something to improve:
[auto build test WARNING on v5.9-rc1]
[cannot apply to ext4/dev next-20200821]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm
The Galaxy Book Ion 15 inches uses the same ALC298 codec as other Samsung
laptops which have the no headphone sound bug. I confirmed on my own
hardware that this fixes the bug.
Commit e17f02d05 mixed up 13 inches and 15 inches models. This clarifies
the situation with the correct model names.
Bug
On Thu, 2020-06-18 at 18:01 +0200, Roberto Sassu wrote:
> If files with portable signatures are copied from one location to another
> or are extracted from an archive, verification can temporarily fail until
> all xattrs/attrs are set in the destination. Portable signatures are the
> only ones that
On Thu, 2020-06-18 at 18:04 +0200, Roberto Sassu wrote:
> If metadata are immutable, they cannot be changed. If metadata are already
> set to the final value before cp and tar restore the value from the source,
> those applications display an error even if the operation is legitimate
> (they don't
On Thu, 2020-06-18 at 18:04 +0200, Roberto Sassu wrote:
> When EVM_ALLOW_METADATA_WRITES is set, EVM allows any operation on
> metadata. Its main purpose is to allow users to freely set metadata when
> they are protected by a portable signature, until the HMAC key is loaded.
>
> However, IMA is no
I am leaving Marvell and already do not have access to my @marvell.com
email address. So switching over to my korg mail address or removing
my address there another maintainer is already listed. For the entries
there no other maintainer is listed I will keep looking into patches
for Cavium systems
On Thu, Aug 06, 2020 at 06:49:23PM +, nao.horigu...@gmail.com wrote:
> From: Naoya Horiguchi
>
> Soft offlining could fail with EIO due to the race condition with
> hugepage migration. This issuse became visible due to the change by
> previous patch that makes soft offline handler take page r
On Mon, Aug 24, 2020 at 05:40:04PM +0530, Viresh Kumar wrote:
> On 24-08-20, 13:30, Stephan Gerhold wrote:
> > You're right. Not sure why I removed it.
> >
> > I suspect I had it in _set_required_opp() at some point, but I moved
> > code around several times until I was happy with the result.
> >
Add a manual page to document the fsconfig() system call.
Signed-off-by: David Howells
---
man2/fsconfig.2 | 277 +++
1 file changed, 277 insertions(+)
create mode 100644 man2/fsconfig.2
diff --git a/man2/fsconfig.2 b/man2/fsconfig.2
new fi
It's a sad state of affairs that I have to write this mail at all and it's
nothing else than an act of desperation.
The x86 exception handling including the various ways of syscall entry/exit
are a constant source of trouble. Aside of being a functional disaster
quite some of these issues have sev
Add manual pages to document the move_mount() system call.
Signed-off-by: David Howells
---
man2/move_mount.2 | 267 +
1 file changed, 267 insertions(+)
create mode 100644 man2/move_mount.2
diff --git a/man2/move_mount.2 b/man2/move_mount.2
Add a manual page to document the open_tree() system call.
Signed-off-by: David Howells
---
man2/open_tree.2 | 249 ++
1 file changed, 249 insertions(+)
create mode 100644 man2/open_tree.2
diff --git a/man2/open_tree.2 b/man2/open_tree.2
ne
Add a manual page to document the fsopen() and fsmount() system calls.
Signed-off-by: David Howells
---
man2/fsmount.2 |1
man2/fsopen.2 | 245
2 files changed, 246 insertions(+)
create mode 100644 man2/fsmount.2
create mode 1006
Add a manual page to document the fspick() system call.
Signed-off-by: David Howells
---
man2/fspick.2 | 180 +
1 file changed, 180 insertions(+)
create mode 100644 man2/fspick.2
diff --git a/man2/fspick.2 b/man2/fspick.2
new file mode
When device_create() fails, dvbdev and dvbdevfops should
be freed just like when dvb_register_media_device() fails.
Signed-off-by: Dinghao Liu
---
drivers/media/dvb-core/dvbdev.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/media/dvb-core/dvbdev.c b/drivers/media/dvb-core/dvbde
On Mon, Aug 24, 2020 at 10:47:20AM +0800, Rong Chen wrote:
>
>
> On 8/21/20 9:01 AM, Qian Cai wrote:
> > On Tue, Aug 18, 2020 at 08:23:51AM +0800, kernel test robot wrote:
> > > Greeting,
> > >
> > > FYI, we noticed the following commit (built with gcc-9):
> > >
> > > commit: c5665868183fec689d
There's a mistake in this. The ID numbers are the wrong way round.
Alex
We've met problems that occasionally tasks with full cpumask
(e.g. by putting it into a cpuset or setting to full affinity)
were migrated to our isolated cpus in production environment.
After some analysis, we found that it is due to the current
select_idle_smt() not considering the sched_domain m
My mistake -- I didn't read your changelog properly. Sorry!
On 24/08/2020 13:30, Alex Dewar wrote:
There's a mistake in this. The ID numbers are the wrong way round.
Alex
On 2020-08-21 18:40:17 [-0700], Lokesh Gidra wrote:
> --- a/fs/userfaultfd.c
> +++ b/fs/userfaultfd.c
> @@ -1966,6 +1969,7 @@ static void init_once_userfaultfd_ctx(void *mem)
>
> SYSCALL_DEFINE1(userfaultfd, int, flags)
> {
> + static const int uffd_flags = UFFD_USER_MODE_ONLY;
> stru
Greetings!
Starting from kernel 5.8 (x86_64), kretprobe handler will always missed if
corresponding kprobe on function entry is not optimized (using break point
instead).
Step to reproduce this:
1) Build the kretprobe example module (CONFIG_SAMPLE_KRETPROBES=m)
2) Disable jump optimization (`sys
On 19/08/20 11:47 am, Leo Yan wrote:
> From: Al Grant
>
> Commit 42bbabed09ce ("perf tools: Add hw_idx in struct branch_stack")
> changed the format of branch stacks in perf samples. When samples use
> this new format, a flag must be set in the corresponding event.
> Synthesized branch stacks gen
On Sat, Aug 22, 2020 at 07:25:05PM -0700, Chris Healy wrote:
> From: Chris Healy
>
> Since commit bcf3440c6dd7 ("net: phy: micrel: add phy-mode support for the
> KSZ9031 PHY") the networking is broken on the imx7d-zii-rmu2 board.
>
> The end result is that network receive behaviour is marginal w
On Sun, Aug 23, 2020 at 09:18:06AM +0200, Guido Günther wrote:
> These patches add the NWL host controller to the imx8mq and make use of it on
> the Librem 5 Devkit enabling the built in MIPI DSI LCD panel.
>
> I opted to add imx8mq internal ports and endpoints between nwl and lcdif to
> the
> ge
On Wed, Aug 19, 2020 at 11:25 AM Amir Goldstein wrote:
> > What I have in mind is things like not coupling the setup of the
> > passthrough fds to open(), but having a separate notification message for
> > this (like what we use for invalidation of cache), and adding not just
> > an "fd" field bu
I do not have hardware anymore, nor there is ongoing development. So
handover maintenance to Andre who already maintains the last
remainings of Calxeda.
Cc: Andre Przywara
Signed-off-by: Robert Richter
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINE
Modify cap_inh_is_capped(), cap_task_prctl() to use current_user_ns().
Signed-off-by: Denis Efremov
---
security/commoncap.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/security/commoncap.c b/security/commoncap.c
index 59bf3c1674c8..82a61f77c07c 100644
--- a/security/
On 24.08.20 13:45, Vignesh Raghavendra wrote:
>
>
> On 8/22/20 11:35 PM, Jan Kiszka wrote:
>> On 01.06.20 09:04, Vignesh Raghavendra wrote:
>>> dma_request_chan_by_mask() can throw EPROBE_DEFER if DMA provider
>>> is not yet probed. Currently driver just falls back to using PIO mode
>>> (which is
Modify vbg_misc_device_requestor() to use current_uid() wrapper.
Signed-off-by: Denis Efremov
---
drivers/virt/vboxguest/vboxguest_linux.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/virt/vboxguest/vboxguest_linux.c
b/drivers/virt/vboxguest/vboxguest_linux.c
inde
From: Dinghao Liu
Date: Mon, 24 Aug 2020 13:44:42 +0800
> hns_nic_dev_probe allocates ndev, but not free it on
> two error handling paths, which may lead to memleak.
>
> Fixes: 63434888aaf1b ("net: hns: net: hns: enet adds support of acpi")
> Signed-off-by: Dinghao Liu
Applied and queued up fo
Modify integrity_audit_message() to use current_uid().
Signed-off-by: Denis Efremov
---
security/integrity/integrity_audit.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/security/integrity/integrity_audit.c
b/security/integrity/integrity_audit.c
index f25e7df099c8..292200
The new version which bases on v5.9-rc2. The first 6 patches was picked into
linux-mm, and add patch 25-32 that do some further post optimization.
The patchset includes 4 parts:
1, some code cleanup and minimum optimization as a preparation. patch 1-15.
2, use TestCleanPageLRU as page isolation's
The func is only used in huge_memory.c, defining it in other file with a
CONFIG_TRANSPARENT_HUGEPAGE macro restrict just looks weird.
Let's move it THP. And make it static as Hugh Dickin suggested.
Signed-off-by: Alex Shi
Reviewed-by: Kirill A. Shutemov
Cc: Andrew Morton
Cc: Johannes Weiner
C
From: Alexander Duyck
Use this new function to replace repeated same code, no func change.
When testing for relock we can avoid the need for RCU locking if we simply
compare the page pgdat and memcg pointers versus those that the lruvec is
holding. By doing this we can avoid the extra pointer wa
It's a clean up patch w/o function changes.
Signed-off-by: Alex Shi
Reviewed-by: Alexander Duyck
Cc: Johannes Weiner
Cc: Andrew Morton
Cc: linux...@kvack.org
Cc: linux-kernel@vger.kernel.org
---
mm/swap.c | 2 ++
mm/workingset.c | 2 --
2 files changed, 2 insertions(+), 2 deletions(-)
Currently lru_lock still guards both lru list and page's lru bit, that's
ok. but if we want to use specific lruvec lock on the page, we need to
pin down the page's lruvec/memcg during locking. Just taking lruvec
lock first may be undermined by the page's memcg charge/migration. To
fix this problem,
The current relock logical will change lru_lock when if found a new
lruvec, so if 2 memcgs are reading file or alloc page equally, they
could hold the lru_lock alternately.
This patch will record the needed lru_lock and only hold them once in
above scenario. That could reduce the lock contention.
We don't have to add a freeable page into lru and then remove from it.
This change saves a couple of actions and makes the moving more clear.
The SetPageLRU needs to be kept before put_page_testzero for list
intergrity, otherwise:
#0 mave_pages_to_lru #1 release_pages
if !put_page
On 2020-08-24 12:28, Will Deacon wrote:
Upstream commits fdfe7cbd5880 ("KVM: Pass MMU notifier range flags to
kvm_unmap_hva_range()") and b5331379bc62 ("KVM: arm64: Only reschedule
if MMU_NOTIFIER_RANGE_BLOCKABLE is not set") fix a "sleeping from
invalid
context" BUG caused by unmap_stage2_range
On 2020-08-24 12:29, Will Deacon wrote:
Upstream commits fdfe7cbd5880 ("KVM: Pass MMU notifier range flags to
kvm_unmap_hva_range()") and b5331379bc62 ("KVM: arm64: Only reschedule
if MMU_NOTIFIER_RANGE_BLOCKABLE is not set") fix a "sleeping from
invalid
context" BUG caused by unmap_stage2_range
Hugh Dickins' found a memcg change bug on original version:
If we want to change the pgdat->lru_lock to memcg's lruvec lock, we have
to serialize mem_cgroup_move_account during pagevec_lru_move_fn. The
possible bad scenario would like:
cpu 0 cpu 1
lruvec =
uen día mi buen amigo.
Cómo estás hoy? Ha pasado mucho tiempo escuché de ti, lo que está pasando
¿tu lado? Hoy estoy muy feliz de informarles sobre mi éxito en
obtener esos fondos de herencia transferidos bajo la cooperación de un nuevo
socio de India Asia. Es canadiense pero vive en la India, per
The func only has one caller, remove it to clean up code and simplify
code.
Signed-off-by: Alex Shi
Cc: Kirill A. Shutemov
Cc: Vlastimil Babka
Cc: Andrew Morton
Cc: linux...@kvack.org
Cc: linux-kernel@vger.kernel.org
---
mm/mlock.c | 22 --
1 file changed, 4 insertions(+),
From: Alexander Duyck
The release_pages function has a number of paths that end up with the
LRU lock having to be released and reacquired. Such an example would be the
freeing of THP pages as it requires releasing the LRU lock so that it can
be potentially reacquired by __put_compound_page.
In o
From: Alexander Duyck
Since we are holding a reference to the page much sooner in
isolate_migratepages_block we can move the PageCompound check out of the
LRU locked section and instead just place it after get_page_unless_zero. By
doing this we can allow any of the items that might trigger a fail
From: Hugh Dickins
Add READ_ONCE on page->mem_cgroup, since we will check it later.
Also the page should not be PageTail(page), so add a check.
Signed-off-by: Hugh Dickins
Signed-off-by: Alex Shi
Cc: Andrew Morton
Cc: Johannes Weiner
Cc: Michal Hocko
Cc: Vladimir Davydov
Cc: linux-kernel@v
From: Alexander Duyck
In isolate_lru_pages we have an exception path where if we call
get_page_unless_zero and that succeeds, but TestClearPageLRU fails we call
put_page. Normally this would be problematic but due to the way that the
calls are ordered and the fact that we are holding the LRU lock
We have to move lru_lock into lru_note_cost, since it cycle up on memcg
tree, for future per lruvec lru_lock replace. It's a bit ugly and may
cost a bit more locking, but benefit from multiple memcg locking could
cover the lost.
Signed-off-by: Alex Shi
Cc: Johannes Weiner
Cc: Andrew Morton
Cc:
From: Alexander Duyck
The only user of test_and_set_skip was isolate_migratepages_block and it
was using it after a call that was testing and clearing the LRU flag. As
such it really didn't need to be behind the LRU lock anymore as it wasn't
really fulfilling its purpose.
Since it is only possib
901 - 1000 of 2272 matches
Mail list logo
