From: Andrey Ryabinin <ryabinin.a.a@gmail.com> To: Dave Jones <davej@codemonkey.org.uk>, Linux Kernel <linux-kernel@vger.kernel.org>, Linus Torvalds <torvalds@linux-foundation.org>, "linux-mm@kvack.org" <linux-mm@kvack.org> Subject: Re: [4.7+] various memory corruption reports. Date: Mon, 1 Aug 2016 14:03:15 +0300 [thread overview] Message-ID: <579F2C73.6090406@gmail.com> (raw) In-Reply-To: <20160729183925.GA28376@codemonkey.org.uk> On 07/29/2016 09:39 PM, Dave Jones wrote: > On Fri, Jul 29, 2016 at 08:56:08PM +0300, Andrey Ryabinin wrote: > > > >> > I suspect this is false positives due to changes in KASAN. > > >> > Bisection probably will point to > > >> > 80a9201a5965f4715d5c09790862e0df84ce0614 ("mm, kasan: switch SLUB to > > >> > stackdepot, enable memory quarantine for SLUB)" > > >> > > >> good call. reverting that changeset seems to have solved it. > > > Could you please try with this? > > Actually, this is not quite right, it should be like this: > > > Seems to have stopped the corruption, but now I get NMi watchdog traces.. > > This should help: --- mm/kasan/kasan.c | 4 ++-- mm/kasan/quarantine.c | 8 ++++++-- 2 files changed, 8 insertions(+), 4 deletions(-) diff --git a/mm/kasan/kasan.c b/mm/kasan/kasan.c index 3019cec..c99ef40 100644 --- a/mm/kasan/kasan.c +++ b/mm/kasan/kasan.c @@ -565,7 +565,7 @@ void kasan_kmalloc(struct kmem_cache *cache, const void *object, size_t size, unsigned long redzone_start; unsigned long redzone_end; - if (flags & __GFP_RECLAIM) + if (gfpflags_allow_blocking(flags)) quarantine_reduce(); if (unlikely(object == NULL)) @@ -596,7 +596,7 @@ void kasan_kmalloc_large(const void *ptr, size_t size, gfp_t flags) unsigned long redzone_start; unsigned long redzone_end; - if (flags & __GFP_RECLAIM) + if (gfpflags_allow_blocking(flags)) quarantine_reduce(); if (unlikely(ptr == NULL)) diff --git a/mm/kasan/quarantine.c b/mm/kasan/quarantine.c index 65793f1..4852625 100644 --- a/mm/kasan/quarantine.c +++ b/mm/kasan/quarantine.c @@ -147,10 +147,14 @@ static void qlink_free(struct qlist_node *qlink, struct kmem_cache *cache) struct kasan_alloc_meta *alloc_info = get_alloc_info(cache, object); unsigned long flags; - local_irq_save(flags); + if (IS_ENABLED(CONFIG_SLAB)) + local_irq_save(flags); + alloc_info->state = KASAN_STATE_FREE; ___cache_free(cache, object, _THIS_IP_); - local_irq_restore(flags); + + if (IS_ENABLED(CONFIG_SLAB)) + local_irq_restore(flags); } static void qlist_free_all(struct qlist_head *q, struct kmem_cache *cache) -- 2.7.3
WARNING: multiple messages have this Message-ID (diff)
From: Andrey Ryabinin <ryabinin.a.a@gmail.com> To: Dave Jones <davej@codemonkey.org.uk>, Linux Kernel <linux-kernel@vger.kernel.org>, Linus Torvalds <torvalds@linux-foundation.org>, "linux-mm@kvack.org" <linux-mm@kvack.org> Subject: Re: [4.7+] various memory corruption reports. Date: Mon, 1 Aug 2016 14:03:15 +0300 [thread overview] Message-ID: <579F2C73.6090406@gmail.com> (raw) In-Reply-To: <20160729183925.GA28376@codemonkey.org.uk> On 07/29/2016 09:39 PM, Dave Jones wrote: > On Fri, Jul 29, 2016 at 08:56:08PM +0300, Andrey Ryabinin wrote: > > > >> > I suspect this is false positives due to changes in KASAN. > > >> > Bisection probably will point to > > >> > 80a9201a5965f4715d5c09790862e0df84ce0614 ("mm, kasan: switch SLUB to > > >> > stackdepot, enable memory quarantine for SLUB)" > > >> > > >> good call. reverting that changeset seems to have solved it. > > > Could you please try with this? > > Actually, this is not quite right, it should be like this: > > > Seems to have stopped the corruption, but now I get NMi watchdog traces.. > > This should help: --- mm/kasan/kasan.c | 4 ++-- mm/kasan/quarantine.c | 8 ++++++-- 2 files changed, 8 insertions(+), 4 deletions(-) diff --git a/mm/kasan/kasan.c b/mm/kasan/kasan.c index 3019cec..c99ef40 100644 --- a/mm/kasan/kasan.c +++ b/mm/kasan/kasan.c @@ -565,7 +565,7 @@ void kasan_kmalloc(struct kmem_cache *cache, const void *object, size_t size, unsigned long redzone_start; unsigned long redzone_end; - if (flags & __GFP_RECLAIM) + if (gfpflags_allow_blocking(flags)) quarantine_reduce(); if (unlikely(object == NULL)) @@ -596,7 +596,7 @@ void kasan_kmalloc_large(const void *ptr, size_t size, gfp_t flags) unsigned long redzone_start; unsigned long redzone_end; - if (flags & __GFP_RECLAIM) + if (gfpflags_allow_blocking(flags)) quarantine_reduce(); if (unlikely(ptr == NULL)) diff --git a/mm/kasan/quarantine.c b/mm/kasan/quarantine.c index 65793f1..4852625 100644 --- a/mm/kasan/quarantine.c +++ b/mm/kasan/quarantine.c @@ -147,10 +147,14 @@ static void qlink_free(struct qlist_node *qlink, struct kmem_cache *cache) struct kasan_alloc_meta *alloc_info = get_alloc_info(cache, object); unsigned long flags; - local_irq_save(flags); + if (IS_ENABLED(CONFIG_SLAB)) + local_irq_save(flags); + alloc_info->state = KASAN_STATE_FREE; ___cache_free(cache, object, _THIS_IP_); - local_irq_restore(flags); + + if (IS_ENABLED(CONFIG_SLAB)) + local_irq_restore(flags); } static void qlist_free_all(struct qlist_head *q, struct kmem_cache *cache) -- 2.7.3 -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-08-01 12:03 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-07-29 15:05 [4.7+] various memory corruption reports Dave Jones 2016-07-29 15:05 ` Dave Jones 2016-07-29 15:19 ` Dave Jones 2016-07-29 15:19 ` Dave Jones 2016-07-29 15:21 ` Andrey Ryabinin 2016-07-29 15:21 ` Andrey Ryabinin 2016-07-29 15:49 ` Dave Jones 2016-07-29 15:49 ` Dave Jones 2016-07-29 17:32 ` Andrey Ryabinin 2016-07-29 17:32 ` Andrey Ryabinin 2016-07-29 17:56 ` Andrey Ryabinin 2016-07-29 17:56 ` Andrey Ryabinin 2016-07-29 18:39 ` Dave Jones 2016-07-29 18:39 ` Dave Jones 2016-08-01 11:03 ` Andrey Ryabinin [this message] 2016-08-01 11:03 ` Andrey Ryabinin 2016-08-01 16:37 ` Dave Jones 2016-08-01 16:37 ` Dave Jones
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=579F2C73.6090406@gmail.com \ --to=ryabinin.a.a@gmail.com \ --cc=davej@codemonkey.org.uk \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=torvalds@linux-foundation.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.