Re: mm/vmalloc.c:3689 vread_iter() error: we previously assumed 'vm' could be null (see line 3667)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Baoquan He <bhe@xxxxxxxxxx>
Subject: Re: mm/vmalloc.c:3689 vread_iter() error: we previously assumed 'vm' could be null (see line 3667)
From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Date: Thu, 19 Oct 2023 09:50:30 -0700
Cc: Dan Carpenter <dan.carpenter@xxxxxxxxxx>, Philip Li <philip.li@xxxxxxxxx>, oe-kbuild@xxxxxxxxxxxxxxx, Lorenzo Stoakes <lstoakes@xxxxxxxxx>, lkp@xxxxxxxxx, oe-kbuild-all@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, Linux Memory Management List <linux-mm@xxxxxxxxx>
In-reply-to: <ZTCURc8ZQE+KrTvS@MiWiFi-R3L-srv>
References: <f82be227-bfde-439a-b339-1b4ee370d59a@kadam.mountain> <ZS+dSd9Z6/2wU0Eg@MiWiFi-R3L-srv> <89caf59a-d3b9-409d-b1ae-9e370cb9ee7d@kadam.mountain> <ZS/LrhcxcMOgiiX5@MiWiFi-R3L-srv> <ZS/TVMT9ed7OdyNy@rli9-mobl> <ZS/2k6DIMd0tZRgK@MiWiFi-R3L-srv> <20231018085248.6f3f36101cbdfe0990c8b467@linux-foundation.org> <ZTCURc8ZQE+KrTvS@MiWiFi-R3L-srv>

On Thu, 19 Oct 2023 10:28:21 +0800 Baoquan He <bhe@xxxxxxxxxx> wrote:

> I think this is not a real runtime bug. The only chance it can hapen is
> when (flags == VMAP_BLOCK) is true. That has been warned and could never
> happen. I updated patch log and paste v2 here. 

Thanks, I updated the changelog in-place.

Follow-Ups:
- Re: mm/vmalloc.c:3689 vread_iter() error: we previously assumed 'vm' could be null (see line 3667)
  - From: Baoquan He

References:
- mm/vmalloc.c:3689 vread_iter() error: we previously assumed 'vm' could be null (see line 3667)
  - From: Dan Carpenter
- Re: mm/vmalloc.c:3689 vread_iter() error: we previously assumed 'vm' could be null (see line 3667)
  - From: Baoquan He
- Re: mm/vmalloc.c:3689 vread_iter() error: we previously assumed 'vm' could be null (see line 3667)
  - From: Dan Carpenter
- Re: mm/vmalloc.c:3689 vread_iter() error: we previously assumed 'vm' could be null (see line 3667)
  - From: Baoquan He
- Re: mm/vmalloc.c:3689 vread_iter() error: we previously assumed 'vm' could be null (see line 3667)
  - From: Philip Li
- Re: mm/vmalloc.c:3689 vread_iter() error: we previously assumed 'vm' could be null (see line 3667)
  - From: Baoquan He
- Re: mm/vmalloc.c:3689 vread_iter() error: we previously assumed 'vm' could be null (see line 3667)
  - From: Andrew Morton
- Re: mm/vmalloc.c:3689 vread_iter() error: we previously assumed 'vm' could be null (see line 3667)
  - From: Baoquan He

Prev by Date: Re: [PATCH v2 1/1] mm: report per-page metadata information
Next by Date: Re: [PATCH v3 3/3] selftests/mm: add UFFDIO_MOVE ioctl test
Previous by thread: Re: mm/vmalloc.c:3689 vread_iter() error: we previously assumed 'vm' could be null (see line 3667)
Next by thread: Re: mm/vmalloc.c:3689 vread_iter() error: we previously assumed 'vm' could be null (see line 3667)
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Bugtraq] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API]