On 2016/11/27 01:46PM, Nicholas Piggin wrote:
> On Sat, 26 Nov 2016 18:30:15 +1100
> Michael Ellerman wrote:
>
> > Nicholas Piggin writes:
> > > On Thu, 24 Nov 2016 00:02:08 +1100
> > > diff --git a/arch/powerpc/Makefile b/arch/powerpc/Makefile
> > > index 617dece..8828807 100644
> > > --- a/arc
/20170202-135830
base: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next
config: powerpc-defconfig (attached as .config)
compiler: powerpc64-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
wget
https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin
/20170202-135830
base: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next
config: powerpc-allmodconfig (attached as .config)
compiler: powerpc64-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
wget
https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain
> @@ -100,6 +132,8 @@ config PPC
> select HAVE_EFFICIENT_UNALIGNED_ACCESS if !(CPU_LITTLE_ENDIAN &&
> POWER7_CPU)
> select HAVE_KPROBES
> select HAVE_ARCH_KGDB
> + select HAVE_ARCH_MMAP_RND_BITS
> + select HAVE_ARCH_MMAP_RND_COMPAT_BITS if COMPAT
COMPAT is on for ppc64 b
On Tue, Jan 31, 2017 at 02:20:20PM -0600, Bjorn Helgaas wrote:
> This is a DT-only driver, so the only way to call rcar_pcie_probe() is to
> match an entry in rcar_pcie_of_match[], so of_id cannot be NULL.
>
> Furthermore, of_id->data can only be NULL if an rcar_pcie_of_match[] entry
> has a NULL
Michael Ellerman writes:
> Currently the kconfig logic for VFIO_IOMMU_SPAPR_TCE and VFIO_SPAPR_EEH
> is broken when SPAPR_TCE_IOMMU=n. Leading to:
>
> warning: (VFIO) selects VFIO_IOMMU_SPAPR_TCE which has unmet direct
> dependencies (VFIO && SPAPR_TCE_IOMMU)
> warning: (VFIO) selects VF
Bhupesh Sharma writes:
> powerpc: arch_mmap_rnd() uses hard-coded values, (23-PAGE_SHIFT) for
> 32-bit and (30-PAGE_SHIFT) for 64-bit, to generate the random offset
> for the mmap base address.
>
> This value represents a compromise between increased
> ASLR effectiveness and avoiding address-spac
Vicky writes:
>> On Jan 26, 2017, at 5:58 PM, Ashley Lai wrote:
>>
>> Adding Vicky from IBM.
>>
>>
>> On 01/26/2017 04:05 PM, Jason Gunthorpe wrote:
>>> On Thu, Jan 26, 2017 at 09:22:48PM +0100, Michal Such??nek wrote:
>>>
This is repeated a few times in the driver so I added memset to
On Wed, 1 Feb 2017 23:40:33 -0500
Vicky wrote:
> > On Jan 26, 2017, at 5:58 PM, Ashley Lai
> > wrote:
> >
> > Adding Vicky from IBM.
> >
> >
> > On 01/26/2017 04:05 PM, Jason Gunthorpe wrote:
> >> On Thu, Jan 26, 2017 at 09:22:48PM +0100, Michal Such??nek wrote:
> >>
> >>> This is repeat
On Thu, 2017-01-12 at 10:17:33 UTC, Anton Blanchard wrote:
> From: Anton Blanchard
>
> We added support for HAVE_CONTEXT_TRACKING, but placed the option inside
> PPC_PSERIES.
>
> This has the undesirable effect that NO_HZ_FULL can be enabled on a
> kernel with both powernv and pseries support, b
On Mon, 2017-01-30 at 06:41:53 UTC, Daniel Axtens wrote:
> In __get_user_check, we create an intermediate pointer for the
> user address we're about to fetch. We currently don't tag this
> pointer as const. Make it const, as we are simply dereferencing
> it, and it's scope is limited to the __get_u
On Fri, 2017-01-06 at 19:25:53 UTC, John Allen wrote:
> When adding and removing LMBs we should make the acquire/release of
> the DRC a separate step to allow for a few improvements. First
> this will ensure that LMBs removed during a remove by count operation
> are all available if a error occurs
On Thu, 2017-01-05 at 11:08:15 UTC, Madhavan Srinivasan wrote:
> Signed-off-by: Madhavan Srinivasan
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/e71ff89c712cb387914abff373ac83
cheers
On Wed, 2017-02-01 at 02:23:44 UTC, Michael Ellerman wrote:
> CONFIG_PPC_PTDUMP currently selects CONFIG_DEBUG_FS. But CONFIG_DEBUG_FS
> is user-selectable, so we shouldn't select it. Instead depend on it.
>
> Signed-off-by: Michael Ellerman
Applied to powerpc next.
https://git.kernel.org/power
On Wed, 2017-01-11 at 17:00:58 UTC, Nathan Fontenot wrote:
> As we add the ability to do DLPAR of additional devices through
> the sysfs interface we need to know which devices are supported.
> This adds the reporting of supported devices with a comma separated
> list reported in the existing /sys/
On Wed, 2017-02-01 at 06:00:11 UTC, Michael Ellerman wrote:
> Add a few things that have been missed from .gitignore over the years.
>
> Signed-off-by: Michael Ellerman
Applied to powerpc next.
https://git.kernel.org/powerpc/c/4eb43875a1859b8d4fb6c56a441a18
cheers
On Thu 2017-01-19 09:46:21, Josh Poimboeuf wrote:
> Change livepatch to use a basic per-task consistency model. This is the
> foundation which will eventually enable us to patch those ~10% of
> security patches which change function or data semantics. This is the
> biggest remaining piece needed
IMPORTANT: Please, forget this version. It is few days old
and incomplete and probably wrong.
I am sorry for confusion.
Best Regards,
Petr
!!! This is the right version. I am sorry again for the confusion. !!!
> Change livepatch to use a basic per-task consistency model. This is the
> foundation which will eventually enable us to patch those ~10% of
> security patches which change function or data semantics. This is the
> biggest r
On Thu, Feb 02, 2017 at 09:23:33PM +1100, Michael Ellerman wrote:
> +config ARCH_MMAP_RND_BITS_MIN
> + # On 64-bit up to 1G of address space (2^30)
> + default 12 if 64BIT && PPC_256K_PAGES # 256K (2^18), = 30 - 18 = 12
> + default 14 if 64BIT && PPC_64K_PAGES# 64K (2^16), = 30 -
On Wed, Feb 1, 2017 at 9:42 PM, Bhupesh Sharma wrote:
> This RFC patchset tries to make the powerpc ASLR elf randomness
> implementation similar to other ARCHs (like x86).
>
> The 1st patch introduces the support of ARCH_MMAP_RND_BITS in powerpc
> mmap implementation to allow a sane balance betwee
On Wed, Feb 1, 2017 at 9:42 PM, Bhupesh Sharma wrote:
> powerpc: arch_mmap_rnd() uses hard-coded values, (23-PAGE_SHIFT) for
> 32-bit and (30-PAGE_SHIFT) for 64-bit, to generate the random offset
> for the mmap base address.
>
> This value represents a compromise between increased
> ASLR effective
Signed-off-by: Nicholas Piggin
---
Hi,
This goes with the previous NMI IPI series, and a new version of
Alistair's opal API I posted to the skiboot list.
Only RFC until the firmware API is agreed on.
Thanks,
Nick
arch/powerpc/include/asm/opal-api.h| 21 -
arch/
On Wed, 1 Feb 2017, Josh Poimboeuf wrote:
> For live patching and possibly other use cases, a stack trace is only
> useful if it can be assured that it's completely reliable. Add a new
> save_stack_trace_tsk_reliable() function to achieve that.
>
> Note that if the target task isn't the current
I was hoping this would be any easy fix, but now it looks like it will
be more difficult.
The basic problem is that xmon memory commands like 'dd' do not properly
display the data on LE instances. This means that not only is it
difficult to read but one cannot copy-paste addresses from the ou
On Wed 2017-02-01 14:02:43, Josh Poimboeuf wrote:
> On Thu, Jan 19, 2017 at 09:46:08AM -0600, Josh Poimboeuf wrote:
> > Here's v4, based on linux-next/master. Mostly minor changes this time,
> > primarily due to Petr's v3 comments.
>
> So far, the only review comments have been related to the fir
From: Michal Suchánek
> Sent: 02 February 2017 11:30
...
> The word is marked correctly as __be64 in that patch because count and
> handle are swapped to BE when saved to it and the whole word is then
> swapped again when loaded. If you just load ((u64)IBMVTPM_VALID_CMD <<
> 56 | ((u64)VTPM_TPM_COM
On Tue, Jan 31, 2017 at 10:22:47AM -0700, Ross Zwisler wrote:
> On Tue, Jan 31, 2017 at 4:48 AM, Mike Galbraith wrote:
> > On Tue, 2017-01-31 at 16:30 +0530, Sachin Sant wrote:
Could some of you test this? It seems to cure things in my (very)
limited testing.
---
diff --git a/kernel/sched/core.
On Thu, 02 Feb 2017 20:50:48 +1100
Michael Ellerman wrote:
> Michael Ellerman writes:
>
> > Currently the kconfig logic for VFIO_IOMMU_SPAPR_TCE and VFIO_SPAPR_EEH
> > is broken when SPAPR_TCE_IOMMU=n. Leading to:
> >
> > warning: (VFIO) selects VFIO_IOMMU_SPAPR_TCE which has unmet direct
On 01/26/2017 11:06 AM, Robert Richter wrote:
> On 26.01.17 10:46:43, William Cohen wrote:
>> From 7e46dbd7dc5bc941926a4a63c28ccebf46493e8d Mon Sep 17 00:00:00 2001
>> From: William Cohen
>> Date: Thu, 26 Jan 2017 10:33:59 -0500
>> Subject: [PATCH] Avoid hypthetical string truncation in oprofile s
On Wed, Feb 01, 2017 at 11:46:23PM +, Chris Packham wrote:
> >> diff --git a/drivers/edac/mpc85xx_edac.c b/drivers/edac/mpc85xx_edac.c
> >> index 8f66cbed70b7..67f7bc3fe5b3 100644
> >> --- a/drivers/edac/mpc85xx_edac.c
> >> +++ b/drivers/edac/mpc85xx_edac.c
> >> @@ -629,6 +629,7 @@ static const
Hi Kees,
On Thu, Feb 2, 2017 at 7:55 PM, Kees Cook wrote:
> On Wed, Feb 1, 2017 at 9:42 PM, Bhupesh Sharma wrote:
>> powerpc: arch_mmap_rnd() uses hard-coded values, (23-PAGE_SHIFT) for
>> 32-bit and (30-PAGE_SHIFT) for 64-bit, to generate the random offset
>> for the mmap base address.
>>
>> Th
On Tue, Jul 19, 2016 at 10:02 PM, Yuantian Tang wrote:
>
> PING.
>
> Regards,
> Yuantian
>
> > -Original Message-
> > From: Scott Wood [mailto:o...@buserror.net]
> > Sent: Saturday, July 09, 2016 5:07 AM
> > To: Michael Turquette ; Russell King
> > ; Stephen Boyd ; Viresh
> > Kumar ; Rafae
HI Balbir,
On Thu, Feb 2, 2017 at 2:41 PM, Balbir Singh wrote:
>> @@ -100,6 +132,8 @@ config PPC
>> select HAVE_EFFICIENT_UNALIGNED_ACCESS if !(CPU_LITTLE_ENDIAN &&
>> POWER7_CPU)
>> select HAVE_KPROBES
>> select HAVE_ARCH_KGDB
>> + select HAVE_ARCH_MMAP_RND_BITS
>> + s
Hi Kees,
Thanks for the review.
Please see my comments inline.
On Thu, Feb 2, 2017 at 7:51 PM, Kees Cook wrote:
> On Wed, Feb 1, 2017 at 9:42 PM, Bhupesh Sharma wrote:
>> This RFC patchset tries to make the powerpc ASLR elf randomness
>> implementation similar to other ARCHs (like x86).
>>
>> T
Hi Balbir,
On Thu, Feb 2, 2017 at 12:14 PM, Balbir Singh wrote:
> On Thu, Feb 02, 2017 at 11:12:46AM +0530, Bhupesh Sharma wrote:
>> This RFC patchset tries to make the powerpc ASLR elf randomness
>> implementation similar to other ARCHs (like x86).
>>
>> The 1st patch introduces the support of A
Hi,
On Wednesday, February 01, 2017 07:55:25 AM Mathieu Malaterre wrote:
> Any chance this patch could be considered for inclusion this time ?
>
> Thanks
>
> On Wed, Nov 23, 2016 at 8:26 AM, Mathieu Malaterre wrote:
> > When the linux kernel is build with (typical kernel ship with Debian
> > i
On Thu, Feb 2, 2017 at 10:08 AM, Bhupesh Sharma wrote:
> On Thu, Feb 2, 2017 at 7:51 PM, Kees Cook wrote:
>> On Wed, Feb 1, 2017 at 9:42 PM, Bhupesh Sharma wrote:
>>> The 2nd patch increases the ELF_ET_DYN_BASE value from the current
>>> hardcoded value of 0x2000_ to something more practical
On 3 Feb 2017 00:49, "Kees Cook" wrote:
On Thu, Feb 2, 2017 at 10:08 AM, Bhupesh Sharma wrote:
> On Thu, Feb 2, 2017 at 7:51 PM, Kees Cook wrote:
>> On Wed, Feb 1, 2017 at 9:42 PM, Bhupesh Sharma
wrote:
>>> The 2nd patch increases the ELF_ET_DYN_BASE value from the current
>>> hardcoded value
On Thu, 02 Feb, at 04:55:06PM, Peter Zijlstra wrote:
> On Tue, Jan 31, 2017 at 10:22:47AM -0700, Ross Zwisler wrote:
> > On Tue, Jan 31, 2017 at 4:48 AM, Mike Galbraith wrote:
> > > On Tue, 2017-01-31 at 16:30 +0530, Sachin Sant wrote:
>
>
> Could some of you test this? It seems to cure things i
Hi all,
Today's linux-next merge of the powerpc tree got a conflict in:
arch/powerpc/Kconfig
between commit:
f2574030b0e3 ("powerpc: Revert the initial stack protector support")
from the powerpc-fixes tree and commit:
d6c569b99558 ("powerpc/64: Move HAVE_CONTEXT_TRACKING from pseries to
Borislav Petkov writes:
> On Wed, Feb 01, 2017 at 11:46:23PM +, Chris Packham wrote:
>> >> diff --git a/drivers/edac/mpc85xx_edac.c b/drivers/edac/mpc85xx_edac.c
>> >> index 8f66cbed70b7..67f7bc3fe5b3 100644
>> >> --- a/drivers/edac/mpc85xx_edac.c
>> >> +++ b/drivers/edac/mpc85xx_edac.c
>> >>
Balbir Singh writes:
> On Thu, Feb 02, 2017 at 09:23:33PM +1100, Michael Ellerman wrote:
>> +config ARCH_MMAP_RND_BITS_MIN
>> +# On 64-bit up to 1G of address space (2^30)
>> +default 12 if 64BIT && PPC_256K_PAGES # 256K (2^18), = 30 - 18 = 12
>> +default 14 if 64BIT && PPC_64K_PAGE
On 03/02/17 12:55, Michael Ellerman wrote:
> Chris if you want to send a patch to add the compatible string to the
> l2cache.txt I would merge that, but honestly it doesn't achieve much
> other than possibly catching a typo in the compatible name.
I think catching a typo might be worthwhile. It's
List all the current valid compatible strings for the l2cache binding.
This should stop checkpatch.pl from complaining and will hopefully save
someone from having to debug a typo in their dts.
Signed-off-by: Chris Packham
---
.../devicetree/bindings/powerpc/fsl/l2cache.txt| 42 ++
Douglas Miller writes:
> I was hoping this would be any easy fix, but now it looks like it will
> be more difficult.
>
> The basic problem is that xmon memory commands like 'dd' do not properly
> display the data on LE instances. This means that not only is it
> difficult to read but one canno
Hi all,
Today's linux-next merge of the rcu tree got a conflict in:
arch/powerpc/Kconfig
between commit:
d6c569b99558 ("powerpc/64: Move HAVE_CONTEXT_TRACKING from pseries to common
Kconfig")
from the powerpc tree and commit:
c7327406b3c3 ("rcu: Make arch select smp_mb__after_unlock_lo
I'm referring to the three commands listed in the help:
d dump bytes
dfdump float values
dddump double values
As it turns out, all three of these commands do exactly the same thing,
and it's certainly not what I'd expect based on experience with other
debuggers. Maybe the origina
On Thu, 2017-02-02 at 16:55 +0100, Peter Zijlstra wrote:
> On Tue, Jan 31, 2017 at 10:22:47AM -0700, Ross Zwisler wrote:
> > On Tue, Jan 31, 2017 at 4:48 AM, Mike Galbraith
> > wrote:
> > > On Tue, 2017-01-31 at 16:30 +0530, Sachin Sant wrote:
>
>
> Could some of you test this? It seems to cure
+++ Ard Biesheuvel [24/01/17 16:16 +]:
This v4 is a followup to [0] 'modversions: redefine kcrctab entries as
relative CRC pointers', but since relative CRC pointers do not work in
modules, and are actually only needed by powerpc with CONFIG_RELOCATABLE=y,
I have made it a Kconfig selectable
b4e8]
ret_from_kernel_thread+0x5c/0x74
[ 243.913715] INFO: task kworker/0:2:380 blocked for more than 120 seconds.
[ 243.913732] Not tainted 4.10.0-rc6-next-20170202 #6
[ 243.913735] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[ 243.913738] kworker/
+++ Jessica Yu [02/02/17 22:54 -0500]:
+++ Ard Biesheuvel [24/01/17 16:16 +]:
This v4 is a followup to [0] 'modversions: redefine kcrctab entries as
relative CRC pointers', but since relative CRC pointers do not work in
modules, and are actually only needed by powerpc with CONFIG_RELOCATABLE
powerpc: arch_mmap_rnd() uses hard-coded values, (23-PAGE_SHIFT) for
32-bit and (30-PAGE_SHIFT) for 64-bit, to generate the random offset
for the mmap base address.
This value represents a compromise between increased
ASLR effectiveness and avoiding address-space fragmentation.
Replace it with a K
Chris Packham writes:
> On 03/02/17 12:55, Michael Ellerman wrote:
>> Chris if you want to send a patch to add the compatible string to the
>> l2cache.txt I would merge that, but honestly it doesn't achieve much
>> other than possibly catching a typo in the compatible name.
>
> I think catching a
On Fri, 3 Feb 2017 00:25:11 +1000
Nicholas Piggin wrote:
> This goes with the previous NMI IPI series, and a new version of
> Alistair's opal API I posted to the skiboot list.
And here is the incremental bit that is required for Alistair's
hardware implementation to work.
If the opal broacast
On Fri, 3 Feb 2017 03:20:48 PM Nicholas Piggin wrote:
> On Fri, 3 Feb 2017 00:25:11 +1000
> Nicholas Piggin wrote:
>
> > This goes with the previous NMI IPI series, and a new version of
> > Alistair's opal API I posted to the skiboot list.
>
> And here is the incremental bit that is required for
When autonuma marks a PTE inaccessible it clears all the protection
bits but leave the PTE valid.
With the Radix MMU, an attempt at executing from such a PTE will
take a fault with bit 35 of SRR1 set "SRR1_ISI_N_OR_G".
It is thus incorrect to treat all such faults as errors. We should
pass them t
On Fri, 03 Feb 2017 17:00:19 +1100
Alistair Popple wrote:
> On Fri, 3 Feb 2017 03:20:48 PM Nicholas Piggin wrote:
> > On Fri, 3 Feb 2017 00:25:11 +1000
> > Nicholas Piggin wrote:
> >
> > > This goes with the previous NMI IPI series, and a new version of
> > > Alistair's opal API I posted to t
Benjamin Herrenschmidt writes:
> When autonuma marks a PTE inaccessible it clears all the protection
> bits but leave the PTE valid.
>
> With the Radix MMU, an attempt at executing from such a PTE will
> take a fault with bit 35 of SRR1 set "SRR1_ISI_N_OR_G".
>
> It is thus incorrect to treat all
During an eeh event when the cxl card is fenced and card sysfs attr
perst_reloads_same_image is set following warning message is seen in the
kernel logs:
[ 60.622727] Adapter context unlocked with 0 active contexts
[ 60.622762] [ cut here ]
[ 60.622771] WARNING: CP
60 matches
Mail list logo
