Le 12/07/2019 à 08:25, Michael Ellerman a écrit :
"Aneesh Kumar K.V" writes:
Avoids confusion when printing Oops message like below
Faulting instruction address: 0xc008bdb4
Oops: Kernel access of bad area, sig: 11 [#1]
LE PAGE_SIZE=64K MMU=Radix MMU=Hash SMP NR_CPUS=2048 NUMA
On Fri, Jul 12, 2019 at 05:14:54AM +0100, Al Viro wrote:
> That's not quite guaranteed (it is possible to bind a symlink on top
> of a regular file, and you will get LOOKUP_JUMPED on the entry into
> trailing_symlink() when looking the result up). Moreover, why bother
> with LOOKUP_JUMPED here?
Nicholas Piggin writes:
> Claudio Carvalho's on June 29, 2019 6:08 am:
>> From: Sukadev Bhattiprolu
>>
>> The ultravisor processor mode is introduced in POWER platforms that
>> supports the Protected Execution Facility (PEF). Ultravisor is higher
>> privileged than hypervisor mode.
>>
>> In PE
"Aneesh Kumar K.V" writes:
> Avoids confusion when printing Oops message like below
>
> Faulting instruction address: 0xc008bdb4
> Oops: Kernel access of bad area, sig: 11 [#1]
> LE PAGE_SIZE=64K MMU=Radix MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV
>
> This was because we never clear the M
Secure Encrypted Virtualization is an x86-specific feature, so it shouldn't
appear in generic kernel code because it forces non-x86 architectures to
define the sev_active() function, which doesn't make a lot of sense.
To solve this problem, add an x86 elfcorehdr_read() function to override
the gen
Secure Memory Encryption is an x86-specific feature, so it shouldn't appear
in generic kernel code.
Introduce ARCH_HAS_DMA_CHECK_MASK so that x86 can define its own
dma_check_mask() for the SME check.
In SWIOTLB code, there's no need to mention which memory encryption
feature is active. Also, oth
powerpc and s390 are going to use this feature as well, so put it in a
generic location.
Signed-off-by: Thiago Jung Bauermann
---
arch/Kconfig | 3 +++
arch/x86/Kconfig | 4 +---
2 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/arch/Kconfig b/arch/Kconfig
index c47b328eada0..4e
Hello,
Both powerpc¹ and s390² are adding headers. Currently,
they have to supply definitions for functions and macros which only have a
meaning on x86: sme_me_mask, sme_active() and sev_active().
Christoph Hellwig made a suggestion to "clean up the Kconfig and generic
headers bits for memory en
Le 11/07/2019 à 16:58, Aneesh Kumar K.V a écrit :
Avoids confusion when printing Oops message like below
Faulting instruction address: 0xc008bdb4
Oops: Kernel access of bad area, sig: 11 [#1]
LE PAGE_SIZE=64K MMU=Radix MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV
This was because we
On Sun, Jul 07, 2019 at 12:57:32AM +1000, Aleksa Sarai wrote:
> @@ -1442,8 +1464,11 @@ static int follow_dotdot_rcu(struct nameidata *nd)
> struct inode *inode = nd->inode;
>
> while (1) {
> - if (path_equal(&nd->path, &nd->root))
> + if (path_equal(&nd->path,
> > The cpu variable is still being used in the of_get_property() call
> > after the of_node_put() call, which may result in use-after-free.
> >
> > Fixes: a9acc26b75f6 ("cpufreq/pasemi: fix possible object reference leak")
> > Signed-off-by: Wen Yang
> > Cc: "Rafael J. Wysocki"
> > Cc: Viresh Ku
On Sun, Jul 07, 2019 at 12:57:31AM +1000, Aleksa Sarai wrote:
> Previously, path_init's handling of *at(dfd, ...) was only done once,
> but with LOOKUP_BENEATH (and LOOKUP_IN_ROOT) we have to parse the
> initial nd->path at different times (before or after absolute path
> handling) depending on whe
On Sun, Jul 07, 2019 at 12:57:28AM +1000, Aleksa Sarai wrote:
> @@ -514,7 +516,14 @@ static void set_nameidata(struct nameidata *p, int dfd,
> struct filename *name)
> p->stack = p->internal;
> p->dfd = dfd;
> p->name = name;
> - p->total_link_count = old ? old->total_link_c
On 12-07-19, 10:44, Wen Yang wrote:
> The cpu variable is still being used in the of_get_property() call
> after the of_node_put() call, which may result in use-after-free.
>
> Fixes: a9acc26b75f6 ("cpufreq/pasemi: fix possible object reference leak")
> Signed-off-by: Wen Yang
> Cc: "Rafael J. Wy
It always returns 0 (success) and its return type should really be void.
Over that, many drivers have added error handling code based on its
return value, which is not required at all.
change its return type to void and update all the callers.
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/bmi
Since we move 'ia64' docs to Documentation/arch/ia64 dir,
redirect the doc pointer to them.
Signed-off-by: Alex Shi
Cc: Ard Biesheuvel
Cc: Tony Luck
Cc: Fenghua Yu
Cc: linux-ker...@vger.kernel.org
Cc: linux-i...@vger.kernel.org
---
MAINTAINERS | 2 +-
arch/ia64/kernel/efi.c | 2 +
Since we move Documentation/s390 docs to Documentation/arch/s390
dir, redirect the doc pointer to them.
Signed-off-by: Alex Shi
Cc: Jonathan Corbet
Cc: Heiko Carstens
Cc: Vasily Gorbik
Cc: Christian Borntraeger
Cc: linux-...@vger.kernel.org
Cc: linux-ker...@vger.kernel.org
Cc: linux-s...@vger
Since we move Documentation/powerpc docs to Documentation/arch/powerpc
dir, redirect the doc pointer to them.
Signed-off-by: Alex Shi
Cc: Sam Bobroff
Cc: Jonathan Corbet
Cc: "Manoj N. Kumar"
Cc: "Matthew R. Ochs"
Cc: Uma Krishnan
Cc: linuxppc-dev@lists.ozlabs.org
Cc: linux-...@vger.kernel.or
Since we move Documentation/m68k docs to Documentation/arch/m68k
dir, redirect the doc pointer to them.
Signed-off-by: Alex Shi
Cc: Jonathan Corbet
Cc: Will Deacon
Cc: linux-...@vger.kernel.org
Cc: linux-ker...@vger.kernel.org
---
Documentation/admin-guide/kernel-parameters.rst | 2 +-
1 file
Since we move Documentation/x86 docs to Documentation/arch/x86
dir, redirect the doc pointer to them.
Signed-off-by: Alex Shi
Cc: Jonathan Corbet
Cc: Tony Luck
Cc: "H. Peter Anvin"
Cc: x...@kernel.org
Cc: Peter Zijlstra
Cc: Changbin Du
Cc: linux-...@vger.kernel.org
Cc: linux-ker...@vger.kern
Since we move Documentation/sparc docs to Documentation/arch/sparc
dir, redirect the doc pointer to them.
Signed-off-by: Alex Shi
Cc: Jonathan Corbet
Cc: linux-...@vger.kernel.org
Cc: sparcli...@vger.kernel.org
Cc: linux-ker...@vger.kernel.org
---
drivers/sbus/char/oradax.c | 2 +-
1 file chang
Since we move Documentation/mips docs to Documentation/arch/mips
dir, redirect the doc pointer to them.
Signed-off-by: Alex Shi
Cc: Mauro Carvalho Chehab
Cc: "David S. Miller"
Cc: linux-ker...@vger.kernel.org
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/M
There are many different archs in Documentation/ dir, it's better to
move them together in 'Documentation/arch' which follows from kernel source.
Signed-off-by: Alex Shi
Cc: Jonathan Corbet
Cc: linux-...@vger.kernel.org
Cc: linux-ker...@vger.kernel.org
Cc: linux-st...@st-md-mailman.stormreply.co
Since we move Documentation/xtensa docs to Documentation/arch/xtensa
dir, redirect the doc pointer to them.
Signed-off-by: Alex Shi
Cc: Jonathan Corbet
Cc: linux-...@vger.kernel.org
Cc: Chris Zankel
Cc: Max Filippov
Cc: linux-xte...@linux-xtensa.org
Cc: linux-ker...@vger.kernel.org
---
arch/x
Since we move 'arm/arm64' docs to Documentation/arch/{arm,arm64} dir,
redirect the doc pointer to them.
Signed-off-by: Alex Shi
Cc: Jonathan Corbet
Cc: Kukjin Kim
Cc: Krzysztof Kozlowski
Cc: linux-...@vger.kernel.org
Cc: linux-ker...@vger.kernel.org
Cc: linux-arm-ker...@lists.infradead.org
Cc:
Since we move Documentation/sh docs to Documentation/arch/sh
dir, redirect the doc pointer to them.
Signed-off-by: Alex Shi
Cc: Jonathan Corbet
Cc: linux-...@vger.kernel.org
Cc: linux-ker...@vger.kernel.org
Cc: linux...@vger.kernel.org
---
Documentation/conf.py | 2 +-
MAINTAINERS | 2
Since we move Documentation/parisc docs to Documentation/arch/parisc
dir, redirect the doc pointer to them.
Signed-off-by: Alex Shi
Cc: Mauro Carvalho Chehab
Cc: linux-ker...@vger.kernel.org
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTA
The cpu variable is still being used in the of_get_property() call
after the of_node_put() call, which may result in use-after-free.
Fixes: a9acc26b75f6 ("cpufreq/pasemi: fix possible object reference leak")
Signed-off-by: Wen Yang
Cc: "Rafael J. Wysocki"
Cc: Viresh Kumar
Cc: Michael Ellerman
On Thu, Jul 11, 2019 at 11:25:44PM +, Hoan Tran OS wrote:
> In NUMA layout which nodes have memory ranges that span across other nodes,
> the mm driver can detect the memory node id incorrectly.
>
> For example, with layout below
> Node 0 address:
> Node 1 address: 111
https://bugzilla.kernel.org/show_bug.cgi?id=204125
--- Comment #7 from Daniel Kolesa (li...@octaforge.org) ---
Btw, turns out an ELFv2 BE kernel requires little to no changes, these two
commits produce a working kernel:
https://github.com/smaeul/linux/commit/7a9d26b7be68c21fd1be524ee4bf797d7b8c3c
Claudio Carvalho's on June 29, 2019 6:08 am:
> From: Sukadev Bhattiprolu
>
> To enter a secure guest, we have to go through the ultravisor, therefore
> we do a ucall when we are entering a secure guest.
>
> This change is needed for any sort of entry to the secure guest from the
> hypervisor, wh
https://bugzilla.kernel.org/show_bug.cgi?id=204125
--- Comment #6 from Daniel Kolesa (li...@octaforge.org) ---
This appears to be the actual reason why the kernel fails to link without
-mcall-aixdesc:
specifically it's the -mcall-aixdesc that's problematic. but removing
it breaks recordmcount.pl
Claudio Carvalho's on June 29, 2019 6:08 am:
> From: Ram Pai
>
> Add the ucall() function, which can be used to make ultravisor calls
> with varied number of in and out arguments. Ultravisor calls can be made
> from the host or guests.
>
> This copies the implementation of plpar_hcall().
>
> Si
Michael Ellerman's on July 11, 2019 10:57 pm:
> Claudio Carvalho writes:
>> From: Sukadev Bhattiprolu
>>
>> The ultravisor processor mode is introduced in POWER platforms that
>> supports the Protected Execution Facility (PEF). Ultravisor is higher
>> privileged than hypervisor mode.
>>
>> In PEF
Claudio Carvalho's on June 29, 2019 6:08 am:
> From: Sukadev Bhattiprolu
>
> The ultravisor processor mode is introduced in POWER platforms that
> supports the Protected Execution Facility (PEF). Ultravisor is higher
> privileged than hypervisor mode.
>
> In PEF enabled platforms, the MSR_S bit
Aneesh Kumar K.V's on July 12, 2019 12:58 am:
> Avoids confusion when printing Oops message like below
>
> Faulting instruction address: 0xc008bdb4
> Oops: Kernel access of bad area, sig: 11 [#1]
> LE PAGE_SIZE=64K MMU=Radix MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV
>
> This was because w
Remove CONFIG_NODES_SPAN_OTHER_NODES as it's enabled
by default with NUMA.
Signed-off-by: Hoan Tran
---
arch/s390/Kconfig | 8
1 file changed, 8 deletions(-)
diff --git a/arch/s390/Kconfig b/arch/s390/Kconfig
index 109243f..788a8e9 100644
--- a/arch/s390/Kconfig
+++ b/arch/s390/Kconfig
Remove CONFIG_NODES_SPAN_OTHER_NODES as it's enabled
by default with NUMA.
Signed-off-by: Hoan Tran
---
arch/sparc/Kconfig | 9 -
1 file changed, 9 deletions(-)
diff --git a/arch/sparc/Kconfig b/arch/sparc/Kconfig
index 26ab6f5..13449ea 100644
--- a/arch/sparc/Kconfig
+++ b/arch/sparc/K
Remove CONFIG_NODES_SPAN_OTHER_NODES as it's enabled
by default with NUMA.
Signed-off-by: Hoan Tran
---
arch/x86/Kconfig | 9 -
1 file changed, 9 deletions(-)
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 2bbbd4d..fa9318c 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@
Remove CONFIG_NODES_SPAN_OTHER_NODES as it's enabled by
default with NUMA.
Signed-off-by: Hoan Tran
---
arch/powerpc/Kconfig | 9 -
1 file changed, 9 deletions(-)
diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
index 8c1c636..bdde8bc 100644
--- a/arch/powerpc/Kconfig
+++ b/arch
In NUMA layout which nodes have memory ranges that span across other nodes,
the mm driver can detect the memory node id incorrectly.
For example, with layout below
Node 0 address:
Node 1 address:
Note:
- Memory from low to high
- 0/1: Node id
- x: Invali
In NUMA layout which nodes have memory ranges that span across other nodes,
the mm driver can detect the memory node id incorrectly.
For example, with layout below
Node 0 address:
Node 1 address:
Note:
- Memory from low to high
- 0/1: Node id
- x: Invali
Hi Anshuman,
On Mon, 8 Jul 2019 09:03:13 +0530
Anshuman Khandual wrote:
> >> Architectures like parisc enable CONFIG_KROBES without having a definition
> >> for kprobe_fault_handler() which results in a build failure.
> >
> > Hmm, as far as I can see, kprobe_fault_handler() is closed inside eac
On Thu, Jul 11, 2019 at 11:28:24PM +0300, Jarkko Sakkinen wrote:
> On Thu, Jul 11, 2019 at 12:13:35PM -0400, Nayna Jain wrote:
> > The nr_allocated_banks and allocated banks are initialized as part of
> > tpm_chip_register. Currently, this is done as part of auto startup
> > function. However, some
On Thu, Jul 11, 2019 at 4:45 PM Joel Fernandes (Google)
wrote:
>
> The rcu_dereference_raw_notrace() API name is confusing.
> It is equivalent to rcu_dereference_raw() except that it also does
> sparse pointer checking.
>
> There are only a few users of rcu_dereference_raw_notrace(). This
> patche
The rcu_dereference_raw_notrace() API name is confusing.
It is equivalent to rcu_dereference_raw() except that it also does
sparse pointer checking.
There are only a few users of rcu_dereference_raw_notrace(). This
patches renames all of them to be rcu_dereference_raw_check with the
"check" indica
On Thu, Jul 11, 2019 at 12:13:35PM -0400, Nayna Jain wrote:
> The nr_allocated_banks and allocated banks are initialized as part of
> tpm_chip_register. Currently, this is done as part of auto startup
> function. However, some drivers, like the ibm vtpm driver, do not run
> auto startup during init
Hi Jarkko,
On 07/09/2019 12:38 PM, Jarkko Sakkinen wrote:
On Mon, Jul 08, 2019 at 03:43:04PM -0700, Christoph Hellwig wrote:
On Mon, Jul 08, 2019 at 06:24:04PM -0400, Mimi Zohar wrote:
static int tpm_get_pcr_allocation(struct tpm_chip *chip)
{
int rc;
rc = (chip->flags & TPM_
On Thu, Jul 11, 2019 at 06:49:46PM +0800, shengjiu.w...@nxp.com wrote:
> From: Shengjiu Wang
>
> There is chip errata ERR008000, the reference doc is
> (https://www.nxp.com/docs/en/errata/IMX6DQCE.pdf),
>
> The issue is "While using ESAI transmit or receive and
> an underrun/overrun happens, cha
The nr_allocated_banks and allocated banks are initialized as part of
tpm_chip_register. Currently, this is done as part of auto startup
function. However, some drivers, like the ibm vtpm driver, do not run
auto startup during initialization. This results in uninitialized memory
issue and causes a
Avoids confusion when printing Oops message like below
Faulting instruction address: 0xc008bdb4
Oops: Kernel access of bad area, sig: 11 [#1]
LE PAGE_SIZE=64K MMU=Radix MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV
This was because we never clear the MMU_FTR_HPTE_TABLE feature flag
even if we
This is similar to what ACPI does. Nvdimm layer doesn't bring the SCM device
numa node online. Hence we need to make sure we always use an online node
as ndr_desc.numa_node. Otherwise this result in kernel crashes. The target
node is used by dax/kmem and that will bring up the numa node online corr
On 07/10/2019 11:35 PM, wen.yan...@zte.com.cn wrote:
>>> we developed a coccinelle script to detect such problems.
>>
>> Would you find the implementation of the function “dt_init_idle_driver”
>> suspicious according to discussed source code search patterns?
>> https://git.kernel.org/pub/scm/linux/
The callback function of call_rcu() just calls a kfree(), so we
can use kfree_rcu() instead of call_rcu() + callback function.
Signed-off-by: YueHaibing
---
arch/powerpc/platforms/powernv/pci-ioda-tce.c | 10 +-
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/arch/powerpc/pl
Claudio Carvalho writes:
> From: Michael Anderson
>
> - Check for MSR_S so that kvmppc_set_msr will include it. Prior to this
>change return to guest would not have the S bit set.
That sounds like it would be bad?
Please spell out what the practical impact of the patch is, ie.
somewhere on
Claudio Carvalho writes:
> From: Sukadev Bhattiprolu
>
> To enter a secure guest, we have to go through the ultravisor, therefore
> we do a ucall when we are entering a secure guest.
>
> This change is needed for any sort of entry to the secure guest from the
> hypervisor, whether it is a return
Claudio Carvalho writes:
> When the ultravisor firmware is available, it takes control over the
> LDBAR register. In this case, thread-imc updates and save/restore
> operations on the LDBAR register are handled by ultravisor.
Please roll up the replies to Alexey's question about LDBAR into the
ch
Claudio Carvalho writes:
> From: Michael Anderson
>
> When running under an ultravisor, the ultravisor controls the real
> partition table and has it in secure memory where the hypervisor can't
> access it, and therefore we (the HV) have to do a ucall whenever we want
> to update an entry.
>
> Th
Claudio Carvalho writes:
> diff --git a/arch/powerpc/include/asm/ultravisor.h
> b/arch/powerpc/include/asm/ultravisor.h
> new file mode 100644
> index ..e5009b0d84ea
> --- /dev/null
> +++ b/arch/powerpc/include/asm/ultravisor.h
> @@ -0,0 +1,15 @@
> +/* SPDX-License-Identifier: GPL-2.0
Claudio Carvalho writes:
> From: Ram Pai
>
> Add the ucall() function, which can be used to make ultravisor calls
> with varied number of in and out arguments. Ultravisor calls can be made
> from the host or guests.
>
> This copies the implementation of plpar_hcall().
.. with quite a few changes
Claudio Carvalho writes:
> From: Sukadev Bhattiprolu
>
> The ultravisor processor mode is introduced in POWER platforms that
> supports the Protected Execution Facility (PEF). Ultravisor is higher
> privileged than hypervisor mode.
>
> In PEF enabled platforms, the MSR_S bit is used to indicate i
Sven Schnelle writes:
> On Wed, Jul 10, 2019 at 05:09:29PM +0200, Christophe Leroy wrote:
>> Le 10/07/2019 à 16:29, Sven Schnelle a écrit :
>> > It had only one definition, so just use the function directly.
>>
>> It had only one definition because it was for ppc64 only.
>> But as far as I unders
From: Shengjiu Wang
Extract the operation to be functions, to improve the
readability.
In this patch, fsl_esai_hw_init, fsl_esai_register_restore,
fsl_esai_trigger_start and fsl_esai_trigger_stop are
extracted.
Signed-off-by: Shengjiu Wang
Acked-by: Nicolin Chen
---
sound/soc/fsl/fsl_esai.c
From: Shengjiu Wang
There is chip errata ERR008000, the reference doc is
(https://www.nxp.com/docs/en/errata/IMX6DQCE.pdf),
The issue is "While using ESAI transmit or receive and
an underrun/overrun happens, channel swap may occur.
The only recovery mechanism is to reset the ESAI."
This issue e
From: Shengjiu Wang
recover the channel swap after xrun
Shengjiu Wang (2):
ASoC: fsl_esai: Wrap some operations to be functions
ASoC: fsl_esai: recover the channel swap after xrun
sound/soc/fsl/fsl_esai.c | 266 ---
1 file changed, 193 insertions(+), 73
On 07/05/2019 11:00 AM, Anshuman Khandual wrote:
> Architectures like parisc enable CONFIG_KROBES without having a definition
> for kprobe_fault_handler() which results in a build failure. Arch needs to
> provide kprobe_fault_handler() as it is platform specific and cannot have
> a generic worki
Santosh Sivaraj's on July 9, 2019 10:15 pm:
> If we take a UE on one of the instructions with a fixup entry, set nip
> to continue execution at the fixup entry. Stop processing the event
> further or print it.
So... what happens if we take a machine check while we happen to be
executing some other
Santosh Sivaraj's on July 9, 2019 10:15 pm:
> From: Balbir Singh
>
> The pmem infrastructure uses memcpy_mcsafe in the pmem layer so as to
> convert machine check exceptions into a return value on failure in case
> a machine check exception is encountered during the memcpy. The return
> value is
Santosh Sivaraj's on July 9, 2019 10:15 pm:
> In real mode, the search_exception tables cannot be called because
> it also searches the module exception tables if entry is not found
> in the kernel exception tables.
This is a patch for generic kernel code, it may not go through
powerpc tree and so
Santosh Sivaraj's on July 9, 2019 10:15 pm:
> From: Balbir Singh
>
> The current code would fail on huge pages addresses, since the shift
> would be incorrect. Use the correct page shift value returned by
> __find_linux_pte() to get the correct pfn. The code is more generic
> and can handle both
> In my experience, when you start looking at these of_node_put things,
> all sorts of strange things appear...
How much will this situation influence the achievement of further improvements
also for your software?
Regards,
Markus
> 180 break; ---> Jump out of
> the loop without releasing it
The device node reference is released behind this for loop.
> 183 if (!of_device_is_available(state_node)) {
> 184 of_node_put(state_node);
Thi
> On 10-Jul-2019, at 8:35 PM, Oliver O'Halloran wrote:
>
> In commit 4a7b06c157a2 ("powerpc/eeh: Handle hugepages in ioremap
> space") support for using hugepages in the vmalloc and ioremap areas was
> enabled for radix. Unfortunately this broke EEH MMIO error checking.
>
> Detection works by
73 matches
Mail list logo
