On Thu, Nov 03, 2016 at 09:48:27AM +1100, Dave Chinner wrote:
> On Wed, Nov 02, 2016 at 08:04:50AM -0700, Deepa Dinamani wrote:
> > The series is aimed at adding timestamp checking and policy
> > related to it to vfs.
> >
> > The series was developed with discussions and guidance from
> > Arnd Ber
Hi,
I see that this patch has not been picked-up yet for i2c-next.
Is it possible it was missed from some reason?
Thanks,
Vadim.
> -Original Message-
> From: Vadim Pasternak
> Sent: Friday, September 23, 2016 2:57 PM
> To: 'Peter Rosin' ; w...@the-dreams.de
> Cc: linux-...@vger.kernel.or
cmd_completion in struct xhci_virt_device is legacy. With command
strutcture and command queue introduced in xhci, cmd_completion is
not used any more. This patch removes it.
Signed-off-by: Lu Baolu
---
drivers/usb/host/xhci-mem.c | 1 -
drivers/usb/host/xhci.h | 1 -
2 files changed, 2 dele
This patch supports the multiple IORESOURCE_MEM resources for one pin-bank.
In the pre-existing Exynos series, the registers of the gpio bank are included
in the one memory map. But, some gpio bank need to support the one more memory
map (IORESOURCE_MEM) because the registers of gpio bank are separ
This patch adds new Exynos5433 dtsi to support 64-bit Exynos5433 SoC based on
Octa-core CPUs (quad Cortex-A57 and quad Cortex-A53). And Exynos5433 supports
PSCI (Power State Coordination Interface) v0.1.
This patch includes following Device Tree node to support Exynos5433 SoC:
1. Octa cores for bi
This patch add the support of GPF[1-5] pin of Exynos5433 SoC. The GPFx need
to support the multiple memory map because the registers of GPFx are located
in the different domain.
Cc: Tomasz Figa
Cc: Krzysztof Kozlowski
Cc: Sylwester Nawrocki
Cc: Kukjin Kim
Cc: Linus Walleij
Cc: Rob Herring
Cc
This patchset adds the Device Tree file for Samsung 64-bit Exynos5433 SoC
and TM/TM2E board based on Exynos5433. The Exynos5433 has Octa-core CPUs
(quad Cortex-A57 and quad Cortex-A53). The TM2 and TM2E are the Samsung board
based on Exynos5433 SoC.
I tested the display controller by using the mod
This patch adds the Device Tree source for Exynos5433-based Samsung TM2 board.
This board fully support the all things for mobile target.
This patch supports the following devices:
1. basic SoC
- Initial booting for Samsung Exynos5433 SoC
- DRAM LPDDR3 (3GB)
- eMMC (32GB)
- ARM architecture timer
This patch adds the Device Tree source for Exynos5433-based Samsung TM2E
board. TM2E board is the most similar with TM2 board. The exynos5433-tm2e.dts
include the difference between TM2 and TM2E.
Signed-off-by: Chanwoo Choi
Signed-off-by: Jaehoon Chung
Signed-off-by: Seung-Woo Kim
Signed-off-by
Hi All,
Miss something in this patch, just ignored it, sorry about that.
On 2016年11月03日 14:16, Lin Huang wrote:
Add suspend frequency support and if needed set it to
the frequency obtained from the suspend opp (can be defined
using opp-v2 bindings and is optional).
Change-Id: Iaa0d3848d63d9
Hi Lin,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.9-rc3 next-20161028]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Lin-Huang/set-specific-ddr-frequency-when-stop-dd
* Linus Torvalds wrote:
> On Wed, Nov 2, 2016 at 4:50 AM, Tetsuo Handa
> wrote:
> >>
> >> So I _think_ the fix is to just remove this. Perhaps something like
> >> the attached? Adding scheduler people since this is in their code..
> >
> > That is not sufficient, for another Oops occurs inside s
Commit-ID: c7faee2109f978f3ef826c48b7e60609061fda4f
Gitweb: http://git.kernel.org/tip/c7faee2109f978f3ef826c48b7e60609061fda4f
Author: Ingo Molnar
AuthorDate: Thu, 3 Nov 2016 07:16:43 +0100
Committer: Ingo Molnar
CommitDate: Thu, 3 Nov 2016 07:21:12 +0100
locking/drm: Fix i915_gem_shri
If display the debug message, this message should be spamming.
If flags is maintained the previous value, didn't display the debug
message.
Signed-off-by: Jaehoon Chung
---
drivers/mmc/host/dw_mmc.c | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/drivers/mmc/host/dw_mm
This patch removed the meaningless value. Instead, use the cookie's enum
values for executing correctly.
Signed-off-by: Jaehoon Chung
---
drivers/mmc/host/dw_mmc.c | 39 +++
1 file changed, 19 insertions(+), 20 deletions(-)
diff --git a/drivers/mmc/host/dw_mm
If DW_MMC_CARD_NO_USE_HOLD isn't set, it's usesd by default.
Enve if SDMMC_CMD_USB_HOLD_REG is set in prepare_command(), but it
doesn't set in pre_stop_abort().
To maintain the consistency, add the checking condition for this.
Signed-off-by: Jaehoon Chung
---
drivers/mmc/host/dw_mmc.c | 3 +++
stop_cmdr should be set to values relevant to stop command.
It migth be assigned to values whatever there is mrq->stop or not.
Then it doesn't need to use dw_mci_prepare_command().
It's enough to use the prep_stop_abort for preparing stop command.
Signed-off-by: Jaehoon Chung
---
drivers/mmc/hos
It's not for only sdhci controller.
So it can be moved from sdhci.h to mmc.h. And renamed from sdhci_cookie
to mmc_cookie.
Signed-off-by: Jaehoon Chung
---
drivers/mmc/host/sdhci.h | 6 --
include/linux/mmc/core.h | 6 ++
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/dri
If there is no property "clock-freq-min-max", mmc->f_min should be set
to 400K by default. But Some SoC can be used 100K.
When 100K is used, MMC core will try to check from 400K to 100K.
Reported-by: Shawn Lin
Signed-off-by: Jaehoon Chung
---
drivers/mmc/host/dw_mmc.c | 2 +-
1 file changed, 1
Remove the "clock-freq-min-max" property.
There is "max-frequency" property in drivers/mmc/core/host.c
It can be used for getting maximum frequency.
And minimum clock value is assigned to 100K by default.
Because MMC core should check the initial clock value from
400K to 100K until finding correct
Developer wants to see the real register value, not register offset.
This patch fixed to display the real value of register.
Signed-off-by: Jaehoon Chung
---
drivers/mmc/host/dw_mmc.c | 14 --
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git a/drivers/mmc/host/dw_mmc.c b/d
Remove the unnecessary mmc_data structure.
Instead, cmd->data can be used.
Signed-off-by: Jaehoon Chung
---
drivers/mmc/host/dw_mmc.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/mmc/host/dw_mmc.c b/drivers/mmc/host/dw_mmc.c
index df151c8..bd8c5ea 100644
---
"support-highspeed" was the obsoleted property.
And "broken-cd" is not synopsys specific property.
It can be referred to mmc.txt binding Documentation.
Signed-off-by: Jaehoon Chung
---
Documentation/devicetree/bindings/mmc/synopsys-dw-mshc.txt | 5 -
1 file changed, 5 deletions(-)
diff --gi
In drivers/mmc/core/host.c, there is "max-freqeuncy" property.
It should be same behavior, So Use the "max-frequency" instead of
"clock-freq-min-max".
Signed-off-by: Jaehoon Chung
---
arch/arm64/boot/dts/rockchip/rk3368-orion-r68-meta.dts | 2 +-
arch/arm64/boot/dts/rockchip/rk3368.dtsi
In drivers/mmc/core/host.c, there is "max-frequency" property.
It should be same behavior. So Use the "max-frequency" instead of
"clock-freq-min-max".
Signed-off-by: Jaehoon Chung
---
arch/arm/boot/dts/exynos3250-artik5-eval.dts | 2 +-
arch/arm/boot/dts/exynos3250-artik5.dtsi | 2 +-
arch/a
In drivers/mmc/core/host.c, there is "max-frequency" property.
It should be same behavior. So use the "max-frequency" instead of
"clock-freq-min-max".
Signed-off-by: Jaehoon Chung
---
arch/arm/boot/dts/rk3036.dtsi | 6 +++---
arch/arm/boot/dts/rk322x.dtsi | 2 +-
arch/arm/boot/dts/rk3288.dtsi |
This patchset is modified the some minor fixing and cleaning code.
If needs to split the patches, i will re-send the patches.
* Major changes
- Use the cookie enum values like sdhci controller.
- Remove the unnecessary codes and use stop_abort() by default.
- Remove the obsoleted property "support
We need ddr run a specific frequency when ddr dvfs stop working. So we
implement get suspend frequency function in devfreq framework, and call
it in rk3399 dmc driver.
Lin Huang (2):
PM/devfreq: add suspend frequency support
PM/devfreq: rk3399: set specific ddr frequency when stop ddr dvfs
d
Add suspend frequency support and if needed set it to
the frequency obtained from the suspend opp (can be defined
using opp-v2 bindings and is optional).
Change-Id: Iaa0d3848d63d9ce03f65ea76f263e4685a4c295e
Signed-off-by: Lin Huang
---
Changes in v2:
- use update_devfreq() instead devfreq_update_
We need ddr run a specific frequency when ddr dvfs stop
working. For example: if we enable two monitor, then we will
stop ddr dvfs, but we hope ddr can run in highest frequency
obviously.
Change-Id: I02460f0becbf0e1a732e2a55b8e529f53c01109c
Signed-off-by: Lin Huang
---
Changes in v2:
- None
dri
You are a recipient to Mrs Julie Leach Donation of $2 million USD. Contact
(julieleach...@gmail.com) for claims
On Fri, Oct 28, 2016 at 7:59 PM, Matt Ranostay wrote:
> On Fri, Oct 28, 2016 at 2:53 PM, Hans Verkuil wrote:
>> Hi Matt,
>>
>> On 28/10/16 22:14, Matt Ranostay wrote:
>>>
>>> So want to toss a few thoughts on adding support for thermopile
>>> devices (could be used for FLIR Lepton as well) that o
Hi,
On 31 October 2016 at 02:47, Sagi Grimberg wrote:
> How is this simpler?
It is simpler in the sense that it is a light weight primitive and that only
one thread waits on the event here. In our case since 'umr_context.done'
is an "on stack" variable, and has only one thread waiting on that e
The find_num_contig() will return 1 when the pmd is not present.
It will cause a kernel dead loop in the following scenaro:
1.) pmd entry is not present.
2.) the page fault occurs:
... hugetlb_fault() --> hugetlb_no_page() --> set_huge_pte_at()
3.) set_huge_pte_at() will only set
Hi Richard,
>> Hmm, the calculations in lpt.c use basic properties of the MTD (number of
>> blocks, etc...).
>> Can you please double check which property causes the failure and also
>> verify whether the MTD driver provides correct properties. i.e. page sizes,
>> block size, number of blocks,
On Wed, Nov 2, 2016 at 4:47 PM, Jakub Kicinski wrote:
>
> Thanks for looking into this! Bisect led me to the following commit:
>
> commit 56989f6d8568c21257dcec0f5e644d5570ba3281
> Author: Johannes Berg
> Date: Mon Oct 24 14:40:05 2016 +0200
>
> genetlink: mark families as __ro_after_init
On Thursday 03 November 2016 02:34 AM, Anton Blanchard wrote:
> Hi Ravi,
>
>> emulate_step() uses a number of underlying kernel functions that were
>> initially not enabled for LE. This has been rectified since. So, fix
>> emulate_step() for LE for the corresponding instructions.
> Thanks. Should
Hi,
small update to be in sync with Russell's comments on arm correspoding
patch.
On 17/10/16 16:46, Juri Lelli wrote:
> Add a sysfs cpu_capacity attribute with which it is possible to read and
> write (thus over-writing default values) CPUs capacity. This might be
> useful in situations where va
We do not ever intend to unregister "user" sysctl table, unfortunately
it leads kmemleak to believe that we are leaking memory:
unreferenced object 0x8807383bfd48 (size 96):
comm "swapper/0", pid 1, jiffies 4294894636 (age 278.320s)
hex dump (first 32 bytes):
a0 b4 b0 ba ff ff ff ff 00
Hi Catalin,
On 30/10/16 14:22, Catalin Marinas wrote:
> On Mon, Oct 17, 2016 at 04:46:41PM +0100, Juri Lelli wrote:
> > I'm thus now assuming that everybody is OK with the patches and that they
> > can
> > be queued for 4.10 (we certainly need this plumbing at this point). Please
> > speak if my
On Wed, Nov 2, 2016 at 10:25 PM, Cong Wang wrote:
> On Wed, Nov 2, 2016 at 5:25 PM, Andrey Konovalov
> wrote:
>> Hi,
>>
>> I've got the following error report while running the syzkaller fuzzer:
>>
>> ==
>> BUG: KASAN: global-out-of
Hi,
apologies for the delay in replying, but I'm attending Linux Plumbers
this week.
On 30/10/16 20:45, Russell King - ARM Linux wrote:
> On Mon, Oct 17, 2016 at 04:46:49PM +0100, Juri Lelli wrote:
> > +#ifdef CONFIG_PROC_SYSCTL
> > +#include
> > +#include
>
> Include files at the top of the f
On Wed, Nov 2, 2016 at 5:25 PM, Andrey Konovalov wrote:
> Hi,
>
> I've got the following error report while running the syzkaller fuzzer:
>
> ==
> BUG: KASAN: global-out-of-bounds in validate_nla+0x49b/0x4e0 at addr
> 8407e3ac
Hi,
On 11/02/2016 06:56 AM, John Stultz wrote:
> On Sun, Oct 30, 2016 at 7:49 PM, Jaehoon Chung wrote:
>> This patch adds the "reset-names" as reset controller for dwmmc controller.
>> Linaro guys had reported the issue about booting stuck.
>>
>> Some SoCs are enabled the CONFIG_RESET_CONTROLLER.
On Wed, Nov 2, 2016 at 5:41 PM, Neri, Ricardo wrote:
> On Sun, 2016-10-30 at 08:59 -0700, Dan Williams wrote:
>> On Sun, Oct 30, 2016 at 5:08 AM, Thorsten Leemhuis
>> wrote:
>> > JFYI: I added this report to the list of regressions for Linux 4.9. I'll
>> > watch this thread for further updates on
You are a recipient to Mrs Julie Leach Donation of $2 million USD. Contact
(julieleach...@gmail.com) for claims
Here we go.
The following program triggers kernel BUG in htab_elem_free.
On commit 0c183d92b20b5c84ca655b45ef57b3318b83eb9e (Oct 31).
Run as "while true; do ./a.out; done".
[ cut here ]
kernel BUG at mm/slub.c:3866!
invalid opcode: [#1] SMP KASAN
Modules linked in:
CP
Hi Bjorn
Thanks for your review.
在 2016/11/3 7:40, Bjorn Helgaas 写道:
On Thu, Oct 20, 2016 at 11:10:34AM +0800, Dongdong Liu wrote:
PCIe controller in Hip05/HIP06/HIP07 SoCs is not ECAM compliant.
It is non ECAM only for the RC bus config space;for any other bus
underneath the root bus we suppo
(1) Backgroud
For the arm64, the hugetlb page size can be 32M (PMD + Contiguous bit).
In the 4K page environment, the max page order is 10 (max_order - 1),
so 32M page is the gigantic page.
The arm64 MMU supports a Contiguous bit which is a hint that the PTE
is one of a set of c
From: Neil Armstrong
On Amlogic SCPI legacy implementation, the GET_CAPABILITIES command is
not supported, failover by using 0.0.0 version.
Signed-off-by: Neil Armstrong
[sudeep.ho...@arm.com: changed the subject]
Signed-off-by: Sudeep Holla
---
drivers/firmware/arm_scpi.c | 4
1 file ch
Since SCPI is a generic protocol and the bindings are intended to be
generic, we need to decouple all the platform specific binding details
out of the generic bindings.
This patch moves are the Juno platform specific details into a separate
binding document.
Cc: Rob Herring
Signed-off-by: Sudeep
From: Neil Armstrong
This patch adds support for the Legacy SCPI protocol that is available
in very early JUNO versions and shipped Amlogic ARMv8 based SoCs. Some
Rockchip SoC are also known to use this version of protocol with
extended vendor commands.
In order to support the legacy SCPI protoc
This patch adds new DT match table to setup the support for legacy SCPI
protocol. It aldo adds "arm,legacy-scpi" to the legacy match entry.
Signed-off-by: Sudeep Holla
---
drivers/firmware/arm_scpi.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/drivers/firmware/arm_scpi.c b/drive
This patch adds specific compatible to support legacy SCPI protocol.
Cc: Rob Herring
Signed-off-by: Sudeep Holla
---
Documentation/devicetree/bindings/arm/arm,scpi.txt | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/arm/arm,scpi.txt
b/Do
From: Neil Armstrong
Since Amlogic SoCs supports more than 8 OPPs per domains, we need increase
the OPP structure size.
This patch increases the MAX_DVFS_OPPS to 16.
Signed-off-by: Neil Armstrong
Signed-off-by: Sudeep Holla
---
drivers/firmware/arm_scpi.c | 2 +-
1 file changed, 1 insertion(
> -Original Message-
> From: Vladimir Zapolskiy [mailto:v...@mleia.com]
> Sent: Thursday, November 03, 2016 1:09 AM
> To: Vadim Pasternak ; w...@the-dreams.de
> Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; j...@resnulli.us;
> Michael Shych
> Subject: Re: [patch v2] i2c: a
From: Neil Armstrong
Cc: Rob Herring
Signed-off-by: Neil Armstrong
(decoupled from the generic scpi binding)
Signed-off-by: Sudeep Holla
---
.../devicetree/bindings/arm/amlogic,scpi.txt | 20
1 file changed, 20 insertions(+)
create mode 100644 Documentation/devic
Since the legacy SCPI and the SCPI v1.0 differ in the command values,
it's better to create some sort of command indirection in the driver
to avoid repeated version check at multiple places.
This patch adds the indirection command table to allow different values
of the command across SCPI versions
Hi,
This is minor rework of the series[1] from Neil Armstrong's to support
legacy SCPI protocol to make DT bindings more generic and move out all
the platform specific bindings out of the generic binding document.
--
Regards,
Sudeep
[1] http://www.spinics.net/lists/arm-kernel/msg534999.html
Nei
On Sun, Oct 30, 2016 at 11:17:57PM +0200, Sagi Grimberg wrote:
>
>
> On 27/10/16 09:59, Binoy Jayan wrote:
> >Convert the completion 'mlx5_ib_umr_context:done' to a wait_event as it
> >just waits for the return value to be filled.
On top of Sagi's response, I'm failing to understand why it is need
On 02/11/16 21:51, Rob Herring wrote:
On Wed, Nov 2, 2016 at 5:20 PM, Sudeep Holla wrote:
On Sat, Oct 29, 2016 at 11:39:05AM -0700, Olof Johansson wrote:
Hi,
On Wed, Oct 5, 2016 at 12:33 AM, Neil Armstrong wrote:
Acked-by: Rob Herring
Signed-off-by: Neil Armstrong
---
Documentation/de
On 03/11/16 00:18, Kirti Wankhede wrote:
>
>
> On 11/2/2016 6:30 PM, Jike Song wrote:
>> On 11/02/2016 08:41 PM, Kirti Wankhede wrote:
>>> On 11/2/2016 5:51 PM, Jike Song wrote:
On 11/02/2016 12:09 PM, Alexey Kardashevskiy wrote:
> Or you could just reference and use @mm as KVM and other
On 11/01/2016 05:31 AM, Sekhar Nori wrote:
On Monday 31 October 2016 08:18 PM, David Lechner wrote:
On 10/31/2016 05:18 AM, Sekhar Nori wrote:
On Tuesday 25 October 2016 11:24 PM, David Lechner wrote:
This fixes pwm name matching for DA850 familiy devices. When using
device
tree, the da850_aux
On Thu, Nov 03, 2016 at 11:40:15AM +0800, Anthony Wong wrote:
> On 1 November 2016 at 12:30, Lee, Chun-Yi wrote:
> >
> > The AMW0_GUID1 wmi is not only found on Acer family but also other
> > machines like Lenovo, Fujitsu and Medion. In the past days, acer-wmi
> > driver handled those non-Acer mac
Congratulations Beneficiary,
You a recipient of USD1.5M
Yours Faithfully,
Mr. Wu Hongbo
Under-Secretary-General for Economic and Social Affairs
The libhugetlbfs meets several failures since the following functions
do not use the correct address:
huge_ptep_get_and_clear()
huge_ptep_set_access_flags()
huge_ptep_set_wrprotect()
huge_ptep_clear_flush()
This patch fixes the wrong address for them.
Acked-by: Steve Capper
Signed-of
On Wed, Nov 2, 2016 at 5:20 PM, Sudeep Holla wrote:
> On Sat, Oct 29, 2016 at 11:39:05AM -0700, Olof Johansson wrote:
>> Hi,
>>
>>
>> On Wed, Oct 5, 2016 at 12:33 AM, Neil Armstrong
>> wrote:
>> > Acked-by: Rob Herring
>> > Signed-off-by: Neil Armstrong
>> > ---
>> > Documentation/devicetree/
On 1 November 2016 at 12:30, Lee, Chun-Yi wrote:
>
> The AMW0_GUID1 wmi is not only found on Acer family but also other
> machines like Lenovo, Fujitsu and Medion. In the past days, acer-wmi
> driver handled those non-Acer machines by quirks list.
>
> But actually acer-wmi driver was loaded on any
Optimize rk3399 clocktree by removing CLK_IGNORE_UNUSED of some clocks.
clocks will managered by usb:
- clk_usbphy0_480m_src
- clk_usbphy1_480m_src
- clk_usbphy_480m
clocks will be managered by pvtm:
- clk_pvtm_core_l
- clk_pvtm_core_b
- clk_pvtm_ddr
clocks will be managered by dfi:
- pclk_ddr_m
On Fri, Oct 28, 2016 at 4:15 PM, David Daney wrote:
> From: David Daney
>
> On arm64 NUMA kernels we can pass "numa=off" on the command line to
> disable NUMA. A side effect of this is that kmalloc_node() calls to
> non-zero nodes will crash the system with an OOPS:
>
> [0.00] ITS@0x
Just wanted to resend the adv7511 hdmi bridge audio support for
review and consideration for merging.
I've taken the core audio work done by Lars-Peter Clausen, and
adapted by Srinivas Kandagatla and Archit Taneja, and tried to
rework it to use the hdmi-codec sound driver.
This patchset, along wi
This patch adds support to Audio for both adv7511 and adv7533
bridge chips.
This patch was originally from [1] by Lars-Peter Clausen
and was adapted by Archit Taneja and
Srinivas Kandagatla .
Then I heavily reworked it to use the hdmi-codec driver. And also
folded in some audio packet initializ
From: Srinivas Kandagatla
This patch enables the Audio Data and Clock pads to the adv7533 bridge.
Without this patch audio can not be played.
Cc: David Airlie
Cc: Archit Taneja
Cc: Laurent Pinchart
Cc: Wolfram Sang
Cc: Srinivas Kandagatla
Cc: "Ville Syrjälä"
Cc: Boris Brezillon
Cc: Andy G
From: Eric Dumazet
A recent commit removed locking from netlink_diag_dump() but forgot
one error case.
=
[ BUG: bad unlock balance detected! ]
4.9.0-rc3+ #336 Not tainted
-
syz-executor/4018 is trying to release lock ([ 36
On Thu, Nov 03, 2016 at 04:04:45AM +0100, Jann Horn wrote:
> SELinux attempts to make it possible to whitelist trustworthy sources of
> code that may be mapped into memory, and Android makes use of this feature.
> To prevent an attacker from bypassing this by modifying R+X memory through
> /proc/$p
Hi Eric,
This fixes the second report, the first one is still there.
Apparently these are two separate issues.
For the second one:
Tested-by: Andrey Konovalov
Thanks for the fix!
On Thu, Nov 3, 2016 at 3:58 AM, Eric Dumazet wrote:
> On Thu, 2016-11-03 at 03:36 +0100, Andrey Konovalov wrote:
>
SELinux attempts to make it possible to whitelist trustworthy sources of
code that may be mapped into memory, and Android makes use of this feature.
To prevent an attacker from bypassing this by modifying R+X memory through
/proc/$pid/mem, PTRACE_POKETEXT or DMA, it is necessary to call a security
This restricts forced writes to private R+X mappings using the EXECMEM
permission. To avoid a breaking change, a new policy capability needs to
be enabled before the new restrictions take effect.
Unlike most other SELinux hooks, this one takes the subject credentials as
an argument instead of look
This shouldn't change behavior in any way - at this point, there should be
no non-writable mappings, only the initial stack mapping -, but this change
makes it easier to reason about the correctness of the following commits
that place restrictions on forced memory writes.
Signed-off-by: Jann Horn
This restricts forced writes to private R+X mappings using the EXECMEM
permission. To avoid a breaking change, a new policy capability needs to
be enabled before the new restrictions take effect.
Unlike most other SELinux hooks, this one takes the subject credentials as
an argument instead of look
SELinux attempts to make it possible to whitelist trustworthy sources of
code that may be mapped into memory, and Android makes use of this feature.
To prevent an attacker from bypassing this by modifying R+X memory through
/proc/$pid/mem, PTRACE_POKETEXT or DMA, it is necessary to call a security
This shouldn't change behavior in any way - at this point, there should be
no non-writable mappings, only the initial stack mapping -, but this change
makes it easier to reason about the correctness of the following commits
that place restrictions on forced memory writes.
Signed-off-by: Jann Horn
From: Larry Finger
Date: Wed, 2 Nov 2016 20:00:03 -0500
> On 10/30/2016 05:21 AM, John Heenan wrote:
>> Code tests show data returned by rtl8xxxu_read8(priv, REG_CR), used to
>> set
>> macpower, is never 0xea. It is only ever 0x01 (first time after
>> modprobe)
>> using wpa_supplicant and 0x00 th
On Thu, 2016-11-03 at 03:36 +0100, Andrey Konovalov wrote:
> On Thu, Nov 3, 2016 at 1:15 AM, Andrey Konovalov
> wrote:
> > On Wed, Oct 19, 2016 at 4:13 PM, Andrey Konovalov
> > wrote:
> >> Hi,
> >>
> >> I've got the following error report while running the syzkaller fuzzer:
> >>
> >> kasan: CON
On Thu, Nov 3, 2016 at 1:15 AM, Andrey Konovalov wrote:
> On Wed, Oct 19, 2016 at 4:13 PM, Andrey Konovalov
> wrote:
>> Hi,
>>
>> I've got the following error report while running the syzkaller fuzzer:
>>
>> kasan: CONFIG_KASAN_INLINE enabled
>> kasan: GPF could be caused by NULL-ptr deref or us
You are a recipient to Mrs Julie Leach Donation of $3 million USD. Contact (
julieleac...@gmail.com) for claims.
On Thu, Sep 29, 2016 at 01:32:56AM +0200, Jann Horn wrote:
> On Wed, Sep 28, 2016 at 04:22:53PM -0700, Andy Lutomirski wrote:
> > On Wed, Sep 28, 2016 at 3:54 PM, Jann Horn wrote:
> > > -struct mm_struct *proc_mem_open(struct inode *inode, unsigned int mode)
> > > +struct mm_struct *proc_mem_open(
On Wed, 2 Nov 2016, Ondrej Zary wrote:
> > Also, you've ignored the irq module parameters. From the user's point
> > of view, surely the least surprising thing is to attempt to configure
> > the card for whatever irq the user asked for.
>
> I haven't. NCR5380_find_irq is only called when irq i
On Wed, 2 Nov 2016, Ondrej Zary wrote:
> On Wednesday 02 November 2016 08:45:26 Finn Thain wrote:
> > On Mon, 31 Oct 2016, Ondrej Zary wrote:
> > > Trigger an IRQ first with a test IRQ handler to find out if it
> > > really works. Disable the IRQ if not.
> > >
> > > This prevents hang when incor
On Wed, 2 Nov 2016, Ondrej Zary wrote:
> On Wednesday 02 November 2016, Finn Thain wrote:
> > On Mon, 31 Oct 2016, Ondrej Zary wrote:
> >
> > > + NCR5380_write(SELECT_ENABLE_REG, hostdata->id_mask);
> > > + NCR5380_write(OUTPUT_DATA_REG, hostdata->id_mask);
> > > + NCR5380_write(INITIATOR_COMMAND
On 02-11-16, 22:49, Robert Jarzmik wrote:
> Would you or Rafael take patch 1/4 "cpufreq: pxa: use generic platdev driver
> for
> device-tree" through your tree please ?
Rafael is the one who applies the patches.
--
viresh
The rk3399 SoC USB2 PHY is comprised of one Host port and
one OTG port. And OTG port is for USB2.0 part of USB3.0 OTG
controller, as a part to construct a fully feature Type-C
subsystem.
With this patch, we can support OTG port with the following
functions:
- Support BC1.2 charger detect, and use
This series add support for rk3399 USB2 PHY0 and PHY1 OTG port.
rk3399 has two USB2 PHYs, and each USB2 PHY is comprised of one
Host port and one OTG port. We have supported Host port before,
and try to support OTG port now.
Test on rk3399-evb board.
William Wu (2):
phy: rockchip-inno-usb2: sup
Add otg-port nodes for both u2phy0 and u2phy1. The otg-port can
be used for USB2.0 part of USB3.0 OTG controller.
Signed-off-by: William Wu
---
Changes in v2:
- None
arch/arm64/boot/dts/rockchip/rk3399.dtsi | 21 +
1 file changed, 21 insertions(+)
diff --git a/arch/arm64/bo
hat (public, well-known) commit your patch series was
built on]
[Check https://git-scm.com/docs/git-format-patch for more information]
url:
https://github.com/0day-ci/linux/commits/Anurup-M/perf-arm64-Support-for-Hisilicon-SoC-Hardware-event-counters/20161102-235009
config: arm-allmodcon
On Tue, Nov 01, 2016 at 01:54:02PM -0600, Ross Zwisler wrote:
> DAX PMDs have been disabled since Jan Kara introduced DAX radix tree based
> locking. This series allows DAX PMDs to participate in the DAX radix tree
> based locking scheme so that they can be re-enabled.
I've seen patch 0/16 - wher
On Thu, Nov 3, 2016 at 5:50 AM, Maxime Ripard
wrote:
> Add the A64 CCU clocks set.
>
> Acked-by: Rob Herring
> Signed-off-by: Maxime Ripard
I thought I acked this one...
Skimming through it again, I think you would want to add CLK_SET_PARENT_RATE
to the hdmi and mipi dsi module clocks.
Otherw
The function becomes used again with the next patch, so bring it back
from dead, only this time make it static.
Reverts: bf2a033360f7 ("staging/lustre/ldlm: Remove unused ldlm_enqueue_pack()")
Signed-off-by: Oleg Drokin
---
drivers/staging/lustre/lustre/ldlm/ldlm_request.c | 21 +
On Tue, Nov 01 2016, Baolin Wang wrote:
>> So I won't be responding on this topic any further until I see a genuine
>> attempt to understand and resolve the inconsistencies with
>> usb_register_notifier().
>
> Any better solution?
I'm not sure exactly what you are asking, so I'll assume you are
1 - 100 of 699 matches
Mail list logo
