Hi Greg,
A couple of important fixes for habanalabs driver:
- Fix host crash upon resume after suspend
- Fix MMU related bugs which result in user's jobs getting stuck
- Fix race between user context cleanup and hard-reset which results in
host crash
- Fix sparse warning
Thanks,
Oded
The
This is never used and the imx_clk_hw_fixed does the same thing.
Signed-off-by: Abel Vesa
---
drivers/clk/imx/clk.h | 5 -
1 file changed, 5 deletions(-)
diff --git a/drivers/clk/imx/clk.h b/drivers/clk/imx/clk.h
index 5748ec8..edc12d6 100644
--- a/drivers/clk/imx/clk.h
+++
> >
> > ddr_signaling is set to true for DDR50 and DDR52 modes but is not set
> > back to false for other modes. This programs incorrect host clock when
> > mode change happens from DDR52/DDR50 to other SDR or HS modes like
> > incase of mmc_retune where it switches from HS400 to HS DDR and
On 3/21/19 7:30 AM, Junhan Zhou wrote:
>>> +config EDAC_BLUEFIELD
>>> + tristate "Mellanox BlueField Memory ECC"
>>> + depends on (MELLANOX_PLATFORM && ARM64 && ACPI) ||
>> COMPILE_TEST
>>
>> Hi,
>>
>> While I am in favor of using COMPILE_TEST whenever possible, I don't see
>> how that is
> >
> > Default tap and trim values are incorrect for Tegra186 SDMMC4.
> > This patch fixes it.
> >
> > Tested-by: Jon Hunter
> > Signed-off-by: Sowjanya Komatineni
>
> Is this a fix and/or for stable?
>
> In either case, I am leaving this for arm-soc.
>
> Kind regards
> Uffe
>
Thanks Uffe. Yes
On 21/03/2019 14:40, Katsuhiro Suzuki wrote:
Add UART dma channels as specified by the rk3399 TRM.
No UART4? That's arguably one of the more useful ones, since 1 and 3
often end up muxed to ethernet instead.
Also, does UART DMA actually work yet? I guess I can try for myself once
I get
From: YueHaibing
Fix sparse warnings:
drivers/uio/uio_fsl_elbc_gpcm.c:71:1: warning:
symbol 'dev_attr_reg_br' was not declared. Should it be static?
drivers/uio/uio_fsl_elbc_gpcm.c:72:1: warning:
symbol 'dev_attr_reg_or' was not declared. Should it be static?
Signed-off-by: YueHaibing
---
From: YueHaibing
Fix sparse warnings:
drivers/hwtracing/coresight/coresight-catu.c:488:35: warning:
symbol 'catu_helper_ops' was not declared. Should it be static?
drivers/hwtracing/coresight/coresight-catu.c:493:28: warning:
symbol 'catu_ops' was not declared. Should it be static?
Originally
Reported-by: Mariusz Bialonczyk
When we have success in 'Channel Access Write' but reading back latch
states fails, a write is retried without doing a proper slave reset.
This leads to protocol errors as the slave treats the next 'Channel
Access Write' as the continuation of previous
From: YueHaibing
Fix sparse warning:
drivers/spi/atmel-quadspi.c:369:12: warning:
symbol 'atmel_qspi_get_name' was not declared. Should it be static?
Signed-off-by: YueHaibing
---
drivers/spi/atmel-quadspi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: YueHaibing
Fix sparse warning:
drivers/irqchip/irq-mvebu-sei.c:481:23: warning:
symbol 'mvebu_sei_ap806_caps' was not declared. Should it be static?
Signed-off-by: YueHaibing
---
drivers/irqchip/irq-mvebu-sei.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Wed, Mar 20, 2019 at 2:21 PM Evan Green wrote:
>
> Add support in code for the new forms of the host sleep event.
> Detects the presence of this version of the command at runtime,
> and use whichever form the EC supports. At this time, always
> request the default timeout, and only report the
Hi,
would it be possible to have a git repository with all patches that are
submitted to stable@ but don't apply directly?
I get notified by mail, that's fine though it's not that convenient to
see all the pending patches for backport to a given version.
My proposal:
- create a separate
Switch waiting for response to fanotify permission events interruptible.
This allows e.g. the system to be suspended while there are some
fanotify permission events pending (which is reportedly pretty common
when for example AV solution is in use). However just making the wait
interruptible can
From: YueHaibing
Fix sparse warnings:
drivers/pinctrl/pinctrl-artpec6.c:691:5: warning:
symbol 'artpec6_pmx_enable' was not declared. Should it be static?
drivers/pinctrl/pinctrl-artpec6.c:705:6: warning:
symbol 'artpec6_pmx_disable' was not declared. Should it be static?
Signed-off-by:
The patch
spi: lpspi: fix dataloss when SS is inactivated between every words
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next
The patch
regulator: add regulator_get_linear_step() stub helper
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
The patch
spi: export tracepoint symbols to modules
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus
The patch
ASoC: da7219: Update DAI clock binding info to cover WCLK/BCLK
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
The patch
ASoC: AMD: Update DA7219 DAI clock name to align with codec updates
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the
The patch
ASoC: da7219: Expose BCLK and WCLK control through CCF
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours)
The patch
regulator: tps65217: Simplify linear range for selector 25-52
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the
The patch
regulator: tps65132: Constify tps65132_regulator_ops and tps_regs_desc
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually
The patch
regulator: tps65132: Remove unneeded fields from struct tps65132_regulator
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually
The patch
ASoC: mchp-i2s-mcc: add driver for I2SC Multi-Channel Controller
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next
The patch
ASoC: mchp-i2s-mcc: dt-bindings: add DT bindings for I2S Multi-Channel
Controller
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually
On Thu, Mar 21, 2019 at 08:54:36AM +, Wei Yongjun wrote:
> Fix a typo in tegra186_usb2_pad_probe(), 'usb2->clk' should be
> 'priv->usb2_trk_clk'.
>
> Fixes: b8998e928030 ("phy: tegra: xusb: Add Tegra186 support")
> Signed-off-by: Wei Yongjun
> ---
> drivers/phy/tegra/xusb-tegra186.c | 4
On 04/02/2019 12:13, Shameer Kolothum wrote:
From: Neil Leeder
Adds a new driver to support the SMMUv3 PMU and add it into the
perf events framework.
Each SMMU node may have multiple PMUs associated with it, each of
which may support different events.
SMMUv3 PMCG devices are named as
On Wed 20-03-19 08:27:39, Yang Shi wrote:
> MPOL_MF_LAZY was added by commit b24f53a0bea3 ("mm: mempolicy: Add
> MPOL_MF_LAZY"), then it was disabled by commit a720094ded8c ("mm:
> mempolicy: Hide MPOL_NOOP and MPOL_MF_LAZY from userspace for now")
> right away in 2012. So, it is never ever
Actually, I just thought about this: do I need to do a `make
olddefconfig` for all the ralink-based defconfigs to let them choose a
default compression method? (I'm somewhat new to kernel
contributions, sorry if this is obvious.)
Thanks,
George
On Thu, Mar 21, 2019 at 8:08 AM George Hilliard
ping again...
Please let me know if there is problem in this patch.
On 2019/03/04 23:00, Katsuhiro Suzuki wrote:
ping...
On 2019/02/19 23:08, Katsuhiro Suzuki wrote:
This patch fixes pin assign of cts and rts signal of UART3.
Currently GPIO3_C2 and C3 pins are assigned but TRM says that
Hello Jonas,
Thank you for reply.
On 2019/03/17 21:33, Jonas Karlman wrote:
Hello Katsuhiro,
Sorry for the delay, I have not been able to fully test this yet but will do
more testing later tonight.
My concern are regarding how to configure a single graph card node to add a
hdmi: (and
Hi, Uwe
Best Regards!
Anson Huang
> -Original Message-
> From: Uwe Kleine-König [mailto:u.kleine-koe...@pengutronix.de]
> Sent: 2019年3月21日 21:42
> To: Anson Huang
> Cc: thierry.red...@gmail.com; robh...@kernel.org; mark.rutl...@arm.com;
> shawn...@kernel.org; s.ha...@pengutronix.de;
On 3/6/2019 4:19 PM, Stephen Boyd wrote:
Quoting Jeffrey Hugo (2019-03-06 13:48:13)
Ping?
Stephen, I know as this depends on your clock parent handling series
(happens to apply just fine to v2), its not going to be accepted until
that gets sorted out, but do you have any thoughts on if this
Am Donnerstag, den 21.03.2019, 05:52 -0700 schrieb Angus Ainslie (Purism):
> Add the imx8mq TMU (Thermal management unit) nodes for CPU,
> GPU, and VPU.
>
> Signed-off-by: Angus Ainslie (Purism)
Reviewed-by: Lucas Stach
> ---
>
> Changes since v3:
>
> Moved the annotation.
>
> Changes
On Fri, Mar 15, 2019 at 02:42:44AM -0500, Kangjie Lu wrote:
> If affs_bread fails, do not use ext_bh to avoid NULL pointer
> dereference
>
> Signed-off-by: Kangjie Lu
Tanks for the patch. I'll need some more time to get familiar with the
AFFS code to review your patch.
From: Dalit Ben Zoor
This patch allows the user to modify the TPC PLL clock relaxation value
on-the-fly in order to reduce power consumption.
To enable this, the patch removes the protection from the specific
register that controls this behavior.
Signed-off-by: Dalit Ben Zoor
Signed-off-by:
For a long time the mt7621 uses a fixed cpu clock which causes a problem
if the cpu frequency is not 880MHz.
This patch fixes the cpu clock calculation and adds the cpu/bus clkdev
which will be used in dts.
Signed-off-by: Weijie Gao
Ported from OpenWrt:
c7ca224299 ramips: fix cpu clock of
From: Dalit Ben Zoor
On init or context switch, set TPC clock relaxation counter
register to a golden value.
Signed-off-by: Dalit Ben Zoor
Signed-off-by: Oded Gabbay
---
drivers/misc/habanalabs/goya/goya.c | 2 ++
1 file changed, 2 insertions(+)
diff --git
Intel WhiskeyCove PMIC has also I2C master interface that is
designed to be used for controlling a discrete battery
charger IC.
Signed-off-by: Heikki Krogerus
---
drivers/mfd/intel_soc_pmic_bxtwc.c | 13 -
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git
Add UART dma channels as specified by the rk3399 TRM.
Refer:
RK3399 TRM V1.4: Chapter 12 DMA Controller
Signed-off-by: Katsuhiro Suzuki
---
arch/arm64/boot/dts/rockchip/rk3399.dtsi | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm64/boot/dts/rockchip/rk3399.dtsi
On Tue, 12 Mar 2019, Dave Hansen wrote:
> > Make both variables static.
>
> "pti_set_kernel_image_nonglobal(void)" is an awfully funny looking
> variable. ;)
>
> > Signed-off-by: Valdis Kletnieks
> >
> > ---
> > diff --git a/arch/x86/mm/pti.c b/arch/x86/mm/pti.c
> > index
Add ECC support for Mellanox BlueField SoC DDR controller.
This requires SMC to the running Arm Trusted Firmware to report
what is the current memory configuration.
Signed-off-by: Junhan Zhou
---
MAINTAINERS | 5 +
drivers/edac/Kconfig | 7 +
drivers/edac/Makefile
> > +config EDAC_BLUEFIELD
> > + tristate "Mellanox BlueField Memory ECC"
> > + depends on (MELLANOX_PLATFORM && ARM64 && ACPI) ||
> COMPILE_TEST
>
> Hi,
>
> While I am in favor of using COMPILE_TEST whenever possible, I don't see
> how that is possible here if:
>
> # MELLANOX_PLATFORM is
All
On 3/21/19 9:28 AM, Dan Murphy wrote:
> Add the lm3532 device tree documentation.
> Remove lm3532 device tree reference from the ti_lmu devicetree
> documentation.
>
> With the addition of the dedicated lm3532 documentation the device
> can be removed from the ti_lmu.txt.
>
> The reason for
Remove the LM3532 backlight driver references from the ti-lmu
code as dedicated driver support is available.
Signed-off-by: Dan Murphy
---
v5 - No changes - https://lore.kernel.org/patchwork/patch/1050411/
v4 - No changes - https://lore.kernel.org/patchwork/patch/1050123/
v3 - No changes -
For a long time the mt7621 uses a fixed cpu clock which causes a problem
if the cpu frequency is not 880MHz.
This patch fixes the cpu clock calculation and adds the cpu/bus clkdev
which will be used in dts.
Signed-off-by: Weijie Gao
Ported from OpenWrt:
c7ca224299 ramips: fix cpu clock of
Add the lm3532 device tree documentation.
Remove lm3532 device tree reference from the ti_lmu devicetree
documentation.
With the addition of the dedicated lm3532 documentation the device
can be removed from the ti_lmu.txt.
The reason for this is that the lm3532 dt documentation now defines
the
Introduce the Texas Instruments LM3532 White LED driver.
The driver supports ALS configurability or manual brightness
control.
The driver also supports associating LED strings with specific
control banks in a group or as individually controlled strings.
Signed-off-by: Dan Murphy
---
v5 - Added
On Thu, Mar 21, 2019 at 5:46 AM Paolo Abeni wrote:
>
> Hi,
>
> On Wed, 2019-03-20 at 11:35 -0700, Christoph Paasch wrote:
> > Hello,
> >
> > On Fri, Mar 24, 2017 at 3:23 PM Alexander Duyck
> > wrote:
> > > From: Alexander Duyck
> > >
> > > > From what I can tell there is only a couple spots
Update the properties for the lm3532 device node for droid4.
With this change the backlight LED string and the keypad
LED strings will be controlled separately.
Signed-off-by: Dan Murphy
---
v5 - No change - https://lore.kernel.org/patchwork/patch/1050409/
v4 - No change -
Hi Angus,
On Wed, 20 Mar 2019 13:21:58 -0700
Angus Ainslie wrote:
> Hi Tomas,
>
> On 2019-03-20 07:53, Tomas Novotny wrote:
> > Hi Angus,
> >
> > On Sun, 17 Mar 2019 08:47:58 -0700
> > "Angus Ainslie (Purism)" wrote:
> >
> >> The VCNL4200 datasheet says that word read and writes should be
Date: Thu, 21 Mar 2019 10:14:34 +0800
Subject: [PATCH] MIPS: ralink: fix cpu clock of mt7621 and add dt clk devices
For a long time the mt7621 uses a fixed cpu clock which causes a problem
if the cpu frequency is not 880MHz.
This patch fixes the cpu clock calculation and adds the cpu/bus clkdev
On Mon, Mar 18, 2019 at 05:42:28PM +, Parshuram Thombare wrote:
> Sorry for sending this patch again, but I didn't sent previous
> email --in-reply-to last comment on v1 of this patch. So
> rectifying this mistake.
>
> This version 2 of patch to modify MDIO read/write functions to support
>
Michael Kelley writes:
> This patch series moves Hyper-V clock/timer code to a separate Hyper-V
> clocksource driver. Previously, Hyper-V clock/timer code and data
> structures were mixed in with other Hyper-V code in the ISA independent
> drivers/hv code as well as in arch dependent code. The
To enable x86 to use the generic walk_page_range() function, the
callers of ptdump_walk_pgd_level_debugfs() need to pass in the mm_struct.
This means that ptdump_walk_pgd_level_core() is now always passed a
valid pgd, so drop the support for pgd==NULL.
Signed-off-by: Steven Price
---
mm/dump_pagetables.c passes both struct seq_file and struct pg_state
down the chain of walk_*_level() functions to be passed to note_page().
Instead place the struct seq_file in struct pg_state and access it from
struct pg_state (which is private to this file) in note_page().
Signed-off-by:
An mm_struct is needed to enable x86 to use of the generic
walk_page_range() function.
In the case of walking the user page tables (when
CONFIG_PAGE_TABLE_ISOLATION is enabled), it is necessary to create a
fake_mm structure because there isn't an mm_struct with a pointer
to the pgd of the user
Make use of the new functionality in walk_page_range to remove the
arch page walking code and use the generic code to walk the page tables.
The effective permissions are passed down the chain using new fields
in struct pg_state.
The KASAN optimisation is implemented by including test_p?d
To enable x86 to use the generic walk_page_range() function, the
callers of ptdump_walk_pgd_level() need to pass an mm_struct rather
than the raw pgd_t pointer. Luckily since commit 7e904a91bf60
("efi: Use efi_mm in x86 as well as ARM") we now have an mm_struct
for EFI on x86.
Signed-off-by:
pgd_entry() and pud_entry() were removed by commit 0b1fbfe50006c410
("mm/pagewalk: remove pgd_entry() and pud_entry()") because there were
no users. We're about to add users so reintroduce them, along with
p4d_entry() as we now have 5 levels of tables.
Note that commit a00cc7d9dd93d66a ("mm, x86:
walk_page_range() is going to be allowed to walk page tables other than
those of user space. For this it needs to know when it has reached a
'leaf' entry in the page tables. This information is provided by the
p?d_large() functions/macros.
For x86 we already have static inline functions, so
walk_page_range() is going to be allowed to walk page tables other than
those of user space. For this it needs to know when it has reached a
'leaf' entry in the page tables. This information is provided by the
p?d_large() functions/macros.
For s390, pud_large() and pmd_large() are already
walk_page_range() is going to be allowed to walk page tables other than
those of user space. For this it needs to know when it has reached a
'leaf' entry in the page tables. This information is provided by the
p?d_large() functions/macros.
For sparc 64 bit, pmd_large() and pud_large() are already
For the /sys/kernel/debug/page_tables/ files, rather than outputing a
mostly empty line when a block of memory isn't present just skip the
line. This keeps the output shorter and will help with a future change
switching to using the generic page walk code as we no longer care about
the 'level'
Since 48684a65b4e3: "mm: pagewalk: fix misbehavior of walk_page_range
for vma(VM_PFNMAP)", page_table_walk() will report any kernel area as
a hole, because it lacks a vma.
This means each arch has re-implemented page table walking when needed,
for example in the per-arch ptdump walker.
Remove
Exposing the pud/pgd levels of the page tables to walk_page_range() means
we may come across the exotic large mappings that come with large areas
of contiguous memory (such as the kernel's linear map).
For architectures that don't provide p?d_large() macros, provide generic
does nothing defaults.
Now walk_page_range() can walk kernel page tables, we can switch the
arm64 ptdump code over to using it, simplifying the code.
Signed-off-by: Steven Price
---
arch/arm64/mm/dump.c | 117 ++-
1 file changed, 59 insertions(+), 58 deletions(-)
diff --git
It is useful to be able to skip parts of the page table tree even when
walking without VMAs. Add test_p?d callbacks similar to test_walk but
which are called just before a table at that level is walked. If the
callback returns non-zero then the entire table is skipped.
Signed-off-by: Steven Price
walk_page_range() is going to be allowed to walk page tables other than
those of user space. For this it needs to know when it has reached a
'leaf' entry in the page tables. This information is provided by the
p?d_large() functions/macros.
For mips, we only support large pages on 64 bit.
For 64
walk_page_range() is going to be allowed to walk page tables other than
those of user space. For this it needs to know when it has reached a
'leaf' entry in the page tables. This information is provided by the
p?d_large() functions/macros.
For riscv a page is large when it has a read, write or
walk_page_range() is going to be allowed to walk page tables other than
those of user space. For this it needs to know when it has reached a
'leaf' entry in the page tables. This information will be provided by the
p?d_large() functions/macros.
For arm64, we already have p?d_sect() macros which
Most architectures current have a debugfs file for dumping the kernel
page tables. Currently each architecture has to implement custom
functions for walking the page tables because the generic
walk_page_range() function is unable to walk the page tables used by the
kernel.
This series extends the
On 03/21/19 at 05:19am, William Kucharski wrote:
>
>
> > On Mar 21, 2019, at 4:35 AM, Michal Hocko wrote:
> >
> > I am sorry to be snarky but hasn't this generated way much more email
> > traffic than it really deserves? A simply and trivial clean up in the
> > beginning that was it, right?
On 18-03-19, 18:39, Andy Shevchenko wrote:
> Intel IOMMU, when enabled, tries to find the domain of the device,
> assuming it's a PCI one, during DMA operations, such as mapping or
> unmapping. Since we are splitting the actual PCI device to couple of
> children via MFD framework (see
On Wed, Mar 20, 2019 at 03:41:53PM -0400, Neil Horman wrote:
> On Wed, Mar 20, 2019 at 06:20:53PM +0200, Jarkko Sakkinen wrote:
> > From: Kai Huang
> >
> > X86_FEATURE_SGX reflects whether or not the CPU supports Intel's
> > Software Guard eXtensions (SGX).
> >
> > Signed-off-by: Kai Huang
> >
On 21 March 2019 12:22, Mark Brown wrote:
> On Tue, Mar 19, 2019 at 05:49:30PM +, Adam Thomson wrote:
>
> > -- #clock-cells : Should be set to '<0>', only one clock source
> > provided;
> > -- clock-output-names : Name given for DAI clocks output;
> > +- #clock-cells : Should be set to
From: David Lechner
This sets CONFIG_CPUFREQ_DT=m in davinci_all_defconfig. This is used for
frequency scaling on device tree boards.
Signed-off-by: David Lechner
Signed-off-by: Bartosz Golaszewski
---
arch/arm/configs/davinci_all_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git
From: Bartosz Golaszewski
This series adds cpufreq-dt operating points for da850 boards supported
with device tree (da850-lcdk, da850-lego-ev3, da850-evm) and also
includes a fix for the da850-evm boardfile which checks an unset variable
to determine the highest available frequency for cpufreq.
From: David Lechner
This adds a cpu node and operating points to the common da850.dtsi file.
Additionally, a regulator is added to the LEGO EV3 board along with
some board-specific CPU configuration.
Regulators need to be hooked up on other boards to get them working.
Signed-off-by: David
From: Bartosz Golaszewski
The system_rev variable is never set on davinci and is always 0, so
we're using the default max operating point of 300MHz. The cvdd supply
is fixed at 1.2V however, so we can go up to 372MHz. Remove the switch
and always set da850_max_speed to 372000.
Signed-off-by:
From: Bartosz Golaszewski
Enable cpufreq-dt support for da850-evm. The cvdd regulator is fixed
at 1.2V on this board so disable the lower operating points and enable
the 375MHz opp.
Signed-off-by: Bartosz Golaszewski
---
arch/arm/boot/dts/da850-evm.dts | 30 ++
1
/selinux.git
tags/selinux-pr-20190321
for you to fetch changes up to 6a1afffb08ce5f9fb9ccc20f7ab24846c0142984:
selinux: fix NULL dereference in policydb_destroy()
(2019-03-18 12:19:48 -0400)
selinux/stable-5.1 PR 20190321
On Thu, Mar 21, 2019 at 08:59:55AM -0500, Pierre-Louis Bossart wrote:
> On 3/21/19 7:31 AM, Mark Brown wrote:
> > On Thu, Mar 21, 2019 at 03:41:25PM +0530, Pankaj Bharadiya wrote:
> > This is very non-obvious - it's not at all clear why we'd need the text
> > to free controls. If there is an
On Thu, Mar 21, 2019 at 9:46 AM CK Hu wrote:
>
> Hi, Hsin-yi:
>
> On Thu, 2019-03-21 at 09:28 +0800, CK Hu wrote:
> > Hi, Hsin-yi:
> >
> > On Wed, 2019-03-20 at 15:18 +0800, Hsin-Yi Wang wrote:
> > > mtk_dsi_stop() should be called after mtk_drm_crtc_atomic_disable(),
> > > which needs
> > > ovl
On Tue, 12 Mar 2019, Ali Saidi wrote:
> Increase mmap_base by the worst-case brk randomization so that
> the stack and heap remain apart.
>
> In Linux 4.13 a change was committed that special cased the kernel ELF
> loader when the loader is invoked directly (eab09532d400; binfmt_elf: use
>
Architecturally, there's nothing preventing compressed images from
working. Bootloaders built with support for the various compression
methods can decompress and run the kernel. In practice, many
bootloaders do not support compressed images, but kernels for those
boards should just not be
On 19/03/2019 18:07, Pierre Morel wrote:
On 19/03/2019 15:54, Halil Pasic wrote:
On Tue, 19 Mar 2019 11:01:44 +0100
Pierre Morel wrote:
On 15/03/2019 18:28, Halil Pasic wrote:
...snip...
We should also do it right for TAPQ with t bit set. I remember
Christian already warned about
On Wed, Mar 20, 2019 at 12:18:42PM -0700, Tadeusz Struk wrote:
> On 3/20/19 11:51 AM, Mantas Mikulėnas wrote:
> > Thanks, this patch seems to work, and I apologize for not responding
> > to test the patches earlier.
>
> Thanks for testing.
>
> >
> > Any chance it'll be submitted for stable
On Tue, Mar 19, 2019 at 01:31:34PM -0700, Tadeusz Struk wrote:
> The poll condition should only check response_length,
> because reads should only be issued if there is data to read.
> The response_read flag only prevents double writes.
> The problem was that the write set the response_read to
On Thu, Mar 21, 2019 at 09:35:26PM +0800, zhuchangc...@cvte.com wrote:
>--> I know your meaning, even though I've did following actions
>instead of unexport,
>
># echo 0 > /sys/class/gpio/gpioXX/value
> # echo in > /sys/class/gpio/gpioXX/direction
>
>the padcfg0 value still
On Thu, 21 Mar 2019 09:32:42 -0400
Steven Rostedt wrote:
> I tested your code and it also fixes the issue,
Although I just hit this:
[ cut here ]
General protection fault in user access. Non-canonical address?
WARNING: CPU: 2 PID: 1620 at arch/x86/mm/extable.c:125
On Mon, Mar 18, 2019 at 04:45:13PM -0700, Dan Williams wrote:
> Rather than fail initialization of the trusted.ko module, arrange for
> the module to load, but rely on trusted_instantiate() to fail
> trusted-key operations.
>
> Fixes: 240730437deb ("KEYS: trusted: explicitly use tpm_chip
On Thu, Mar 21, 2019 at 08:06:56AM -0400, Joel Fernandes wrote:
> On Wed, Mar 20, 2019 at 12:28:35PM +0100, Sebastian Andrzej Siewior wrote:
> > On 2019-03-19 20:26:13 [-0400], Joel Fernandes wrote:
> > > > @@ -2769,19 +2782,121 @@ static void invoke_rcu_callbacks(struct
> > > > rcu_data *rdp)
>
On Wed, Mar 20, 2019 at 03:01:12PM -0400, Andrea Arcangeli wrote:
> but
> that would be better be achieved through SECCOMP and not globally.'.
That begs the question why not use seccomp for this? What if everyone
decided to add a knob for all syscalls to do the same? For the commit
log, why is it
Convert coda to fs_context. Note this is slightly tricky as coda currently
only has a binary mount data interface. This is handled through the
parse_monolithic hook.
Also add a more conventional interface with a parameter named "fd" that
takes an fd that refers to a coda psdev, thereby
Requests a contents of one or more string sets, i.e. indexed arrays of
strings; this information is provided by ETHTOOL_GSSET_INFO and
ETHTOOL_GSTRINGS commands of ioctl interface. There are three types of
requests:
- no NLM_F_DUMP, no device: get "global" stringsets
- no NLM_F_DUMP, with
Hello,
On Thu, Mar 21, 2019 at 12:47:32PM +, Anson Huang wrote:
> > On Thu, Mar 21, 2019 at 09:54:15AM +, Anson Huang wrote:
> > > > On Thu, Mar 21, 2019 at 12:47:57AM +, Anson Huang wrote:
> > > > > +static void pwm_imx_tpm_setup_period(struct pwm_chip *chip,
> > > > > +
On 3/16/19 3:10 PM, Jonathan Cameron wrote:
> On Fri, 15 Mar 2019 19:01:47 +0100
> Fabrice Gasnier wrote:
>
>> On 3/10/19 11:21 AM, Jonathan Cameron wrote:
>>> On Wed, 6 Mar 2019 09:55:23 +0100
>>> Fabrice Gasnier wrote:
>>>
DFSDM can operate using these buffer modes:
-
Allow setting device message level using ETHA_SETTINGS_DEBUG nested
attribute.
Unlike in ioctl interface "message level" is called "message mask" (as it
is in fact used as a bit mask) and put inside a nested attribute to allow
future extensions.
Signed-off-by: Michal Kubecek
---
501 - 600 of 847 matches
Mail list logo
