On Wed, Jun 12, 2019 at 12:52:31PM -0300, André Almeida wrote:
> Wikipedia now has a main article to "tracing garbage collector" topic.
> Change the URL and use the reStructuredText syntax for hyperlinks and add
> more details about the use of the tool. Add a section about how to use
> the kmemleak
On 6/13/2019 3:16 PM, Christophe Leroy wrote:
>
>
> Le 13/06/2019 à 14:13, Horia Geanta a écrit :
>> On 6/11/2019 5:39 PM, Christophe Leroy wrote:
>>> Next patch will require struct talitos_edesc to be defined
>>> earlier in talitos.c
>>>
>>> This patch moves it into talitos.h so that it can be u
On 6/11/2019 5:39 PM, Christophe Leroy wrote:
> When building for SEC1 only, talitos2_done functions are unneeded
> and should go away.
>
> For this, use has_ftr_sec1() which will always return true when only
> SEC1 support is being built, allowing GCC to drop TALITOS2 functions.
>
> Signed-off-b
test
Chopping max delay in 4 seems excessive. Let's just cut it in half.
Signed-off-by: Marc Gonzalez
---
When max_us=100, old_min was 26 us; new_min would be 50 us
Was there a good reason for the 1/4th?
Is new_min=0 a problem? (for max=1)
---
include/linux/iopoll.h | 2 +-
1 file changed, 1 insertio
ROHM BD71847 PMIC datasheet was published.
Add datasheet link for BD71847 as well.
Signed-off-by: Matti Vaittinen
---
Documentation/devicetree/bindings/mfd/rohm,bd71837-pmic.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/mfd/rohm,bd71837-pmic.txt
b/D
13.06.2019 13:49, Peter De Schrijver пишет:
> On Fri, May 24, 2019 at 08:23:46PM +0300, Dmitry Osipenko wrote:
>> A proper External Memory Controller clock rounding and parent selection
>> functionality is required by the EMC drivers. It is not available using
>> the generic clock implementation, h
On Thu 13 Jun 08:12 PDT 2019, Bjorn Andersson wrote:
> On Thu 13 Jun 07:22 PDT 2019, Jeffrey Hugo wrote:
>
> > spmi_regulator_common_get_mode and spmi_regulator_common_set_mode use
> > multi-level ifs which mirror a switch statement. Refactor to use a switch
> > statement to make the code flow m
On Wed, Jun 12, 2019 at 12:52:30PM -0300, André Almeida wrote:
> According to POSIX, EBUSY means that the "device or resource is busy",
> and this can lead to people thinking that the file
> `/sys/kernel/debug/kmemleak/` is somehow locked or being used by other
> process. Change this error code to
On Thu, Jun 13, 2019 at 2:07 PM Hillf Danton wrote:
>
>
> Hello Jason
>
> On Thu, 13 Jun 2019 17:10:39 +0800 Jason Wang wrote:
> >
> > This is basically a kfree(ubuf) after the second vhost_net_flush() in
> > vhost_net_release().
> >
> Fairly good catch.
>
> > Could you please post a formal patch?
(added Roman)
On Tue, Jun 11, 2019 at 11:03:49AM +0100, Mark Rutland wrote:
> On Mon, Jun 10, 2019 at 01:26:15PM -0400, Qian Cai wrote:
> > On Mon, 2019-06-10 at 12:43 +0100, Will Deacon wrote:
> > > On Tue, Jun 04, 2019 at 03:23:38PM +0100, Mark Rutland wrote:
> > > > On Tue, Jun 04, 2019 at 10:0
On 6/6/19 11:27 PM, Dmitry Osipenko wrote:
07.06.2019 8:37, Bitan Biswas пишет:
Post suspend I2C registers have power on reset values. Before any
transfer initialize I2C registers to prevent I2C transfer timeout
and implement suspend and resume callbacks needed. Fix below errors
post suspend:
On Tue, May 28, 2019 at 02:10:37PM +0200, Michal Koutný
wrote:
> Although, on v1 we will lose the "no longer affine to..." message
> (which is what happens in your demo IIUC).
FWIW, I was wrong, off by one 'state' transition. So the patch doesn't
cause change in messaging (not tested though).
On Thu 13 Jun 07:23 PDT 2019, Jeffrey Hugo wrote:
> The PM8005 is used on the msm8998 MTP. The S1 regulator is VDD_GFX, ie
> it needs to be on and controlled inorder to use the GPU. Add support to
> drive the PM8005 regulators so that we can bring up the GPU on msm8998.
>
Reviewed-by: Bjorn An
On Wednesday 12 June 2019 03:54 PM, Wolfram Sang wrote:
On Tue, Jun 11, 2019 at 03:51:13AM -0700, Bitan Biswas wrote:
Fix expression for residual bytes(less than word) transfer
in I2C PIO mode RX/TX.
Signed-off-by: Bitan Biswas
I applied patches 1-5 to my for-next tree now. No need to rese
On Tuesday, 11. Juni 2019, 16:42:37 Benjamin Tissoires wrote:
> On Tue, Jun 11, 2019 at 2:13 PM Nicolas Saenz Julienne
>
> wrote:
> > NOTE: I CC'd Wolfgang as he's the one who can test this.
>
> I'll wait for Wolfram to confirm that the patch works before pushing then.
My name is Wolfgang, not
> On Jun 13, 2019, at 8:14 AM, Kirill A. Shutemov
> wrote:
>
> On Thu, Jun 13, 2019 at 03:03:01PM +, Song Liu wrote:
>>
>>
>>> On Jun 13, 2019, at 7:16 AM, Kirill A. Shutemov
>>> wrote:
>>>
>>> On Thu, Jun 13, 2019 at 01:57:30PM +, Song Liu wrote:
> And I'm not convinced that
On Thu, Jun 13, 2019 at 11:18 AM Tomer Maimon wrote:
>
>
> Probably the only vendors that will use the snoop will be Nuvoton and Aspeed.
> is it worth to create new snoop common user interface for it,
> if we will develop a new snoop user interface who will be the maintainer?
One or more of you w
Hi Naga,
On Thu, Jun 13, 2019 at 10:18:00AM +, Naga Sureshkumar Relli wrote:
> I spent much of time to address all your comments.
> All are addressed and tested. except the above one(address offset calculation)
> I didn't see any issue with the address calculation.
Let me first point out that
Right justified format is actually not supported by the amlogic tdm input
decoder.
Fixes: 13a22e6a98f8 ("ASoC: meson: add tdm input driver")
Signed-off-by: Jerome Brunet
---
sound/soc/meson/axg-tdmin.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/sound/soc/meson/axg-tdmin.c b/sound/soc/mes
Right justified format is actually not supported by the amlogic tdm output
encoder.
Fixes: c41c2a355b86 ("ASoC: meson: add tdm output driver")
Signed-off-by: Jerome Brunet
---
sound/soc/meson/axg-tdmout.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/sound/soc/meson/axg-tdmout.c b/sound/soc
There a mix of SND_SOC_DAIFMT_ and SND_SOC_DAI_FORMAT_ in
axg-tdm-interface.c. Even, if this is currently the same thing, lets use
the same group consistently.
Signed-off-by: Jerome Brunet
---
sound/soc/meson/axg-tdm-interface.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --g
Hi Dave,
On Thu, Jun 13, 2019 at 12:02:35PM +0100, Dave P Martin wrote:
> On Wed, Jun 12, 2019 at 01:43:20PM +0200, Andrey Konovalov wrote:
> > +/*
> > + * Global sysctl to disable the tagged user addresses support. This control
> > + * only prevents the tagged address ABI enabling via prctl() and
Daniel Axtens writes:
> Pawel Dembicki writes:
>
>> Enable kernel XZ compression option on PPC_85xx. Tested with
>> simpleImage on TP-Link TL-WDR4900 (Freescale P1014 processor).
>>
>> Suggested-by: Christian Lamparter
>> Signed-off-by: Pawel Dembicki
>> ---
>> arch/powerpc/Kconfig | 2 +-
>>
The patchset fixes a few mistakes regarding the format on the i2s bus
on the Amlogic axg tdm drivers.
Jerome Brunet (4):
ASoC: meson: axg-tdmin: right_j is not supported
ASoC: meson: axg-tdmout: right_j is not supported
ASoC: meson: axg-tdm: fix sample clock inversion
ASoC: meson: axg-tdm:
On 6/12/19 3:24 AM, Wolfram Sang wrote:
On Tue, Jun 11, 2019 at 03:51:13AM -0700, Bitan Biswas wrote:
Fix expression for residual bytes(less than word) transfer
in I2C PIO mode RX/TX.
Signed-off-by: Bitan Biswas
I applied patches 1-5 to my for-next tree now. No need to resend them
anymore
On Thu, Jun 13, 2019 at 11:15:34AM +0100, Vincenzo Frascino wrote:
> Hi Catalin,
>
> On 12/06/2019 16:35, Catalin Marinas wrote:
> > Hi Vincenzo,
> >
> > Some minor comments below but it looks fine to me overall. Cc'ing
> > Szabolcs as well since I'd like a view from the libc people.
> >
>
> Th
On Thu, Jun 13, 2019 at 05:56:47AM +0800, Yang Shi wrote:
> The later patch would make THP deferred split shrinker memcg aware, but
> it needs page->mem_cgroup information in THP destructor, which is called
> after mem_cgroup_uncharge() now.
>
> So, move mem_cgroup_uncharge() from __page_cache_rel
On Thu, Jun 13, 2019 at 10:55 AM Arnd Bergmann wrote:
>
> - efi.tpm_final_log is a physical address that gets passed into
> memremap() to return a pointer
> - tpm2_calc_event_log_size() takes a pointer argument and
> dereferences it.
Where does it? It's passed with some added offset to
__calc
Hi Marco,
On 6/12/19 7:21 PM, Marco Felsch wrote:
> Hi Sébastien,
>
> On 19-06-06 18:46, Sébastien Szymanski wrote:
>> Add PXP node for i.MX6UL/L SoC.
>>
>> Signed-off-by: Sébastien Szymanski
>> ---
>> arch/arm/boot/dts/imx6ul.dtsi | 9 +
>> arch/arm/boot/dts/imx6ull.dtsi | 6 ++
>>
On Wed, Jun 12, 2019 at 12:32:58PM +0800, Hsin-Yi Wang wrote:
> Currently in arm64, FDT is mapped to RO before it's passed to
> early_init_dt_scan(). However, there might be some codes
> (eg. commit "fdt: add support for rng-seed") that need to modify FDT
> during init. Map FDT to RO after early fi
The content of SND_SOC_DAIFMT_FORMAT_MASK is a number, not a bitfield,
so the test to check if the format is i2s is wrong. Because of this the
clock setting may be wrong. For example, the sample clock gets inverted
in DSP B mode, when it should not.
Fix the lrclk invert helper function
Fixes: 1a1
On Thu, Jun 13, 2019 at 10:37:51AM +0800, Su Yanjun wrote:
>
> 在 2019/6/12 21:13, Neil Horman 写道:
> > On Tue, Jun 11, 2019 at 10:33:17AM +0800, Su Yanjun wrote:
> > > 在 2019/6/10 19:12, Neil Horman 写道:
> > > > On Mon, Jun 10, 2019 at 11:20:00AM +0800, Su Yanjun wrote:
> > > > > syzbot found a cras
When building with CONFIG_NET_DSA_REALTEK_SMI and CONFIG_REALTEK_PHY
enabled as loadable modules, we see the following warning:
warning: same module names found:
drivers/net/phy/realtek.ko
drivers/net/dsa/realtek.ko
Rework so the driver name is realtek-smi instead of realtek.
Reviewed-by: Li
Unfortunately, a couple of mistakes were made while implementing
Enlightened VMCS support, in particular, wrong clean fields were
used in copy_enlightened_to_vmcs12():
- exception_bitmap is covered by CONTROL_EXCPN;
- vm_exit_controls/pin_based_vm_exec_control/secondary_vm_exec_control
are covere
Building the userspace part of the flow_dissector resulted in:
prog_tests/flow_dissector.c: In function ‘tx_tap’:
prog_tests/flow_dissector.c:176:9: warning: implicit declaration
of function ‘writev’; did you mean ‘write’? [-Wimplicit-function-declaration]
return writev(fd, iov, ARRAY_SIZE(iov))
On 6/12/19 6:33 AM, Dmitry Osipenko wrote:
11.06.2019 21:22, Bitan Biswas пишет:
On 6/11/19 4:34 AM, Dmitry Osipenko wrote:
11.06.2019 10:38, Bitan Biswas пишет:
On 6/10/19 2:00 PM, Dmitry Osipenko wrote:
10.06.2019 22:41, Bitan Biswas пишет:
On 6/10/19 11:12 AM, Dmitry Osipenko wro
readl_poll_timeout() calls usleep_range() to sleep between reads.
usleep_range() doesn't work efficiently for tiny values.
Raise the polling delay in qcom_qmp_phy_enable() to bring it in line
with the delay in qcom_qmp_phy_com_init().
Signed-off-by: Marc Gonzalez
---
Vivek, do you remember why y
Get the reset control properties for the QSPI controller and bring them
out of reset. Most will have just one reset bit, but there is an additional
OCP reset bit that is used ECC. The OCP reset bit will also need to get
de-asserted as well. [1]
The reason this patch is needed is in the case where
On Thu, Jun 13, 2019 at 10:25:55AM +1000, Dave Chinner wrote:
> e.g. Process A has an exclusive layout lease on file F. It does an
> IO to file F. The filesystem IO path checks that Process A owns the
> lease on the file and so skips straight through layout breaking
> because it owns the lease and
On Thu, Jun 13, 2019 at 9:10 AM Bjorn Andersson
wrote:
>
> On Thu 13 Jun 07:22 PDT 2019, Jeffrey Hugo wrote:
>
> > From: Jorge Ramirez-Ortiz
> >
> > Signed-off-by: Jorge Ramirez-Ortiz
> > Signed-off-by: Jeffrey Hugo
> > ---
> > drivers/regulator/qcom_spmi-regulator.c | 7 +++
> > 1 file ch
On 6/12/19 7:30 AM, Dmitry Osipenko wrote:
11.06.2019 13:51, Bitan Biswas пишет:
Fix expression for residual bytes(less than word) transfer
in I2C PIO mode RX/TX.
Signed-off-by: Bitan Biswas
---
[snip]
/*
-* Update state before writing to FIFO. If this c
Dear Friend,
I came across your e-mail contact prior a private search while in need of
your assistance. My name is Aisha Gaddafi a single Mother and a Widow with
three Children. I am the only biological Daughter of late Libyan President
(Late Colonel Muammar Gaddafi).
I have investment funds
The QSPI module can have an optional reset signals that will hold the
module in a reset state.
Signed-off-by: Dinh Nguyen
---
v6: no change
v5: document reset-names
v4: no change
v3: created base on review comments
v2: did not exist
v1: did not exist
---
Documentation/devicetree/bindings/mtd/cad
As a preliminary step to AT_RANDOM alignment and randomization,
replaces STACK_ macros by elf_stack_ inline functions to make them
easier to reuse.
STACK_ROUND() needed a pointer to elf_addr_t, while STACK_ADD() and
STACK_ALLOC() don't. In the new functions, the current stack pointer
is an obvious
Hi,
The following patches are mostly focused on ensuring AT_RANDOM array is
aligned on 16bytes boundary, and while being located at a pseudo-random
offset on stack (at most 256 bytes).
This patchset also insert a random sized (at most 15 bytes) padding between
AT_RANDOM and AT_PLATFORM and/or AT_
As AT_RANDOM is on top of the stack, retrieving AT_RANDOM value
through getauxval() could help, if needed, an attacker accesses
interesting locations in program stack, if offset from top of the
stack is fixed/known beforehand.
As a pure cargo-cult feature, inspired by "x86/entry/64: randomize
kern
On 6/13/19 7:25 AM, Doug Ledford wrote:
So, to revive this patch, what I'd like to see is some attempt to
actually quantify a reasonable timeout for the default backlog depth,
then the patch should actually change the default to that reasonable
timeout, and then put in the ability to adjust the t
Hi James,
On 2019/6/6 0:29, James Morse wrote:
> Hello,
>
> On 07/05/2019 04:50, Chen Zhou wrote:
>> When crashkernel is reserved above 4G in memory, kernel should
>> reserve some amount of low memory for swiotlb and some DMA buffers.
>
>> Meanwhile, support crashkernel=X,[high,low] in arm64. Wh
On 05/06/2019 22:08, Bjorn Andersson wrote:
Boot splash screen or EFI framebuffer requires the display hardware to
operate while the Linux iommu driver probes. Therefore, we cannot simply
wipe out the SMR register settings programmed by the bootloader.
Detect which SMR registers are in use durin
If RC_CORE is not set, building fails:
drivers/media/pci/ttpci/av7110_ir.o: In function `av7110_ir_init':
av7110_ir.c:(.text+0x1b0): undefined reference to `rc_allocate_device'
av7110_ir.c:(.text+0x2c1): undefined reference to `rc_register_device'
av7110_ir.c:(.text+0x2dc): undefined reference to
> On 12 Jun 2019, at 21:25, Sean Christopherson
> wrote:
>
> On Wed, Jun 12, 2019 at 07:08:24PM +0200, Marius Hillenbrand wrote:
>> The Linux kernel has a global address space that is the same for any
>> kernel code. This address space becomes a liability in a world with
>> processor informat
Dear Friend,
I am Mrs Patricia lugan.am sending you this brief letter to solicit
your
partnership to transfer $18.5 million US Dollars.I shall send you more
information and procedures when I receive positive response from you.
please send me a message in my Email box(mrs.patricialu...@gmail.c
On 2019/6/6 0:32, James Morse wrote:
> Hi!
>
> On 07/05/2019 04:50, Chen Zhou wrote:
>> We use crashkernel=X to reserve crashkernel below 4G, which will fail
>> when there is no enough memory. Currently, crashkernel=Y@X can be used
>> to reserve crashkernel above 4G, in this case, if swiotlb or
Because AT_RANDOM array is put on stack after AT_PLATFORM and
AT_BASE_PLATFORM strings, it's aligned on a 1 byte boundary:
on x86:
$ for i in 1 2 3 ; do LD_SHOW_AUXV=1 ./bin32 | grep AT_RANDOM ; done
AT_RANDOM:0xffb91ffb
AT_RANDOM:0xffcd60eb
AT_RANDOM:0
Hi James,
On 2019/6/12 20:48, James Morse wrote:
Hi,
On 12/06/2019 10:08, Zenghui Yu wrote:
In current KVM/ARM code, no one will invoke trace_kvm_mmio_emulate().
Remove this TRACE_EVENT definition.
Oooer. We can't just go removing these things, they are visible to user-space.
I recall an ar
On Wed, Jun 12, 2019 at 08:23:20PM -0700, Matthew Wilcox wrote:
> On Thu, Jun 13, 2019 at 10:25:55AM +1000, Dave Chinner wrote:
> > On Wed, Jun 12, 2019 at 05:37:53AM -0700, Matthew Wilcox wrote:
> > > That's rather different from the normal meaning of 'exclusive' in the
> > > context of locks, whi
On 04-06-19, 16:47, Gary R Hook wrote:
> Well, I was uncomfortable with documentation that didn't match behavior.
That is the right way :)
>
> I see two choices (and I just chose one to start a conversation):
>
> 1) Accept this patch, with an infinite timeout, or
> 2) Leave the data type alone,
Hi Szabolcs,
thank you for your review.
On 13/06/2019 11:14, Szabolcs Nagy wrote:
> On 13/06/2019 10:20, Catalin Marinas wrote:
>> Hi Szabolcs,
>>
>> On Wed, Jun 12, 2019 at 05:30:34PM +0100, Szabolcs Nagy wrote:
>>> On 12/06/2019 15:21, Vincenzo Frascino wrote:
+2. ARM64 Tagged Address ABI
Hi Mathieu, Mark,
On 6/11/19 8:33 PM, Mathieu Desnoyers wrote:
- On Jun 11, 2019, at 6:57 PM, Mark Rutland mark.rutl...@arm.com wrote:
Hi Arnaldo,
On Tue, Jun 11, 2019 at 11:33:46AM -0300, Arnaldo Carvalho de Melo wrote:
Em Tue, Jun 11, 2019 at 01:53:11PM +0100, Raphael Gault escreveu:
On Thu, Jun 13, 2019 at 07:32:39AM +0200, Stefan Roese wrote:
> On 12.06.19 11:16, Andy Shevchenko wrote:
> > On Wed, Jun 12, 2019 at 10:13:05AM +0200, Stefan Roese wrote:
> > > On 11.06.19 16:48, Andy Shevchenko wrote:
> > > Do you something like this in mind?
> >
> > More likely
> >
> > static
Even when asynchronous page fault is disabled, KVM does not want to pause
the host if a guest triggers a page fault; instead it will put it into
an artificial HLT state that allows running other host processes while
allowing interrupt delivery into the guest.
However, the way this feature is trigg
On Wed, Jun 12, 2019 at 01:43:20PM +0200, Andrey Konovalov wrote:
> From: Catalin Marinas
>
> It is not desirable to relax the ABI to allow tagged user addresses into
> the kernel indiscriminately. This patch introduces a prctl() interface
> for enabling or disabling the tagged ABI with a global
On Thu, Jun 13, 2019 at 12:28:41AM -0700, Christoph Hellwig wrote:
> On Mon, Jun 10, 2019 at 03:14:18PM -0400, Kent Overstreet wrote:
> > Prep work for bcachefs - being a fork of bcache it also uses closures
>
> NAK. This obsfucation needs to go away from bcache and not actually be
> spread furth
On 10-06-19, 09:51, Peng Ma wrote:
> >> + goto err;
> >> +
> >> + comp_temp->fl_virt_addr =
> >> + (void *)((struct dpaa2_fd *)
> >> + comp_temp->fd_virt_addr + 1);
> >
> >casts and pointer math, what could go wrong!!
On 13/06/2019 12:12, Simon Horman wrote:
> On Thu, May 09, 2019 at 02:29:49PM +0200, Simon Horman wrote:
>> From: Cao Van Dong
>>
>> Document SoC specific bindings for R-Car H3/M3-N/E3 SoCs.
>
> Hi Daniel and Thomas,
>
> would you object to me taking this patch through the renesas tree.
> It has
Lu Shuaibing wrote on Thu, Jun 13, 2019:
> The p9_tag_alloc() does not initialize the transport error t_err field.
> The struct p9_req_t *req is allocated and stored in a struct p9_client
> variable. The field t_err is never initialized before p9_conn_cancel()
> checks its value.
>
> KUMSAN(Kernel
'mask_com_pcs_ready' is only useful if 'has_phy_com_ctrl' is true.
Since msm8998_pciephy_cfg.has_phy_com_ctrl is false, let's drop
msm8998_pciephy_cfg.mask_com_pcs_ready altogether.
Signed-off-by: Marc Gonzalez
---
This was a relic from copying msm8996_pciephy_cfg
---
drivers/phy/qualcomm/phy-qc
Sometimes, we want to control which of the matching drivers
binds to a subchannel device (e.g. for subchannels we want to
handle via vfio-ccw).
For pci devices, a mechanism to do so has been introduced in
782a985d7af2 ("PCI: Introduce new device binding path using
pci_dev.driver_override"). It mak
On Thu, 2019-06-13 at 10:22 +0100, Marc Zyngier wrote:
>
> It looks to me that masking at the PCI level is rather superfluous as
> long as the MSI controller HW has the capability to mask the interrupt
> on a per MSI basis. After all, most non MSI-X endpoint lack support
> for masking of individua
On Thu, Jun 13, 2019 at 08:51:17PM +0530, Anshuman Khandual wrote:
> acceptable ? What we have currently is wrong where vmap_pmd_range() could
> just wrap EBUSY as ENOMEM and send up the call chain.
It's not wrong. We do it in lots of places. Unless there's a caller
which really needs to know th
From: Oleg Nesterov
> Sent: 13 June 2019 10:43
> On 06/13, David Laight wrote:
> >
> > I tested NetBSD last night.
> > pselect() always calls the signal handlers even when an fd is ready.
> > I'm beginning to suspect that this is the 'standards conforming' behaviour.
>
> May be. May be not. I have
On 5/31/19 6:08 PM, Marco Elver wrote:
> This adds a new header to asm-generic to allow optionally instrumenting
> architecture-specific asm implementations of bitops.
>
> This change includes the required change for x86 as reference and
> changes the kernel API doc to point to bitops-instrumen
On Thu, Jun 13, 2019 at 04:00:30PM +0530, Sumit Garg wrote:
> Add support for TEE based trusted keys where TEE provides the functionality
> to seal and unseal trusted keys using hardware unique key.
>
> Refer to Documentation/tee.txt for detailed information about TEE.
>
> Approach taken in this
On 5/31/19 6:08 PM, Marco Elver wrote:
> This patch is a pre-requisite for enabling KASAN bitops instrumentation;
> using static_cpu_has instead of boot_cpu_has avoids instrumentation of
> test_bit inside the uaccess region. With instrumentation, the KASAN
> check would otherwise be flagged by o
On Thu, Jun 13, 2019 at 7:49 AM Ira Weiny wrote:
>
> On Wed, Jun 12, 2019 at 09:54:58PM +0800, Pingfan Liu wrote:
> > On Tue, Jun 11, 2019 at 04:29:11PM +, Weiny, Ira wrote:
> > > > Pingfan Liu writes:
> > > >
> > > > > As for FOLL_LONGTERM, it is checked in the slow path
> > > > > __gup_long
On Fri, May 24, 2019 at 08:23:46PM +0300, Dmitry Osipenko wrote:
> A proper External Memory Controller clock rounding and parent selection
> functionality is required by the EMC drivers. It is not available using
> the generic clock implementation, hence add a custom one. The clock rate
> rounding
On Thu, Jun 13, 2019 at 02:36:49PM +1000, Dave Chinner wrote:
> On Wed, Jun 12, 2019 at 08:23:20PM -0700, Matthew Wilcox wrote:
> > On Thu, Jun 13, 2019 at 10:25:55AM +1000, Dave Chinner wrote:
> > > On Wed, Jun 12, 2019 at 05:37:53AM -0700, Matthew Wilcox wrote:
> > > > That's rather different fro
These three patches have no dependency of each other, but related with the same
purpose
to improve get_user_page_fast(), patch [2/3]. Put them together.
v3->v4:
Place the check on FOLL_LONGTERM in gup_pte_range() instead of
get_user_page_fast()
Cc: Ira Weiny
Cc: Andrew Morton
Cc: Mike Rapop
FOLL_LONGTERM suggests a pin which is going to be given to hardware and
can't move. It would truncate CMA permanently and should be excluded.
FOLL_LONGTERM has already been checked in the slow path, but not checked in
the fast path, which means a possible leak of CMA page to longterm pinned
requir
On 13/06/2019 15:03, Vincenzo Frascino wrote:
> On 13/06/2019 13:28, Szabolcs Nagy wrote:
>> On 13/06/2019 12:16, Vincenzo Frascino wrote:
>>> On 13/06/2019 11:14, Szabolcs Nagy wrote:
On 13/06/2019 10:20, Catalin Marinas wrote:
> On Wed, Jun 12, 2019 at 05:30:34PM +0100, Szabolcs Nagy wro
In sock_getsockopt(), 'optlen' is fetched the first time from userspace.
'len < 0' is then checked. Then in condition 'SO_MEMINFO', 'optlen' is
fetched the second time from userspace without check.
if a malicious user can change it between two fetches may cause security
problems or unexpected beha
To better reflect the held state of pages and make code self-explaining,
rename nr as nr_pinned.
Signed-off-by: Pingfan Liu
Cc: Ira Weiny
Cc: Andrew Morton
Cc: Mike Rapoport
Cc: Dan Williams
Cc: Matthew Wilcox
Cc: John Hubbard
Cc: "Aneesh Kumar K.V"
Cc: Keith Busch
Cc: Christoph Hellwig
find_extend_vma assumes the caller holds mmap_sem as a reader (explained
in expand_downwards()). The path when we are extending the stack VMA to
accommodate argv[] pointers happens without the lock.
I was not able to cause an mm_struct corruption but an inserted
BUG_ON(!rwsem_is_locked(&mm->mmap_s
Introduce a GUP_LONGTERM_BENCHMARK ioctl to test longterm pin in gup fast
path.
Signed-off-by: Pingfan Liu
Cc: Ira Weiny
Cc: Andrew Morton
Cc: Mike Rapoport
Cc: Dan Williams
Cc: Matthew Wilcox
Cc: John Hubbard
Cc: "Aneesh Kumar K.V"
Cc: Keith Busch
Cc: Christoph Hellwig
Cc: Shuah Khan
C
On Thu 13 Jun 07:24 PDT 2019, Jeffrey Hugo wrote:
> From: Jorge Ramirez
>
> The PMS405 has 5 HFSMPS and 13 LDO regulators,
>
> This commit adds support for one of the 5 HFSMPS regulators (s3) to
> the spmi regulator driver.
>
> The PMIC HFSMPS 430 regulators have 8 mV step size and a voltage
>
On 11/06/19 12:56 PM, Manish Narani wrote:
> Apart from taps set by auto tuning, ZynqMP platform has feature to set
> the tap values manually. Add support to read tap delay values from
> DT and set the same in HW via ZynqMP SoC framework. Reading Tap
> Delays from DT is optional, if the property is
Add DT nodes for following devices on Tegra186 and Tegra194
* ACONNECT
* ADMA
* AGIC
Signed-off-by: Sameer Pujar
---
changes from previous revision
* fixed size value for ranges property in aconnect
arch/arm64/boot/dts/nvidia/tegra186.dtsi | 67
arch/arm64
Enable ACONNECT, ADMA and AGIC devices for following platforms
* Jetson TX2
* Jetson Xavier
Verified driver probe path and devices get registered fine.
Signed-off-by: Sameer Pujar
---
changes from previous revision - None
arch/arm64/boot/dts/nvidia/tegra186-p2771-.dts | 12 +++
spin_cpu_yield is unused, therefore remove it.
Signed-off-by: Heiko Carstens
---
arch/powerpc/include/asm/processor.h | 2 --
include/linux/processor.h| 9 -
2 files changed, 11 deletions(-)
diff --git a/arch/powerpc/include/asm/processor.h
b/arch/powerpc/include/asm/proces
stop_machine is the only user left of cpu_relax_yield. Given that it
now has special semantics which are tied to stop_machine introduce a
weak stop_machine_yield function which architectures can override, and
get rid of the generic cpu_relax_yield implementation.
Signed-off-by: Heiko Carstens
---
FWIW, it would be nice to get some Acks.
Given that this patch set touches common code only in a way that
shouldn't have any effect on any architecture except s390, I'll add
this to the s390 tree, unless somebody objects.
RFC->v2:
Use cpumask_next_wrap as suggested by Peter Zijlstra.
RFC:
The
Provide documentation for usage of TEE based Trusted Keys via existing
user-space "keyctl" utility. Also, document various use-cases.
Signed-off-by: Sumit Garg
---
Documentation/security/keys/tee-trusted.rst | 93 +
1 file changed, 93 insertions(+)
create mode 100644
On Wed, Jun 12, 2019 at 08:24:34AM -0700, Shobhit Kukreti wrote:
> On Wed, Jun 12, 2019 at 11:26:15AM +0100, Daniel Thompson wrote:
> > Hi Shobhit
> >
> > Thanks for the patch. Feedback below...
>
> Hi Daneil,
>
> You provided some valuable feedback. Thank you for your time and
> effort.
Hi Guenter,
> Thanks for the confirmation. Do you see the problem only with the
> ohci-sm501 driver or also with others ?
All are likely affected, but it depends, because I believe the problem is
that the USB subsystem runs out of memory. Please try the attached patch!
The pool assumed 4096 byte
Our platforms with below registers(CHCFG0 - CHCFG15) of eDMA
*---*
| Offset | Big endian Register| Little endian Register|
|--||---|
| 0x0 |CHCFG0 | CHCF
Add MAINTAINERS entry for TEE based Trusted Keys framework.
Signed-off-by: Sumit Garg
---
MAINTAINERS | 9 +
1 file changed, 9 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 57f496c..db84fc4 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -8728,6 +8728,15 @@ F: include/k
From: Martin Schwidefsky
The stop_machine loop to advance the state machine and to wait for all
affected CPUs to check-in calls cpu_relax_yield in a tight loop until
the last missing CPUs acknowledged the state transition.
On a virtual system where not all logical CPUs are backed by real CPUs
al
Enable support to register kernel memory reference with TEE. This change
will allow TEE bus drivers to register memory references.
Signed-off-by: Sumit Garg
---
drivers/tee/tee_shm.c | 16 ++--
include/linux/tee_drv.h | 1 +
2 files changed, 15 insertions(+), 2 deletions(-)
diff
Hello,
This issue was spotted on Ubuntu linux-kvm kernel, on which the
CONFIG_KALLSYMS was disabled intentionally.
I think this extra check could be helpful when running the net test directly.
$ make -C tools/testing/selftests TARGETS=net run_tests
Also, there is an identical check implemented in
201 - 300 of 1728 matches
Mail list logo
