On Wed, Nov 25, 2020 at 12:20:48PM +0100, Oscar Salvador wrote:
> diff --git a/drivers/acpi/acpi_memhotplug.c b/drivers/acpi/acpi_memhotplug.c
> index b02fd51e5589..1fe645ef0b6c 100644
> --- a/drivers/acpi/acpi_memhotplug.c
> +++ b/drivers/acpi/acpi_memhotplug.c
> @@ -172,6 +172,7 @@ static int
On Fri, 2020-11-27 at 06:21 -0500, Paolo Bonzini wrote:
> +* FIXME: interrupt.injected represents an interrupt that it's
You can drop the stray apostrophe from that "its" while you're moving
it...
smime.p7s
Description: S/MIME cryptographic signature
Hi Bjorn Lorenzo,
On 2020/11/25 19:23, Lorenzo Pieralisi wrote:
On Tue, Nov 24, 2020 at 05:20:37PM -0600, Bjorn Helgaas wrote:
On Wed, Oct 28, 2020 at 10:31:43AM +0900, Kunihiko Hayashi wrote:
This patch adds misc interrupt handler to detect and invoke PME/AER event.
In UniPhier PCIe
On Fri 27-11-20 15:53:14, Charan Teja Kalla wrote:
> Thanks Michal!!
>
> On 11/26/2020 2:48 PM, Michal Hocko wrote:
> > On Wed 25-11-20 16:18:06, Charan Teja Kalla wrote:
> >>
> >>
> >> On 11/24/2020 1:11 PM, Michal Hocko wrote:
> >>> On Mon 23-11-20 20:40:40, Charan Teja Kalla wrote:
>
>
On Sat, Nov 21, 2020 at 5:38 PM Jonathan Cameron wrote:
>
> On Thu, 19 Nov 2020 12:07:45 +0200
> Alexandru Ardelean wrote:
>
> > This change converts the configuration of the dual-channel mode from the
> > old platform-data, to the device_property_present() function, which
> > supports both
On 11/27/20 6:03 AM, Wei Li wrote:
Armv8.3 extends the SPE by adding:
- Alignment field in the Events packet, and filtering on this event
using PMSEVFR_EL1.
- Support for the Scalable Vector Extension (SVE).
The main additions for SVE are:
- Recording the vector length for SVE operations in
On Fri, 20 Nov 2020 at 16:27, Marc Zyngier wrote:
>
> On 2020-11-05 15:29, Ard Biesheuvel wrote:
> > When reseeding the CRNG periodically, arch_get_random_seed_long() is
> > called to obtain entropy from an architecture specific source if one
> > is implemented. In most cases, these are special
On 20-11-26 19:09:37, Greg Kroah-Hartman wrote:
> From: Will McVicker
>
> Needed for SuperSpeed Plus support for f_midi. This allows the
> gadget to work properly without crashing at SuperSpeed rates.
>
> Cc: Felipe Balbi
> Cc: stable
> Signed-off-by: Will McVicker
> Signed-off-by: Greg
On 27/11/2020 09:56, Srinivasa Rao Mandadapu wrote:
To support playback continuation after hard suspend(bypass powerd)
and resume:
Prepare device in platform trigger callback.
Make I2s and DMA control registers as non volatile.
Looks like there are two changes here, One is fixing the
Hello,
This series adds Last Level Cache Controller (LLCC) support for SM8250
SoC from Qualcomm.
All 3 patches in this series are expected to go through arm-soc tree.
Thanks,
Mani
Manivannan Sadhasivam (3):
dt-bindings: msm: Add LLCC for SM8250
arm64: dts: qcom: sm8250: Add support for
Add LLCC compatible for SM8250 SoC.
Signed-off-by: Manivannan Sadhasivam
---
Documentation/devicetree/bindings/arm/msm/qcom,llcc.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/arm/msm/qcom,llcc.yaml
SM8250 SoC uses LLCC IP version 2. In this version, the WRSC_EN register
needs to be written to enable the Write Sub Cache for each SCID. Hence,
use a dedicated "write_scid_en" member with predefined values and write
them for SoCs enabling the "llcc_v2" flag.
Signed-off-by: Manivannan Sadhasivam
I have just noticed that the title of this cover letter is wrong.
It should have been:
"clk: at91: adapt for dvfs"
Please let me know if you want me to send a new version for this update.
Thank you,
Claudiu
On 19.11.2020 17:43, Claudiu Beznea wrote:
> Hi,
>
> SAMA7G5 is capable of DVFS. The
Add support for Last Level Cache Controller (LLCC) in SM8250 SoC.
This LLCC is used to provide common cache memory pool for the cores in
the SM8250 SoC thereby minimizing the percore caches.
Signed-off-by: Manivannan Sadhasivam
---
arch/arm64/boot/dts/qcom/sm8250.dtsi | 6 ++
1 file
On Fri, Nov 13, 2020 at 10:26:54AM -0800, Sami Tolvanen wrote:
> e820__mapped_all is passed as a callback to is_mmconf_reserved, which
> expects a function of type:
>
> typedef bool (*check_reserved_t)(u64 start, u64 end, unsigned type);
>
> This trips indirect call checking with Clang's
On Mon, Nov 23, 2020 at 09:22:08PM +0800, Yunfeng Ye wrote:
> In realtime scenarios, the "nohz_full" parameter is configured. Tick
> interference is not expected when there is only one realtime thread.
> But when the idle thread is switched to the realtime thread, the tick
> timer is restarted
> On Nov 26, 2020, at 22:45, Chen Yu wrote:
>
> On Thu, Nov 26, 2020 at 08:05:02PM +0800, Kai-Heng Feng wrote:
>>
>>
>>> On Nov 26, 2020, at 19:10, Chen Yu wrote:
>>>
>>> On Thu, Nov 26, 2020 at 02:36:42PM +0800, Kai-Heng Feng wrote:
>>
>> What about plugging ethernet cable and
On Thu, Nov 26, 2020 at 05:23:59PM -0500, Peter Xu wrote:
> For missing mode uffds, fault around does not help because if the page cache
> existed, then the page should be there already. If the page cache is not
> there, nothing else we can do, either. If the fault-around code is destined
> to
On Fri 20-11-20 19:04:52, David Hildenbrand wrote:
> commit 6471384af2a6 ("mm: security: introduce init_on_alloc=1 and
> init_on_free=1 boot options") resulted with init_on_alloc=1 in all pages
> leaving the buddy via alloc_pages() and friends to be
> initialized/cleared/zeroed on allocation.
>
>
On Thu, 26 Nov 2020 at 17:35, Willem de Bruijn
wrote:
> On Thu, Nov 26, 2020 at 3:19 AM Marco Elver wrote:
[...]
> > Will send v2.
>
> Does it make more sense to revert the patch that added the extensions
> and the follow-on fixes and add a separate new patch instead?
That doesn't work, because
From: Lars-Peter Clausen
Add support for the Analog Devices ADAU1372 audio CODEC.
[Alexandre Belloni: allow 32kHz for TDM4 in slave mode]
Signed-off-by: Lars-Peter Clausen
Signed-off-by: Alexandre Belloni
---
Changes in v2:
- Fix Microphone bias
sound/soc/codecs/Kconfig| 16 +
Add device tree binding documentation for Analog Devices ADAU1372.
Signed-off-by: Alexandre Belloni
Reviewed-by: Rob Herring
---
Changes in v2:
- Added Rob's reviewed-by
.../bindings/sound/adi,adau1372.yaml | 67 +++
1 file changed, 67 insertions(+)
create mode
Hi,
On 11/27/20 12:41 PM, Hans de Goede wrote:
> Hi,
>
> On 11/24/20 11:27 AM, Christoph Hellwig wrote:
>> On Mon, Nov 23, 2020 at 03:49:09PM +0100, Hans de Goede wrote:
>>> Hi,
>>>
>>> +Cc Christoph Hellwig
>>>
>>> Christoph, this is still an issue, so I've been looking around a bit and
>>>
Hello,
syzbot found the following issue on:
HEAD commit:418baf2c Linux 5.10-rc5
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=171555b950
kernel config: https://syzkaller.appspot.com/x/.config?x=b81aff78c272da44
dashboard link:
After migration to the shared interrupt support, the KSZ8031 PHY with
enabled interrupt support was not able to notify about link status
change.
Fixes: 59ca4e58b917 ("net: phy: micrel: implement generic .handle_interrupt()
callback")
Signed-off-by: Oleksij Rempel
---
drivers/net/phy/micrel.c |
On Thu 2020-11-26 20:32:18, Kefeng Wang wrote:
>
> On 2020/11/26 19:48, John Ogness wrote:
> > Any record with a trailing newline (LOG_NEWLINE flag) cannot
> > be continued because the newline has been stripped and will
> > not be visible if the message is appended. This was already
> > handled
On Fri, Nov 27, 2020 at 09:42:03AM +0530, Srinivasa Rao Mandadapu wrote:
> To support playback continuation after resume problem in chrome
> audio server:
> Prepare device in platform trigger callback.
> Make I2s and DMA control registers as non volatile.
What is the actual issue this is fixing?
Hi Chun-Kuang,
On 20/11/2020 00:46, Chun-Kuang Hu wrote:
Hi, Matthias:
I've provided the example for why of this patch. How do you think
about this patch?
Patch looks good to me. If you want to take it through your tree you can add my
Acked-by: Matthias Brugger
Beware that you might need
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media
tags/media/v5.10-3
For a series of fixes for the new the virtual digital TV driver (vidtv),
which is meant to help doing tests with the digital TV core and media
userspace apps and libraries.
They
On 19/11/2020 15:13, Enric Balletbo Serra wrote:
Hi Weiyi,
Missatge de Weiyi Lu del dia dj., 19 de nov.
2020 a les 14:10:
On Thu, 2020-11-19 at 13:13 +0100, Enric Balletbo Serra wrote:
Hi Weiyi,
Thank you for the patch
Missatge de Weiyi Lu del dia dj., 19 de nov.
2020 a les 11:48:
The commit 281f1f99cf3a ("PCI: dwc: Detect number of iATU windows") gets
the values of pci->num_ib_windows and pci->num_ob_windows from iATU
registers instead of DT properties.
However, before the values are set, the allocations in dw_pcie_ep_init()
refer them to determine the sizes of
On 18.11.20 11:01, Andy Shevchenko wrote:
>>> So a system without CONFIG_OF might still make use of .of_match_table?
>>
>> Yep!
>
> If you are curious:
> https://elixir.bootlin.com/linux/latest/source/drivers/acpi/bus.c#L615
Phuh, this changes everything ... sorry, didn't know that.
If ACPI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Linus,
Please pull some more powerpc fixes for 5.10.
Note this includes a merge of the powerpc-cve-2020-4788 tag, which you already
have, so that I could fix a build break it introduced. That merge should be a
nop from your POV.
cheers
The
On 27/11/2020 09:57, Marc Zyngier wrote:
If I understand the code correctly, MSI_ALLOC_FLAGS_SHARED_DEVICE is
supposed to be set in info->flags in platform_msi_set_desc(), but this
is called per-msi after its_msi_prepare(), so we don't the flags set
at the right time. That's how it looks to
On Fri, Nov 27, 2020 at 1:31 PM Swapnil Ingle wrote:
>
> Adding name to the Contributors List
>
> Signed-off-by: Swapnil Ingle
Hi, Swapnil,
Thanks for your past contributions, sorry for missing your name on the list.
Acked-by: Jack Wang
> ---
> drivers/block/rnbd/README | 1 +
> 1 file
On 2020-11-27 12:45, John Garry wrote:
On 27/11/2020 09:57, Marc Zyngier wrote:
If I understand the code correctly, MSI_ALLOC_FLAGS_SHARED_DEVICE is
supposed to be set in info->flags in platform_msi_set_desc(), but
this
is called per-msi after its_msi_prepare(), so we don't the flags set
at
On Fri, 2020-11-27 at 06:21 -0500, Paolo Bonzini wrote:
> This is my take on the split irqchip bug that David reported. It's a
> much more complicated patch, but I think it really gets to the bottom
> of the issue and the code is clearer.
Looks good to me; thanks. With the exception of the
Extend speed-bin support to a618 gpu.
Signed-off-by: Akhil P Oommen
---
drivers/gpu/drm/msm/adreno/adreno_device.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/msm/adreno/adreno_device.c
b/drivers/gpu/drm/msm/adreno/adreno_device.c
index e0ff16c..21db7ae 100644
---
Add support for gpu fuse to help identify the supported opps.
Signed-off-by: Akhil P Oommen
---
arch/arm64/boot/dts/qcom/sc7180.dtsi | 22 ++
1 file changed, 22 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sc7180.dtsi
b/arch/arm64/boot/dts/qcom/sc7180.dtsi
index
So far a530v2 gpu has support for detecting its supported opps
based on a fuse value called speed-bin. This patch makes this
support generic across gpu families. This is in preparation to
extend speed-bin support to a6x family.
Signed-off-by: Akhil P Oommen
---
Changes from v1:
1. Added
On 11/16/2020 10:44 PM, Jordan Crouse wrote:
On Mon, Nov 16, 2020 at 07:40:03PM +0530, Akhil P Oommen wrote:
On 11/12/2020 10:05 PM, Jordan Crouse wrote:
On Thu, Nov 12, 2020 at 09:19:04PM +0530, Akhil P Oommen wrote:
So far a530v2 gpu has support for detecting its supported opps
based on a
"regualtor" -> "regulator"
Signed-off-by: Michael Klein
---
Changes in v2:
- split patch
- make subject line more forthcoming
include/linux/mfd/si476x-core.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/mfd/si476x-core.h
"REGUALTOR" -> "REGULATOR"
Signed-off-by: Michael Klein
---
Changes in v2:
- split patch
- make subject line more forthcoming
drivers/regulator/da9055-regulator.c | 4 ++--
include/linux/mfd/da9055/reg.h | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git
On 11/27/20 12:21 PM, Paolo Bonzini wrote:
Centralize handling of interrupts from the userspace APIC
in kvm_cpu_has_extint and kvm_cpu_get_extint, since
userspace APIC interrupts are handled more or less the
same as ExtINTs are with split irqchip. This removes
duplicated code from
This allows downstream supplies and userspace to detect whether external power
is supplied.
The Librem 5 has the tp65982 in front of bq25980 charge controller. Since that
is capable of sinking and sourcing power the online property helps to decide
what to do. It also makes upower happy.
There
This is more in line with what tcpm does and will be needed
to avoid recursive dependency like
> drivers/power/supply/Kconfig:2:error: recursive dependency detected!
drivers/power/supply/Kconfig:2: symbol POWER_SUPPLY is selected by
TYPEC_TPS6598X
drivers/usb/typec/Kconfig:64: symbol
Signed-off-by: Michael Klein
---
No changes in v2
.../devicetree/bindings/regulator/mcp16502-regulator.txt| 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/regulator/mcp16502-regulator.txt
On 11/27/20 12:21 PM, Paolo Bonzini wrote:
kvm_cpu_accept_dm_intr and kvm_vcpu_ready_for_interrupt_injection are
a hodge-podge of conditions, hacked together to get something that
more or less works. But what is actually needed is much simpler;
in both cases the fundamental question is, do
This allows downstream supplies and userspace to detect
whether external power is supplied.
Signed-off-by: Guido Günther
---
drivers/usb/typec/Kconfig| 1 +
drivers/usb/typec/tps6598x.c | 105 +++
2 files changed, 106 insertions(+)
diff --git
On Fri, Nov 27, 2020 at 1:31 PM Swapnil Ingle wrote:
>
> Adding name to the Contributors List
>
> Signed-off-by: Swapnil Ingle
Acked-by: Danil Kipnis
> ---
> drivers/block/rnbd/README | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/block/rnbd/README
On Tue, Nov 24, 2020 at 2:58 PM Pratyush Yadav wrote:
>
> Hi,
>
> On 18/11/20 11:54PM, Pratyush Yadav wrote:
> > Hi,
> >
> > The Cypress Semper S28 flash family uses 2-bit ECC by default. Under
> > this ECC scheme, multi-pass page programs result in a program error.
> > This means that unlike
> On Fri, Nov 20, 2020 at 02:47:42PM +0100, Vincent Whitchurch wrote:
> > On Fri, Nov 20, 2020 at 01:14:50PM +0100, Adam Ward wrote:
> Actually, perhaps I'm missing something, but I don't quite see why this
> move to a sub-node is needed. There is some flexibility in the
> regulator framework for
On 27/11/2020 10:41, Sergey Senozhatsky wrote:
> We need to always set ->need_cache_sync_on_prepare and
> ->need_cache_sync_on_finish when we initialize vb2 buffer.
>
> Currently these flags are set/adjusted only in V4L2's
> vb2_queue_or_prepare_buf(), which means that for the code
> paths that
Hi Greg,
gentle reminder for this patch, lost in the middle of a DT series (DT
part already in stm32-next).
Thanks and regards,
Amelie
On 11/6/20 5:58 PM, Amelie Delaunay wrote:
Device tree property is named typec-power-opmode, not power-opmode.
Fixes: da0cb6310094 ("usb: typec: add
The following commit has been merged into the x86/cleanups branch of tip:
Commit-ID: 638920a66a17c8e1f4415cbab0d49dc4a344c2a7
Gitweb:
https://git.kernel.org/tip/638920a66a17c8e1f4415cbab0d49dc4a344c2a7
Author:Alex Shi
AuthorDate:Fri, 13 Nov 2020 16:58:14 +08:00
Committer:
When CONFIG_MTD_XIP=y, local_irq_disable() is called in xip_disable().
To avoid sleep in interrupt context, we need to call local_irq_enable()
before schedule().
The problem call stack is as follows:
bug1:
do_write_oneword_retry()
xip_disable()
Quoting Xing Zhengjun (2020-11-27 01:51:41)
>
>
> On 11/27/2020 5:34 AM, Chris Wilson wrote:
> > Quoting Xing Zhengjun (2020-11-26 01:44:55)
> >>
> >>
> >> On 11/25/2020 4:47 AM, Chris Wilson wrote:
> >>> Quoting Oliver Sang (2020-11-19 07:20:18)
> On Fri, Nov 13, 2020 at 04:27:13PM +0200,
On Fri, Nov 27, 2020 at 02:01:29PM +0100, Amelie DELAUNAY wrote:
> Hi Greg,
>
> gentle reminder for this patch, lost in the middle of a DT series (DT part
> already in stm32-next).
Odd, I don't see this anymore, can you resend just this one so I can
apply it directly?
thanks,
greg k-h
On 27 November 2020 12:52, Michael Klein wrote:
> "REGUALTOR" -> "REGULATOR"
>
> Signed-off-by: Michael Klein
Reviewed-by: Adam Thomson
From: Dragos Bogdan
Transmit/receive only is a valid SPI mode. For example, the MOSI/TX line
might be missing from an ADC while for a DAC the MISO/RX line may be
optional. This patch adds these two new modes: SPI_NO_TX and
SPI_NO_RX. This way, the drivers will be able to identify if any of
these
Following a change to the SPI framework, providing a value of zero for
'spi-rx-bus-width' and 'spi-tx-bus-width' is now possible and will
essentially mean than no RX or TX is allowed.
Signed-off-by: Alexandru Ardelean
---
Documentation/devicetree/bindings/spi/spi-controller.yaml | 6 --
1
This change moves all the SPI mode bits into a separate 'spi.h' header in
uapi. This is meant to re-use these definitions inside the kernel as well
as export them to userspace (via uapi).
The SPI mode definitions have usually been duplicated between between
'include/linux/spi/spi.h' and
Hallo
Mein Name ist George Mike. Ich bin von Beruf Rechtsanwalt. Ich möchte
Ihnen anbieten
der nächste Verwandte meines Klienten. Sie erben die Summe von (8,5
Millionen US-Dollar)
Dollar, die mein Kunde vor seinem Tod auf der Bank gelassen hat.
Mein Kunde ist ein Staatsbürger Ihres Landes, der
On 11/24/20 15:50, Will Deacon wrote:
> When confronted with a mixture of CPUs, some of which support 32-bit
Confronted made me laugh, well chosen word! :D
For some reason made me think of this :p
https://www.youtube.com/watch?v=NJbXPzSPzxc=1m33s
> applications and others which don't,
On Fri, Nov 27, 2020 at 5:29 AM Andrii Nakryiko
wrote:
>
> On Tue, Nov 24, 2020 at 7:16 AM KP Singh wrote:
> >
> > From: KP Singh
> >
[...]
>
> > +cleanup() {
> > +local tmp_dir="$1"
> > +local mount_img="${tmp_dir}/test.img"
> > +local mount_dir="${tmp_dir}/mnt"
> > +
On 27.11.20 г. 13:45 ч., Tomi Valkeinen wrote:
On 27/11/2020 01:17, Ivaylo Dimitrov wrote:
Hi Tomi,
On 26.11.20 г. 16:11 ч., Tomi Valkeinen wrote:
Hi Aaro, Ivaylo,
On 24/11/2020 23:03, Ivaylo Dimitrov wrote:
Is there any progress on the issue? I tried 5.9.1 and still nothing displayed.
On 11/24/20 15:50, Will Deacon wrote:
> Scheduling a 32-bit application on a 64-bit-only CPU is a bad idea.
>
> Ensure that 32-bit applications always take the slow-path when returning
> to userspace on a system with mismatched support at EL0, so that we can
> avoid trying to run on a 64-bit-only
On 11/27/20 2:07 PM, Greg Kroah-Hartman wrote:
On Fri, Nov 27, 2020 at 02:01:29PM +0100, Amelie DELAUNAY wrote:
Hi Greg,
gentle reminder for this patch, lost in the middle of a DT series (DT part
already in stm32-next).
Odd, I don't see this anymore, can you resend just this one so I can
code indent should use tabs where possible
Signed-off-by: Yevhen Viktorov
---
drivers/s390/scsi/zfcp_def.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/s390/scsi/zfcp_def.h b/drivers/s390/scsi/zfcp_def.h
index da8a5ceb615c..a2a59cbb330a 100644
---
On Thu, Nov 19, 2020 at 03:41:29PM +0100, Daniel Vetter wrote:
> I feel like this is ready for some wider soaking. Since the remaining bits
> are all kinda connnected probably simplest if it all goes through -mm.
Did you figure out a sumbission plan for this stuff?
> Daniel Vetter (17):
>
On 11/24/20 15:50, Will Deacon wrote:
> Allow systems with mismatched 32-bit support at EL0 to run 32-bit
> applications based on a new kernel parameter.
>
> Signed-off-by: Will Deacon
> ---
> Documentation/admin-guide/kernel-parameters.txt | 7 +++
> arch/arm64/kernel/cpufeature.c
Device tree property is named typec-power-opmode, not power-opmode.
Fixes: da0cb6310094 ("usb: typec: add support for STUSB160x Type-C controller
family")
Signed-off-by: Amelie Delaunay
Reviewed-by: Heikki Krogerus
---
drivers/usb/typec/stusb160x.c | 2 +-
1 file changed, 1 insertion(+), 1
On Fri, 27 Nov 2020, Michael Klein wrote:
> "REGUALTOR" -> "REGULATOR"
>
> Signed-off-by: Michael Klein
> ---
> Changes in v2:
> - split patch
> - make subject line more forthcoming
>
> drivers/regulator/da9055-regulator.c | 4 ++--
> include/linux/mfd/da9055/reg.h | 4 ++--
> 2
On 11/24/20 15:50, Will Deacon wrote:
[...]
> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> index d2003a7d5ab5..818c8f7bdf2a 100644
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -1860,24 +1860,18 @@ void do_set_cpus_allowed(struct task_struct *p, const
> struct cpumask
This is v2 of
https://sourceware.org/pipermail/libc-alpha/2020-November/119305.html
To enable BTI support, re-mmap executable segments instead of
mprotecting them in case mprotect is seccomp filtered.
I would like linux to change to map the main exe with PROT_BTI when
that is marked as BTI
The _dl_open_check and _rtld_main_check hooks are not called on the
dependencies of a loaded module, so BTI protection was missed on
every module other than the main executable and directly dlopened
libraries.
The fix just iterates over dependencies to enable BTI.
Fixes bug 26926.
---
Simple refactoring to keep failure handling next to
_dl_map_object_from_fd.
---
elf/dl-load.c | 48
1 file changed, 24 insertions(+), 24 deletions(-)
diff --git a/elf/dl-load.c b/elf/dl-load.c
index f3201e7c14..21e55deb19 100644
---
From: Chao Yu
For multi-device case, one f2fs image includes multi devices, so it
needs to account bytes written of all block devices belong to the image
rather than one main block device, fix it.
Signed-off-by: Chao Yu
---
fs/f2fs/checkpoint.c | 27 +++
fs/f2fs/f2fs.h
There are many failure paths that call lose to do local cleanups
in _dl_map_object_from_fd, but it did not clean everything.
Handle l_phdr, l_libname and mapped segments in the common failure
handling code.
There are various bits that may not be cleaned properly on failure
(e.g. executable
On Fri, 27 Nov 2020, Michael Klein wrote:
> "regualtor" -> "regulator"
>
> Signed-off-by: Michael Klein
> ---
> Changes in v2:
> - split patch
> - make subject line more forthcoming
>
> include/linux/mfd/si476x-core.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied,
On Fri, 27 Nov 2020, Miguel Ojeda wrote:
> On Fri, Nov 27, 2020 at 10:21 AM Lee Jones wrote:
> >
> > It's a per-subsystem convention thing.
>
> I think some allow both, too. For people that send tree-wide patches,
> it would be if we agreed on the convention...
I have no problem with that ...
On Fri, Nov 27, 2020 at 03:06:24PM +0200, Joonas Lahtinen wrote:
> Quoting ira.we...@intel.com (2020-11-24 08:07:39)
> > From: Ira Weiny
> >
> > Working through a conversion to a call such as kmap_thread() revealed
> > many places where the pattern kmap/memcpy/kunmap occurred.
> >
> > Eric
Program headers are processed in two pass: after the first pass
load segments are mmapped so in the second pass target specific
note processing logic can access the notes.
The second pass is moved later so various link_map fields are
set up that may be useful for note processing such as l_phdr.
To handle GNU property notes on aarch64 some segments need to
be mmaped again, so the fd of the loaded ELF module is needed.
When the fd is not available (kernel loaded modules), then -1
is passed.
The fd is passed to both _dl_process_pt_gnu_property and
_dl_process_pt_note for consistency.
Re-mmap executable segments if possible instead of using mprotect
to add PROT_BTI. This allows using BTI protection with security
policies that prevent mprotect with PROT_EXEC.
If the fd of the ELF module is not available because it was kernel
mapped then mprotect is used and failures are
On Fri, 27 Nov 2020, Bartosz Golaszewski wrote:
> On Fri, Nov 27, 2020 at 10:16 AM Lee Jones wrote:
> >
> >
> >
> > On Mon, 9 Nov 2020 at 16:34, Bartosz Golaszewski wrote:
> >>
> >> From: Bartosz Golaszewski
> >>
> >> rtc_register_device() is a managed interface but it doesn't use devres
> >>
On 11/24/20 15:50, Will Deacon wrote:
> When exec'ing a 32-bit task on a system with mismatched support for
> 32-bit EL0, try to ensure that it starts life on a CPU that can actually
> run it.
>
> Signed-off-by: Will Deacon
> ---
> arch/arm64/kernel/process.c | 42
Hi Lukasz,
On 27/11/2020 10:27, Lukasz Luba wrote:
>
>
> On 11/27/20 8:35 AM, gao.yunxi...@gmail.com wrote:
>> From: "jeson.gao"
>>
>> virtual thermal node definition description in dts file
>>
>> Signed-off-by: jeson.gao
>> ---
[ ... ]
> It's coming back. There were attempts to solve
From: Colin Ian King
Currently the call to vidtv_psi_pat_table_destroy frees the object
m->si.pat however m->si.pat->num_pmt is being accessed after the
free. Fix this by destroying m->si.pat after the m->si.pmt_secs[]
objects have been freed.
Addresses-Coverity: ("Read from pointer after
as-read-only/20201126-204442
base: https://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git
for-next
:: branch date: 10 hours ago
:: commit date: 10 hours ago
config: x86_64-randconfig-c002-20201127 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
If you fix the issue
On Fri, Nov 27, 2020 at 10:16:05AM +0200, Mike Rapoport wrote:
> On Thu, Nov 26, 2020 at 05:23:59PM -0500, Peter Xu wrote:
> > Faulting around for reads are in most cases helpful for the performance so
> > that
> > continuous memory accesses may avoid another trip of page fault. However it
> >
On 11/24/20 15:50, Will Deacon wrote:
> If the scheduler cannot find an allowed CPU for a task,
> cpuset_cpus_allowed_fallback() will widen the affinity to cpu_possible_mask
> if cgroup v1 is in use.
>
> In preparation for allowing architectures to provide their own fallback
> mask, just return
This series provides the Microchip Sparx5 Switch Driver
The Sparx5 Carrier Ethernet and Industrial switch family delivers 64 Ethernet
ports and up to 200 Gbps of switching bandwidth.
It provides a rich set of Ethernet switching features such as hierarchical QoS,
hardware-based OAM and service
Document the Sparx5 switch device driver bindings
Signed-off-by: Steen Hegelund
---
.../bindings/net/microchip,sparx5-switch.yaml | 633 ++
1 file changed, 633 insertions(+)
create mode 100644
Documentation/devicetree/bindings/net/microchip,sparx5-switch.yaml
diff --git
This provides switchdev support for the Microship Sparx5 PCB134 and PCB135
reference boards.
This commit depends on the following series currently on their way
into the kernel:
- Sparx5 SerDes Driver
Link:
https://lore.kernel.org/r/20201123114234.2292766-1-steen.hegel...@microchip.com/
-
Hello,
On Tue, Nov 24, 2020 at 7:37 PM Zhen Lei wrote:
>
> An appropriate return value should be set on the failed path.
>
> Reported-by: Hulk Robot
> Signed-off-by: Zhen Lei
Acked-by: Namhyung Kim
Thanks,
Namhyung
> ---
> tools/perf/builtin-diff.c | 4 +++-
> 1 file changed, 3
From: Bongsu Jeon
implement the NCI 2.x initial sequence to support NCI 2.x NFCC.
Since NCI 2.0, CORE_RESET and CORE_INIT sequence have been changed.
If NFCEE supports NCI 2.x, then NCI 2.x initial sequence will work.
In NCI 1.0, Initial sequence and payloads are as below:
(DH)
Thanks for digging into this everyone!
Assuming Tomasz doesn't find any stretching, I think we can conclude
that this mode works, and should be kept. Thanks Dongchun for parsing
the datasheet and finding the Bayer mode issue for the two other
recently added resolutions.
On Fri, 27 Nov 2020 at
Hi Mani,
On 2020-11-27 17:41, Manivannan Sadhasivam wrote:
SM8250 SoC uses LLCC IP version 2. In this version, the WRSC_EN
register
needs to be written to enable the Write Sub Cache for each SCID. Hence,
use a dedicated "write_scid_en" member with predefined values and write
them for SoCs
During cci_isr() errors read from register fields belonging to
i2c master1 are currently assigned to the status field belonging to
i2c master0. This patch corrects this error, and always assigns
master1 errors to the status field of master1.
Fixes: e517526195de ("i2c: Add Qualcomm CCI I2C
201 - 300 of 742 matches
Mail list logo
