From: "machael" <dony.he@huawei.com>
To: "Ralf Baechle" <ralf@oss.sgi.com>
Cc: <linux-mips@oss.sgi.com>
Subject: Re: vmalloc bugs in 2.4.5???
Date: Wed, 7 Nov 2001 19:29:59 +0800 [thread overview]
Message-ID: <000f01c1677f$88fd6560$4a1c690a@huawei.com> (raw)
In-Reply-To: 20011107024146.A1740@dea.linux-mips.net
> On Wed, Nov 07, 2001 at 10:39:47AM +0900, Atsushi Nemoto wrote:
>
> > In 2.4.5, flush_cache_all() (and flush_tlb_all()) is called in
> > vmalloc_area_pages(). I think this call protect us from virtual
> > aliasing problem.
> >
> > By the way, does anybody have any problem with vmalloc on recent
> > kernel?
> >
> > In somewhere between 2.4.6 and 2.4.9, the call to flush_cache_all()
> > disappered from vmalloc_area_pages(). I have a data corruption
> > problem in vmalloc()ed area without this call. I think we still need
> > this call.
>
> Entirely correct. I'm just trying to find why this call got removed
> in 2.4.10. Clearly wrong; I had not noticed that these two lines
> got removed and thus was assuming the code of those two must somehow
> be malfunctioning.
I have added these two lines to vmalloc_area_pages in 2.4.10,but the
problems still appear.
Why?
machael
WARNING: multiple messages have this Message-ID (diff)
From: "machael" <dony.he@huawei.com>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: vmalloc bugs in 2.4.5???
Date: Wed, 7 Nov 2001 19:29:59 +0800 [thread overview]
Message-ID: <000f01c1677f$88fd6560$4a1c690a@huawei.com> (raw)
Message-ID: <20011107112959.5ieQn4y1yXzt8zs3sFRdxQCS-X3upYA__GHmChaIC5I@z> (raw)
In-Reply-To: 20011107024146.A1740@dea.linux-mips.net
> On Wed, Nov 07, 2001 at 10:39:47AM +0900, Atsushi Nemoto wrote:
>
> > In 2.4.5, flush_cache_all() (and flush_tlb_all()) is called in
> > vmalloc_area_pages(). I think this call protect us from virtual
> > aliasing problem.
> >
> > By the way, does anybody have any problem with vmalloc on recent
> > kernel?
> >
> > In somewhere between 2.4.6 and 2.4.9, the call to flush_cache_all()
> > disappered from vmalloc_area_pages(). I have a data corruption
> > problem in vmalloc()ed area without this call. I think we still need
> > this call.
>
> Entirely correct. I'm just trying to find why this call got removed
> in 2.4.10. Clearly wrong; I had not noticed that these two lines
> got removed and thus was assuming the code of those two must somehow
> be malfunctioning.
I have added these two lines to vmalloc_area_pages in 2.4.10,but the
problems still appear.
Why?
machael
next prev parent reply other threads:[~2001-11-07 11:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-05 7:34 vmalloc bugs in 2.4.5??? machael
2001-11-05 7:34 ` machael
2001-11-06 21:08 ` Ralf Baechle
2001-11-07 0:47 ` machael
2001-11-07 0:47 ` machael
2001-11-07 1:39 ` Atsushi Nemoto
2001-11-07 2:09 ` machael
2001-11-07 2:09 ` machael
2001-11-07 10:41 ` Ralf Baechle
2001-11-07 11:29 ` machael [this message]
2001-11-07 11:29 ` machael
2001-11-08 15:16 ` Maciej W. Rozycki
2001-12-26 3:32 ` Ralf Baechle
2001-12-27 1:55 ` Atsushi Nemoto
2001-12-27 3:12 ` Ralf Baechle
2001-12-27 3:51 ` Atsushi Nemoto
2001-12-27 4:29 ` Ralf Baechle
2001-12-27 16:01 ` Tommy S. Christensen
2001-12-27 21:19 ` Ralf Baechle
2001-12-28 0:48 ` machael thailer
2001-12-28 0:48 ` machael thailer
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='000f01c1677f$88fd6560$4a1c690a@huawei.com' \
--to=dony.he@huawei.com \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@oss.sgi.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 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.