On 13/03/2015 at 18:12:29 +0100, Nicolas Ferre wrote :
> Another cleanup series on top of the previous one that I sent you this
> afternoon ;-) I think it is the last time that we can remove a whole bunch of
> files and legacy code... We were getting used to it!
Actually, the switch to multiplatfo
Switch AT91 to multiplatform as all SoCs are properly handled.
Signed-off-by: Alexandre Belloni
---
arch/arm/Kconfig| 13 -
arch/arm/mach-at91/Kconfig | 119 +++-
arch/arm/mach-at91/Makefile | 2 +
3 files changed, 52 insertions(+), 82
Signed-off-by: Alexandre Belloni
---
arch/arm/configs/at91_dt_defconfig | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/arch/arm/configs/at91_dt_defconfig
b/arch/arm/configs/at91_dt_defconfig
index 811e72bbe642..bcef49a21801 100644
--- a/arch/arm/configs/at91_dt_defconfig
AT91 is now ready to switch to multiplatform. Do it and clean the remaining mach
includes.
Changes in v3:
- use a menu structure as asked by Arnd
- remove useless selects as pointed by Rob
- drop a patch that has already been applied
- add a patch to remove AT91_TIMER_HZ
Changes in v2:
- mov
Following the switch to multiplatform, uncompress.h is not used anymore. Remove
it.
at91_dbgu.h is also not used anymore
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/include/mach/at91_dbgu.h | 63
arch/arm/mach-at91/include/mach/uncompress.h | 218 --
UEFI Secure Boot provides a mechanism for ensuring that the firmware will
only load signed bootloaders and kernels. Certain use cases may also
require that the kernel prevent userspace from inserting untrusted kernel
code at runtime. Add a configuration option that enforces this automatically
when
Permitting write access to MSRs allows userspace to modify the running
kernel. Prevent this if trusted_kernel is true. Based on a patch by Kees
Cook.
Cc: Kees Cook
Signed-off-by: Matthew Garrett
---
arch/x86/kernel/msr.c | 8
1 file changed, 8 insertions(+)
diff --git a/arch/x86/kerne
We have no way of validating what all of the Asus WMI methods do on a
given machine, and there's a risk that some will allow hardware state to
be manipulated in such a way that arbitrary code can be executed in the
kernel. Prevent that if trusted_kernel is true.
Signed-off-by: Matthew Garrett
---
On Fri, Mar 13, 2015 at 2:45 PM, wrote:
> On Fri, Mar 13, 2015 at 02:33:44PM -0700, Andy Lutomirski wrote:
>> On Fri, Mar 13, 2015 at 12:42 PM, Josh Triplett
>> wrote:
>> > On Fri, Mar 13, 2015 at 04:05:29PM +, David Drysdale wrote:
>> >> On Fri, Mar 13, 2015 at 1:40 AM, Josh Triplett
>>
This fixes the problem on my C8000.
Tested-by: graham.go...@gmail.com
On 13 March 2015 at 21:00, Kirill A. Shutemov
wrote:
> There's hack in pgd_alloc() on parisc to initialize one pmd, which is
> not accounted. It leads to underflow on exit.
>
> Let's adjust nr_pmds on pgd_alloc() to get accoun
On Fri, Mar 13, 2015 at 02:33:44PM -0700, Andy Lutomirski wrote:
> On Fri, Mar 13, 2015 at 12:42 PM, Josh Triplett wrote:
> > On Fri, Mar 13, 2015 at 04:05:29PM +, David Drysdale wrote:
> >> On Fri, Mar 13, 2015 at 1:40 AM, Josh Triplett
> >> wrote:
> >> > This patch series introduces a new
On Fri, Mar 13, 2015 at 02:16:07PM -0700, Thiago Macieira wrote:
> On Friday 13 March 2015 12:42:52 Josh Triplett wrote:
> > > Hi Josh,
> > >
> > > From the overall description (i.e. I haven't looked at the code yet)
> > > this looks very interesting. However, it seems to cover a lot of the
> > >
Any hardware that can potentially generate DMA has to be locked down from
userspace in order to avoid it being possible for an attacker to modify
kernel code. This should be prevented if trusted_kernel has been set, so
this patch disables userspace access to PCI regions and config access.
In future
uswsusp allows a user process to dump and then restore kernel state, which
makes it possible to modify the running kernel. Disable this if
trusted_kernel is true.
Signed-off-by: Matthew Garrett
---
kernel/power/user.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/kernel/p
From: Josh Boyer
This option allows userspace to pass the RSDP address to the kernel, which
makes it possible for a user to execute arbitrary code in the kernel.
Disable this when trusted_kernel is true.
Signed-off-by: Josh Boyer
---
drivers/acpi/osl.c | 3 ++-
1 file changed, 2 insertions(+),
custom_method effectively allows arbitrary access to system memory, making
it possible for an attacker to modify the kernel at runtime. Prevent this
if trusted_kernel is true.
Signed-off-by: Matthew Garrett
---
drivers/acpi/custom_method.c | 4
1 file changed, 4 insertions(+)
diff --git a/
kexec permits the loading and execution of arbitrary code in ring 0, which
permits the modification of the running kernel. Restrict it such that only
images which have been verified may be loaded when trusted_kernel is true.
Signed-off-by: Matthew Garrett
---
kernel/kexec.c | 18
Allowing users to write to address space provides mechanisms that may permit
modification of the kernel at runtime. Prevent this if trusted_kernel is
true.
Signed-off-by: Matthew Garrett
---
drivers/char/mem.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/char/mem.c b/drivers
On 03/13/2015 10:56 PM, Rafael J. Wysocki wrote:
On Friday, March 13, 2015 06:42:30 PM Daniel Lezcano wrote:
Hi Rafael,
this pull request contains a couple of fixes:
- Fix the cpu_pm_enter/exit symmetry in the mvebu driver (Gregory Clement)
- Fix the mvebu drivers latency/residency val
If trusted_kernel is true, require that all modules have valid signatures.
Signed-off-by: Matthew Garrett
---
include/linux/module.h| 6 ++
kernel/module.c | 6 ++
security/trusted_kernel.c | 6 +-
3 files changed, 17 insertions(+), 1 deletion(-)
diff --git a/include/l
Provide a boolean runtime configuration option for restricting userspace's
ability to modify the running kernel. This can be used when some external
validation of the kernel's state has been performed.
Signed-off-by: Matthew Garrett
---
Documentation/kernel-parameters.txt | 6 ++
Documen
This is a slightly cleaned up version of the patchset posted last year
(https://lkml.org/lkml/2014/2/26/554). I've made a couple of minor changes
based on feedback, but otherwise this is pretty much the same. Some things
I *haven't* done:
1) Disabled CAP_SYS_RAWIO
Disabling CAP_SYS_RAWIO has the
IO port access would permit users to gain access to PCI configuration
registers, which in turn (on a lot of hardware) give access to MMIO register
space. This would potentially permit root to trigger arbitrary DMA, so lock
it down when trusted_kernel is true
Signed-off-by: Matthew Garrett
---
ar
fixing a syntax-error .
Signed-off-by : Ameen Ali
---
arch/x86/crypto/sha-mb/sha1_mb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/crypto/sha-mb/sha1_mb.c b/arch/x86/crypto/sha-mb/sha1_mb.c
index fd9f6b0..ec0b989 100644
--- a/arch/x86/crypto/sha-mb/sha1_mb.c
+++
Am Tue, 10 Mar 2015 12:49:19 +0200
schrieb Tomi Valkeinen :
> On 09/02/15 10:52, Maxime Ripard wrote:
> > On Sat, Feb 07, 2015 at 05:42:44PM +0100, Thomas Niederprüm wrote:
> +static struct device_attribute device_attrs[] = {
> +__ATTR(contrast, S_IRUGO|S_IWUSR, show_contrast,
>
MTRRs contain fixed and variable entries. mtrr_type_lookup()
may repeatedly call __mtrr_type_lookup() to handle a request
that overlaps with variable entries. However,
__mtrr_type_lookup() also handles the fixed entries, which
do not have to be repeated. Therefore, this patch creates
separate fu
Am Tue, 10 Mar 2015 12:45:49 +0200
schrieb Tomi Valkeinen :
> On 14/02/15 17:54, Maxime Ripard wrote:
> > On Sat, Feb 07, 2015 at 05:05:03PM +0100, Thomas Niederprüm wrote:
> >> Am Sat, 7 Feb 2015 12:20:43 +0100
> >> schrieb Maxime Ripard :
> >>
> >>> On Fri, Feb 06, 2015 at 11:28:11PM +0100, nied
On Wed, Mar 11, 2015 at 2:08 PM, Pranith Kumar wrote:
> After commit 3e1d0bb6224f019893d1c498cc3327559d183674 ("audit: Convert int
> limit
> uses to u32"), by converting an int to u32, few conditions will always
> evaluate
> to false.
>
> These warnings were emitted during compilation:
>
> kerne
Am Tue, 10 Mar 2015 13:28:25 +0200
schrieb Tomi Valkeinen :
> On 14/02/15 16:22, Thomas Niederprüm wrote:
> > Am Thu, 12 Feb 2015 16:11:21 +0100
> > schrieb Maxime Ripard :
> >
> >> On Sat, Feb 07, 2015 at 04:35:41PM +0100, Thomas Niederprüm wrote:
> >>> Am Sat, 7 Feb 2015 12:18:21 +0100
> >>> sc
Document the return values of KVA mapping functions,
pud_set_huge(), pmd_set_huge, pud_clear_huge() and
pmd_clear_huge().
Simplify the conditions to select HAVE_ARCH_HUGE_VMAP
in the Kconfig, since X86_PAE depends on X86_32.
There is no functional change in this patch.
Signed-off-by: Toshi Kani
On Fri, Mar 13, 2015 at 12:57 PM, wrote:
> On Fri, Mar 13, 2015 at 05:21:13PM +0100, Oleg Nesterov wrote:
>> Josh,
>>
>> I'll certainly try to read this series, but not before next week.
>
> Thanks for looking at it.
>
>> but a couple of nits right now.
>>
>> On 03/12, Josh Triplett wrote:
>> >
>
When an MTRR entry is inclusive to a requested range, i.e.
the start and end of the request are not within the MTRR
entry range but the range contains the MTRR entry entirely,
__mtrr_type_lookup() ignores such a case because both
start_state and end_state are set to zero.
This patch fixes the issu
This patch adds an additional argument, 'uniform', to
mtrr_type_lookup(), which returns 1 when a given range is
covered uniformly by MTRRs, i.e. the range is fully covered
by a single MTRR entry or the default type.
pud_set_huge() and pmd_set_huge() are changed to check the
new 'uniform' flag to s
'mtrr_state.enabled' contains FE (fixed MTRRs enabled) and
E (MTRRs enabled) flags in MSR_MTRRdefType. Intel SDM,
section 11.11.2.1, defines these flags as follows:
- All MTRRs are disabled when the E flag is clear.
The FE flag has no affect when the E flag is clear.
- The default type is ena
On Fri, Mar 13, 2015 at 12:42 PM, Josh Triplett wrote:
> On Fri, Mar 13, 2015 at 04:05:29PM +, David Drysdale wrote:
>> On Fri, Mar 13, 2015 at 1:40 AM, Josh Triplett wrote:
>> > This patch series introduces a new clone flag, CLONE_FD, which lets the
>> > caller
>> > handle child process exi
This patchset enhances MTRR checks for the kernel huge I/O mapping,
which was enabled by the patchset below:
https://lkml.org/lkml/2015/3/3/589
The following functional changes are made in patch 5/5.
- Allow pud_set_huge() and pmd_set_huge() to create a huge page
mapping to a range covered b
On Fri, 2015-03-13 at 23:13 +0200, Ameen Ali wrote:
> fixing a syntax-error .
>
> Signed-off-by : Ameen Ali
> ---
> arch/x86/crypto/sha-mb/sha1_mb.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/x86/crypto/sha-mb/sha1_mb.c
> b/arch/x86/crypto/sha-mb/sha1_mb.c
>
On Friday, March 13, 2015 06:42:30 PM Daniel Lezcano wrote:
>
> Hi Rafael,
>
> this pull request contains a couple of fixes:
>
> - Fix the cpu_pm_enter/exit symmetry in the mvebu driver (Gregory Clement)
>
> - Fix the mvebu drivers latency/residency values to reach an
> acceptable tradeoff
On 03/13/2015 11:20 AM, Shuah Khan wrote:
> On 03/10/2015 10:06 PM, Michael Ellerman wrote:
>> This adds make install support to selftests. The basic usage is:
>>
>> $ cd tools/testing/selftests
>> $ make install
>>
>> That installs into tools/testing/selftests/install, which can then be
>> copied
On 03/13/2015 09:51 PM, Rob Herring wrote:
On Thu, Mar 12, 2015 at 9:25 AM, Daniel Lezcano
wrote:
Catalin, Rob,
do you agree with this patchset ?
There's very little to do with DT, but looks fine to me.
Shall I consider as a acked-by for the entire patchset or only the DT part ?
Thanks f
On 3/13/15, 1:27 AM, "Josh Triplett" wrote:
>On Fri, Mar 13, 2015 at 03:21:37PM +0900, Masahiro Yamada wrote:
>>
>> This series is related to mergeconfig (scripts/kconfig/merge_config.sh):
>>
>> 1/6 and 2/6 fix bugs related to the parallel build. (-j option).
>> 3/6 thru 5/6 are minor clean-ups
On Fri, Mar 13 2015 at 14:02 -0600, Andy Gross wrote:
On Thu, Mar 12, 2015 at 04:16:00PM -0600, Lina Iyer wrote:
>It looks like the remote side unlocks it too? It doesn't seem like this
>will work with the framework very well. The framework has a kernel
>spinlock attached to the hwspinlock so
On 03/13/2015 07:29 PM, Catalin Marinas wrote:
On Thu, Mar 12, 2015 at 03:25:34PM +0100, Daniel Lezcano wrote:
do you agree with this patchset ?
In principle yes, apart from some function naming and I'm waiting for
Lorenzo's ack as well. Do you plan to upstream this directly via your
tree? If
On Friday, March 13, 2015 04:14:29 PM Hanjun Guo wrote:
> From: Graeme Gregory
>
> ACPI 5.1 does not currently support S states for ARM64 hardware but
> ACPI code will call acpi_target_system_state() and acpi_sleep_init()
> for device power management, so introduce CONFIG_ACPI_GENERIC_SLEEP
> and
On 03/13/2015 07:21 PM, Catalin Marinas wrote:
On Tue, Mar 03, 2015 at 01:29:34PM +0100, Daniel Lezcano wrote:
Call the common ARM/ARM64 'arm_cpuidle_suspend' instead of cpu_suspend function
which is specific to ARM64.
Signed-off-by: Daniel Lezcano
---
drivers/cpuidle/cpuidle-arm64.c | 2 +-
On Friday, March 13, 2015 10:06:43 AM Jiang Liu wrote:
> To support IOAPIC hot-removal, we need to release PCI interrupt resource
> when unbinding PCI device driver. But due to historical reason,
> /*
> * We would love to complain here if pci_dev->is_enabled is set, that
> * the driver should hav
Hi Linus,
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
pm+acpi-4.0-rc4
to receive power management and ACPI fixes for v4.0-rc4 with top-most
commit b176023392360f28c0c8964a10effbc9a1f36c04
Merge branch 'pm-tools'
on top of commit 9eccca0843205f87c0040
On Friday 13 March 2015 12:42:52 Josh Triplett wrote:
> > Hi Josh,
> >
> > From the overall description (i.e. I haven't looked at the code yet)
> > this looks very interesting. However, it seems to cover a lot of the
> > same ground as the process descriptor feature that was added to FreeBSD
> >
fixing a syntax-error .
Signed-off-by : Ameen Ali
---
arch/x86/crypto/sha-mb/sha1_mb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/crypto/sha-mb/sha1_mb.c b/arch/x86/crypto/sha-mb/sha1_mb.c
index fd9f6b0..ec0b989 100644
--- a/arch/x86/crypto/sha-mb/sha1_mb.c
+++
On 03/13/2015 07:22 PM, Stephen Boyd wrote:
On 03/13/15 11:14, Daniel Lezcano wrote:
On 03/13/2015 07:09 PM, Stephen Boyd wrote:
This code is no longer used now that mach-msm has been removed.
Delete it.
Cc: Daniel Lezcano
Cc: David Brown
Cc: Bryan Huntsman
Cc: Daniel Walker
Signed-off-by:
On Friday 13 March 2015 18:12:29 Nicolas Ferre wrote:
> Arnd, Olof, Kevin,
>
> Another cleanup series on top of the previous one that I sent you this
> afternoon ;-) I think it is the last time that we can remove a whole bunch of
> files and legacy code... We were getting used to it!
> I still hav
Hi,
Several hardware related cipher implementations are implemented as follows: a
"helper" cipher implementation is registered with the kernel crypto API.
Such helper ciphers are never intended to be called by normal users. In some
cases, calling them via the normal crypto API may even cause fa
Remove mentioning of block barriers since they were removed.
Signed-off-by: Leonid V. Fedorenchik
---
Documentation/block/biodoc.txt | 36 +---
1 file changed, 9 insertions(+), 27 deletions(-)
diff --git a/Documentation/block/biodoc.txt b/Documentation/block/biod
On 03/12/2015 12:14 PM, Giedrius Statkevičius wrote:
On 2015.03.12 12:08, Greg KH wrote:
On Mon, Mar 09, 2015 at 06:29:38PM +0200, Giedrius Statkevičius wrote:
Remove BOARD_FAILED and don't save dgnc_boards which failed to
initialize.
Assign the result of kzalloc() to brd in dgnc_found_board()
On Thu, Mar 12, 2015 at 9:25 AM, Daniel Lezcano
wrote:
>
> Catalin, Rob,
>
> do you agree with this patchset ?
There's very little to do with DT, but looks fine to me.
Rob
>
> Thanks
> -- Daniel
>
>
> On 03/03/2015 01:29 PM, Daniel Lezcano wrote:
>>
>> There is a big number of cpuidle drivers
Nokia N900 is switching to device tree, make sure we can use flash
there, too.
Signed-off-by: Pavel Machek
diff --git a/drivers/media/i2c/adp1653.c b/drivers/media/i2c/adp1653.c
index 873fe19..0341009 100644
--- a/drivers/media/i2c/adp1653.c
+++ b/drivers/media/i2c/adp1653.c
@@ -8,6 +8,7 @@
*
On 03/13/15 12:55, Arnd Bergmann wrote:
> On Friday 13 March 2015 11:09:33 Stephen Boyd wrote:
>> The maintainers for mach-msm no longer have any plans to support
>> or test the platforms supported by this architecture[1]. Most likely
>> there aren't any active users of this code anyway, so let's
>
On 03/13/15 12:36, Paul Bolle wrote:
> I've checked this series with my local Kconfig checker (for no other
> reason than that it removes board-sapphire.c and I had promised to do so
> too a week ago).
>
> On Fri, 2015-03-13 at 11:09 -0700, Stephen Boyd wrote:
>> --- a/arch/arm/mach-msm/Kconfig
>>
On Fri, 2015-03-13 at 15:23 -0400, Nicholas Mc Guire wrote:
> Currently checkpatch will fuss if one uses world writable settings in debugfs
> files by passing S_IWUGO but not when passing S_IWOTH, S_IRWXUGO or S_IALLUGO.
> This patch extends the check to catches all cases exporting world writable
ti,codec property is not used in omap-twl4030 driver in linux kernel but
we keep it as optional property, so that the existing dtbs do not
become noncompliant after the change on other OS.
Signed-off-by: Marek Belisko
---
Documentation/devicetree/bindings/sound/omap-twl4030.txt | 3 +--
1 file c
ti,codec in not parsed in omap-twl4030 sound driver. It's not necessary
to specify this property in DT because ti,twl4030-audio which ti,codec
was pointing to by phandle is mfd driver and device for ASoC ic created w/o
any DT property (codec name is hardcoded in ASoC driver).
Please see reply [1]
ti,codec property is not used (parsed) in omap-twl4030 driver. The
ti,twl4030-audio
which ti,codec points by phandle is mfd driver and device for ASoC codec is
created
w/o DT compatible string. Removing all references in DT files.
Signed-off-by: Marek Belisko
---
arch/arm/boot/dts/omap3-beagle
Jaehoon,
On Fri, Mar 13, 2015 at 4:19 AM, Jaehoon Chung wrote:
> Hi Doug.
>
> This patch is a right process. Just i wonder something.
>
> On 03/10/2015 08:18 AM, Doug Anderson wrote:
>> In the Designware databook's description of the "Voltage Switch Normal
>> Scenario" it instructs us to set a ti
On 13/03/2015 at 20:50:59 +0100, Arnd Bergmann wrote :
> >
> > Actually, I had a closer look today and there is already just one level
> > in my current version of patches.
> >
> > I can put everything under menuconfig ARCH_AT91 but I can't remove
> > SOC_SAM_V7 and SOC_SAM_V4_V5 because that is
On 03/13/2015 11:19 AM, Shuah Khan wrote:
> On 03/10/2015 10:05 PM, Michael Ellerman wrote:
>> This adds a Make include file which most selftests can then include to
>> get the run_tests logic.
>>
>> On its own this has the advantage of some reduction in repetition, and
>> also means the pass/fail
Hi,
On Fri, Mar 13, 2015 at 4:30 AM, Jaehoon Chung wrote:
> Hi, Doug.
>
> On 03/11/2015 12:48 AM, Doug Anderson wrote:
>> The dw_mmc driver enables HLE errors as part of DW_MCI_ERROR_FLAGS but
>> nothing in the interrupt handler actually handles them and ACKs them.
>> That means that if we ever g
Em Fri, Mar 13, 2015 at 05:20:11PM +0100, Jiri Olsa escreveu:
> On Fri, Mar 13, 2015 at 12:36:21PM -0300, Arnaldo Carvalho de Melo wrote:
>
> SNIP
>
> >
> > Auto-detecting system features:
> > ... dwarf: [ on ]
> > ... glibc: [ on ]
> > ...
Currently we check that execveat returns non-positive value
when an error is expected. But we need to check that execveat() doesn't
return zero in such cases too.
Cc: Shuah Khan
Signed-off-by: Andrey Vagin
---
tools/testing/selftests/exec/execveat.c | 2 +-
1 file changed, 1 insertion(+), 1 del
On Wed, 2015-03-11 at 16:04 +0100, Valentin Rothberg wrote:
> Paul, how long does your monster run? Maybe I just call it wrong or
> mess up with caches.
Even longer, I presume. Because an update for just a new linux next
release can take over a minute on my fastest machine (a ThinkPad X220).
(Re
On Fri 13-03-15 15:09:15, Eric B Munson wrote:
> On Fri, 13 Mar 2015, Rik van Riel wrote:
>
> > On 03/13/2015 01:26 PM, Eric B Munson wrote:
> >
> > > --- a/mm/compaction.c
> > > +++ b/mm/compaction.c
> > > @@ -1046,6 +1046,8 @@ typedef enum {
> > > ISOLATE_SUCCESS,/* Pages isolated, mi
On Fri, 2015-03-13 at 15:23 -0400, Nicholas Mc Guire wrote:
> Currently checkpatch will fuss if one uses world writable settings in debugfs
> files by passing S_IWUGO but not when passing S_IWOTH, S_IRWXUGO or S_IALLUGO.
> This patch extends the check to catches all cases exporting world writable
Hi,
On Tue, Apr 1, 2014 at 1:35 PM, wrote:
> From: Stefan Agner
>
> To get the SD/MMC host device ID, read the alias from the device
> tree.
>
> This is useful in case a SoC has multipe SD/MMC host controllers while
> the second controller should logically be the first device (e.g. if
> the sec
Hi Greg,
On 2015.03.12 12:08, Greg KH wrote:
> On Mon, Mar 09, 2015 at 06:29:38PM +0200, Giedrius Statkevičius wrote:
>> Remove BOARD_FAILED and don't save dgnc_boards which failed to
>> initialize.
>>
>> Assign the result of kzalloc() to brd in dgnc_found_board() and only put
>> it in the dgnc_Bo
On Thu, Mar 12, 2015 at 04:16:00PM -0600, Lina Iyer wrote:
> >It looks like the remote side unlocks it too? It doesn't seem like this
> >will work with the framework very well. The framework has a kernel
> >spinlock attached to the hwspinlock so when we lock the hwspinlock we
> >also lock the ke
On Fri 13-03-15 13:26:37, Eric B Munson wrote:
[...]
> +compact_unevictable
> +
> +Available only when CONFIG_COMPACTION is set. When set to 1, compaction is
> +allowed to examine the unevictable lru (mlocked pages) for pages to compact.
> +This should be used on systems where stalls for minor page
On Thu, 2015-03-12 at 11:58 +0100, Ingo Molnar wrote:
> > > +/**
> > > + * pcommit_sfence() - persistent commit and fence
> > > + *
> > > + * The pcommit instruction ensures that data that has been flushed from
> > > the
> > > + * processor's cache hierarchy with clwb, clflushopt or clflush is
>
On Friday 13 March 2015 20:55:30 Arnd Bergmann wrote:
>
> I think the MMC driver should also be removed when the platform
> code is deleted, new code would use the mmci driver anyway.
Nevermind, I now see patch 6/12, which does just this.
Arnd
--
To unsubscribe from this list: send the l
On Fri, Mar 13, 2015 at 05:21:13PM +0100, Oleg Nesterov wrote:
> Josh,
>
> I'll certainly try to read this series, but not before next week.
Thanks for looking at it.
> but a couple of nits right now.
>
> On 03/12, Josh Triplett wrote:
> >
> > When passed CLONE_FD, clone4 will return a file des
On Friday 13 March 2015 11:09:33 Stephen Boyd wrote:
> The maintainers for mach-msm no longer have any plans to support
> or test the platforms supported by this architecture[1]. Most likely
> there aren't any active users of this code anyway, so let's
> delete it and the associated drivers/code. W
On Fri, Mar 13, 2015 at 11:19:52PM +0530, Sricharan R wrote:
> Signed-off-by: Sricharan R
> ---
Reviewed-by: Andy Gross
> arch/arm/boot/dts/qcom-msm8974.dtsi | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/arm/boot/dts/qcom-msm8974.dtsi
> b/arch/arm/boot/dts/qcom-msm8974.dtsi
On Friday 13 March 2015 11:09:38 Stephen Boyd wrote:
> This config no longer exists now that mach-msm has been removed.
> Delete it and the associated code.
>
> Cc: David S. Miller
> Cc: David Brown
> Cc: Bryan Huntsman
> Cc: Daniel Walker
> Signed-off-by: Stephen Boyd
> ---
>
> This can be
On Fri, Mar 13, 2015 at 12:03 PM, Andy Lutomirski wrote:
> On Fri, Mar 13, 2015 at 11:52 AM, Kees Cook wrote:
>>
>> All this said, almost half of the capabilities, if passed to flawed
>> children with attacker controlled execution, can be elevated to full
>> root privileges pretty easily[1], so I
Prepare for pipeline operation mode configuration, in particular
for DSI and WB modes.
Signed-off-by: Stephane Viau
---
drivers/gpu/drm/msm/mdp/mdp5/mdp5.xml.h | 68 -
1 file changed, 33 insertions(+), 35 deletions(-)
diff --git a/drivers/gpu/drm/msm/mdp/mdp5/mdp
Up until now, we assume that eDP is tight to intf_0 and HDMI to
intf_3. This information shall actually come from the mdp5_cfg
module since it can change from one chip to another.
v2: rename macro to mdp5_cfg_intf_is_virtual() [pointed by Archit]
v3: add sanity check before writing in INTF_TIMING_
Some interfaces (WB, DSI Command Mode) need to be kicked off
through a START Signal. This signal needs to be sent at the right
time and requests in some cases to keep track of the pipeline
status (eg: whether pipeline registers are flushed AND output WB
buffers are ready, in case of WB interface).
On Friday 13 March 2015 19:32:00 Alexandre Belloni wrote:
> On 10/03/2015 at 14:42:24 +0100, Arnd Bergmann wrote :
> > On Tuesday 10 March 2015 10:42:09 Alexandre Belloni wrote:
> > > >
> > > > I actually added a bunch of these in other places, but have stopped
> > > > doing so because Russell did
DSI and WB interfaces need a more complex pipeline configuration
than the current mdp5_ctl_set_intf().
For example, memory output connections need to be selected for
WB. Interface mode (Video vs. Command modes) also need to be
configured for DSI.
This change takes care of configuring the whole pi
WB and DSI support are in the pipe and will come out soon. Before that,
we need to prepare the MDP5 driver so we can support these connectors.
v2: rename macro to mdp5_cfg_intf_is_virtual() [pointed by Archit]
v3: add sanity check before writing in INTF_TIMING_ENGINE_EN registers
Note:
"drm/msm:
Hi,
> Hi,
>
> On 03/09/2015 06:41 PM, Stephane Viau wrote:
>> This change adds the hw configuration for msm8x16 chipsets in
>> mdp5_cfg module.
>>
>> Note that only one external display interface is present in this
>> configuration (DSI) but has not been enabled yet. It will be enabled
>> once drm
On Fri, Mar 13, 2015 at 12:04:30PM +0100, David Sterba wrote:
> On Wed, Mar 11, 2015 at 09:40:17PM -0700, Omar Sandoval wrote:
> > Ping. For anyone following along, it looks like commit cc87317726f8
> > ("mm: page_alloc: revert inadvertent !__GFP_FS retry behavior change")
> > reverted the commit t
On Fri, Mar 13, 2015 at 04:05:29PM +, David Drysdale wrote:
> On Fri, Mar 13, 2015 at 1:40 AM, Josh Triplett wrote:
> > This patch series introduces a new clone flag, CLONE_FD, which lets the
> > caller
> > handle child process exit notification via a file descriptor rather than
> > SIGCHLD.
Hi!
> > @@ -384,25 +385,10 @@ int ti_bandgap_set_sensor_data(struct ti_bandgap
> > *bgp, int id, void *data);
> > void *ti_bandgap_get_sensor_data(struct ti_bandgap *bgp, int id);
> > int ti_bandgap_get_trend(struct ti_bandgap *bgp, int id, int *trend);
> >
> > -#ifdef CONFIG_OMAP4_THERMAL
>
Previous post of the patch is lost, so I repost. This is helpful, for
example, using scsi-mq for a sata drive.
plug is still helpful for workload with IO merge, but it can be harmful
otherwise especially with multiple hardware queues, as there is (supposed) no
lock contention in this case and plug
* Matthijs van Duin [150313 11:39]:
> Given that the documentation mentions the actual phy used, it may be
> worth mentioning this also in the driver? i.e. that it's not a
> "dm816x phy" but a "SR70LX Synopsys USB 2.0 OTG nanoPHY" (in contrast
> to the dm814x and am335x which use a phy TI made th
I've checked this series with my local Kconfig checker (for no other
reason than that it removes board-sapphire.c and I had promised to do so
too a week ago).
On Fri, 2015-03-13 at 11:09 -0700, Stephen Boyd wrote:
> --- a/arch/arm/mach-msm/Kconfig
> +++ /dev/null
> -config MSM_SMD
> - bool
Af
On Fri, 13 Mar 2015 09:37:34 -0700
Tony Luck wrote:
> > int sysctl_memory_failure_early_kill __read_mostly = 0;
> >
> > @@ -837,6 +838,8 @@ static struct page_state {
> > */
> > static void action_result(unsigned long pfn, char *msg, int result)
> > {
> > + trace_memory_failure_event(
On Fri, Mar 13, 2015 at 05:26:54PM +0100, Oleg Nesterov wrote:
> > One example where drop_init_fpu() seems to make sense is
> > __kernel_fpu_end(): kernel is done with FPU and current was using the
> > FPU prior so let's restore it for the eagerfpu case.
>
> No, no, this is another case or I misun
s_create_file("id", S_IALLUGO, t_dir, NULL, &t_fops);
and
t_file = debugfs_create_file("id", S_IWOTH | S_IXOTH, t_dir, NULL, &t_fops);
Patch is against 4.0-rc3 (localversion-next is -next-20150313)
scripts/checkpatch.pl | 10 --
1 file changed, 8 inser
From: Frank Rowand
If CONFIG_OF_UNITTEST=y then a kernel image make will always cause .version to
be incremented, even if there are not source changes. This is caused by
a lack of dependency tracking and checking for
drivers/of/unittest-data/testcases.dtb.o.
Signed-off-by: Frank Rowand
---
On 3/13/2015 6:13 AM, Rob Herring wrote:
> On Thu, Mar 12, 2015 at 8:15 AM, Frank Rowand wrote:
>> From: Frank Rowand
>>
>> This 3 patch series is not bisectable. If CONFIG_OF_UNITTEST=y then the
>> kernel
>> will not build with just patch 1 or just patches 1 and 2 applied.
>
> If you did 2 pa
101 - 200 of 843 matches
Mail list logo
