linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "K.R. Foley" <kr@cybsft.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Jeff Moyer <jmoyer@redhat.com>, linux-fsdevel@vger.kernel.org
Subject: Re: BUG triggers running lsof
Date: Fri, 20 Nov 2020 15:28:09 -0600	[thread overview]
Message-ID: <55e19a5d6a64d24280c3eb82ef7cf183@cybsft.com> (raw)
In-Reply-To: <d070f189-d8ee-73e5-5502-6618080e64bc@infradead.org>



On 2020-11-20 15:13, Randy Dunlap wrote:
> On 11/20/20 12:59 PM, K.R. Foley wrote:
>> 
>> 
>> 
>> On 2020-11-20 13:51, Jeff Moyer wrote:
>>> 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
>>>                                                                 
>>> ^^^^^^^^
> 
> Thanks for noticing that, Jeff.  I should have seen it.
> 
>>>>> [ 8057.297219] Modules linked in: ITXico7100Module(O)
>>>                                          ^^^^
>> 
>> Perhaps this is a dumb question, but how could this happen?
> 
> 
> We don't know what is in that loadable kernel module, so we can't
> give a definitive answer to your question, other than it's buggy.
> Or maybe it was just written for an older kernel version.
> Or a kernel with different build options/settings.

I am starting to look at this now. It was written for an older kernel by 
someone else. Thank you for the tips.

> 
> Have you contacted IT support?
> 
> It would (will) be interesting to see if you can reproduce the problem
> without these modules being loaded...
> I kind of doubt it, but if it does still fail, it will give us 
> something
> to look at.

Knowing a little more now. I doubt it will be reproducible without the 
module.

-- 
Regards,
K.R. Foley

  reply	other threads:[~2020-11-20 21:28 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
2020-11-20 20:59     ` K.R. Foley
2020-11-20 21:13       ` Randy Dunlap
2020-11-20 21:28         ` K.R. Foley [this message]
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=55e19a5d6a64d24280c3eb82ef7cf183@cybsft.com \
    --to=kr@cybsft.com \
    --cc=jmoyer@redhat.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).