All of lore.kernel.org
 help / color / mirror / Atom feed
From: sharathv@codeaurora.org
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: tgraf@suug.ch, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, edumazet@google.com
Subject: Re: Internal error: Oops  from inet_frag_find, when inserting a IP frag into a rhashtable
Date: Wed, 26 May 2021 20:06:55 +0530	[thread overview]
Message-ID: <221220f299ac4e6af858ce4e5d877d43@codeaurora.org> (raw)
In-Reply-To: <20210519112029.3jbw74fuqe4p2tjm@gondor.apana.org.au>

On 2021-05-19 16:50, Herbert Xu wrote:
> On Wed, May 19, 2021 at 12:52:27AM +0530, sharathv@codeaurora.org 
> wrote:
>> 
>>   784.185172:   <2>  (2)[71:kworker/2:1][20210408_17:01:54.754415]@2
>> __get_vm_area_node.llvm.17374696036975823682+0x1ac/0x1c8
>>    784.185179:   <2>  (2)[71:kworker/2:1][20210408_17:01:54.754422]@2
>> __vmalloc_node_flags_caller+0xb4/0x170
>>    784.185189:   <2>  (2)[71:kworker/2:1][20210408_17:01:54.754432]@2
>> kvmalloc_node+0x40/0xa8
>>    784.185199:   <2>  (2)[71:kworker/2:1][20210408_17:01:54.754442]@2
>> rhashtable_insert_rehash+0x84/0x264
> 
> Something very fishy is going on here.
> 
> The code path in rhashtable_insert_rehash cannot possibly trigger
> vmalloc because it uses GFP_ATOMIC.  Is this a pristine upstream
> kernel or are there patches that may change things?
> 
> Cheers,

Thanks for the reply Herbert, we have got this crash reported from 
external
folks and I am trying to get the answers for your questions.

      reply	other threads:[~2021-05-26 14:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-18 19:22 Internal error: Oops from inet_frag_find, when inserting a IP frag into a rhashtable sharathv
2021-05-19 11:20 ` Herbert Xu
2021-05-26 14:36   ` sharathv [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=221220f299ac4e6af858ce4e5d877d43@codeaurora.org \
    --to=sharathv@codeaurora.org \
    --cc=edumazet@google.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=tgraf@suug.ch \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.