From: Jeff Moyer <jmoyer@redhat.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: "K.R. Foley" <kr@cybsft.com>, linux-fsdevel@vger.kernel.org
Subject: Re: BUG triggers running lsof
Date: Fri, 20 Nov 2020 14:51:48 -0500 [thread overview]
Message-ID: <x49im9zn6wb.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <4cc7a530-41ed-81f4-82cd-6a3a93661dce@infradead.org> (Randy Dunlap's message of "Fri, 20 Nov 2020 11:42:48 -0800")
Randy Dunlap <rdunlap@infradead.org> writes:
> On 11/20/20 11:16 AM, K.R. Foley wrote:
>> I have found an issue that triggers by running lsof. The problem is
>> reproducible, but not consistently. I have seen this issue occur on
>> multiple versions of the kernel (5.0.10, 5.2.8 and now 5.4.77). It
>> looks like it could be a race condition or the file pointer is being
>> corrupted. Any pointers on how to track this down? What additional
>> information can I provide?
>
> Hi,
>
> 2 things in general:
>
> a) Can you test with a more recent kernel?
>
> b) Can you reproduce this without loading the proprietary & out-of-tree
> kernel modules? They should never have been loaded after bootup.
> I.e., don't just unload them -- that could leave something bad behind.
Heh, the EIP contains part of the name of one of the modules:
>
>> [ 8057.297159] BUG: unable to handle page fault for address: 31376f63
^^^^^^^^
>> [ 8057.297219] Modules linked in: ITXico7100Module(O)
^^^^
-Jeff
next prev parent reply other threads:[~2020-11-20 19:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 19:16 BUG triggers running lsof K.R. Foley
2020-11-20 19:42 ` Randy Dunlap
2020-11-20 19:51 ` Jeff Moyer [this message]
2020-11-20 20:59 ` K.R. Foley
2020-11-20 21:13 ` Randy Dunlap
2020-11-20 21:28 ` K.R. Foley
2020-11-20 20:56 ` K.R. Foley
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=x49im9zn6wb.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=kr@cybsft.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=rdunlap@infradead.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).