From: Max Dubois <makemehappy@rocketmail.com>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"Harshit Mogalapalli" <harshit.m.mogalapalli@oracle.com>,
ilpo.jarvinen@linux.intel.com, gregkh@linuxfoundation.org,
"Dan Carpenter" <error27@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Bug related with a 6.6.24 platform/x86 commit signed by you - Enormous memory leak
Date: Fri, 19 Jul 2024 17:40:59 +0200 [thread overview]
Message-ID: <CBDDDC2F-34FC-42B3-84EF-5F3BEA5AC480@rocketmail.com> (raw)
In-Reply-To: <9b0e7f6a-0432-46ba-bd75-7ba324934716@suswa.mountain>
I’m sorry, yes that file i called ‘working’ contain multiple kernels instances becouae I had to do a path to find out the crash happened at 6.6.24 level and that the last working kernel was 6.6.23. So I did a try to a lot of kernels over and under 6.6.24 to isolate the problem to 6.6.24 and everything after.
If needed I can try to isolate the instance of the working 6.6.23 and I can’t confirm it does NO ERRORS at all like the kernels before it.
Buggy 6.6.24 log it is corrrext, the real 6.6.24 log with buga on vmalloc.
If needed I can confirm I can test any possible fix and/or patch against 6.6.24.
Thank you
MD
Inviato da iPhone
> Il giorno 19 lug 2024, alle ore 17:12, Dan Carpenter <dan.carpenter@linaro.org> ha scritto:
>
> On Fri, Jul 19, 2024 at 10:01:14AM -0500, Dan Carpenter wrote:
>>
>> The interesting thing about that is the working kernel had tons of these
>> allocation failures as well.
>> https://bugzilla.kernel.org/show_bug.cgi?id=219061
>> See the attachment which called "This is a session with the last WORKING
>> KERNEL 6.6.23, NO ERRORS, everything fine".
>
> Never mind. There are a bunch of different reboots in that file with
> different kernels.
>
> regards,
> dan carpenter
>
next prev parent reply other threads:[~2024-07-19 15:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <707784492.392759.1721383145890.ref@mail.yahoo.com>
[not found] ` <707784492.392759.1721383145890@mail.yahoo.com>
2024-07-19 12:04 ` Harshit Mogalapalli
2024-07-19 12:32 ` Thomas Weißschuh
2024-07-19 15:01 ` Dan Carpenter
2024-07-19 15:12 ` Dan Carpenter
2024-07-19 15:40 ` Max Dubois [this message]
2024-07-19 16:33 ` Thomas Weißschuh
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=CBDDDC2F-34FC-42B3-84EF-5F3BEA5AC480@rocketmail.com \
--to=makemehappy@rocketmail.com \
--cc=dan.carpenter@linaro.org \
--cc=error27@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=harshit.m.mogalapalli@oracle.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.weissschuh@linutronix.de \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®