[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <86fd0ccb-f460-651f-8048-1026d905a2d6@redhat.com>
Date: Mon, 24 Jul 2023 08:23:55 +0200
From: David Hildenbrand <david@...hat.com>
To: Baoquan He <bhe@...hat.com>, Jiri Olsa <olsajiri@...il.com>
Cc: Lorenzo Stoakes <lstoakes@...il.com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Uladzislau Rezki <urezki@...il.com>,
Matthew Wilcox <willy@...radead.org>,
Liu Shixin <liushixin2@...wei.com>,
Jens Axboe <axboe@...nel.dk>,
Alexander Viro <viro@...iv.linux.org.uk>
Subject: Re: [PATCH v8 1/4] fs/proc/kcore: avoid bounce buffer for ktext data
Hi,
>
> I met this too when I executed below command to trigger a kcore reading.
> I wanted to do a simple testing during system running and got this.
>
> makedumpfile --mem-usage /proc/kcore
>
> Later I tried your above objdump testing, it corrupted system too.
>
What do you mean with "corrupted system too" -- did it not only fail to
dump the system, but also actually harmed the system?
@Lorenzo do you plan on reproduce + fix, or should we consider reverting
that change?
--
Cheers,
David / dhildenb
Powered by blists - more mailing lists