On 04/12/19 at 02:55pm, Baoquan He wrote:
> kernel_randomize_memory() uses __PHYSICAL_MASK_SHIFT to calculate
> the maximum amount of system RAM supported. The size of the direct
> mapping section is obtained from the smaller one of the below two
> values:
>
> (actual system RAM size + padding si
On Sun, Apr 14, 2019 at 4:04 AM Darrick J. Wong wrote:
>
> On Sat, Apr 13, 2019 at 03:54:39PM -0500, Shawn Landden wrote:
>
> /me pulls out his close-reading glasses and the copy_file_range manpage...
>
> > If flags includes COPY_FILE_RANGE_FILESIZE then the length
> > copied is the length of the
Resend:
Fine tuning the patch log.
v1->v2:
Rewrite log of the two patches. No new code change.
~
v1 background:
The fixes for these two bugs were carried in the earlier patchset, patch
4/6 and patch 5/6:
[PATCH v4 0/6] S
On Sun, Apr 07, 2019 at 02:09:08PM -1000, Linus Torvalds wrote:
> On Sun, Apr 7, 2019 at 10:04 AM Kirill Smelkov wrote:
> >
> > Fixing regression on FUSE side is my reason to do this whole work -
> > that's why I care about it the most and ask.
>
> Yeah, we can do the actual FUSE fix, I think. Pr
kernel_randomize_memory() uses __PHYSICAL_MASK_SHIFT to calculate
the maximum amount of system RAM supported. The size of the direct
mapping section is obtained from the smaller one of the below two
values:
(actual system RAM size + padding size) vs (max system RAM size supported)
This calculati
kernel_randomize_memory() hardcodes the size of vmemmap section as 1 TB,
to support the maximum amount of system RAM in 4-level paging mode, 64 TB.
However, 1 TB is not enough for vmemmap in 5-level paging mode. Assuming
the size of struct page is 64 Bytes, to support 4 PB system RAM in 5-level,
6
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 4443f8e6ac7755cd775c70d08be8042dc2f936cb
commit: a1d642266c147b9e34bd683bed1b7a935cdbfb8c iio: chemical: add support for
Plantower PMS7003 sensor
date: 9 weeks ago
config: x86_64-randconfig-s3-04141349 (at
Am Donnerstag, 11. April 2019, 11:49:40 CEST schrieb Bartosz Golaszewski:
> From: Bartosz Golaszewski
>
> Resending again - this time with tags collected.
Queued for next merge window.
Thanks,
//richard
On Sat 2019-04-13 19:55:00, syzbot wrote:
> syzbot has bisected this bug to:
>
> commit 430e48ecf31f4f897047f22e02abdfa75730cad8
> Author: Amitoj Kaur Chawla
> Date: Thu Aug 10 16:28:09 2017 +
>
> leds: lm3533: constify attribute_group structure
>
> bisection log: https://syzkaller.a
Hello,
syzbot found the following crash on:
HEAD commit:6d0a5984 Merge branch 'x86-urgent-for-linus' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15629ab720
kernel config: https://syzkaller.appspot.com/x/.config?x=4fb64439e07a1ec0
da
On Sat, 13 Apr 2019 10:40:52 +0200
Richard Weinberger wrote:
> Stop using the legacy interface.
Thanks for converting the nandsim driver.
>
> Signed-off-by: Richard Weinberger
> ---
> drivers/mtd/nand/raw/nandsim.c | 78 --
> 1 file changed, 47 insertions(+),
On Sat, 13 Apr 2019 10:40:51 +0200
Richard Weinberger wrote:
> We well need struct nand_controller soon, so more stuff need to
> be parts of struct nandsim.
> While we are here, rename "nand" to "ns" to use the same naming scheme
> everywhere in nandsim.
>
> Signed-off-by: Richard Weinberger
R
On 04-04-19, 09:12, Jan Kotas wrote:
> On arm64 the cadence_master.c file doesn't compile.
>
> readl and writel are undefined.
> This patch fixes that by including io.h.
And I cant verify that without hacking kconfig to force compile the lib.
>
> Signed-off-by: Jan Kotas
> ---
> drivers/sound
On 10-04-19, 22:16, Pierre-Louis Bossart wrote:
> Visual inspections confirmed by checkpatch.pl --strict expose a number
> of style issues, specifically parameter alignment is inconsistent as
> if different contributors used different styles. Before we restart
> support for SoundWire with Sound Ope
On Sat, 13 Apr 2019, Xose Vazquez Perez wrote:
> [0.00] NX (Execute Disable) protection: disabled by kernel command
> line option
> [0.00] [ cut here ]
> [0.00] attempted to set unsupported pgprot: 8163 bits:
> 8000 supported
On 10-04-19, 22:16, Pierre-Louis Bossart wrote:
> SoundWire support will be provided in Linux with the Sound Open
> Firmware (SOF) on Intel platforms. Before we start adding the missing
> pieces, there are a number of warnings and style issues reported by
> checkpatch, cppcheck and Coccinelle that
On 11-04-19, 14:28, Pierre-Louis Bossart wrote:
> 0-day/Kbuild starts complaining about missed module dependencies and
> compilation issues. Since codecs and soc drivers need to be compilable
> independently, let's fix this using the following model:
I have not seen a build report on this one, is
I hope you had a lovely night, and you having a wonderful weekend.It is my
pleasure meeting you. Am sorry to bother you, i apologize for intruding upon
your privacy. My name is Wesley. I`m from the State. I am currently looking for
a relationship in which I feel loved. I hope you will be kind en
On 12-04-19, 16:21, Takashi Iwai wrote:
> On Fri, 12 Apr 2019 16:18:41 +0200,
> Mark Brown wrote:
> >
> > On Fri, Apr 12, 2019 at 09:07:41AM -0500, Pierre-Louis Bossart wrote:
> >
> > > config CODEC_XYX_SDW
> > >tristate "XYZ SDW Codec"
> > > depends on SOUNDWIRE
> > > sele
On 13-04-19, 11:12, Paul Gortmaker wrote:
> These two files are implicitly relying on an instance of including
> module.h from .
>
> Ideally, header files under include/linux shouldn't be adding
> includes of other headers, in anticipation of their consumers,
> but just the headers needed for the
On 08-04-19, 12:43, Pierre-Louis Bossart wrote:
>
>
> On 4/8/19 2:12 AM, Jan Kotas wrote:
> >
> >
> > > On 5 Apr 2019, at 17:04, Pierre-Louis Bossart
> > > wrote:
> > >
> > > On 4/5/19 2:26 AM, Jan Kotas wrote:
> > > >
> > > > ret = pm_runtime_get_sync(slave->bus->dev);
> > > > -
On Sun, 24 Mar 2019 15:27:25 +
Jonathan Cameron wrote:
> On Sat, 23 Mar 2019 18:28:06 +0100
> Artur Rojek wrote:
>
> > Extend the inkern API with a function for reading available
> > attribute values of iio channels.
> >
> > Signed-off-by: Artur Rojek
> If this goes through a route othe
On Sun, 24 Mar 2019 15:27:50 +
Jonathan Cameron wrote:
> On Sat, 23 Mar 2019 18:28:07 +0100
> Artur Rojek wrote:
>
> > Convert "iio_read_avail_channel_raw" over to a wrapper around
> > "iio_read_avail_channel_attribute".
> >
> > With the introduction of "iio_read_avail_channel_attribute",
On Thu, 11 Apr 2019, Huw Davies wrote:
> The 'mask' member of struct vsyscall_gtod_data is unused, so remove
> it. Its use was removed in commit a51e996d48ac (x86/vdso: Enforce
> 64bit clocksource).
That's true, but we are moving the VDSO to generic code, so the mask will stay.
Thanks,
On Sun, 7 Apr 2019 18:52:34 +0200
Sebastian Reichel wrote:
> Hi,
>
> On Sun, Mar 24, 2019 at 03:31:37PM +, Jonathan Cameron wrote:
> > On Sat, 23 Mar 2019 18:28:09 +0100
> > Artur Rojek wrote:
> >
> > > Add a driver for battery present on Ingenic JZ47xx SoCs.
> > >
> > > Signed-off-by:
On Mon, 8 Apr 2019 14:32:00 +
Jean-Baptiste Maneyrol wrote:
> Hello,
>
> overall looks good for me.
>
> I would just prefer to change the define name for temperature to
> INV_ICM20602_SCAN_TEMP. It is the chip temperature that can be used for
> temperature compensation for both accel and
Hello,
Recently, Naresh reported that the function-graph tracer on the latest
kernel crashes on arm. I could reproduce it and bisected. I finally found
the commit f9b58e8c7d03 ("ARM: 8800/1: use choice for kernel unwinders")
was the first bad commit.
Actually, this commit is just changing Kconfig
On Thu, 11 Apr 2019, Huw Davies wrote:
CC+: Vincenzo Frascino who is working on the generic VDSO.
> This will allow clocks with different mult and shift values,
> e.g. CLOCK_MONOTONIC_RAW, to be supported in the vDSO.
>
> The coarse clocks do not require these data so the values are not
> copied
syzbot has bisected this bug to:
commit 706249c222f68471b6f8e9e8e9b77665c404b226
Author: Peter Zijlstra
Date: Fri Jul 24 13:06:37 2015 +
locking/static_keys: Rework update logic
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=175cc58720
start commit: 1d2ba7fe Merge
Hi Bjorn,
Thanks a lot for your comments!
> -Original Message-
> From: Bjorn Helgaas [mailto:helg...@kernel.org]
> Sent: 2019年4月12日 22:01
> To: Z.q. Hou
> Cc: linux-...@vger.kernel.org; linux-arm-ker...@lists.infradead.org;
> devicet...@vger.kernel.org; linux-kernel@vger.kernel.org;
> ro
This fixes the -WDecl sparse warning in journal.c. Function was declared
as static void but the definition was void.
Signed-off-by: Bharath Vedartham
---
fs/reiserfs/journal.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/reiserfs/journal.c b/fs/reiserfs/journal.c
index
On Mon, 8 Apr 2019 15:15:56 +0200
H. Nikolaus Schaller wrote:
> Hi Jonathan,
>
> > Am 07.04.2019 um 14:30 schrieb Jonathan Cameron :
> >
> > On Sun, 31 Mar 2019 12:09:46 +0200
> > "H. Nikolaus Schaller" wrote:
> >
> > Hi Nikolaus,
> >
> > I'm probably going to repeat a few things I sent for
Depending on MACH_JZ4780 prevent us from creating a generic kernel that
works on more than one MIPS board. Instead, we just depend on MIPS being
set.
Signed-off-by: Paul Cercueil
Reviewed-by: Boris Brezillon
---
v2: No change
v3: No change
drivers/memory/Kconfig | 2 +-
1 file changed, 1 ins
Add support for the JZ4740 SoC from Ingenic.
Signed-off-by: Paul Cercueil
Reviewed-by: Boris Brezillon
---
v2: No change
v3: Support the JZ4740 instead of the JZ4725B (exact same functionality
but JZ4740 is already fully upstream)
drivers/memory/jz4780-nemc.c | 24 +--
Add a compatible string to support the memory controller built into the
JZ4740 SoC from Ingenic.
Signed-off-by: Paul Cercueil
Reviewed-by: Boris Brezillon
Reviewed-by: Rob Herring
---
v2: No change
v3: Change compatible string for jz4740 instead of j4725b
.../devicetree/bindings/memory-cont
The maximum value found in that array is 15, there's no need to store
these values as uint32_t, a uint8_t is enough.
Signed-off-by: Paul Cercueil
---
v2: Remove casts to uint32_t
v3: No change
drivers/memory/jz4780-nemc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dri
It's a beautiful morning from here lovely, i hope this letter met you in the
good health, Am Wesley willing to make good friends, bored just wish to know
you better, if I may be so bold. I consider myself an easy-going man,
adventurous, honest and fun loving person, Please forgive my manners am
I hope you had a lovely night, and you having a wonderful weekend.It is my
pleasure meeting you. Am sorry to bother you, i apologize for intruding upon
your privacy. My name is Wesley. I`m from the State. I am currently looking for
a relationship in which I feel loved. I hope you will be kind en
Silly sizeof(pointer) vs sizeof(uint8_t[]) bug.
Fixes: e483b0208784 ("proc: test /proc/*/maps, smaps, smaps_rollup, statm")
Signed-off-by: Alexey Dobriyan
---
tools/testing/selftests/proc/proc-pid-vm.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- a/tools/testing/selftests/p
On Mon, 8 Apr 2019 09:09:37 -0700
Randy Dunlap wrote:
> On 4/7/19 10:41 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20190405:
> >
>
> on i386 or x86_64:
>
> modular:
> ERROR: "is_stm32_timer_trigger" [drivers/iio/adc/stm32-dfsdm-adc.ko]
> undefined!
>
> or builtin:
> ld:
F29 bans mapping first 64KB even for root making test fail.
Iterate from address 0 until mmap() works.
Gentoo (root):
openat(AT_FDCWD, "/dev/zero", O_RDONLY) = 3
mmap(NULL, 4096, PROT_NONE, MAP_PRIVATE|MAP_FIXED, 3, 0) = 0
Gentoo (non-root):
openat(AT_FDCWD, "/dev/zero",
Add documentation for the "charge-status-gpios" property.
Update the "gpios" property with a valid example.
Signed-off-by: Artur Rojek
Reviewed-by: Rob Herring
---
Changes:
v2: - add a better description for the "status-gpios" property,
- add valid examples for the "gpios" and "status-gpio
Introduce optional support of POWER_SUPPLY_PROP_STATUS for chargers
which provide charging status GPIO.
Signed-off-by: Artur Rojek
---
Changes:
v2: no change
v3: rename "status_irq" and "status" fields to "charge_status_irq"
and "charge_status" accordingly
drivers/power/supply/gpio-charg
These regulator_ops variables never need to be modified, make them const so
compiler can put them to .rodata.
Signed-off-by: Axel Lin
---
drivers/regulator/max8998.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/regulator/max8998.c b/drivers/regulator/max8998.
The struct voltage_map_desc is used for storing min/max/step fileds, and
then setup the min_uV, uV_step and n_voltages fields for regulator_desc.
Introduce MAX8998_LINEAR_REG/MAX8998_OTHERS_REG macro to setup these filds
directly in regulator_desc to simplify the code.
Signed-off-by: Axel Lin
---
On Wed, 10 Apr 2019 19:23:51 +0100
Colin King wrote:
> From: Colin Ian King
>
> Currently if mask is neither CHAN_INFO_RAW or CHAN_INFO_SCALE then
> then an uninitialized error return 'ret' is returned. Fix this by
> adding a default case that ensures -EINVAL is returned for this
> specific cas
On Tue, 9 Apr 2019 16:35:21 +0300
Mircea Caprioru wrote:
> This patch will ensure compatibility with the new revision of the AD5758
> dac converter. The modifications consist of removing the fault_prot_switch
> function since this option is no longer available, and enabling the
> ENABLE_PPC_BUFFE
On Tue, 9 Apr 2019 21:10:22 +0200
Andreas Klinger wrote:
> add Maxbotix LV ultrasonic sensor types mb1000, mb1010, mb1020, mb1030
> and mb1040
>
> add a configuration struct with the different trigger pulse lengths
>
> Signed-off-by: Andreas Klinger
Applied to the togreg branch of iio.git and
On Tue, 9 Apr 2019 16:08:02 -0500
Rob Herring wrote:
> On Tue, Apr 9, 2019 at 2:11 PM Andreas Klinger wrote:
> >
> > add compatibles for Maxbotix ultrasonic iio sensor types to yaml
> > documentation
> >
> > Signed-off-by: Andreas Klinger
> > ---
> > .../bindings/iio/proximity/devantech-srf04.
On Tue, 9 Apr 2019 21:11:28 +0200
Andreas Klinger wrote:
> reword configuration option for SRF04
>
> list supported types in help text
>
> Signed-off-by: Andreas Klinger
Applied and pushed out as testing for the autobuilders to play with it.
thanks,
Jonathan
> ---
> drivers/iio/proximity/K
> @@ -1367,6 +1367,7 @@ static int pistachio_gpio_register(struct
> pistachio_pinctrl *pctl)
> if (!of_find_property(child, "gpio-controller", NULL)) {
> dev_err(pctl->dev,
> "No gpio-controller property for bank %u\n", i);
> +
On Sun, Apr 14, 2019 at 07:47:05PM +0900, Masami Hiramatsu wrote:
> Hello,
>
> Recently, Naresh reported that the function-graph tracer on the latest
> kernel crashes on arm. I could reproduce it and bisected. I finally found
> the commit f9b58e8c7d03 ("ARM: 8800/1: use choice for kernel unwinders
The assignment of variable ret is redundant because the
value of ret is 0 after calling v2_read_header() in normal
case.
Signed-off-by: Chengguang Xu
---
fs/quota/quota_v2.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs/quota/quota_v2.c b/fs/quota/quota_v2.c
index a73e5b34db41..25d36607b
On Mon, 8 Apr 2019 02:07:24 +
Anson Huang wrote:
> Hi, Jonathan
>
> Best Regards!
> Anson Huang
>
> > -Original Message-
> > From: Jonathan Cameron [mailto:ji...@kernel.org]
> > Sent: 2019年4月7日 18:40
> > To: Anson Huang
> > Cc: knaac...@gmx.de; l...@metafoo.de; pme...@pmeerw.net; L
On Fri, 12 Apr 2019 13:09:23 +0300
Mohan Kumar wrote:
> As per Documentation/timers/timers-howto.txt Msleep < 20ms can sleep for
> up to 20ms. so use usleep_range.
>
> Signed-off-by: Mohan Kumar
Please resend, ccing the linux-...@vger.kernel.org mailing list.
Thanks,
Jonathan
> ---
> driver
On Fri, Apr 12, 2019 at 01:14:54PM -0700, Atish Patra wrote:
> On 4/10/19 11:56 PM, Christoph Hellwig wrote:
> > Given that this option enables generic code (which you reuse for RISC-V
> > later in this series) please also move the config option to
> > mm/Kconfig, proabbly keyed off another ARCH_HA
> @@ -538,8 +538,10 @@ static int cci_probe(void)
> struct resource res;
>
> np = of_find_matching_node(NULL, arm_cci_matches);
> - if (!of_device_is_available(np))
> + if (!of_device_is_available(np)) {
> + of_node_put(np);
> return -ENODEV;
> + }
On Wed, Apr 10, 2019 at 12:28:15PM +0200, Thomas Gleixner wrote:
> @@ -430,20 +429,16 @@ static int proc_pid_stack(struct seq_fil
> if (!entries)
> return -ENOMEM;
>
> - trace.nr_entries= 0;
> - trace.max_entries = MAX_STACK_TRACE_DEPTH;
> - trace.ent
On Sun, 14 Apr 2019 14:34:58 +0100
Russell King - ARM Linux admin wrote:
> On Sun, Apr 14, 2019 at 07:47:05PM +0900, Masami Hiramatsu wrote:
> > Hello,
> >
> > Recently, Naresh reported that the function-graph tracer on the latest
> > kernel crashes on arm. I could reproduce it and bisected. I f
On 4/14/19 5:36 AM, Alexey Dobriyan wrote:
> F29 bans mapping first 64KB even for root making test fail.
so there is an F29-only patch that prevents that?
something that is not in mainline?
thanks.
> Iterate from address 0 until mmap() works.
>
> Gentoo (root):
>
> openat(AT_FDCWD, "/dev
04.03.2019 16:42, Dmitry Osipenko пишет:
> 04.03.2019 11:18, Peter De Schrijver пишет:
>> On Wed, Feb 27, 2019 at 06:15:04PM +0300, Dmitry Osipenko wrote:
>>> 24.02.2019 18:32, Dmitry Osipenko пишет:
Initially Common Clock Framework isn't aware of the clock-enable status,
this results in
On Sun, Apr 14, 2019 at 11:52:38PM +0900, Masami Hiramatsu wrote:
> On Sun, 14 Apr 2019 14:34:58 +0100
> Russell King - ARM Linux admin wrote:
>
> > On Sun, Apr 14, 2019 at 07:47:05PM +0900, Masami Hiramatsu wrote:
> > > Hello,
> > >
> > > Recently, Naresh reported that the function-graph tracer
The `np->permission' structure is smaller than the `np' structure but
sizeof(*np) worth of data is copied in there. Fix the size passed to
copy_from_user() to avoid overrun.
Fixes: 3d2ec9dcd5539d42 ("staging: Android: Add 'vsoc' driver for cuttlefish.")
Signed-off-by: Vincent Stehlé
Cc: Greg Kroa
> @@ -260,8 +260,10 @@ tegra_xusb_pad_create(struct tegra_xusb_
> int err;
>
> np = tegra_xusb_find_pad_node(padctl, soc->name);
> - if (!np || !of_device_is_available(np))
> + if (!np || !of_device_is_available(np)) {
> + of_node_put(np);
> return NUL
The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git
tags/samsung-dt-5.2
for you to fetch changes up to 8cc76b1c7572219
The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git
tags/samsung-dt64-5.2
for you to fetch changes up to 77fc46976e0bf
The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git
tags/samsung-soc-5.2
for you to fetch changes up to 7676e667c84137
As per Documentation/timers/timers-howto.txt Msleep < 20ms can sleep for
up to 20ms. so use usleep_range.
Signed-off-by: Mohan Kumar
---
drivers/iio/gyro/mpu3050-core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/iio/gyro/mpu3050-core.c b/drivers/iio/gyro/mpu3050-
Hi!
This is an updated version of the guard page series:
V1: https://lkml.kernel.org/r/20190331214020.836098...@linutronix.de
V2: https://lkml.kernel.org/r/20190405150658.237064...@linutronix.de
Changes vs. V2:
- Fixed the broken stack trace storage in slub
- Adjust the guard page or
I hope you had a lovely night, and you having a wonderful weekend.It is my
pleasure meeting you. Am sorry to bother you, i apologize for intruding upon
your privacy. My name is Wesley. I`m from the State. I am currently looking for
a relationship in which I feel loved. I hope you will be kind en
On Sun, Apr 14, 2019 at 08:24:53AM -0700, Randy Dunlap wrote:
> On 4/14/19 5:36 AM, Alexey Dobriyan wrote:
> > F29 bans mapping first 64KB even for root making test fail.
>
> so there is an F29-only patch that prevents that?
> something that is not in mainline?
Ehh, no. F29 ships stable kernels a
kstack_end() is broken on interrupt stacks as they are not guaranteed to be
sized THREAD_SIZE and THREAD_SIZE aligned.
Use the stack tracer instead. Remove the pointless pointer increment at the
end of the function while at it.
Fixes: 98eb235b7feb ("[PATCH] page unmapping debug") - History tree
S
Nothing requires those for 32bit builds.
Signed-off-by: Thomas Gleixner
---
arch/x86/include/asm/page_32_types.h |6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
--- a/arch/x86/include/asm/page_32_types.h
+++ b/arch/x86/include/asm/page_32_types.h
@@ -22,11 +22,7 @@
#define THREAD
From: Andy Lutomirski
stack_overflow_check() is using both irq_stack_ptr and irq_stack_union to
find the IRQ stack. That's going to break when vmapped irq stacks are
introduced.
Change it to just use irq_stack_ptr.
Signed-off-by: Andy Lutomirski
Signed-off-by: Thomas Gleixner
Reviewed-by: Sea
The debug IST stack is actually two separate debug stacks to handle #DB
recursion. This is required because the CPU starts always at top of stack
on exception entry, which means on #DB recursion the second #DB would
overwrite the stack of the first.
The low level entry code therefore adjusts the t
All usage sites which expected that the exception stacks in the CPU entry
area are mapped linearly are fixed up. Enable guard pages between the
IST stacks.
Signed-off-by: Thomas Gleixner
---
arch/x86/include/asm/cpu_entry_area.h |8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
-
Preparatory patch to share code with 32bit.
Signed-off-by: Thomas Gleixner
---
arch/x86/entry/entry_64.S|2 +-
arch/x86/include/asm/processor.h |2 +-
arch/x86/kernel/cpu/common.c |2 +-
arch/x86/kernel/dumpstack_64.c |2 +-
arch/x86/kernel/irq_64.c |2 +
On x86 stacks go top to bottom, but the stack overflow check uses it the
other way round, which is just confusing. Clean it up and sanitize the
warning string a bit.
Signed-off-by: Thomas Gleixner
Reviewed-by: Sean Christopherson
---
arch/x86/kernel/irq_64.c | 22 +++---
1 fil
The orig_ist[] array is a shadow copy of the IST array in the TSS. The
reason why it exists is that older kernels used two TSS variants with
different pointers into the debug stack. orig_ist[] contains the real
starting points.
There is no point anymore to do so because the same information can be
From: Andy Lutomirski
The get_stack_info() function is off-by-one when checking whether an
address is on a IRQ stack or a IST stack. This prevents a overflowed IRQ
or IST stack from being dumped properly.
[ tglx: Do the same for 32-bit ]
Signed-off-by: Andy Lutomirski
Signed-off-by: Thomas Gl
All users gone.
Signed-off-by: Thomas Gleixner
---
arch/x86/include/asm/processor.h |9 -
arch/x86/kernel/cpu/common.c |6 --
2 files changed, 15 deletions(-)
--- a/arch/x86/include/asm/processor.h
+++ b/arch/x86/include/asm/processor.h
@@ -374,16 +374,7 @@ DECLARE_PER_C
There is no reason to have an u32 array in struct irq_stack. The only
purpose of the array is to size the struct properly.
Preparatory change for sharing struct irq_stack with 64-bit.
Signed-off-by: Thomas Gleixner
---
arch/x86/include/asm/processor.h |2 +-
1 file changed, 1 insertion(+),
The entry order of the TSS.IST array and the order of the stack
storage/mapping are not required to be the same.
With the upcoming split of the debug stack this is going to fall apart as
the number of TSS.IST array entries stays the same while the actual stacks
are increasing.
Make them separate
Store a pointer to the per cpu entry area exception stack mappings to allow
fast retrieval.
Required for converting various places from using the shadow IST array to
directly doing address calculations on the actual mapping address.
Signed-off-by: Thomas Gleixner
---
arch/x86/include/asm/cpu_en
From: Andy Lutomirski
The IRQ stack lives in percpu space, so an IRQ handler that overflows it
will overwrite other data structures.
Use vmap() to remap the IRQ stack so that it will have the usual guard
pages that vmap/vmalloc allocations have. With this the kernel will panic
immediately on an
All stack types on x86 64-bit have guard pages now.
So there is no point in executing probabilistic overflow checks as the
guard pages are a accurate and reliable overflow prevention.
Signed-off-by: Thomas Gleixner
---
arch/x86/Kconfig |2 -
arch/x86/kernel/irq_64.c | 56 -
I hope you had a lovely night, and you having a wonderful weekend.It is my
pleasure meeting you. Am sorry to bother you, i apologize for intruding upon
your privacy. My name is Wesley. I`m from the State. I am currently looking for
a relationship in which I feel loved. I hope you will be kind en
irq_ctx_init() crashes hard on page allocation failures. While that's ok
during early boot, it's just wrong in the CPU hotplug bringup code.
Check the page allocation failure and return -ENOMEM and handle it at the
call sites. On early boot the only way out is to BUG(), but on CPU hotplug
there is
The current implementation of in_exception_stack() iterates over the
exception stacks array. Most of the time this is an useless exercise, but
even for the actual use cases (perf and ftrace) it takes at least 2
iterations to get to the NMI stack.
As the exception stacks and the guard pages are pag
Preparatory change for distangling the irq stack union as a prerequisite
for irq stacks with guard pages.
Signed-off-by: Thomas Gleixner
---
arch/x86/include/asm/irq.h |4
arch/x86/kernel/cpu/common.c |4 +---
arch/x86/kernel/irq_64.c | 15 +++
3 files changed, 1
On 32-bit IRQ_STACK_SIZE is the same as THREAD_SIZE.
To allow sharing struct irq_stack with 32-bit, define IRQ_STACK_SIZE for
32-bit and use of for struct irq_stack.
No functional change.
Signed-off-by: Thomas Gleixner
---
arch/x86/include/asm/page_32_types.h |2 ++
arch/x86/include/asm/pr
Convert the TSS.IST setup code to use the cpu entry area information
directly instead of assuming a linear mapping of the IST stacks.
The store to orig_ist[] is no longer required as there are no users
anymore.
This is the last preparatory step for IST guard pages.
Signed-off-by: Thomas Gleixner
To allow guard pages between the IST stacks each stack needs to be mapped
individually.
Signed-off-by: Thomas Gleixner
---
arch/x86/mm/cpu_entry_area.c | 37 ++---
1 file changed, 30 insertions(+), 7 deletions(-)
--- a/arch/x86/mm/cpu_entry_area.c
+++ b/arch/x8
Nothing uses that and before people get the wrong ideas, get rid of it.
Signed-off-by: Thomas Gleixner
---
arch/x86/include/asm/page_64_types.h |1 -
1 file changed, 1 deletion(-)
--- a/arch/x86/include/asm/page_64_types.h
+++ b/arch/x86/include/asm/page_64_types.h
@@ -14,7 +14,6 @@
#def
Hi!
This is an updated version of the guard page series:
V1: https://lkml.kernel.org/r/20190331214020.836098...@linutronix.de
V2: https://lkml.kernel.org/r/20190405150658.237064...@linutronix.de
Changes vs. V2:
- Fixed the broken stack trace storage in slub
- Adjust the guard page or
The percpu storage holds a pointer to the stack not the stack
itself. Rename it before sharing struct irq_stack with 64-bit.
Signed-off-by: Thomas Gleixner
---
arch/x86/include/asm/processor.h |4 ++--
arch/x86/kernel/dumpstack_32.c |4 ++--
arch/x86/kernel/irq_32.c | 19
From: Andy Lutomirski
Currently the IRQ stack is hardcoded as the first page of the percpu area,
and the stack canary lives on the IRQ stack. The former gets in the way of
adding an IRQ stack guard page, and the latter is a potential weakness in
the stack canary mechanism.
Split the IRQ stack i
commit 37fe6a42b343 ("x86: Check stack overflow in detail") added a broad
check for the full exception stack area, i.e. it considers the full
exception stack area as valid.
That's wrong in two aspects:
1) It does not check the individual areas one by one
2) #DF, NMI and #MCE are not enabling i
The orig_ist[] array is a shadow copy of the IST array in the TSS. The
reason why it exists is that older kernels used two TSS variants with
different pointers into the debug stack. orig_ist[] contains the real
starting points.
There is no point anymore to do so because the same information can be
The defines for the exception stack (IST) array in the TSS are using the
SDM convention IST1 - IST7. That causes all sorts of code to subtract 1 for
array indices related to IST. That's confusing at best and does not provide
any value.
Make the indices zero based and fixup the usage sites. The onl
1 - 100 of 277 matches
Mail list logo
