From: Andrea Arcangeli <andrea@suse.de>
To: linux-kernel@vger.kernel.org
Subject: 2.4.19pre9aa2
Date: Fri, 31 May 2002 07:18:41 +0200 [thread overview]
Message-ID: <20020531051841.GA1172@dualathlon.random> (raw)
This in particular includes a fix from Denis Lunev to cure the
instability in 2.4.19pre9aa1 introduced by the first revision of the
inode-highmem fix (I also changed invalidate_inode_pages so that it runs
try_to_release_page for ext3 as suggested by Andrew a few days ago). So
everybody running 2.4.19pre9aa1 is recommended to upgrade to
2.4.19pre9aa2 ASAP.
http://www.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.19pre9aa2.gz
http://www.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.19pre9aa2/
Full changlog follows:
Only in 2.4.19pre9aa2: 00_fix-stat-irq-1
avoid showing those 10000... numbers in /proc/stat. From -ac.
Only in 2.4.19pre9aa2: 00_flock-posix-2001-1
Update to posix 2001 semantics for negative length. From -ac.
Only in 2.4.19pre9aa2: 00_ipc-sem-set-pid-during-setval-1
Set the sempid during serval operation, so getpid
operation will see it. From -ac.
Only in 2.4.19pre9aa2: 00_loop-handling-pages-in-cache-1
If the pagecache was preallocated it could be in highmem.
From -ac.
Only in 2.4.19pre9aa2: 00_mmap-TASK_SIZE-len-1
Avoid returning -EINVAL for length <= TASK_SIZE. From -ac,
Spotted by DervishD.
Only in 2.4.19pre9aa2: 00_scsi-error-thread-reparent-1
Reparent to init scsi-error kernel thread so it's not left
zombie floating around when it exists. From -ac.
Only in 2.4.19pre9aa2: 00_sig_ign-discard-sigurg-1
Update semantics while setting sigurg as sig_ign, the
pending sigurg will be flushed. From -ac.
Only in 2.4.19pre9aa2: 00_vm86-drop-v86mode-dead-thread-var-1
Drop dead variable in vm86 part of the thread struct. From -ac.
Only in 2.4.19pre9aa2: 00_wmem-default-lowmem-machines-1
Typo fix from -ac.
Only in 2.4.19pre9aa2: 00_x86-optimize-apic-irq-and-cacheline-1
cachelin-optimize the apic irq stats and cacheline align
the irq_stat array. From -ac.
Only in 2.4.19pre9aa2: 03_sched-pipe-bandwidth-1
If the pipe-writer fills the pipe reschedule the reader
in the same cpu of the writer to maximaze memory copy
bandwith in the local cpu over the pipe page. From Mike Kravetz.
Only in 2.4.19pre9aa1: 05_vm_10_read_write_tweaks-2
Only in 2.4.19pre9aa2: 05_vm_10_read_write_tweaks-3
Updated comments per Christoph's suggestion.
Only in 2.4.19pre9aa1: 10_inode-highmem-1
Only in 2.4.19pre9aa2: 10_inode-highmem-2
Fix showstopper bug that was corrupting the inode unused_list
if the number of unused inodes was < vm_vfs_scan_ratio.
Spotted and fixed by Denis Lunev.
Only in 2.4.19pre9aa1: 00_gcc-3_1-compile-2
Only in 2.4.19pre9aa2: 61_tux-exports-gcc-3_1-compile-1
Moved later in the patch stage for clarity (suggested by
Christoph Hellwig).
Andrea
next reply other threads:[~2002-05-31 5:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-31 5:18 Andrea Arcangeli [this message]
2002-05-31 13:13 ` 2.4.19pre9aa2 Andrey Nekrasov
2002-05-31 18:40 ` 2.4.19pre9aa2 Andrea Arcangeli
2002-05-31 19:55 ` 2.4.19pre9aa2 Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2002-06-03 12:15 2.4.19pre9aa2 rwhron
2002-06-03 23:59 ` 2.4.19pre9aa2 Andrea Arcangeli
2002-06-04 12:44 2.4.19pre9aa2 rwhron
2002-06-04 13:01 ` 2.4.19pre9aa2 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=20020531051841.GA1172@dualathlon.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