From: Andrea Arcangeli <andrea@suse.de>
To: linux-kernel@vger.kernel.org
Subject: 2.4.9aa3
Date: Sun, 19 Aug 2001 08:07:42 +0200 [thread overview]
Message-ID: <20010819080742.A725@athlon.random> (raw)
Only in 2.4.9aa2: 00_silent-stack-overflow-5
Only in 2.4.9aa3: 00_silent-stack-overflow-6
Updated to run expand_stack always with the mm write semaphore acquired
to fix the race conditions. Upgrading the semaphore during
map_user_kiobuf was quite painful so I just disallowed to do direct I/O
on a growsdown VMA (you can still do that as far as it doesn't need to
be live extended on the fly).
Only in 2.4.9aa3: 00_vm_raend-race-1
Sanitize the vm_raend field before trusting it, such field is racy.
Only in 2.4.9aa2: 10_expand-stack-smp-1
Dropped (it wasn't needed).
Only in 2.4.9aa2: 70_mmap-rb-4
Only in 2.4.9aa3: 70_mmap-rb-5
Backed out a few unnecessary minor changes.
Andrea
next reply other threads:[~2001-08-19 6:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-19 6:07 Andrea Arcangeli [this message]
2001-09-03 15:24 ` expand_stack fix [was Re: 2.4.9aa3] Andrea Arcangeli
2001-09-07 18:47 ` Linus Torvalds
2001-09-08 16:04 ` Andrea Arcangeli
2001-09-08 16:28 ` Linus Torvalds
2001-09-09 4:23 ` Jeff Dike
2001-09-09 3:50 ` Andrea Arcangeli
2001-09-09 5:42 ` Jeff Dike
2001-09-11 11:24 ` Andrea Arcangeli
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=20010819080742.A725@athlon.random \
--to=andrea@suse.de \
--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