From: Christophe Saout <christophe@saout.de>
To: akpm@osdl.org, linux-kernel@vger.kernel.org
Cc: James Morris <jmorris@redhat.com>, "David S. Miller" <davem@redhat.com>
Subject: Re: Fw: IPsec/crypto kernel panic in 2.6.[456]
Date: Sun, 23 May 2004 16:33:22 +0200 [thread overview]
Message-ID: <1085322803.32532.1.camel@leto.cs.pocnet.net> (raw)
In-Reply-To: <20040520213743.GA9702@leto.cs.pocnet.net>
Hello,
Small update: Tobias Ringström told me that the Oops goes away when he
applies the bugfix I sent Andrew. We're still trying to find out what
exactly was happening.
> The two problems I found:
>
> After calling scatterwalk_copychunks walk_in might point to the next
> page which will break scatterwalk_samebuf (in this case src_p should
> point to tmp_src anyway and scatterwalk_samembuf returns 0).
>
> scatterwalk_samebuf should also check for equal offsets inside the
> page (just bad for performance in some cases).
prev parent reply other threads:[~2004-05-23 14:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040520003739.624cc2d2.akpm@osdl.org>
[not found] ` <Xine.LNX.4.44.0405200409530.15731-100000@thoron.boston.redhat.com>
[not found] ` <20040520081049.4bfa7e3f.davem@redhat.com>
2004-05-20 21:37 ` Christophe Saout
2004-05-23 14:33 ` Christophe Saout [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=1085322803.32532.1.camel@leto.cs.pocnet.net \
--to=christophe@saout.de \
--cc=akpm@osdl.org \
--cc=davem@redhat.com \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®