From: "Zeng, MingwangX" <mingwangx.zeng@intel.com>
To: "libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Subject: RE: A clash happened in kernel by glibc-2.33
Date: Thu, 1 Jul 2021 01:49:51 +0000 [thread overview]
Message-ID: <BL0PR11MB3379E1817C25296E513609DB9D009@BL0PR11MB3379.namprd11.prod.outlook.com> (raw)
In-Reply-To: <87669f23-c5f0-e742-5dc1-638f5bc89bec@redhat.com>
Hi, alpha
I tried kernel versions 4.9.257, 4.9.258, and they all crashed.
I don't use the option --enable-kernel, as we update kernel more frequently than glibc .
Is this option --enable-kernel=4.9.255 compatible with versions after 4.9.255?
BR,
Mingwang
-----Original Message-----
From: Carlos O'Donell <carlos@redhat.com>
Sent: Wednesday, June 30, 2021 10:29 PM
To: Zeng, MingwangX <mingwangx.zeng@intel.com>; libc-maintainers@gnu.org
Subject: Re: A clash happened in kernel by glibc-2.33
On 6/30/21 2:29 AM, Zeng, MingwangX wrote:
> Hi, Glibc maintainers
Zeng,
Please send this to libc-alpha@sourceware.org, and we'll have a development discussion there?
Please provide the exact value of --enable-kernel that was used to trigger this defect and why you selected that given kernel version.
No default selection will trigger this because we set the Z component of the version to 0 in the defaults.
> A clash happened in kernel by glibc-2.33.
>
> Scene:
> when kernel mini version lager then 255, glibc could cause the clash.
>
> FATAL: kernel too old
> Kernel panic - not syncing: Attempted to kill init!
> exitcode=0x00007f00
>
> Reason:
> sysdeps/unix/sysv/linux/dl-sysdep.c
> line:
> 110 while ((*cp >= '0') && (*cp <= '9'))
> 111 {
> 112 unsigned int here = *cp++ - '0';
> 113
> 114 while ((*cp >= '0') && (*cp <= '9'))
> 115 {
> 116 here *= 10;
> 117 here += *cp++ - '0';
> 118 }
> 119
> 120 ++parts;
> 121 version <<= 8;
> 122 version | = here; // root case.
>
> Such as Kernel version is 4.9.256 , it will be : version |= 256 ;
> Version == 4.9.0
>
> Would you please provide me with a temporary patch, think you very much!
>
> BR,
> Mingwang.
>
>
>
--
Cheers,
Carlos.
next parent reply other threads:[~2021-07-01 1:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BL0PR11MB3379A7ABFE499F1E4BC333179D019@BL0PR11MB3379.namprd11.prod.outlook.com>
[not found] ` <87669f23-c5f0-e742-5dc1-638f5bc89bec@redhat.com>
2021-07-01 1:49 ` Zeng, MingwangX [this message]
2021-07-01 6:06 ` Florian Weimer
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=BL0PR11MB3379E1817C25296E513609DB9D009@BL0PR11MB3379.namprd11.prod.outlook.com \
--to=mingwangx.zeng@intel.com \
--cc=libc-alpha@sourceware.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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).