Rationale:
Reduces attack surface on kernel devs opening the links for MITM
as HTTPS traffic is much harder to manipulate.
Deterministic algorithm:
For each file:
If not .svg:
For each line:
If doesn't contain `\bxmlns\b`:
For each link, `\bhttp://[^# \t\r\n]*(?:\w|/)`:
On Wed, Jul 8, 2020 at 1:08 PM Catalin Marinas wrote:
>
> On Wed, Jul 08, 2020 at 09:17:37AM +0200, Dmitry Vyukov wrote:
> > On Tue, Jul 7, 2020 at 8:17 PM Catalin Marinas
> > wrote:
> > > Kmemleak never performs well under heavy load. Normally you'd need to
> > > let the system settle for a bit
On 6/13/20 11:37 PM, Markus Elfring wrote:
From: Markus Elfring
Date: Sat, 13 Jun 2020 19:12:24 +0200
The brelse() function tests whether its argument is NULL
and then returns immediately.
Thus remove the tests which are not needed around the shown calls.
This issue was detected by using th
On Wed, Jul 8, 2020 at 9:14 AM Xia Jiang wrote:
>
> On Tue, 2020-07-07 at 15:35 +0200, Tomasz Figa wrote:
> > On Tue, Jul 7, 2020 at 8:47 AM Xia Jiang wrote:
> > >
> > > On Tue, 2020-06-30 at 16:53 +, Tomasz Figa wrote:
> > > > Hi Xia,
> > > >
> > > > On Tue, Jun 30, 2020 at 10:56:21AM +0800,
On 29-06-20, 21:57, Rikard Falkeborn wrote:
> sun6i_dphy_ops and sun6i_dphy_regmap_config are not modified so make them
> const structs to allow the compiler to put them in read-only memory.
>
> Before:
>textdata bss dec hex filename
>44071944 646415190f
>
On 7/7/20 7:36 PM, Roman Gushchin wrote:
> charge_slab_page() is not using the gfp argument anymore,
> remove it.
>
> Signed-off-by: Roman Gushchin
Acked-by: Vlastimil Babka
> ---
> mm/slab.c | 2 +-
> mm/slab.h | 3 +--
> mm/slub.c | 2 +-
> 3 files changed, 3 insertions(+), 4 deletions(-)
>
On 7/7/20 7:36 PM, Roman Gushchin wrote:
> Currently memcg_kmem_enabled() is optimized for the kernel memory
> accounting being off. It was so for a long time, and arguably the
> reason behind was that the kernel memory accounting was initially an
> opt-in feature. However, now it's on by default o
On 7/7/20 7:36 PM, Roman Gushchin wrote:
> charge_slab_page() and uncharge_slab_page() are not related anymore
> to memcg charging and uncharging. In order to make their names
> less confusing, let's rename them to account_slab_page() and
> unaccount_slab_page() respectively.
>
> Signed-off-by: Ro
Em Tue, Jul 07, 2020 at 02:14:49PM -0700, Ian Rogers escreveu:
> Setting the parse_events_error directly doesn't increment num_errors
> causing the error message not to be displayed. Use the
> parse_events__handle_error function that sets num_errors and handle
> multiple errors.
What was the comma
On 15-06-20, 22:53, Ansuel Smith wrote:
> Document dwc3 qcom phy hs and ss phy bindings needed to correctly
> inizialize and use usb on ipq806x SoC.
Rob ?
>
> Signed-off-by: Ansuel Smith
> ---
> v7:
> * Drop useless AllOf
> v6:
> * Add maximum value
> v5:
> * Fix dt_binding_check error
> v4:
>
On 2020/7/7 下午10:45, Kishon Vijay Abraham I wrote:
Hi Jason,
On 7/7/2020 3:17 PM, Jason Wang wrote:
On 2020/7/6 下午5:32, Kishon Vijay Abraham I wrote:
Hi Jason,
On 7/3/2020 12:46 PM, Jason Wang wrote:
On 2020/7/2 下午9:35, Kishon Vijay Abraham I wrote:
Hi Jason,
On 7/2/2020 3:40 PM, Jason W
On 08/07/20 11:36, Vitaly Kuznetsov wrote:
> @@ -4973,7 +4969,28 @@ void kvm_init_shadow_mmu(struct kvm_vcpu *vcpu, u32
> cr0, u32 cr4, u32 efer)
> context->mmu_role.as_u64 = new_role.as_u64;
> reset_shadow_zero_bits_mask(vcpu, context);
> }
> -EXPORT_SYMBOL_GPL(kvm_init_shadow_mmu);
On Wed, Jul 8, 2020 at 8:53 AM Alexander A. Klimov
wrote:
>
> Rationale:
> Reduces attack surface on kernel devs opening the links for MITM
> as HTTPS traffic is much harder to manipulate.
>
> Deterministic algorithm:
> For each file:
> If not .svg:
> For each line:
> If doesn't contai
On Fri, Jul 03, 2020 at 05:59:14PM +0200, Laurent Dufour wrote:
> When a secure memslot is dropped, all the pages backed in the secure device
> (aka really backed by secure memory by the Ultravisor) should be paged out
> to a normal page. Previously, this was achieved by triggering the page
> fault
Hi Guenter,
Agreed with the suggestion with regards to fan profile support.
Looked at thermal driver and further planning to implement required changes in
thermal core instead of pwm-fan driver.
Dropping the current series.
Thanks & Regards,
Sandipan
> -Original Message-
> From: Guent
On Wed 2020-07-08 09:09:00, Marek Szyprowski wrote:
> Since commit 4977caef05aa ("kthread: work could not be queued when worker
> being destroyed")
This commit should disappear from linux-next soon. We did not expect
that it would cause these warnings. We first want to fix the callers
before we pu
Use the devm_platform_get_and_ioremap_resource to simplify the code
a bit.
Signed-off-by: Jay Chen
---
drivers/perf/arm_smmuv3_pmu.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/perf/arm_smmuv3_pmu.c b/drivers/perf/arm_smmuv3_pmu.c
index 48e28ef93a70..2d09f3e47d1
Hi Prabhakar,
On Tue, Jul 7, 2020 at 6:18 PM Lad Prabhakar
wrote:
> From: Marian-Cristian Rotariu
>
> Add support for the RZ/G2H (R8A774E1) SoC to the Renesas Clock
> Pulse Generator / Module Standby and Software Reset driver.
>
> Signed-off-by: Marian-Cristian Rotariu
>
> Signed-off-by: Lad P
On Tue, Jul 7, 2020 at 6:18 PM Lad Prabhakar
wrote:
> From: Marian-Cristian Rotariu
>
> Document PFC support for the RZ/G2H (R8A774E1) SoC.
>
> Signed-off-by: Marian-Cristian Rotariu
>
> Signed-off-by: Lad Prabhakar
Reviewed-by: Geert Uytterhoeven
i.e. will queue in sh-pfc-for-v5.9.
Gr{oetj
As for the intel-iommu implementation, relegate the opportunistic
attempt to allocate a SAC address to the domain of conventional PCI
devices only, to avoid it increasingly causing far more performance
issues than possible benefits on modern PCI Express systems.
Signed-off-by: Robin Murphy
---
d
On Wed 08-07-20 16:27:16, Aneesh Kumar K.V wrote:
> Vlastimil Babka writes:
>
> > On 7/8/20 9:41 AM, Michal Hocko wrote:
> >> On Wed 08-07-20 16:16:02, Joonsoo Kim wrote:
> >>> On Tue, Jul 07, 2020 at 01:22:31PM +0200, Vlastimil Babka wrote:
> >>>
> >>> Simply, I call memalloc_nocma_{save,restor
For devices stuck behind a conventional PCI bus, saving extra cycles at
33MHz is probably fairly significant. However since native PCI Express
is now the norm for high-performance devices, the optimisation to always
prefer 32-bit addresses for the sake of avoiding DAC is starting to look
rather ana
Rationale:
Reduces attack surface on kernel devs opening the links for MITM
as HTTPS traffic is much harder to manipulate.
Deterministic algorithm:
For each file:
If not .svg:
For each line:
If doesn't contain `\bxmlns\b`:
For each link, `\bhttp://[^# \t\r\n]*(?:\w|/)`:
Hi all,
Changes since 20200707:
New tree: set_fs
My fixes tree contains:
dbf24e30ce2e ("device_cgroup: Fix RCU list debugging warning")
b236d81d9e4f ("powerpc/boot/dts: Fix dtc "pciex" warnings")
The kbuild tree still had its build failure for which I reverted a commit.
The f2fs tree gain
Hi,
On 7/8/20 1:01 PM, Hans de Goede wrote:
Hi,
On 7/7/20 10:19 AM, Kees Cook wrote:
Hi,
In looking for closely at the additions that got made to the
kernel_read_file() enums, I noticed that FIRMWARE_PREALLOC_BUFFER
and FIRMWARE_EFI_EMBEDDED were added, but they are not appropriate
*kinds* of
Am 2020-07-08 12:47, schrieb Vladimir Oltean:
On Tue, Jul 07, 2020 at 11:21:29PM +0200, Michael Walle wrote:
Now that there are USXGMII constants available, drop the old
definitions
and reuse the generic ones.
Signed-off-by: Michael Walle
---
drivers/net/dsa/ocelot/felix_vsc9959.c | 45
Move spi4_pins_a nodes from pinctrl_z to pinctrl
as the associated pins are not in BANK Z.
Fixes: 498a7014989dfdd9a47864b55704dc829ed0dc90
Signed-off-by: Patrick Delaunay
---
arch/arm/boot/dts/stm32mp15-pinctrl.dtsi | 28
1 file changed, 14 insertions(+), 14 deletions(-
Hi Parav, Hi Shay,
On 7/8/20 12:43 PM, Parav Pandit wrote:
> Hi Niklas,
>
... snip ...
>>>
>
> Sorry for my late response.
> Yes, this looks good and I also found same in my analysis.
> With latest code mlx5_pci_close() already does drain_health_wq(), so the
> additional call in remove_one() is
A complete correction of the unix name actually becomes SD-X, supply and
demand OS.
So this is now what it is called, with all things discussed included.
Supply and Demand being a monotheistic principle that decides what
happens on the OS, like indeed school teaches.
(Rather than "Uni" which
On 08/07/20 11:36, Vitaly Kuznetsov wrote:
> Undesired triple fault gets injected to L1 guest on SVM when L2 is
> launched with certain CR3 values. #TF is raised by mmu_check_root()
> check in fast_pgd_switch() and the root cause is that when
> kvm_set_cr3() is called from nested_prepare_vmcb_save(
On Wed, Jul 08, 2020 at 09:13:37AM +0200, Alexander A. Klimov wrote:
> Rationale:
> Reduces attack surface on kernel devs opening the links for MITM
> as HTTPS traffic is much harder to manipulate.
>
> Deterministic algorithm:
> For each file:
> If not .svg:
> For each line:
> If doesn
On Wed, Jul 08, 2020 at 01:37:41PM +0200, Hans de Goede wrote:
> Hi,
>
> On 7/8/20 1:01 PM, Hans de Goede wrote:
> > Hi,
> >
> > On 7/7/20 10:19 AM, Kees Cook wrote:
> > > Hi,
> > >
> > > In looking for closely at the additions that got made to the
> > > kernel_read_file() enums, I noticed that
Rationale:
Reduces attack surface on kernel devs opening the links for MITM
as HTTPS traffic is much harder to manipulate.
Deterministic algorithm:
For each file:
If not .svg:
For each line:
If doesn't contain `\bxmlns\b`:
For each link, `\bhttp://[^# \t\r\n]*(?:\w|/)`:
HI Ondrej,
On Wed, Jul 8, 2020 at 6:55 PM Ondrej Jirman wrote:
>
> I noticed several mobile Linux distributions failing to enable the
> thermal regulation correctly, because the kernel is silent
> when thermal driver fails to probe. Add enough error reporting
> to debug issues and warn users in ca
On 27/05/20 6:54 pm, Peter Zijlstra wrote:
> On Wed, May 27, 2020 at 12:47:16PM -0300, Arnaldo Carvalho de Melo wrote:
>> Em Wed, May 20, 2020 at 05:56:34PM +0200, Peter Zijlstra escreveu:
>>> On Tue, May 19, 2020 at 10:40:01PM -0300, Arnaldo Carvalho de Melo wrote:
PeterZ, from what we discus
To avoid complex and in some cases incorrect logic in
kvm_spec_ctrl_test_value, just try the guest's given value on the host
processor instead, and if it doesn't #GP, allow the guest to set it.
One such case is when host CPU supports STIBP mitigation
but doesn't support IBRS (as is the case with s
On Tue, Jul 7, 2020 at 6:18 PM Lad Prabhakar
wrote:
> Renesas RZ/G2H (r8a774e1) is pin compatible with R-Car H3 (R8A77951),
> however it doesn't have several automotive specific peripherals. Add
> automotive-specific pin groups/functions along with common pin
> groups/functions for supporting both
Hi,
On 7/8/20 1:55 PM, Luis Chamberlain wrote:
On Wed, Jul 08, 2020 at 01:37:41PM +0200, Hans de Goede wrote:
Hi,
On 7/8/20 1:01 PM, Hans de Goede wrote:
Hi,
On 7/7/20 10:19 AM, Kees Cook wrote:
Hi,
In looking for closely at the additions that got made to the
kernel_read_file() enums, I no
Hi Miao-chen,
> Even with one advertisement monitor in place, the scan policy should use
> the whitelist while the system is going to suspend to prevent waking by
> random advertisement.
>
> The following test was performed.
> - With a paired device, register one advertisement monitor, suspend
>
On 08/07/20 08:50, Xiaoyao Li wrote:
> +Note, when this IOCTL fails, KVM gives no guarantees that previous valid
> CPUID
> +configuration (if there is) is not corrupted. Userspace can get a copy of
> valid
> +CPUID configuration through KVM_GET_CPUID2 in case.
> +
> ::
I assume you mean "of the
This is my fault (can't even blame copy/paste).
Cc: Hannes Reinecke
Reported-by: Johannes Thumshirn
Signed-off-by: Lee Jones
---
drivers/scsi/libfc/fc_disc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/libfc/fc_disc.c b/drivers/scsi/libfc/fc_disc.c
index 42
Fixes the following W=1 kernel build warning(s):
drivers/scsi/libfc/fc_exch.c:66: warning: Function parameter or member 'left'
not described in 'fc_exch_pool'
drivers/scsi/libfc/fc_exch.c:66: warning: Function parameter or member 'right'
not described in 'fc_exch_pool'
drivers/scsi/libfc/fc_e
A couple of headers make no attempt to document their associated function
parameters. Others looks as if they are suffering with a little bitrot.
Fixes the following W=1 kernel build warning(s):
drivers/scsi/fcoe/fcoe.c:654: warning: Function parameter or member 'lport'
not described in 'fcoe_
This set is part of a larger effort attempting to clean-up W=1
kernel builds, which are currently overwhelmingly riddled with
niggly little warnings.
Slowly working through the SCSI related ones. There are many.
Lee Jones (30):
scsi: libfc: fc_exch: Supply some missing kerneldoc struct/functio
Fixes the following W=1 kernel build warning(s):
drivers/scsi/libfc/fc_rport.c:129: warning: Function parameter or member
'port_id' not described in 'fc_rport_create'
drivers/scsi/libfc/fc_rport.c:129: warning: Excess function parameter 'ids'
description in 'fc_rport_create'
drivers/scsi/libf
Mostly due to descriptions not keeping up with API changes.
Fixes the following W=1 kernel build warning(s):
drivers/scsi/libfc/fc_fcp.c:299: warning: Function parameter or member
'status_code' not described in 'fc_fcp_retry_cmd'
drivers/scsi/libfc/fc_fcp.c:595: warning: Function parameter or
Looks like the return value of readw() has never been checked.
Fixes the following W=1 kernel build warning(s):
drivers/scsi/qedf/qedf_main.c: In function ‘__qedf_probe’:
drivers/scsi/qedf/qedf_main.c:3203:6: warning: variable ‘tmp’ set but not used
[-Wunused-but-set-variable]
Cc: qlogic-stor
Description should state 'remote' port, not 'local'.
Fixes the following W=1 kernel build warning(s):
drivers/scsi/libfc/fc_rport.c:1452: warning: Function parameter or member
'rdata_arg' not described in 'fc_rport_logo_resp'
drivers/scsi/libfc/fc_rport.c:1452: warning: Excess function paramet
Fixes the following W=1 kernel build warning(s):
drivers/scsi/qedf/qedf_io.c: In function ‘qedf_cmd_timeout’:
drivers/scsi/qedf/qedf_io.c:25:5: warning: variable ‘op’ set but not used
[-Wunused-but-set-variable]
25 | u8 op = 0;
| ^~
drivers/scsi/qedf/qedf_io.c: In function ‘qedf_map_sg’:
dr
More bitrot issues with function documentation not keeping up with API changes.
Fixes the following W=1 kernel build warning(s):
drivers/scsi/pm8001/pm8001_init.c:64: warning: cannot understand function
prototype: 'const struct pm8001_chip_info pm8001_chips[] = '
drivers/scsi/pm8001/pm8001_ini
This is the only use of kerneldoc in the sourcefile and no
descriptions are provided.
Fixes the following W=1 kernel build warning(s):
drivers/scsi/aic94xx/aic94xx_init.c:538: warning: Function parameter or member
'asd_ha' not described in 'asd_free_edbs'
Cc: YueHaibing
Cc: Luben Tuikov
Sign
On Tue, Jul 07, 2020 at 05:24:11PM +0200, Jan Kara wrote:
> On Mon 06-07-20 08:42:24, syzbot wrote:
> > syzbot found the following crash on:
> >
> > HEAD commit:7cc2a8ea Merge tag 'block-5.8-2020-07-01' of git://git.ker..
> > git tree: upstream
> > console output: https://syzkaller.appsp
Function parameters need to be documented with format '@.*: '.
'to' is not longer asd_start_timers()'s function parameter.
Fixes the following W=1 kernel build warning(s):
drivers/scsi/aic94xx/aic94xx_hwi.c:589: warning: Function parameter or member
'asd_ha' not described in 'asd_init_ctxmem'
No attempt has been made to document any of the demoted functions here.
Fixes the following W=1 kernel build warning(s):
drivers/scsi/qedf/qedf_debugfs.c:25: warning: Function parameter or member
'qedf' not described in 'qedf_dbg_host_init'
drivers/scsi/qedf/qedf_debugfs.c:25: warning: Functio
Kerneldoc function parameter references need to be in the format '@.*: ',
else the kerneldoc checker gets confused.
Fixes the following W=1 kernel build warning(s):
drivers/scsi/qla4xxx/ql4_init.c: In function ‘ql4xxx_set_mac_number’:
drivers/scsi/qla4xxx/ql4_init.c:17:10: warning: variable ‘fu
'amount_xferred' is used, but only in certain circumstances. Place
the same stipulations on the defining/allocating of 'amount_xferred'
as is placed when using it.
We've been careful not to change any of the ordering semantics here.
Fixes the following W=1 kernel build warning(s):
drivers/scsi
And a few missing/excessive parameter descriptions.
Fixes the following W=1 kernel build warning(s):
drivers/scsi/aacraid/aachba.c:358: warning: Function parameter or member 'dev'
not described in 'aac_get_config_status'
drivers/scsi/aacraid/aachba.c:358: warning: Function parameter or member
Looks as though 'ahc' hasn't been used since 2005.
Fixes the following W=1 kernel build warning(s):
drivers/scsi/aic7xxx/aic7xxx_osm.c: In function ‘ahc_linux_slave_configure’:
drivers/scsi/aic7xxx/aic7xxx_osm.c:674:20: warning: variable ‘ahc’ set but not
used [-Wunused-but-set-variable]
674
Most likely caused by bitrot (docs not keeping in sync with API).
Fixes the following W=1 kernel build warning(s):
drivers/scsi/aacraid/linit.c: In function ‘aac_biosparm’:
drivers/scsi/aacraid/linit.c:368:41: warning: suggest braces around empty body
in an ‘if’ statement [-Wempty-body]
drive
Fixes the following W=1 kernel build warning(s):
drivers/scsi/aacraid/linit.c: In function ‘aac_biosparm’:
drivers/scsi/aacraid/linit.c:368:41: warning: suggest braces around empty body
in an ‘if’ statement [-Wempty-body]
368 | param->heads, param->sectors, num));
| ^
Cc: Adaptec OEM Raid So
Looks like none of the artifact from ahc_fetch_transinfo() are used anymore.
Fixes the following W=1 kernel build warning(s):
drivers/scsi/aic7xxx/aic7xxx_osm.c: In function ‘ahc_linux_target_alloc’:
drivers/scsi/aic7xxx/aic7xxx_osm.c:567:30: warning: variable ‘tinfo’ set but
not used [-Wunus
Mainly due to misdocumentation or bitrotted descriptions.
Fixes the following W=1 kernel build warning(s):
drivers/scsi/fcoe/fcoe_transport.c:396: warning: Function parameter or member
'skb' not described in 'fcoe_check_wait_queue'
drivers/scsi/fcoe/fcoe_transport.c:447: warning: Function para
Mostly missing or incorrect (bitrotted) function parameters.
Fixes the following W=1 kernel build warning(s):
drivers/scsi/fcoe/fcoe_ctlr.c:139: warning: Function parameter or member
'mode' not described in 'fcoe_ctlr_init'
drivers/scsi/fcoe/fcoe_ctlr.c:604: warning: Function parameter or memb
>From bitrotted and missing function parameters to misuse of kerneldoc format.
Fixes the following W=1 kernel build warning(s):
drivers/scsi/bnx2fc/bnx2fc_fcoe.c:1082: warning: Function parameter or member
'lport' not described in 'bnx2fc_update_src_mac'
drivers/scsi/bnx2fc/bnx2fc_fcoe.c:1082:
Looks like checking the 'targ' was removed in 2005.
Fixes the following W=1 kernel build warning(s):
drivers/scsi/aic7xxx/aic7xxx_osm.c: In function ‘ahc_send_async’:
drivers/scsi/aic7xxx/aic7xxx_osm.c:1604:28: warning: variable ‘targ’ set but
not used [-Wunused-but-set-variable]
1604 | struc
No attempt has been made to document either of the demoted functions here.
Fixes the following W=1 kernel build warning(s):
drivers/scsi/qedf/qedf_main.c:1027: warning: Function parameter or member
'lport' not described in 'qedf_xmit'
drivers/scsi/qedf/qedf_main.c:1027: warning: Function param
Likely a result of documentation not keeping up with API updates (a.k.a.
bitrot).
Fixes the following W=1 kernel build warning(s):
drivers/scsi/bnx2fc/bnx2fc_hwi.c:493: warning: Function parameter or member
'hba' not described in 'bnx2fc_send_session_destroy_req'
drivers/scsi/bnx2fc/bnx2fc_hw
No attempt has been made to document either of the demoted functions here.
Fixes the following W=1 kernel build warning(s):
drivers/scsi/bnx2fc/bnx2fc_tgt.c:442: warning: Function parameter or member
'lport' not described in 'bnx2fc_rport_event_handler'
drivers/scsi/bnx2fc/bnx2fc_tgt.c:442: wa
Looks good,
Reviewed-by: Johannes Thumshirn
I think Martin can fold this one into the original one
Ensure we do not copy the final one (which is not overwitten).
Fixes the following W=1 kernel build warning(s):
In file included from include/linux/bitmap.h:9,
from include/linux/nodemask.h:95,
from include/linux/mmzone.h:17,
from include/linux/gfp.h:6,
from include/linux/umh.h:4,
from incl
Fixes the following W=1 kernel build warning(s):
drivers/scsi/arcmsr/arcmsr_hba.c: In function ‘arcmsr_remap_pciregion’:
drivers/scsi/arcmsr/arcmsr_hba.c:286:30: warning: variable ‘flags’ set but not
used [-Wunused-but-set-variable]
286 | unsigned long addr, range, flags;
| ^
drivers/scs
Either misdocumentation and/or bitrot.
Fixes the following W=1 kernel build warning(s):
drivers/scsi/libfc/fc_lport.c:412: warning: Function parameter or member
'in_fp' not described in 'fc_lport_recv_echo_req'
drivers/scsi/libfc/fc_lport.c:412: warning: Excess function parameter 'fp'
descrip
According to 'include/scsi/scsi_transport_fc.h':
"Attributes are based on HBAAPI V2.0 definitions"
... so it seems sane to match the 'HBA Attribute Length' to them.
If we don't, the compiler complains that the copied data will be truncated.
Fixes the following W=1 kernel build warning(s):
In
On 08/07/2020 06:00, Krishna Reddy wrote:
> Move TLB timeout and spin count macros to header file to
> allow using the same from vendor specific implementations.
>
> Signed-off-by: Krishna Reddy
> ---
> drivers/iommu/arm-smmu.c | 3 ---
> drivers/iommu/arm-smmu.h | 2 ++
> 2 files changed, 2 i
On 08/07/2020 06:00, Krishna Reddy wrote:
> ioremap smmu mmio region before calling into implementation init.
> This is necessary to allow mapped address available during vendor
> specific implementation init.
>
> Signed-off-by: Krishna Reddy
> ---
> drivers/iommu/arm-smmu.c | 8
> 1
On 08/07/20 08:50, Xiaoyao Li wrote:
> Split the part of updating vcpu model out of kvm_update_cpuid(), and put
> it into a new kvm_update_vcpu_model(). So it's more clear that
> kvm_update_cpuid() is to update guest CPUID settings, while
> kvm_update_vcpu_model() is to update vcpu model (settings)
Hi Andreas,
> -Original Message-
> From: Andreas Schwab
> Sent: 01 July 2020 16:11
> To: Yash Shah
> Cc: Paul Walmsley ( Sifive) ;
> pal...@dabbelt.com; robh...@kernel.org; linux-ri...@lists.infradead.org;
> linux-kernel@vger.kernel.org; devicet...@vger.kernel.org; Sachin Ghadi
> ; a...@
On 08/07/20 08:50, Xiaoyao Li wrote:
> The name of callback cpuid_update() is misleading that it's not about
> updating CPUID settings of vcpu but updating the configurations of vcpu
> based on the CPUIDs. So rename it to update_vcpu_model().
>
> Signed-off-by: Xiaoyao Li
With the change suggest
On 08/07/20 08:50, Xiaoyao Li wrote:
> This serial is the extended version of
> https://lkml.kernel.org/r/20200528151927.14346-1-xiaoyao...@intel.com
>
> First two patches are bug fixing, and the others aim to refactor the flow
> of SET_CPUID* as:
>
> 1. cpuid check: check if userspace provides l
On Wed, 08 Jul 2020, Johannes Thumshirn wrote:
> Looks good,
>
> Reviewed-by: Johannes Thumshirn
>
> I think Martin can fold this one into the original one
Obviously I'd be okay with that, but it will depend on whether his
tree is able to be rebased. Many public trees are unrebasable (if
that
On 08/07/2020 14:12, Lee Jones wrote:
> Obviously I'd be okay with that, but it will depend on whether his
> tree is able to be rebased. Many public trees are unrebasable (if
> that's a word).
Yeah but in this early stage SCSI usually is re-baseable.
Richard Cochran writes:
> On Tue, Jul 07, 2020 at 08:56:41PM +0300, Sergey Organov wrote:
>> It won't. Supposedly it'd force clock (that doesn't tick by default and
>> stays at 0) to start ticking.
>
> No existing clockid_t has this behavior. Consider CLOCK_REALTIME or
> CLOCK_MONOTONIC.
>
> T
On 08/07/2020 14:04, Lee Jones wrote:
> @@ -1445,7 +1445,7 @@ static void fc_rport_recv_rtv_req(struct fc_rport_priv
> *rdata,
> * fc_rport_logo_resp() - Handler for logout (LOGO) responses
> * @sp: The sequence the LOGO was on
> * @fp: The LOGO response frame
> - * @
Rationale:
Reduces attack surface on kernel devs opening the links for MITM
as HTTPS traffic is much harder to manipulate.
Deterministic algorithm:
For each file:
If not .svg:
For each line:
If doesn't contain `\bxmlns\b`:
For each link, `\bhttp://[^# \t\r\n]*(?:\w|/)`:
On 08.07.20 08:50, David Hildenbrand wrote:
> On 07.07.20 14:13, David Hildenbrand wrote:
>> On 07.07.20 14:08, Heiko Carstens wrote:
>>> On Fri, Jul 03, 2020 at 03:39:08PM +0200, David Hildenbrand wrote:
This series is based on the latest s390/features branch [1]. It implements
vmemmap_f
Le 08/07/2020 à 13:25, Bharata B Rao a écrit :
On Fri, Jul 03, 2020 at 05:59:14PM +0200, Laurent Dufour wrote:
When a secure memslot is dropped, all the pages backed in the secure device
(aka really backed by secure memory by the Ultravisor) should be paged out
to a normal page. Previously, this
On Wed, Jul 8, 2020 at 2:03 PM Lee Jones wrote:
>
> More bitrot issues with function documentation not keeping up with API
> changes.
>
> Fixes the following W=1 kernel build warning(s):
>
> drivers/scsi/pm8001/pm8001_init.c:64: warning: cannot understand function
> prototype: 'const struct pm8
15 years ago, commit 6eded061b126 ("Fix up bus code and remove use of
rwsem") removed the bus rwsem, but left over a reference to it in a
kernel-doc comment. Drop it.
Signed-off-by: Lukas Wunner
---
drivers/base/dd.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/dri
On 08/07/2020 14:04, Lee Jones wrote:
> Description should state 'remote' port, not 'local'.
>
> Fixes the following W=1 kernel build warning(s):
>
> drivers/scsi/libfc/fc_rport.c:1452: warning: Function parameter or member
> 'rdata_arg' not described in 'fc_rport_logo_resp'
> drivers/scsi/lib
On Wed, Jul 08, 2020 at 07:57:23AM +, Song Bao Hua (Barry Song) wrote:
> > int dma_map_batch_start(struct device *dev, size_t rounded_len,
> > enum dma_data_direction dir, unsigned long attrs, dma_addr_t *addr);
> > int dma_map_batch_add(struct device *dev, dma_addr_t *addr, struct page
> >
On Wed, 8 Jul 2020 at 13:03, 彭浩(Richard) wrote:
>
>
> On Tue, Jul 07, 2020 at 07:46:08AM -0400, Peng Hao wrote:
> >> If plt_max_entries is 0, a warning is triggered.
> >> WARNING: CPU: 200 PID: 3000 at arch/arm64/kernel/module-plts.c:97
> >> module_emit_plt_entry+0xa4/0x150
> >
> > Which kernel a
Remove __packed attribute from struct scmi_event_header.
Signed-off-by: Cristian Marussi
---
drivers/firmware/arm_scmi/notify.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/firmware/arm_scmi/notify.c
b/drivers/firmware/arm_scmi/notify.c
index c4d006cfde88..7524153
Drop size_t in favour of fixed size u32 for consistency and shuffle
around fields definitions to minimize implicit padding.
Signed-off-by: Cristian Marussi
---
drivers/firmware/arm_scmi/notify.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/firmware/arm_scmi
Event reports are used to convey information describing events to the
registered user-callbacks: they are necessarily derived from the underlying
raw SCMI events' messages but they are not meant to expose or directly
mirror any of those messages data layout, which belong to the protocol
layer.
Usi
Substitute zero-length array defined in scmi_base_error_report with
a flexible length array definition.
Signed-off-by: Cristian Marussi
---
include/linux/scmi_protocol.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/scmi_protocol.h b/include/linux/scmi_protoco
On Wed, 08 Jul 2020, Johannes Thumshirn wrote:
> On 08/07/2020 14:04, Lee Jones wrote:
> > Description should state 'remote' port, not 'local'.
> >
> > Fixes the following W=1 kernel build warning(s):
> >
> > drivers/scsi/libfc/fc_rport.c:1452: warning: Function parameter or member
> > 'rdata_
On Wed, 08 Jul 2020, Johannes Thumshirn wrote:
> On 08/07/2020 14:04, Lee Jones wrote:
> > @@ -1445,7 +1445,7 @@ static void fc_rport_recv_rtv_req(struct
> > fc_rport_priv *rdata,
> > * fc_rport_logo_resp() - Handler for logout (LOGO) responses
> > * @sp: The sequence the LOGO was o
On 08/07/2020 06:00, Krishna Reddy wrote:
> NVIDIA's Tegra194 SoC has three ARM MMU-500 instances.
> It uses two of the ARM MMU-500s together to interleave IOVA
> accesses across them and must be programmed identically.
> This implementation supports programming the two ARM MMU-500s
> that must b
Richard Cochran writes:
> On Mon, Jul 06, 2020 at 06:27:21PM +0300, Vladimir Oltean wrote:
>> There's no correct answer, I'm afraid. Whatever the default value of the
>> clock may be, it's bound to be confusing for some reason, _if_ the
>> reason why you're investigating it in the first place is
On 08/07/2020 06:00, Krishna Reddy wrote:
> Add binding for NVIDIA's Tegra194 SoC SMMU.
>
> Signed-off-by: Krishna Reddy
> ---
> .../devicetree/bindings/iommu/arm,smmu.yaml| 18 ++
> 1 file changed, 18 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/iommu/
401 - 500 of 1549 matches
Mail list logo
