From: Tobias Hommel <netdev-list@genoetigt.de>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: Wolfgang Walter <linux@stwm.de>,
Kristian Evensen <kristian.evensen@gmail.com>,
Network Development <netdev@vger.kernel.org>,
weiwan@google.com, edumazet@google.com
Subject: Re: kernels > v4.12 oops/crash with ipsec-traffic: bisected to b838d5e1c5b6e57b10ec8af2268824041e3ea911: ipv4: mark DST_NOGC and remove the operation of dst_free()
Date: Wed, 19 Sep 2018 20:38:39 +0200 [thread overview]
Message-ID: <20180919183839.2k4jw4cmyzbtgjfh@delI> (raw)
In-Reply-To: <20180912151823.z2wk7hnex4zxly3e@arbeitstier>
> After running for about 24 hours, I now encountered another panic. This time it
> is caused by an out of memory situation. Although the trace shows action in the
> filesystem code I'm posting it here because I cannot isolate the error and
> maybe it is caused by our NULL pointer bug or by the new fix.
> I do not have a serial console attached, so I could only attach a screenshot of
> the panic to this mail.
>
> I am running v4.19-rc3 from git with the above mentioned patch applied.
> After 19 hours everything still looked fine, XfrmFwdHdrError value was at ~950.
> Overall memory usage shown by htop was at 1.2G/15.6G.
> I had htop running via ssh so I was able to see at least some status post
> mortem. Uptime: 23:50:57
> Overall memory usage was at 10.2G/15.6G and user processes were just
> using the usual amount of memory, so it looks like the kernel was eating up at
> least 9G of RAM.
>
> Maybe this information is not very helpful for debugging, but it is at least a
> warning that something might still be wrong.
>
> I'll try to gather some more information and keep you updated.
Running stable under load for more than 5 days now, I was not able to reproduce
that OOM situation. I leave it at that, the fix for the initial bug is fine for
me.
next prev parent reply other threads:[~2018-09-20 0:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 10:48 kernels >= v4.12 oops/crash with ipsec-traffic: partly bisected Wolfgang Walter
2018-08-30 18:53 ` kernels > v4.12 oops/crash with ipsec-traffic: bisected to b838d5e1c5b6e57b10ec8af2268824041e3ea911: ipv4: mark DST_NOGC and remove the operation of dst_free() Wolfgang Walter
2018-08-31 6:50 ` Steffen Klassert
2018-09-07 9:53 ` Wolfgang Walter
2018-09-07 20:22 ` Wolfgang Walter
2018-09-07 21:10 ` Wolfgang Walter
2018-09-10 6:37 ` Steffen Klassert
2018-09-10 8:18 ` Kristian Evensen
2018-09-10 10:46 ` Wolfgang Walter
2018-09-11 10:33 ` Steffen Klassert
2018-09-11 16:53 ` Wolfgang Walter
2018-09-11 19:02 ` Tobias Hommel
2018-09-12 8:50 ` Steffen Klassert
2018-09-12 15:18 ` Tobias Hommel
2018-09-19 18:38 ` Tobias Hommel [this message]
2018-09-10 9:06 ` Tobias Hommel
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=20180919183839.2k4jw4cmyzbtgjfh@delI \
--to=netdev-list@genoetigt.de \
--cc=edumazet@google.com \
--cc=kristian.evensen@gmail.com \
--cc=linux@stwm.de \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
--cc=weiwan@google.com \
/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