From: Andrea Arcangeli <andrea@suse.de>
To: linux-kernel@vger.kernel.org
Subject: 2.4.19rc1aa2
Date: Mon, 8 Jul 2002 20:41:49 +0200 [thread overview]
Message-ID: <20020708184149.GL8878@dualathlon.random> (raw)
URL:
http://www.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.19rc1aa2.gz
http://www.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.19rc1aa2/
Only in 2.4.19rc1aa2: 000_e100-2.0.30-k1.gz
Only in 2.4.19rc1aa2: 000_e1000-4.2.17-k1.gz
Only in 2.4.19rc1aa1: 07_e100-1.8.38.gz
Only in 2.4.19rc1aa1: 08_e100-includes-1
Only in 2.4.19rc1aa1: 09_e100-compilehack-1
New patch.
Only in 2.4.19rc1aa2: 00_drop-broken-flock-account-1
per-task flock accounting was broken across tasks sharing the same
files. Removed temporarly. This should fix sendmail. If somebody
wanted to bypass the rlimit he needed simply to use fcntl instead
so it's not going to make much difference for 2.4. Fix from
Matthew Wilcox.
Only in 2.4.19rc1aa1: 00_o_direct-open-check-1
Only in 2.4.19rc1aa2: 10_o_direct-open-check-2
Rediffed and changed some check for ->mapping that didn't made much
sense (if either mapping or a_ops are missing we shouldn't let O_DIRECT
to succeed either).
Only in 2.4.19rc1aa2: 00_parport_pc-compile-1
Compile parport_pc from Eyal Lebedinsky.
Only in 2.4.19rc1aa2: 00_poll-speedup-1
This allocates some hundred bytes from the stack to handle most
poll common cases, with a small number of fd. At least the stack hungry
places aren't going to be stacked one on top of the other (i.e. poll
cannot run under follow_link etc..). Patch from Andi Kleen.
Only in 2.4.19rc1aa2: 00_setfl-race-fix-1
Fix race with ->fasync and O_DIRECT fcntl F_SETFL. O_DIRECT
problem noticed by Matthew Wilcox, fasync problem noticed by
Marcus Alanen.
Only in 2.4.19rc1aa2: 10_o1-sched-updates-A4-3
Only in 2.4.19rc1aa1: 20_o1-sched-updates-A4-2
Rediffed before rcu_poll.
Only in 2.4.19rc1aa1: 10_rcu-poll-6
Only in 2.4.19rc1aa2: 20_rcu-poll-7
Fixed potential starvation if idle task was scheduled by the time
force_cpu_reschedule was executed. Also the original o1
force_cpu_reschedule implementation for 2.5 was not correct. This new
corrected one is getting merged soon into the rcu-poll for 2.5 too.
Only in 2.4.19rc1aa2: 50_uml-patch-2.4.18-36.gz
New update from Jeff.
Only in 2.4.19rc1aa1: 90_acpi-2.5.24-1.gz
Dropped, my laptop had an hardware problem so I'm not going to test it
soon. Also it needed the backport of the pci-irq enable callbacks, it
was very near to be finished. If my future laptop will deadlock at boot
again with the 2.4 ACPI I will be willing to finish it :). If somebody
wants to contine on its own I've an unreleased -2 revision that was a
bit more uptodate than the above one too.
Only in 2.4.19rc1aa1: 90_init-survive-threaded-race-3
Only in 2.4.19rc1aa2: 90_init-survive-threaded-race-4
Fixed merging error, good spotting by by Sami Farin.
Only in 2.4.19rc1aa1: 93_NUMAQ-3
Only in 2.4.19rc1aa2: 93_NUMAQ-4
Rediffed.
Only in 2.4.19rc1aa1: 94_numaq-tsc-2
Only in 2.4.19rc1aa2: 94_numaq-tsc-3
s/==/=/. Apparently menuconfig understand the C like "==" syntax too,
because it worked as expected until somebody tried xconfig. Fix from
J.A. Magallon. (I use menuconfig so I could hardly notice it :)
Andrea
next reply other threads:[~2002-07-08 18:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-08 18:41 Andrea Arcangeli [this message]
2002-07-10 10:20 ` 2.4.19rc1aa2 Andrey Nekrasov
2002-07-10 10:47 ` 2.4.19rc1aa2 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=20020708184149.GL8878@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