[PATCH v3 2/2] arm64/sve: should not depend on

arm64: ssbd: explicitly depend on " for kernel >= 4.18 Fixes: 43d4da2c45b2 ("arm64/sve: ptrace and ELF coredump support") Cc: sta...@vger.kernel.org Signed-off-by: Anisse Astier --- arch/arm64/include/uapi/asm/ptrace.h | 8 +++- 1 file changed, 3 insertions(+), 5 deletions(-)

[PATCH v3 1/2] arm64: ssbd: explicitly depend on

: 9cdc0108baa8 ("arm64: ssbd: Add prctl interface for per-thread mitigation") Cc: sta...@vger.kernel.org Signed-off-by: Anisse Astier --- Contrary to what I said in the previous email, I can reproduce the build error on Linus' master when ARM64_SSBD is enabled. Changes since v2: - fix

[PATCH v2] arm64/sve: should not depend on

4/sve: ptrace and ELF coredump support") Cc: sta...@vger.kernel.org Signed-off-by: Anisse Astier --- Changes since v1: - made a bit more explicit that we copied defined symbols, in commit and code. - Use Fixes: tag in commit message Thanks to Dave Martin and Will Deacon for the review. ---

Re: [PATCH] arm64/sve: should not depend on

Hi Dave, Thanks for taking the time to review this patch, On Thu, Jun 13, 2019 at 06:14:44PM +0100, Dave Martin wrote: > On Thu, Jun 13, 2019 at 06:38:01PM +0200, Anisse Astier wrote: > > Otherwise this will create userspace build issues for any program > > (strace, qemu) tha

[PATCH] arm64/sve: should not depend on

/6d4a106e191b5d79c41b9ac78fd321316d3013c0 for a public example of people working around this issue. This fixes an UAPI regression introduced in commit 43d4da2c45b2 ("arm64/sve: ptrace and ELF coredump support"). Cc: sta...@vger.kernel.org Signed-off-by: Anisse Astier --- arch/arm64/includ

Re: [PATCH] staging: vchiq: Fix local event signalling

e, and then nothing would work until the process was killed. Sample log: bcm2835_audio bcm2835_audio: failed to close VCHI service connection (status=1) > > Fixes: 852b2876a8a8 ("staging: vchiq: rework remove_event handling") > Signed-off-by: Phil Elwell Tested-by: Anisse Astier Regards, Anisse

Re: [PATCH v2 3/3] mmc: sdhci-pci: only install voltage switch method when useful

On Mon, Nov 19, 2018 at 09:45:03AM +0200, Adrian Hunter wrote: > On 16/11/18 6:58 PM, Anisse Astier wrote: > > Hi Adrian, > > > > On Tue, Oct 23, 2018 at 12:07:29PM +0200, Anisse Astier wrote: > >> If there's no ACPI DSM for voltage switch, it will just cause

Re: [PATCH v2 3/3] mmc: sdhci-pci: only install voltage switch method when useful

On Mon, Nov 19, 2018 at 09:45:03AM +0200, Adrian Hunter wrote: > On 16/11/18 6:58 PM, Anisse Astier wrote: > > Hi Adrian, > > > > On Tue, Oct 23, 2018 at 12:07:29PM +0200, Anisse Astier wrote: > >> If there's no ACPI DSM for voltage switch, it will just cause

Re: [PATCH v2 3/3] mmc: sdhci-pci: only install voltage switch method when useful

Hi Adrian, On Tue, Oct 23, 2018 at 12:07:29PM +0200, Anisse Astier wrote: > If there's no ACPI DSM for voltage switch, it will just cause a lot of > debug info down the line, we only need one at startup. > > Signed-off-by: Anisse Astier > --- > drivers/mmc/host/sdh

Re: [PATCH v2 3/3] mmc: sdhci-pci: only install voltage switch method when useful

Hi Adrian, On Tue, Oct 23, 2018 at 12:07:29PM +0200, Anisse Astier wrote: > If there's no ACPI DSM for voltage switch, it will just cause a lot of > debug info down the line, we only need one at startup. > > Signed-off-by: Anisse Astier > --- > drivers/mmc/host/sdh

[PATCH v2 0/3] sdhci-pci voltage switch fixes

, but for which the issue is harder to reproduce. I've kept the previous cleanup of the voltage_switch callback in an optional third patch, but it does not enable any quirk. Anisse Astier (3): mmc: sdhci-pci: disable 1.8V with dmi quirk mmc: sdhci-pci: add new machine with 1.8V dmi quirk mmc

[PATCH v2 0/3] sdhci-pci voltage switch fixes

, but for which the issue is harder to reproduce. I've kept the previous cleanup of the voltage_switch callback in an optional third patch, but it does not enable any quirk. Anisse Astier (3): mmc: sdhci-pci: disable 1.8V with dmi quirk mmc: sdhci-pci: add new machine with 1.8V dmi quirk mmc

[PATCH v2 3/3] mmc: sdhci-pci: only install voltage switch method when useful

If there's no ACPI DSM for voltage switch, it will just cause a lot of debug info down the line, we only need one at startup. Signed-off-by: Anisse Astier --- drivers/mmc/host/sdhci-pci-core.c | 11 +++ 1 file changed, 11 insertions(+) diff --git a/drivers/mmc/host/sdhci-pci-core.c b

[PATCH v2 3/3] mmc: sdhci-pci: only install voltage switch method when useful

If there's no ACPI DSM for voltage switch, it will just cause a lot of debug info down the line, we only need one at startup. Signed-off-by: Anisse Astier --- drivers/mmc/host/sdhci-pci-core.c | 11 +++ 1 file changed, 11 insertions(+) diff --git a/drivers/mmc/host/sdhci-pci-core.c b

[PATCH v2 1/3] mmc: sdhci-pci: disable 1.8V with dmi quirk

, the problem existed, but only delayed boot for about 10 seconds after an I/O error, allowing booting on the eMMC (almost) unnoticed. Signed-off-by: Anisse Astier --- drivers/mmc/host/sdhci-pci-core.c | 17 + 1 file changed, 17 insertions(+) diff --git a/drivers/mmc/host/sdhci-pci

[PATCH v2 2/3] mmc: sdhci-pci: add new machine with 1.8V dmi quirk

This machine also displays the same issue that is fixed by the quirk. Signed-off-by: Anisse Astier --- drivers/mmc/host/sdhci-pci-core.c | 6 ++ 1 file changed, 6 insertions(+) diff --git a/drivers/mmc/host/sdhci-pci-core.c b/drivers/mmc/host/sdhci-pci-core.c index 396413f7c854

[PATCH v2 1/3] mmc: sdhci-pci: disable 1.8V with dmi quirk

, the problem existed, but only delayed boot for about 10 seconds after an I/O error, allowing booting on the eMMC (almost) unnoticed. Signed-off-by: Anisse Astier --- drivers/mmc/host/sdhci-pci-core.c | 17 + 1 file changed, 17 insertions(+) diff --git a/drivers/mmc/host/sdhci-pci

[PATCH v2 2/3] mmc: sdhci-pci: add new machine with 1.8V dmi quirk

This machine also displays the same issue that is fixed by the quirk. Signed-off-by: Anisse Astier --- drivers/mmc/host/sdhci-pci-core.c | 6 ++ 1 file changed, 6 insertions(+) diff --git a/drivers/mmc/host/sdhci-pci-core.c b/drivers/mmc/host/sdhci-pci-core.c index 396413f7c854

[PATCH] PM / Hibernate: allow hibernation with PAGE_POISONING_ZERO

PAGE_POISONING_ZERO is enabled. We free the pages just after resume because we can't do it later: going through any device resume code might allocate some memory and invalidate the free pages bitmap. Thus we don't need to disable hibernation when PAGE_POISONING_ZERO is enabled. Signed-off-by: Anisse

[PATCH] PM / Hibernate: allow hibernation with PAGE_POISONING_ZERO

PAGE_POISONING_ZERO is enabled. We free the pages just after resume because we can't do it later: going through any device resume code might allocate some memory and invalidate the free pages bitmap. Thus we don't need to disable hibernation when PAGE_POISONING_ZERO is enabled. Signed-off-by: Anisse

Re: [PATCH] pinctrl: cherryview: Do not mask all interrupts on probe

On Thu, Aug 18, 2016 at 2:13 PM, Mika Westerberg <mika.westerb...@linux.intel.com> wrote: > On Wed, Aug 17, 2016 at 03:42:58PM +0200, Anisse Astier wrote: >> pin 25 (GPIO_SUS6) GPIO ctrl0 0xec918201 ctrl1 0x05c1 > > It is this one (GPIO_SUS6). > > I wonder if

Re: [PATCH] pinctrl: cherryview: Do not mask all interrupts on probe

On Thu, Aug 18, 2016 at 2:13 PM, Mika Westerberg wrote: > On Wed, Aug 17, 2016 at 03:42:58PM +0200, Anisse Astier wrote: >> pin 25 (GPIO_SUS6) GPIO ctrl0 0xec918201 ctrl1 0x05c1 > > It is this one (GPIO_SUS6). > > I wonder if we can relax the driver so that it

Re: [PATCH] pinctrl: cherryview: Do not mask all interrupts on probe

On Wed, Aug 17, 2016 at 10:13 AM, Mika Westerberg <mika.westerb...@linux.intel.com> wrote: > On Tue, Aug 16, 2016 at 06:12:40PM +0200, Anisse Astier wrote: >> Hi Mika, >> >> Did you find a way to fix this issue ? I'm seeing a similar problem on a >> laptop wh

Re: [PATCH] pinctrl: cherryview: Do not mask all interrupts on probe

On Wed, Aug 17, 2016 at 10:13 AM, Mika Westerberg wrote: > On Tue, Aug 16, 2016 at 06:12:40PM +0200, Anisse Astier wrote: >> Hi Mika, >> >> Did you find a way to fix this issue ? I'm seeing a similar problem on a >> laptop where this masks the interrupt used for ACPI

Re: [PATCH] pinctrl: cherryview: Do not mask all interrupts on probe

Hi Mika, On Tue, Jun 2, 2015 at 4:15 PM, Mika Westerberg wrote: > On Tue, Jun 02, 2015 at 03:53:40PM +0200, Linus Walleij wrote: >> On Mon, Jun 1, 2015 at 11:23 AM, Mika Westerberg >> wrote: >> > On Fri, May 22, 2015 at

Re: [PATCH] pinctrl: cherryview: Do not mask all interrupts on probe

Hi Mika, On Tue, Jun 2, 2015 at 4:15 PM, Mika Westerberg wrote: > On Tue, Jun 02, 2015 at 03:53:40PM +0200, Linus Walleij wrote: >> On Mon, Jun 1, 2015 at 11:23 AM, Mika Westerberg >> wrote: >> > On Fri, May 22, 2015 at 10:56:08AM +0300, Mika Westerberg wrote: >> >> BIOS/platform may use some

Re: [PATCH v4 2/3] mm/page_alloc.c: add config option to sanitize freed pages

On Tue, May 19, 2015 at 3:58 AM, yalin wang wrote: > 2015-05-18 21:04 GMT+08:00 Anisse Astier : >> On Mon, May 18, 2015 at 3:02 PM, Pavel Machek wrote: >>> >>> Ok. So there is class of errors where this helps, but you are not >>> aware of any such errors in ke

Re: [PATCH v4 0/3] Sanitizing freed pages

On Tue, May 19, 2015 at 2:46 PM, Mel Gorman wrote: > On Thu, May 14, 2015 at 04:19:45PM +0200, Anisse Astier wrote: >> Hi, >> >> - it can help with long-term memory consumption in an environment with >>multiple VMs and Kernel Same-page Merging on the host. [2]

Re: [PATCH v4 1/3] PM / Hibernate: prepare for SANITIZE_FREED_PAGES

On Wed, May 20, 2015 at 1:45 PM, PaX Team wrote: > >> Moreover, why is the resume code path the only one where freed pages need to >> be sanitized? > > ... i had a bug report before (http://marc.info/?l=linux-pm=132871433416256) > which is why i asked Anisse to figure this out before upstreaming

Re: [PATCH v4 1/3] PM / Hibernate: prepare for SANITIZE_FREED_PAGES

On Wed, May 20, 2015 at 1:46 AM, Rafael J. Wysocki wrote: > On Monday, May 18, 2015 12:23:00 PM Anisse Astier wrote: >> Hi Rafael, >> >> Thanks for taking the time to review this. >> >> On Sat, May 16, 2015 at 2:28 AM, Rafael J. Wysocki >> wrote: >

Re: [PATCH v4 1/3] PM / Hibernate: prepare for SANITIZE_FREED_PAGES

On Wed, May 20, 2015 at 1:46 AM, Rafael J. Wysocki r...@rjwysocki.net wrote: On Monday, May 18, 2015 12:23:00 PM Anisse Astier wrote: Hi Rafael, Thanks for taking the time to review this. On Sat, May 16, 2015 at 2:28 AM, Rafael J. Wysocki r...@rjwysocki.net wrote: On Thursday, May 14

Re: [PATCH v4 1/3] PM / Hibernate: prepare for SANITIZE_FREED_PAGES

On Wed, May 20, 2015 at 1:45 PM, PaX Team pagee...@freemail.hu wrote: Moreover, why is the resume code path the only one where freed pages need to be sanitized? ... i had a bug report before (http://marc.info/?l=linux-pmm=132871433416256) which is why i asked Anisse to figure this out before

Re: [PATCH v4 0/3] Sanitizing freed pages

On Tue, May 19, 2015 at 2:46 PM, Mel Gorman mgor...@suse.de wrote: On Thu, May 14, 2015 at 04:19:45PM +0200, Anisse Astier wrote: Hi, - it can help with long-term memory consumption in an environment with multiple VMs and Kernel Same-page Merging on the host. [2] This is not quantified

Re: [PATCH v4 2/3] mm/page_alloc.c: add config option to sanitize freed pages

On Tue, May 19, 2015 at 3:58 AM, yalin wang yalin.wang2...@gmail.com wrote: 2015-05-18 21:04 GMT+08:00 Anisse Astier ani...@astier.eu: On Mon, May 18, 2015 at 3:02 PM, Pavel Machek pa...@ucw.cz wrote: Ok. So there is class of errors where this helps, but you are not aware of any such errors

Re: [PATCH v4 2/3] mm/page_alloc.c: add config option to sanitize freed pages

On Mon, May 18, 2015 at 3:02 PM, Pavel Machek wrote: > > Ok. So there is class of errors where this helps, but you are not > aware of any such errors in kernel, so you can't fix them... Right? Correct. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a

Re: [PATCH v4 2/3] mm/page_alloc.c: add config option to sanitize freed pages

On Mon, May 18, 2015 at 1:21 PM, Pavel Machek wrote: > On Thu 2015-05-14 16:19:47, Anisse Astier wrote: >> This new config option will sanitize all freed pages. This is a pretty >> low-level change useful to track some cases of use-after-free, help >> kernel same-page mergi

Re: [PATCH v4 1/3] PM / Hibernate: prepare for SANITIZE_FREED_PAGES

Hi Rafael, Thanks for taking the time to review this. On Sat, May 16, 2015 at 2:28 AM, Rafael J. Wysocki wrote: > On Thursday, May 14, 2015 04:19:46 PM Anisse Astier wrote: >> SANITIZE_FREED_PAGES feature relies on having all pages going through >> the free_pages_prepar

Re: [PATCH v4 2/3] mm/page_alloc.c: add config option to sanitize freed pages

On Mon, May 18, 2015 at 1:21 PM, Pavel Machek pa...@ucw.cz wrote: On Thu 2015-05-14 16:19:47, Anisse Astier wrote: This new config option will sanitize all freed pages. This is a pretty low-level change useful to track some cases of use-after-free, help kernel same-page merging in VM

Re: [PATCH v4 2/3] mm/page_alloc.c: add config option to sanitize freed pages

On Mon, May 18, 2015 at 3:02 PM, Pavel Machek pa...@ucw.cz wrote: Ok. So there is class of errors where this helps, but you are not aware of any such errors in kernel, so you can't fix them... Right? Correct. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body

Re: [PATCH v4 1/3] PM / Hibernate: prepare for SANITIZE_FREED_PAGES

Hi Rafael, Thanks for taking the time to review this. On Sat, May 16, 2015 at 2:28 AM, Rafael J. Wysocki r...@rjwysocki.net wrote: On Thursday, May 14, 2015 04:19:46 PM Anisse Astier wrote: SANITIZE_FREED_PAGES feature relies on having all pages going through the free_pages_prepare path

[PATCH v4 3/3] mm: Add debug code for SANITIZE_FREED_PAGES

Add debug code for sanitize freed pages to print status and verify pages at alloc to make sure they're clean. It can be useful if you have crashes when using SANITIZE_FREED_PAGES. Signed-off-by: Anisse Astier --- kernel/power/snapshot.c | 8 ++-- mm/Kconfig | 10 ++ mm

[PATCH v4 0/3] Sanitizing freed pages

t/Articles/334747/ [2] https://staff.aist.go.jp/k.suzaki/EuroSec12-SUZAKI-revised2.pdf [3] http://en.wikibooks.org/wiki/Grsecurity/Appendix/Grsecurity_and_PaX_Configuration_Options#Sanitize_all_freed_memory [4] http://article.gmane.org/gmane.linux.kernel.mm/34398 Anisse Astier (3): PM /

[PATCH v4 1/3] PM / Hibernate: prepare for SANITIZE_FREED_PAGES

sure free pages are cleared on resume; when we'll enable SANITIZE_FREED_PAGES. We free the pages just after resume because we can't do it later: going through any device resume code might allocate some memory and invalidate the free pages bitmap. Signed-off-by: Anisse Astier --- kernel/power

[PATCH v4 2/3] mm/page_alloc.c: add config option to sanitize freed pages

This new config option will sanitize all freed pages. This is a pretty low-level change useful to track some cases of use-after-free, help kernel same-page merging in VM environments, and counter a few info leaks. Signed-off-by: Anisse Astier --- mm/Kconfig | 12 mm

[PATCH v4 3/3] mm: Add debug code for SANITIZE_FREED_PAGES

Add debug code for sanitize freed pages to print status and verify pages at alloc to make sure they're clean. It can be useful if you have crashes when using SANITIZE_FREED_PAGES. Signed-off-by: Anisse Astier ani...@astier.eu --- kernel/power/snapshot.c | 8 ++-- mm/Kconfig

[PATCH v4 0/3] Sanitizing freed pages

/334747/ [2] https://staff.aist.go.jp/k.suzaki/EuroSec12-SUZAKI-revised2.pdf [3] http://en.wikibooks.org/wiki/Grsecurity/Appendix/Grsecurity_and_PaX_Configuration_Options#Sanitize_all_freed_memory [4] http://article.gmane.org/gmane.linux.kernel.mm/34398 Anisse Astier (3): PM / Hibernate: prepare

[PATCH v4 2/3] mm/page_alloc.c: add config option to sanitize freed pages

This new config option will sanitize all freed pages. This is a pretty low-level change useful to track some cases of use-after-free, help kernel same-page merging in VM environments, and counter a few info leaks. Signed-off-by: Anisse Astier ani...@astier.eu --- mm/Kconfig | 12

[PATCH v4 1/3] PM / Hibernate: prepare for SANITIZE_FREED_PAGES

sure free pages are cleared on resume; when we'll enable SANITIZE_FREED_PAGES. We free the pages just after resume because we can't do it later: going through any device resume code might allocate some memory and invalidate the free pages bitmap. Signed-off-by: Anisse Astier ani...@astier.eu

Re: [PATCH v3 2/4] PM / Hibernate: prepare for SANITIZE_FREED_PAGES

Hi Pavel, Thanks a lot for taking the time to review this. On Sat, May 9, 2015 at 5:44 PM, Pavel Machek wrote: >> +#ifdef CONFIG_SANITIZE_FREED_PAGES >> + clear_free_pages(); >> + printk(KERN_INFO "PM: free pages cleared after restore\n"); >> +#endif >> + } >>

Re: [PATCH v3 2/4] PM / Hibernate: prepare for SANITIZE_FREED_PAGES

Hi Pavel, Thanks a lot for taking the time to review this. On Sat, May 9, 2015 at 5:44 PM, Pavel Machek pa...@ucw.cz wrote: +#ifdef CONFIG_SANITIZE_FREED_PAGES + clear_free_pages(); + printk(KERN_INFO PM: free pages cleared after restore\n); +#endif + }

[PATCH v3 1/4] mm/page_alloc.c: cleanup obsolete KM_USER*

It's been five years now that KM_* kmap flags have been removed and that we can call clear_highpage from any context. So we remove prep_zero_pages accordingly. Signed-off-by: Anisse Astier --- mm/page_alloc.c | 17 ++--- 1 file changed, 2 insertions(+), 15 deletions(-) diff --git

[PATCH v3 0/4] Sanitizing freed pages

aist.go.jp/k.suzaki/EuroSec12-SUZAKI-revised2.pdf [3] http://en.wikibooks.org/wiki/Grsecurity/Appendix/Grsecurity_and_PaX_Configuration_Options#Sanitize_all_freed_memory [4] http://article.gmane.org/gmane.linux.kernel.mm/34398 Anisse Astier (4): mm/page_alloc.c: cleanup obsolete KM_USER* mm/pa

[PATCH v3 2/4] PM / Hibernate: prepare for SANITIZE_FREED_PAGES

; when we'll enable SANITIZE_FREED_PAGES. We free the pages just after resume because we can't do it later: going through any device resume code might allocate some memory and invalidate the free pages bitmap. Signed-off-by: Anisse Astier --- kernel/power/hibernate.c | 7 ++- kernel/power

[PATCH v3 4/4] mm: Add debug code for SANITIZE_FREED_PAGES

Add debug code for sanitize freed pages to print status and verify pages at alloc to make sure they're clean. It can be useful if you have crashes when using SANITIZE_FREED_PAGES. Signed-off-by: Anisse Astier --- kernel/power/snapshot.c | 8 ++-- mm/Kconfig | 10 ++ mm

[PATCH v3 3/4] mm/page_alloc.c: add config option to sanitize freed pages

This new config option will sanitize all freed pages. This is a pretty low-level change useful to track some cases of use-after-free, help kernel same-page merging in VM environments, and counter a few info leaks. Signed-off-by: Anisse Astier --- mm/Kconfig | 12 mm

[PATCH v3 1/4] mm/page_alloc.c: cleanup obsolete KM_USER*

It's been five years now that KM_* kmap flags have been removed and that we can call clear_highpage from any context. So we remove prep_zero_pages accordingly. Signed-off-by: Anisse Astier ani...@astier.eu --- mm/page_alloc.c | 17 ++--- 1 file changed, 2 insertions(+), 15 deletions

[PATCH v3 0/4] Sanitizing freed pages

/k.suzaki/EuroSec12-SUZAKI-revised2.pdf [3] http://en.wikibooks.org/wiki/Grsecurity/Appendix/Grsecurity_and_PaX_Configuration_Options#Sanitize_all_freed_memory [4] http://article.gmane.org/gmane.linux.kernel.mm/34398 Anisse Astier (4): mm/page_alloc.c: cleanup obsolete KM_USER* mm/page_alloc.c

[PATCH v3 3/4] mm/page_alloc.c: add config option to sanitize freed pages

This new config option will sanitize all freed pages. This is a pretty low-level change useful to track some cases of use-after-free, help kernel same-page merging in VM environments, and counter a few info leaks. Signed-off-by: Anisse Astier ani...@astier.eu --- mm/Kconfig | 12

[PATCH v3 4/4] mm: Add debug code for SANITIZE_FREED_PAGES

Add debug code for sanitize freed pages to print status and verify pages at alloc to make sure they're clean. It can be useful if you have crashes when using SANITIZE_FREED_PAGES. Signed-off-by: Anisse Astier ani...@astier.eu --- kernel/power/snapshot.c | 8 ++-- mm/Kconfig

[PATCH v3 2/4] PM / Hibernate: prepare for SANITIZE_FREED_PAGES

; when we'll enable SANITIZE_FREED_PAGES. We free the pages just after resume because we can't do it later: going through any device resume code might allocate some memory and invalidate the free pages bitmap. Signed-off-by: Anisse Astier ani...@astier.eu --- kernel/power/hibernate.c | 7

Re: [PATCH v2 4/4] mm: Add debug code for SANITIZE_FREED_PAGES

On Mon, May 4, 2015 at 11:50 PM, PaX Team wrote: > On 4 May 2015 at 23:16, Anisse Astier wrote: > >> diff --git a/mm/page_alloc.c b/mm/page_alloc.c >> index c29e3a0..ba8aa25 100644 >> --- a/mm/page_alloc.c >> +++ b/mm/page_alloc.c >> @@ -975,6 +975,31 @@ static

Re: [PATCH v2 2/4] mm/page_alloc.c: add config option to sanitize freed pages

On Mon, May 4, 2015 at 11:50 PM, PaX Team wrote: > On 4 May 2015 at 23:16, Anisse Astier wrote: > >> @@ -960,9 +966,15 @@ static int prep_new_page(struct page *page, unsigned >> int order, gfp_t gfp_flags, >> kernel_map_pages(page, 1 << order, 1); >>

Re: [PATCH v2 3/4] PM / Hibernate: fix SANITIZE_FREED_PAGES

On Tue, May 5, 2015 at 12:29 AM, Rafael J. Wysocki wrote: > I haven't seen it, for one, and I'm wondering why the "clearing" cannot be > done > at the swsusp_free() time? Because the validity of the free pages bitmap is short-lived since device resume code might do some allocations. > > In any

Re: [PATCH v2 3/4] PM / Hibernate: fix SANITIZE_FREED_PAGES

On Tue, May 5, 2015 at 12:29 AM, Rafael J. Wysocki r...@rjwysocki.net wrote: I haven't seen it, for one, and I'm wondering why the clearing cannot be done at the swsusp_free() time? Because the validity of the free pages bitmap is short-lived since device resume code might do some

Re: [PATCH v2 4/4] mm: Add debug code for SANITIZE_FREED_PAGES

On Mon, May 4, 2015 at 11:50 PM, PaX Team pagee...@freemail.hu wrote: On 4 May 2015 at 23:16, Anisse Astier wrote: diff --git a/mm/page_alloc.c b/mm/page_alloc.c index c29e3a0..ba8aa25 100644 --- a/mm/page_alloc.c +++ b/mm/page_alloc.c @@ -975,6 +975,31 @@ static int prep_new_page(struct

Re: [PATCH v2 2/4] mm/page_alloc.c: add config option to sanitize freed pages

On Mon, May 4, 2015 at 11:50 PM, PaX Team pagee...@freemail.hu wrote: On 4 May 2015 at 23:16, Anisse Astier wrote: @@ -960,9 +966,15 @@ static int prep_new_page(struct page *page, unsigned int order, gfp_t gfp_flags, kernel_map_pages(page, 1 order, 1); kasan_alloc_pages(page

[PATCH v2 3/4] PM / Hibernate: fix SANITIZE_FREED_PAGES

. Signed-off-by: Anisse Astier --- kernel/power/hibernate.c | 7 ++- kernel/power/power.h | 4 kernel/power/snapshot.c | 21 + 3 files changed, 31 insertions(+), 1 deletion(-) diff --git a/kernel/power/hibernate.c b/kernel/power/hibernate.c index 2329daa..3193b9a

[PATCH v2 2/4] mm/page_alloc.c: add config option to sanitize freed pages

This new config option will sanitize all freed pages. This is a pretty low-level change useful to track some cases of use-after-free, help kernel same-page merging in VM environments, and counter a few info leaks. Signed-off-by: Anisse Astier --- mm/Kconfig | 12 mm

[PATCH v2 4/4] mm: Add debug code for SANITIZE_FREED_PAGES

Add debug code for sanitize freed pages to print status and verify pages at alloc to make sure they're clean. It can be useful if you have crashes when using SANITIZE_FREED_PAGES. Signed-off-by: Anisse Astier --- kernel/power/snapshot.c | 8 ++-- mm/Kconfig | 10 ++ mm

[PATCH v2 1/4] mm/page_alloc.c: cleanup obsolete KM_USER*

It's been five years now that KM_* kmap flags have been removed and that we can call clear_highpage from any context. So we remove prep_zero_pages accordingly. Signed-off-by: Anisse Astier --- mm/page_alloc.c | 17 ++--- 1 file changed, 2 insertions(+), 15 deletions(-) diff --git

[PATCH v2 0/4] Sanitizing freed pages

be merged. [1] https://lwn.net/Articles/334747/ [2] https://staff.aist.go.jp/k.suzaki/EuroSec12-SUZAKI-revised2.pdf [3] http://en.wikibooks.org/wiki/Grsecurity/Appendix/Grsecurity_and_PaX_Configuration_Options#Sanitize_all_freed_memory [4] http://article.gmane.org/gmane.linux.kernel.mm/34398

[PATCH v2 3/4] PM / Hibernate: fix SANITIZE_FREED_PAGES

. Signed-off-by: Anisse Astier ani...@astier.eu --- kernel/power/hibernate.c | 7 ++- kernel/power/power.h | 4 kernel/power/snapshot.c | 21 + 3 files changed, 31 insertions(+), 1 deletion(-) diff --git a/kernel/power/hibernate.c b/kernel/power/hibernate.c index

[PATCH v2 2/4] mm/page_alloc.c: add config option to sanitize freed pages

This new config option will sanitize all freed pages. This is a pretty low-level change useful to track some cases of use-after-free, help kernel same-page merging in VM environments, and counter a few info leaks. Signed-off-by: Anisse Astier ani...@astier.eu --- mm/Kconfig | 12

[PATCH v2 4/4] mm: Add debug code for SANITIZE_FREED_PAGES

Add debug code for sanitize freed pages to print status and verify pages at alloc to make sure they're clean. It can be useful if you have crashes when using SANITIZE_FREED_PAGES. Signed-off-by: Anisse Astier ani...@astier.eu --- kernel/power/snapshot.c | 8 ++-- mm/Kconfig

[PATCH v2 1/4] mm/page_alloc.c: cleanup obsolete KM_USER*

It's been five years now that KM_* kmap flags have been removed and that we can call clear_highpage from any context. So we remove prep_zero_pages accordingly. Signed-off-by: Anisse Astier ani...@astier.eu --- mm/page_alloc.c | 17 ++--- 1 file changed, 2 insertions(+), 15 deletions

[PATCH v2 0/4] Sanitizing freed pages

. [1] https://lwn.net/Articles/334747/ [2] https://staff.aist.go.jp/k.suzaki/EuroSec12-SUZAKI-revised2.pdf [3] http://en.wikibooks.org/wiki/Grsecurity/Appendix/Grsecurity_and_PaX_Configuration_Options#Sanitize_all_freed_memory [4] http://article.gmane.org/gmane.linux.kernel.mm/34398 Anisse

Re: [PATCH 2/2] mm/page_alloc.c: add config option to sanitize freed pages

On Mon, Apr 27, 2015 at 11:25 AM, PaX Team wrote: > > the PaX SANITIZE feature does exactly this in mm/page_alloc.c:prep_new_page: > > #ifndef CONFIG_PAX_MEMORY_SANITIZE > if (gfp_flags & __GFP_ZERO) > prep_zero_page(page, order, gfp_flags); > #endif > Thanks, I'll do

Re: [PATCH 2/2] mm/page_alloc.c: add config option to sanitize freed pages

Hi Andi, Thinks for taking the time to review this. On Sun, Apr 26, 2015 at 10:12 PM, Andi Kleen wrote: > Anisse Astier writes: >> + If unsure, say N. >> diff --git a/mm/page_alloc.c b/mm/page_alloc.c >> index 05fcec9..c71440a 100644 >> --- a/mm/page_alloc

Re: [PATCH 2/2] mm/page_alloc.c: add config option to sanitize freed pages

On Mon, Apr 27, 2015 at 11:25 AM, PaX Team pagee...@freemail.hu wrote: the PaX SANITIZE feature does exactly this in mm/page_alloc.c:prep_new_page: #ifndef CONFIG_PAX_MEMORY_SANITIZE if (gfp_flags __GFP_ZERO) prep_zero_page(page, order, gfp_flags); #endif Thanks,

Re: [PATCH 2/2] mm/page_alloc.c: add config option to sanitize freed pages

Hi Andi, Thinks for taking the time to review this. On Sun, Apr 26, 2015 at 10:12 PM, Andi Kleen a...@firstfloor.org wrote: Anisse Astier ani...@astier.eu writes: + If unsure, say N. diff --git a/mm/page_alloc.c b/mm/page_alloc.c index 05fcec9..c71440a 100644 --- a/mm/page_alloc.c

Re: [PATCH 2/2] mm/page_alloc.c: add config option to sanitize freed pages

On Fri, Apr 24, 2015 at 11:38 PM, David Rientjes wrote: > On Fri, 24 Apr 2015, Anisse Astier wrote: > >> diff --git a/mm/Kconfig b/mm/Kconfig >> index 390214d..cb2df5f 100644 >> --- a/mm/Kconfig >> +++ b/mm/Kconfig >> @@ -635,3 +635,15 @@ config MAX_STACK_SIZ

Re: [PATCH 1/2] mm/page_alloc.c: cleanup obsolete KM_USER*

Hi David, First of all, thanks a lot for your time reviewing this series. On Fri, Apr 24, 2015 at 11:36 PM, David Rientjes wrote: > On Fri, 24 Apr 2015, Anisse Astier wrote: > >> diff --git a/mm/page_alloc.c b/mm/page_alloc.c >> index ebffa0e..05fcec9 100644 >> --- a/mm/

Re: [PATCH 2/2] mm/page_alloc.c: add config option to sanitize freed pages

On Fri, Apr 24, 2015 at 11:38 PM, David Rientjes rient...@google.com wrote: On Fri, 24 Apr 2015, Anisse Astier wrote: diff --git a/mm/Kconfig b/mm/Kconfig index 390214d..cb2df5f 100644 --- a/mm/Kconfig +++ b/mm/Kconfig @@ -635,3 +635,15 @@ config MAX_STACK_SIZE_MB changed

Re: [PATCH 1/2] mm/page_alloc.c: cleanup obsolete KM_USER*

Hi David, First of all, thanks a lot for your time reviewing this series. On Fri, Apr 24, 2015 at 11:36 PM, David Rientjes rient...@google.com wrote: On Fri, 24 Apr 2015, Anisse Astier wrote: diff --git a/mm/page_alloc.c b/mm/page_alloc.c index ebffa0e..05fcec9 100644 --- a/mm/page_alloc.c

[PATCH 2/2] mm/page_alloc.c: add config option to sanitize freed pages

This new config option will sanitize all freed pages. This is a pretty low-level change useful to track some cases of use-after-free, help kernel same-page merging in VM environments, and counter a few info leaks. Signed-off-by: Anisse Astier --- mm/Kconfig | 12 mm

[PATCH 1/2] mm/page_alloc.c: cleanup obsolete KM_USER*

It's been five years now that KM_* kmap flags have been removed and that we can call clear_highpage from any context. So we simplify prep_zero_pages accordingly and rename it in the process. Signed-off-by: Anisse Astier --- mm/page_alloc.c | 10 ++ 1 file changed, 2 insertions(+), 8

[PATCH 0/2] Sanitizing freed pages

://article.gmane.org/gmane.linux.kernel.mm/34398 Anisse Astier (2): mm/page_alloc.c: cleanup obsolete KM_USER* mm/page_alloc.c: add config option to sanitize freed pages mm/Kconfig | 12 mm/page_alloc.c | 15 +++ 2 files changed, 19 insertions(+), 8 deletions

[PATCH 0/2] Sanitizing freed pages

://article.gmane.org/gmane.linux.kernel.mm/34398 Anisse Astier (2): mm/page_alloc.c: cleanup obsolete KM_USER* mm/page_alloc.c: add config option to sanitize freed pages mm/Kconfig | 12 mm/page_alloc.c | 15 +++ 2 files changed, 19 insertions(+), 8 deletions

[PATCH 2/2] mm/page_alloc.c: add config option to sanitize freed pages

This new config option will sanitize all freed pages. This is a pretty low-level change useful to track some cases of use-after-free, help kernel same-page merging in VM environments, and counter a few info leaks. Signed-off-by: Anisse Astier ani...@astier.eu --- mm/Kconfig | 12

[PATCH 1/2] mm/page_alloc.c: cleanup obsolete KM_USER*

It's been five years now that KM_* kmap flags have been removed and that we can call clear_highpage from any context. So we simplify prep_zero_pages accordingly and rename it in the process. Signed-off-by: Anisse Astier ani...@astier.eu --- mm/page_alloc.c | 10 ++ 1 file changed, 2

Re: [PATCH 1/1] platform: x86: Deletion of checks before backlight_device_unregister()

t; - backlight_device_unregister(backlight); > + backlight_device_unregister(backlight); > } > > module_init(msi_wmi_init); For this part: Acked-by: Anisse Astier Regards, Anisse -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message

Re: [PATCH 1/1] platform: x86: Deletion of checks before backlight_device_unregister()

); + backlight_device_unregister(backlight); } module_init(msi_wmi_init); For this part: Acked-by: Anisse Astier ani...@astier.eu Regards, Anisse -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http

Re: [PATCH 1/2] deb-pkg: split debug symbols in their own package

On Fri, 19 Apr 2013 10:05:19 +0200, Anisse Astier wrote : > On Tue, 9 Apr 2013 12:05:47 +0200, Anisse Astier wrote : > > > > > > > From: Anisse Astier > > Subject: [PATCH v3] deb-pkg: split debug symbols in their own package > > > > This can r

Re: [PATCH 1/2] deb-pkg: split debug symbols in their own package

On Fri, 19 Apr 2013 10:05:19 +0200, Anisse Astier ani...@astier.eu wrote : On Tue, 9 Apr 2013 12:05:47 +0200, Anisse Astier ani...@astier.eu wrote : From: Anisse Astier ani...@astier.eu Subject: [PATCH v3] deb-pkg: split debug symbols in their own package This can reduce almost

Re: [PATCH 1/2] deb-pkg: split debug symbols in their own package

On Tue, 9 Apr 2013 12:05:47 +0200, Anisse Astier wrote : > > > From: Anisse Astier > Subject: [PATCH v3] deb-pkg: split debug symbols in their own package > > This can reduce almost 3 times the size of the linux-image package, > while keeping the debug symbols availabl

Re: [PATCH 1/2] deb-pkg: split debug symbols in their own package

On Tue, 9 Apr 2013 12:05:47 +0200, Anisse Astier ani...@astier.eu wrote : From: Anisse Astier ani...@astier.eu Subject: [PATCH v3] deb-pkg: split debug symbols in their own package This can reduce almost 3 times the size of the linux-image package, while keeping the debug symbols

Re: [PATCH 1/2] deb-pkg: split debug symbols in their own package

From: Anisse Astier Subject: [PATCH v3] deb-pkg: split debug symbols in their own package This can reduce almost 3 times the size of the linux-image package, while keeping the debug symbols available for this particular build, in their own package. This mimics the way kernels are built

Re: [PATCH 1/2] deb-pkg: split debug symbols in their own package

From: Anisse Astier ani...@astier.eu Subject: [PATCH v3] deb-pkg: split debug symbols in their own package This can reduce almost 3 times the size of the linux-image package, while keeping the debug symbols available for this particular build, in their own package. This mimics the way kernels

Re: [PATCH 1/2] deb-pkg: split debug symbols in their own package

On Mon, 08 Apr 2013 12:29:19 +0200, Michal Marek wrote : > On 22.3.2013 11:06, Anisse Astier wrote: > > This can reduce almost 3 times the size of the linux-image package, > > while keeping the debug symbols available for this particular build, in > > their own package.

Re: [PATCH 1/2] deb-pkg: split debug symbols in their own package

On Mon, 08 Apr 2013 12:29:19 +0200, Michal Marek mma...@suse.cz wrote : On 22.3.2013 11:06, Anisse Astier wrote: This can reduce almost 3 times the size of the linux-image package, while keeping the debug symbols available for this particular build, in their own package. This mimics

  1   2   >