From: Herbert Xu <herbert@gondor.apana.org.au>
To: Eric Sesterhenn <snakebyte@gmx.de>
Cc: netdev@vger.kernel.org
Subject: Re: VM_BUG_ON triggered with udp6fuzz
Date: Tue, 24 Feb 2009 15:12:28 +0800 [thread overview]
Message-ID: <20090224071227.GA20887@gondor.apana.org.au> (raw)
In-Reply-To: <20090223142213.GA22327@alice>
Eric Sesterhenn <snakebyte@gmx.de> wrote:
> hi,
>
> first of all, i am not able to replicate this after a clean boot,
> running the command sudo -u snakebyte lf6/udp6fuzz -n 100 -r 9343
> produced the following BUG on my test box
> Not sure where the get_page was triggered from, could not
> find it in udp6.c ...
It's a weird crash. The stuff that we do with sk_sndmsg_page on
the UDP path is nonstandard to say the least. However, it does
look kosher.
So please let us know if you can reproduce this again.
Thanks,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2009-02-24 7:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 14:22 VM_BUG_ON triggered with udp6fuzz Eric Sesterhenn
2009-02-24 7:12 ` Herbert Xu [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=20090224071227.GA20887@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=snakebyte@gmx.de \
/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