From: Jeffrin Thalakkottoor <jeffrin@rajagiritech.edu.in>
To: Sasha Levin <sashal@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
oleg@redhat.com, christian@brauner.io, tj@kernel.org,
peterz@infradead.org, prsood@codeaurora.org, avagin@gmail.com,
aarcange@redhat.com, lkml <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org
Subject: Re: PROBLEM: objtool: __x64_sys_exit_group()+0x14: unreachable instruction
Date: Fri, 15 Nov 2019 22:32:41 +0530 [thread overview]
Message-ID: <CAG=yYw=N6fRJfsQG08-h5SX1RBqgcZjhCU44e1QFHaJ6_YS_Ng@mail.gmail.com> (raw)
In-Reply-To: <CAG=yYwnJKcriaHcZFFrznxq1V9-ZcLzC-O=fAhQ6Skmn4eFPAg@mail.gmail.com>
On Thu, Nov 14, 2019 at 3:07 AM Jeffrin Thalakkottoor
<jeffrin@rajagiritech.edu.in> wrote:
>
> On Wed, Nov 13, 2019 at 7:00 AM Sasha Levin <sashal@kernel.org> wrote:
> > Could you bisect it please? I'm not seeing the warning here, and
> > kernel/exit.c wasn't touched during the life of the 5.3 stable tree.
>
>
> I tried using related to "git bisect" and managed to check based
> on kernel revision related. The warning existed even on 5.3.5 and
> may be even back . i think may be it is a compiler issue which creates
> the warning and not the kernel.
i saw a link related to our issue:
https://lore.kernel.org/lkml/20170726191008.jk2cdqr4wqnc33es@treble/
please see the above link.
--
software engineer
rajagiri school of engineering and technology
prev parent reply other threads:[~2019-11-15 17:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 22:33 PROBLEM: objtool: __x64_sys_exit_group()+0x14: unreachable instruction Jeffrin Jose
2019-11-13 1:30 ` Sasha Levin
2019-11-13 21:37 ` Jeffrin Thalakkottoor
2019-11-15 17:02 ` Jeffrin Thalakkottoor [this message]
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=N6fRJfsQG08-h5SX1RBqgcZjhCU44e1QFHaJ6_YS_Ng@mail.gmail.com' \
--to=jeffrin@rajagiritech.edu.in \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=avagin@gmail.com \
--cc=christian@brauner.io \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=prsood@codeaurora.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tj@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).