From: Jeffrin Thalakkottoor <jeffrin@rajagiritech.edu.in>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: review for 5.16.3-rc2
Date: Tue, 25 Jan 2022 22:32:26 +0530 [thread overview]
Message-ID: <CAG=yYw=BK1gU0UV8g5_ZT5gOe5P2W2rKHWdFyPi4ZHSy4CGMFw@mail.gmail.com> (raw)
In-Reply-To: <YfAk90OPjlpjruV5@kroah.com>
On Tue, Jan 25, 2022 at 9:57 PM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Tue, Jan 25, 2022 at 09:49:00PM +0530, Jeffrin Thalakkottoor wrote:
> > On Tue, Jan 25, 2022 at 8:04 PM Greg KH <gregkh@linuxfoundation.org> wrote:
> > >
> > > On Tue, Jan 25, 2022 at 06:15:46PM +0530, Jeffrin Jose T wrote:
> > > > hello greg,
> > > >
> > > > compile failed for 5.16.3-rc2 related.
> > > > a relevent file attached.
> > > >
> > > > Tested-by : Jeffrin Jose T <jeffrin@rajagiritech.edu.in>
> > >
> > > But it failed for you, how did you test it?
> >
> > i compiled 5.16.3-rc2 related to "make localmodconfig" and "make -j4"
>
> So it somehow failed?
Yes i think so
>
> > >
> > > >
> > > >
> > >
> > > > char * typetab; /* 24 8 */
> > > >
> > > > /* size: 32, cachelines: 1, members: 4 */
> > > > /* sum members: 28, holes: 1, sum holes: 4 */
> > > > /* last cacheline: 32 bytes */
> > > > };
> > > > struct klp_modinfo {
> > > > Elf64_Ehdr hdr; /* 0 64 */
> > > > /* --- cacheline 1 boundary (64 bytes) --- */
> > > > Elf64_Shdr * sechdrs; /* 64 8 */
> > > > char * secstrings; /* 72 8 */
> > > > unsigned int symndx; /* 80 4 */
> > > >
> > > > /* size: 88, cachelines: 2, members: 4 */
> > > > /* padding: 4 */
> > > > /* last cacheline: 24 bytes */
> > > > };
> > > > Segmentation fault
> > >
> > > What "faulted"? Look higher up in the log please.
> >
> > a top view...
> >
> > CALL scripts/atomic/check-atomics.sh
> > CALL scripts/checksyscalls.sh
> > CHK include/generated/compile.h
> > GEN .version
> > CHK include/generated/compile.h
> > UPD include/generated/compile.h
> > CC init/version.o
> > AR init/built-in.a
> > LD vmlinux.o
> > MODPOST vmlinux.symvers
> > MODINFO modules.builtin.modinfo
> > GEN modules.builtin
> > LD .tmp_vmlinux.btf
> > BTF .btf.vmlinux.bin.o
> > struct list_head {
> > struct list_head * next; /* 0 8 */
> > struct list_head * prev; /* 8 8 */
> >
> > /* size: 16, cachelines: 1, members: 2 */
> > /* last cacheline: 16 bytes */
> > };
> > struct hlist_head {
> > struct hlist_node * first; /* 0 8 */
> >
> > /* size: 8, cachelines: 1, members: 1 */
> > /* last cacheline: 8 bytes */
> > };
> > struct hlist_node {
> > struct hlist_node * next; /* 0 8 */
> > struct hlist_node * * pprev; /* 8 8 */
> >
> > /* size: 16, cachelines: 1, members: 2 */
> > /* last cacheline: 16 bytes */
> > };
> > struct callback_head {
> > struct callback_head * next; /* 0 8 */
> > void (*func)(struct callback_head *); /*
> > 8 8 */
> > .
> > .
> > .
> > .
> > .
> > .
>
> I do not know what is failing, there is no error message here. Does
> 5.16.2 build properly for you?
stderr has captured the following...
-------------x-----------------x--------------x---
FAILED: load BTF from vmlinux: No such file or directory
make: *** [Makefile:1161: vmlinux] Error 255
make: *** Deleting file 'vmlinux'
------------x----------------x------------x--
5.16.2-rc1 builds for me.
Will the following link help...
https://unix.stackexchange.com/questions/616392/failed-load-btf-from-vmlinux-unknown-error-2make-makefile1162-vmlinu
--
software engineer
rajagiri school of engineering and technology
next prev parent reply other threads:[~2022-01-25 17:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 12:45 review for 5.16.3-rc2 Jeffrin Jose T
2022-01-25 14:34 ` Greg KH
2022-01-25 16:19 ` Jeffrin Thalakkottoor
2022-01-25 16:27 ` Greg KH
2022-01-25 17:02 ` Jeffrin Thalakkottoor [this message]
2022-01-25 18:55 ` Jeffrin Thalakkottoor
2022-01-26 10:45 ` Salvatore Bonaccorso
2022-01-26 12:36 ` Jeffrin Thalakkottoor
2022-01-26 14:37 ` Jeffrin Thalakkottoor
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='CAG=yYw=BK1gU0UV8g5_ZT5gOe5P2W2rKHWdFyPi4ZHSy4CGMFw@mail.gmail.com' \
--to=jeffrin@rajagiritech.edu.in \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.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 NNTP newsgroup(s).