From: B K Karthik
Date: Sun, 26 Jul 2020 08:38:55 +0530
> @@ -103,10 +103,10 @@ static int __xfrm6_tunnel_spi_check(struct net *net,
> u32 spi)
> {
> struct xfrm6_tunnel_net *xfrm6_tn = xfrm6_tunnel_pernet(net);
> struct xfrm6_tunnel_spi *x6spi;
> - int index = xfrm6_tunnel_spi_
Joe Perches, le mar. 28 juil. 2020 17:24:47 -0700, a ecrit:
> On Tue, 2020-07-28 at 23:12 +0200, Samuel Thibault wrote:
> > diff --git a/MAINTAINERS b/MAINTAINERS
> []
> > @@ -16077,6 +16077,15 @@ Q:
> > https://patchwork.kernel.org/project/linux-sparse/list/
> > B: https://bugzilla.kernel.org/en
On Sat, Jul 18, 2020 at 4:35 PM Yu-cheng Yu wrote:
>
> On Sat, 2020-07-18 at 15:41 -0700, Dave Hansen wrote:
> > On 7/18/20 11:24 AM, Yu-cheng Yu wrote:
> > > On Sat, 2020-07-18 at 11:00 -0700, Andy Lutomirski wrote:
> > > > On Sat, Jul 18, 2020 at 10:58 AM Yu-cheng Yu
> > > > wrote:
> > > > > H
The nasty TODO items are done.
Signed-off-by: Samuel Thibault
---
v2: keep S: line in MAINTAINERS
.../ABI/stable}/sysfs-driver-speakup | 0
.../admin-guide}/spkguide.txt | 0
MAINTAINERS | 20 +--
drivers/accessibility
Added a missing comma and changed 'it it useful' to 'it is useful'.
Signed-off-by: Ankit Baluni
---
drivers/staging/iio/Documentation/overview.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/iio/Documentation/overview.txt
b/drivers/staging/iio/Documen
From: B K Karthik
Date: Sat, 25 Jul 2020 19:00:31 +0530
> use spi_byaddr instead of spi_byspi
...
> diff --git a/net/ipv6/xfrm6_tunnel.c b/net/ipv6/xfrm6_tunnel.c
> index 25b7ebda2fab..cab7693ccfe3 100644
> --- a/net/ipv6/xfrm6_tunnel.c
> +++ b/net/ipv6/xfrm6_tunnel.c
> @@ -103,10 +103,10 @@ sta
Hello,
On Tue, Jul 28, 2020 at 03:35:43PM -0700, Laurent Pinchart wrote:
> On Wed, Jul 29, 2020 at 12:02:05AM +0200, dan...@ffwll.ch wrote:
> > Hi Hyun Kwon,
> >
> > Are you all sorted with drm-misc commit rights so you can push the 3
> > (maybe there's more) xlnx fixup patches to drm-misc-next-fi
From: B K Karthik
Date: Sat, 25 Jul 2020 18:15:53 +0530
> fix slab-out-of-bounds Read in xfrm6_tunnel_alloc_spi
> by checking for existance of head for the list spi_byspi
spi_byspi is an array, therefore as long as xfrm6_tn is not NULL
then spi_byspi will also not be NULL.
Le mer. 29 juil. 2020 à 0:00, dan...@ffwll.ch a écrit :
On Tue, Jul 28, 2020 at 10:17:36PM +0200, Sam Ravnborg wrote:
Hi Paul.
On Tue, Jul 28, 2020 at 05:16:39PM +0200, Paul Cercueil wrote:
> Here are a few cleanups to the ingenic-drm driver.
> - some error paths were missing and have be
On Tue, 2020-07-28 at 17:37 -0500, Alex Elder wrote:
> On 7/27/20 1:32 PM, Gustavo A. R. Silva wrote:
> > Replace the existing /* fall through */ comments and its variants with
> > the new pseudo-keyword macro fallthrough[1].
> >
> > [1]
> > https://www.kernel.org/doc/html/v5.7/process/deprecated
On Tue, 2020-07-28 at 23:12 +0200, Samuel Thibault wrote:
> The nasty TODO items are done.
Nice.
> diff --git a/MAINTAINERS b/MAINTAINERS
[]
> @@ -16077,6 +16077,15 @@ Q:
> https://patchwork.kernel.org/project/linux-sparse/list/
> B: https://bugzilla.kernel.org/enter_bug.cgi?component=Spars
From: Xiyu Yang
Date: Sat, 25 Jul 2020 16:02:18 +0800
> ip6_route_info_create() invokes nexthop_get(), which increases the
> refcount of the "nh".
>
> When ip6_route_info_create() returns, local variable "nh" becomes
> invalid, so the refcount should be decreased to keep refcount balanced.
>
>
From: Luo bin
Date: Sat, 25 Jul 2020 15:11:17 +0800
> patch #1: support to handle hw abnormal event
> patch #2: improve the error messages when functions return failure and
> dump relevant registers in some exception handling processes
Series applied, thanks.
On 7/21/20 2:35 PM, William Breathitt Gray wrote:
This patch introduces a character device interface for the Counter
subsystem. Device data is exposed through standard character device read
operations. Device data is gathered when a Counter event is pushed by
the respective Counter device driver.
i386 randconfig-a003-20200728
i386 randconfig-a004-20200728
i386 randconfig-a005-20200728
i386 randconfig-a002-20200728
i386 randconfig-a006-20200728
i386 randconfig-a001-20200728
x86_64
A new field smt_active in cpuinfo_x86 identifies if the current core/cpu
is in SMT mode or not. This can be very helpful if the system has some
of its cores with threads offlined and can be used for cases where
action is taken based on the state of SMT. The follow up patches use
this feature.
Sugg
Implement a mechanism that allows tasks to conditionally flush
their L1D cache (mitigation mechanism suggested in 2). The previous
posts of these patches were sent for inclusion (see 3) and were not
included due to the concern for the need for additional checks,
those checks were:
1. Implement thi
Use the existing PR_GET/SET_SPECULATION_CTRL API to expose the L1D
flush capability. For L1D flushing PR_SPEC_FORCE_DISABLE and
PR_SPEC_DISABLE_NOEXEC are not supported.
There is also no seccomp integration for the feature.
Signed-off-by: Balbir Singh
---
arch/x86/kernel/cpu/bugs.c | 54 +++
Add documentation of l1d flushing, explain the need for the
feature and how it can be used.
Signed-off-by: Balbir Singh
---
Documentation/admin-guide/hw-vuln/index.rst | 1 +
.../admin-guide/hw-vuln/l1d_flush.rst | 70 +++
.../admin-guide/kernel-parameters.txt
cond_ibpb() has the necessary bits required to track the previous mm in
switch_mm_irqs_off(). This can be reused for other use cases like L1D
flushing on context switch.
[ tglx: Moved comment, added a separate define for state (re)initialization ]
Suggested-by: Thomas Gleixner
Signed-off-by: Bal
Implement a mechanism to selectively flush the L1D cache. The goal is to
allow tasks that want to save sensitive information, found by the recent
snoop assisted data sampling vulnerabilites, to flush their L1D on being
switched out. This protects their data from being snooped or leaked via
side ch
On Tue, Jul 28, 2020 at 4:37 PM Babu Moger wrote:
>
> The following series adds the support for PCID/INVPCID on AMD guests.
> While doing it re-structured the vmcb_control_area data structure to
> combine all the intercept vectors into one 32 bit array. Makes it easy
> for future additions.
>
> IN
From: David Woodhouse
Date: Thu, 23 Jul 2020 20:07:10 +0100
> From: René van Dorst
>
> Modify mtk_gmac0_rgmii_adjust() so it can always be called.
> mtk_gmac0_rgmii_adjust() sets-up the TRGMII clocks.
>
> Signed-off-by: René van Dorst
> Signed-off-By: David Woodhouse
> Tested-by: Frank Wunde
Hi Greg,
I love your patch! Perhaps something to improve:
[auto build test WARNING on char-misc/char-misc-testing]
[cannot apply to linux/master linus/master v5.8-rc7 next-20200728]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to
On Thu, Jul 09, 2020 at 09:31:37PM -0700, Kees Cook wrote:
> On Thu, Jul 09, 2020 at 04:51:15PM -0700, Julius Hemanth Pitti wrote:
> > protected_* files have 600 permissions which prevents
> > non-superuser from reading them.
> >
> > Container like "AWS greengrass" refuse to launch unless
> > prot
Signed-off-by: kernel test robot
---
gaudi/gaudi.c |2 +-
goya/goya.c |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/misc/habanalabs/gaudi/gaudi.c
b/drivers/misc/habanalabs/gaudi/gaudi.c
index d4b3b995f69d8..00a0a7238d814 100644
--- a/drivers/misc/haban
On Tue, Jul 28, 2020 at 4:38 PM Babu Moger wrote:
>
> host_intercept_exceptions is not used anywhere. Clean it up.
>
> Signed-off-by: Babu Moger
Reviewed-by: Jim Mattson
On Tue, Jul 28, 2020 at 4:38 PM Babu Moger wrote:
>
> Remove set_cr_intercept, clr_cr_intercept and is_cr_intercept. Instead
> call generic set_intercept, clr_intercept and is_intercept for all
> cr intercepts.
>
> Signed-off-by: Babu Moger
Reviewed-by: Jim Mattson
On Thu, Jul 09, 2020 at 02:19:20PM -0700, Palmer Dabbelt wrote:
> As part of adding STRICT_DEVMEM support to the RISC-V port, Zong provided an
> implementation of devmem_is_allowed() that's exactly the same as the version
> in
> a handful of other ports. Rather than duplicate code, I've put a gen
On Tue, Jul 28, 2020 at 4:38 PM Babu Moger wrote:
>
> Modify intercept_dr to generic intercepts in vmcb_control_area.
> Use generic __set_intercept, __clr_intercept and __is_intercept
> to set/clear/test the intercept_dr bits.
>
> Signed-off-by: Babu Moger
> ---
> arch/x86/include/asm/svm.h |
On Tue, Jul 28, 2020 at 4:38 PM Babu Moger wrote:
>
> Change intercept_cr to generic intercepts in vmcb_control_area.
> Use the new __set_intercept, __clr_intercept and __is_intercept
> where applicable.
>
> Signed-off-by: Babu Moger
> ---
> arch/x86/include/asm/svm.h | 42
On 7/28/2020 3:40 PM, Al Viro wrote:
On Tue, Jul 28, 2020 at 03:22:59PM -0700, Casey Schaufler wrote:
+ hlist_for_each_entry(p, &security_hook_heads.bdev_setsecurity, list) {
+ rc = p->hook.bdev_setsecurity(bdev, name, value, size);
+
+ if (rc == -ENOSYS)
+
On 7/28/2020 2:50 PM, Eric Biggers wrote:
On Tue, Jul 28, 2020 at 02:36:06PM -0700, Deven Bowers wrote:
The CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG introduced by Jaskaran was
intended to be used to allow an LSM to enforce verifications for all
dm-verity volumes.
However, with it's current imple
Hi Nicholas,
I love your patch! Yet something to improve:
[auto build test ERROR on openrisc/for-next]
[also build test ERROR on sparc-next/master sparc/master linus/master
asm-generic/master xtensa/for_next v5.8-rc7 next-20200728]
[cannot apply to nios2/for-linus]
[If your patch is applied to
Hi Greg,
I love your patch! Perhaps something to improve:
[auto build test WARNING on char-misc/char-misc-testing]
[cannot apply to linux/master linus/master v5.8-rc7 next-20200728]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to
On Tue, Jul 28, 2020 at 4:37 PM Babu Moger wrote:
>
> This is in preparation for the future intercept vector additions.
>
> Add new functions __set_intercept, __clr_intercept and __is_intercept
> using kernel APIs __set_bit, __clear_bit and test_bit espectively.
>
> Signed-off-by: Babu Moger
Sean
On 29/07/2020 03:42, Greg Kurz wrote:
> Hi Alexey,
>
> Working on 9p now ?!? ;-)
No, I am running syzkaller and seeing things :)
> Cc'ing Dominique Martinet who appears to be the person who takes care of 9p
> these days.
>
> On Tue, 28 Jul 2020 22:41:29 +1000
> Alexey Kardashevskiy wrote:
Hello Rob,
On Saturday 04 of January 2020 00:53:59 Rob Herring wrote:
> On Sat, Dec 21, 2019 at 03:07:31PM +0100, p...@cmp.felk.cvut.cz wrote:
> > From: Pavel Pisa
> >
> > Signed-off-by: Pavel Pisa
> > ---
> > .../devicetree/bindings/net/can/ctu,ctucanfd.txt | 61
> > ++ 1
The new intercept bits have been added in vmcb control area to support
few more interceptions. Here are the some of them.
- INTERCEPT_INVLPGB,
- INTERCEPT_INVLPGB_ILLEGAL,
- INTERCEPT_INVPCID,
- INTERCEPT_MCOMMIT,
- INTERCEPT_TLBSYNC,
Add new intercept vector in vmcb_control_area to support t
The following intercept bit has been added to support VMEXIT
for INVPCID instruction:
CodeNameCause
A2h VMEXIT_INVPCID INVPCID instruction
The following bit has been added to the VMCB layout control area
to control intercept of INVPCID:
Byte Offset Bit(s)Function
14h
Remove set_cr_intercept, clr_cr_intercept and is_cr_intercept. Instead
call generic set_intercept, clr_intercept and is_intercept for all
cr intercepts.
Signed-off-by: Babu Moger
---
arch/x86/kvm/svm/svm.c | 34 +-
arch/x86/kvm/svm/svm.h | 25 -
host_intercept_exceptions is not used anywhere. Clean it up.
Signed-off-by: Babu Moger
---
arch/x86/kvm/svm/nested.c |2 --
arch/x86/kvm/svm/svm.h|1 -
2 files changed, 3 deletions(-)
diff --git a/arch/x86/kvm/svm/nested.c b/arch/x86/kvm/svm/nested.c
index b0e47f474bb6..1318cf1cd0fe
Convert all the intercepts to one array of 32 bit vectors in
vmcb_control_area. This makes it easy for future intercept vector
additions. Also update trace functions.
Signed-off-by: Babu Moger
---
arch/x86/include/asm/svm.h | 14 +++---
arch/x86/kvm/svm/nested.c | 25 ++
Modify intercept_dr to generic intercepts in vmcb_control_area.
Use generic __set_intercept, __clr_intercept and __is_intercept
to set/clear/test the intercept_dr bits.
Signed-off-by: Babu Moger
---
arch/x86/include/asm/svm.h | 36 ++--
arch/x86/kvm/svm/nested.c
INVPCID instruction handling is mostly same across both VMX and
SVM. So, move the code to common x86.c.
Signed-off-by: Babu Moger
---
arch/x86/kvm/vmx/vmx.c | 62 +--
arch/x86/kvm/x86.c | 69
arch/x8
Modify intercept_exceptions to generic intercepts in vmcb_control_area.
Use the generic __set_intercept, __clr_intercept and __is_intercept to
set the intercept_exceptions bits.
Signed-off-by: Babu Moger
---
arch/x86/include/asm/svm.h | 22 +-
arch/x86/kvm/svm/nested.c |
Remove set_exception_intercept and clr_exception_intercept.
Replace with generic set_intercept and clr_intercept for these calls.
Signed-off-by: Babu Moger
---
arch/x86/kvm/svm/svm.c | 20 ++--
arch/x86/kvm/svm/svm.h | 18 --
2 files changed, 10 insertions(+),
The following series adds the support for PCID/INVPCID on AMD guests.
While doing it re-structured the vmcb_control_area data structure to
combine all the intercept vectors into one 32 bit array. Makes it easy
for future additions.
INVPCID interceptions are added only when the guest is running wit
This is in preparation for the future intercept vector additions.
Add new functions __set_intercept, __clr_intercept and __is_intercept
using kernel APIs __set_bit, __clear_bit and test_bit espectively.
Signed-off-by: Babu Moger
---
arch/x86/kvm/svm/svm.h | 15 +++
1 file changed,
Change intercept_cr to generic intercepts in vmcb_control_area.
Use the new __set_intercept, __clr_intercept and __is_intercept
where applicable.
Signed-off-by: Babu Moger
---
arch/x86/include/asm/svm.h | 42 --
arch/x86/kvm/svm/nested.c | 26
Hi, Guenter
> Subject: Re: [PATCH 1/2] watchdog: imx7ulp: Strictly follow the sequence for
> wdog operations
>
> On 7/27/20 11:42 PM, Anson Huang wrote:
> > According to reference manual, the i.MX7ULP WDOG's operations should
> > follow below sequence:
> >
> > 1. disable global interrupts;
> > 2
On 7/28/20 18:04, Gustavo A. R. Silva wrote:
> Tomas,
>
> Please, see some comments below...
>
> On 7/28/20 17:29, Winkler, Tomas wrote:
>>
>> Hi Tomas,
>>
>> On 7/28/20 16:41, Tomas Winkler wrote:
>>> Greg please revert, this commit it changes size of struct
>>> wired_
There's a race between rxrpc_sendmsg setting up a call, but then failing to
send anything on it due to an error, and recvmsg() seeing the call
completion occur and trying to return the state to the user.
An assertion fails in rxrpc_recvmsg() because the call has already been
released from the sock
> On Tue, 2020-07-28 at 22:14 +, Winkler, Tomas wrote:
> > > -Original Message-
> > > From: Gustavo A. R. Silva
> []
> > > I'm using this command:
> > >
> > > $ scripts/get_maintainer.pl --nokeywords --nogit --nogit-fallback
> > >
> > > and this is the output for both files:
> > >
> >
Expose recovery mechanism through sysfs rather than exposing through
debugfs. Some operating systems may limit access to debugfs through
access policies. This restricts user access to recovery mechanism,
hence move it to sysfs.
Signed-off-by: Rishabh Bhatnagar
---
Documentation/ABI/testing/sysfs
Expose coredump configuration from sysfs instead of debugfs.
In some operating systems access to debugfs might be limited.
This restricts user from selecting the coredump configuration
at all, hence move this interface to sysfs.
Signed-off-by: Rishabh Bhatnagar
---
Documentation/ABI/testing/sysf
>From Android R onwards Google has restricted access to debugfs in user
and user-debug builds. This restricts access to most of the features
exposed through debugfs. 'Coredump' and 'Recovery' are critical interfaces
that are required for remoteproc to work on Qualcomm Chipsets. Coredump
configurati
>
> Tomas,
>
> Please, see some comments below...
>
> On 7/28/20 17:29, Winkler, Tomas wrote:
> >
> > Hi Tomas,
> >
> > On 7/28/20 16:41, Tomas Winkler wrote:
> >> Greg please revert, this commit it changes size of struct
> >> wired_cmd_repeater_auth_stream_req_in, this
Uses .probe_new in place of .probe. Also uses device_get_match_data()
for whoami matching.
Signed-off-by: Daniel Campello
Reviewed-by: Andy Shevchenko
Reviewed-by: Stephen Boyd
---
Changes in v2:
- Added '\n' to dev_err()
drivers/iio/proximity/sx9310.c | 39 -
Makes use __aligned(8) to ensure that the timestamp is correctly aligned
when we call io_push_to_buffers_with_timestamp().
Also makes use of sizeof() for regmap_bulk_read instead of static value.
Signed-off-by: Daniel Campello
---
Changes in v2:
- Fixed commit message from "iio: sx9310: Align m
Uses for_each_set_bit() macro to loop over channel bitmaps.
Signed-off-by: Daniel Campello
Reviewed-by: Andy Shevchenko
---
Changes in v2:
- Changed prox_stat to chan_prox_stat bitmap.
drivers/iio/proximity/sx9310.c | 38 ++
1 file changed, 20 insertions(+), 1
Fixes enable/disable irq handling at various points. The driver needs to
only enable/disable irqs if there is an actual irq handler installed.
Signed-off-by: Daniel Campello
---
Changes in v2:
- Reordered error handling on sx9310_resume()
drivers/iio/proximity/sx9310.c | 26 --
Simplify compensation stage by using regmap_read_poll_timeout().
Signed-off-by: Daniel Campello
Reviewed-by: Andy Shevchenko
---
Changes in v2:
- Fixed dev_err() message
drivers/iio/proximity/sx9310.c | 25 ++---
1 file changed, 10 insertions(+), 15 deletions(-)
diff --g
Follows spec sheet for macro declarations.
Signed-off-by: Daniel Campello
Reviewed-by: Stephen Boyd
---
Changes in v2: None
drivers/iio/proximity/sx9310.c | 143 +++--
1 file changed, 67 insertions(+), 76 deletions(-)
diff --git a/drivers/iio/proximity/sx9310.c b/
On Tue, 2020-07-28 at 22:14 +, Winkler, Tomas wrote:
> > -Original Message-
> > From: Gustavo A. R. Silva
[]
> > I'm using this command:
> >
> > $ scripts/get_maintainer.pl --nokeywords --nogit --nogit-fallback
> >
> > and this is the output for both files:
> >
> > $ scripts/get_mai
Adds device tree bandings for sx9310 sensor.
Signed-off-by: Daniel Campello
Cc: Hartmut Knaack
Cc: Lars-Peter Clausen
Cc: Peter Meerwald-Stadler
Cc: Rob Herring
Reviewed-by: Douglas Anderson
[swb...@chromium.org: Add both regulators and make them optional]
Signed-off-by: Stephen Boyd
---
C
From: Stephen Boyd
This struct member isn't used. Drop it.
Fixes: 72ad02b15d63 ("iio: Add SEMTECH SX9310/9311 sensor driver")
Signed-off-by: Stephen Boyd
Reviewed-by: Douglas Anderson
Reviewed-by: Daniel Campello
Signed-off-by: Daniel Campello
Reviewed-by: Andy Shevchenko
---
Changes in v2
Improves readability by storing &client->dev in a local variable.
Signed-off-by: Daniel Campello
Reviewed-by: Andy Shevchenko
Reviewed-by: Stephen Boyd
---
Changes in v2:
- Added '\n' to dev_err()
drivers/iio/proximity/sx9310.c | 30 +++---
1 file changed, 15 inserti
On Tue, Jul 28, 2020 at 09:57:55PM +0100, James Ettle wrote:
> On Mon, 2020-07-27 at 16:47 -0500, Bjorn Helgaas wrote:
> >
> > I don't see anything in rtsx that enables L0s. Can you collect
> > the dmesg log when booting with "pci=earlydump"? That will show
> > whether the BIOS left it this way.
Fixes wrong copyright year.
Signed-off-by: Daniel Campello
---
Changes in v2: None
drivers/iio/proximity/sx9310.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/iio/proximity/sx9310.c b/drivers/iio/proximity/sx9310.c
index f7f44fd9198499..964fae90fefc25 10064
From: Stephen Boyd
Enable the main power supply (vdd) and digital IO power supply (svdd)
during probe so that the i2c communication and device works properly on
boards that aggressively power gate these supplies.
Signed-off-by: Stephen Boyd
Reviewed-by: Douglas Anderson
Signed-off-by: Daniel C
The first patch resends the DT binding for the driver that was merged in
v5.8-rc1 with a small change to update for proper regulators. The second
through the eleventh patch fixes several issues dropped from v8 to v9
when the initial patch was merged. The twelveth patch fixes a few
printks that are
Miscellaneous format fixes throughout the whole file.
Signed-off-by: Daniel Campello
Reviewed-by: Andy Shevchenko
Reviewed-by: Stephen Boyd
---
Changes in v2: None
drivers/iio/proximity/sx9310.c | 28 ++--
1 file changed, 10 insertions(+), 18 deletions(-)
diff --git
Avoids unused warnings due to acpi/of table macros.
Reported-by: kbuild test robot
Signed-off-by: Daniel Campello
---
Changes in v2:
- Added #include
drivers/iio/proximity/sx9310.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/iio/proximity/sx9310.c b/dri
Checks for non-zero return values to signal error conditions.
Signed-off-by: Daniel Campello
Reviewed-by: Andy Shevchenko
---
Changes in v2: None
drivers/iio/proximity/sx9310.c | 52 +-
1 file changed, 26 insertions(+), 26 deletions(-)
diff --git a/drivers/iio
From: Ankit Baluni
Removed braces for a 'if' condition as it contain only single line &
there is no need for braces for such case according to coding style
rules.
Signed-off-by: Ankit Baluni
---
Changes in v2:
-Added more description about the patch.
-Added space before the sy
Drop the warning on seeing "--" in handle_mem_options. This will trigger
whenever one of the memory options is present in the command line
together with "--", but there's no problem if that is the case.
Replace goto with break.
Signed-off-by: Arvind Sankar
---
arch/x86/boot/compressed/kaslr.c |
Drop unnecessary alignment of image_size to CONFIG_PHYSICAL_ALIGN in
find_random_virt_addr, it cannot change the result: the largest valid
slot is the largest n that satisfies
minimum + n * CONFIG_PHYSICAL_ALIGN + image_size <= KERNEL_IMAGE_SIZE
(since minimum is already aligned) and so n is eq
This check doesn't save anything. In the case when none of the
parameters are present, each strstr will scan args twice (once to find
the length and then for searching), six scans in total. Just going ahead
and parsing the arguments only requires three scans: strlen, memcpy, and
parsing. This will
Drop unnecessary check that number of slots is not zero in
store_slot_info, it's guaranteed to be at least 1 by the calculation.
Signed-off-by: Arvind Sankar
---
arch/x86/boot/compressed/kaslr.c | 9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/arch/x86/boot/compressed
Change type of minimum/image_size arguments in process_mem_region to
unsigned long. These actually can never be above 4G (even on x86_64),
and they're unsigned long in every other function except this one.
Signed-off-by: Arvind Sankar
---
arch/x86/boot/compressed/kaslr.c | 4 ++--
1 file changed
On 64-bit, the kernel must be placed below MAXMEM (64TiB with 4-level
paging or 4PiB with 5-level paging). This is currently not enforced by
KASLR, which thus implicitly relies on physical memory being limited to
less than 64TiB.
On 32-bit, the limit is KERNEL_IMAGE_SIZE (512MiB). This is enforced
Tomas,
Please, see some comments below...
On 7/28/20 17:29, Winkler, Tomas wrote:
>
> Hi Tomas,
>
> On 7/28/20 16:41, Tomas Winkler wrote:
>> Greg please revert, this commit it changes size of struct
>> wired_cmd_repeater_auth_stream_req_in, this is not what firmware
>
In case of an overlap, the beginning of the region should be used even
if it is exactly image_size, not just strictly larger.
Signed-off-by: Arvind Sankar
---
arch/x86/boot/compressed/kaslr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/boot/compressed/kaslr.c b/a
If the remaining size of the region is exactly 1Gb, there is still one
hugepage that can be reserved.
Signed-off-by: Arvind Sankar
---
arch/x86/boot/compressed/kaslr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/boot/compressed/kaslr.c b/arch/x86/boot/compressed/
v2->v3:
- Fix the first patch: command line size should be strlen + 1 to account
for terminating NUL. Avoid calling add_identity_map if cmdline was
NULL, though it should do nothing in that case anyway.
- Add a patch to drop the check to see if there are arguments we care
about before parsing
Since commit
0982adc74673 ("x86/boot/KASLR: Work around firmware bugs by excluding
EFI_BOOT_SERVICES_* and EFI_LOADER_* from KASLR's choice")
process_efi_entries will return true if we have an EFI memmap, not just
if it contained EFI_MEMORY_MORE_RELIABLE regions.
Signed-off-by: Arvind Sankar
-
32-bit does not have GB pages, so don't bother checking for them. Using
the IS_ENABLED allows the compiler to completely remove the
gb_huge_pages code.
Signed-off-by: Arvind Sankar
---
arch/x86/boot/compressed/kaslr.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x
Just a trivial rearrangement to do all the processing together, and only
have one call to slots_fetch_random in the source.
Signed-off-by: Arvind Sankar
---
arch/x86/boot/compressed/kaslr.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/arch/x86/boot/compressed/kaslr.c
Check in find_random_phys_addr that the chosen address is inside the
range that was required.
Signed-off-by: Arvind Sankar
---
arch/x86/boot/compressed/kaslr.c | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/arch/x86/boot/compressed/kaslr.c b/arch/x86/boot/compre
Replace the loop to determine the number of 1Gb pages with arithmetic.
Signed-off-by: Arvind Sankar
---
arch/x86/boot/compressed/kaslr.c | 46 ++--
1 file changed, 20 insertions(+), 26 deletions(-)
diff --git a/arch/x86/boot/compressed/kaslr.c b/arch/x86/boot/compres
The number of slots can be unsigned int, since on 64-bit, the maximum
amount of memory is 2^52, the minimum alignment is 2^21, so the slot
number cannot be greater than 2^31. But in case future processors have
more than 52 physical address bits, make it unsigned long.
The slot areas are limited by
No functional change.
Signed-off-by: Arvind Sankar
---
arch/x86/boot/compressed/kaslr.c | 13 ++---
arch/x86/boot/compressed/misc.h | 4 ++--
2 files changed, 8 insertions(+), 9 deletions(-)
diff --git a/arch/x86/boot/compressed/kaslr.c b/arch/x86/boot/compressed/kaslr.c
index b6ef77b
Change the type of local variables/fields that store mem_vector
addresses to u64 to make it less likely that 32-bit overflow will cause
issues on 32-bit.
Signed-off-by: Arvind Sankar
---
arch/x86/boot/compressed/kaslr.c | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
diff --
Clip the start and end of the region to minimum and mem_limit prior to
the loop. region.start can only increase during the loop, so raising it
to minimum before the loop is enough.
A region that becomes empty due to this will get checked in
the first iteration of the loop.
Drop the check for over
region.size can be trimmed to store the portion of the region before the
overlap, instead of a separate mem_vector variable.
Signed-off-by: Arvind Sankar
---
arch/x86/boot/compressed/kaslr.c | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/arch/x86/boot/compressed/kaslr
Handle the possibility that the command line is NULL.
Replace open-coded strlen with a function call.
Signed-off-by: Arvind Sankar
---
arch/x86/boot/compressed/kaslr.c | 26 ++
1 file changed, 14 insertions(+), 12 deletions(-)
diff --git a/arch/x86/boot/compressed/kaslr
cur_entry is only used as cur_entry.start + cur_entry.size, which is
always equal to end.
Signed-off-by: Arvind Sankar
---
arch/x86/boot/compressed/kaslr.c | 9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/arch/x86/boot/compressed/kaslr.c b/arch/x86/boot/compressed/kas
Set the region.size within the loop, which removes the need for
start_orig.
Signed-off-by: Arvind Sankar
---
arch/x86/boot/compressed/kaslr.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/arch/x86/boot/compressed/kaslr.c b/arch/x86/boot/compressed/kaslr.c
index f245
For additional robustness in the face of Hyper-V errors or malicious
behavior, validate all values that originate from packets that Hyper-V
has sent to the guest in the host-to-guest ring buffer. Ensure that
invalid values cannot cause indexing off the end of an array, or
subvert an existing valida
201 - 300 of 1385 matches
Mail list logo
