From: Alan Cox <alan@redhat.com>
To: linux-kernel@vger.kernel.org
Subject: Linux 2.2.22rc2
Date: Fri, 30 Aug 2002 10:55:54 -0400 (EDT) [thread overview]
Message-ID: <200208301455.g7UEtsS16348@devserv.devel.redhat.com> (raw)
This is going straight to rc1 because it contains a lot of security fixes
for local security problems found by Silvio's audit Solar Designer and
a couple of other folks. The other stuff is minor and is the entire 2.2
pending queue anyway.
Special thanks go to Openwall who did pretty much all of the security
backporting work. This is mostly their kernel update not mine.
2.2.22-rc2
o Fix isofs over loopback problems (Balazs Takacs)
o Backport 2.4 shutdown/reset SIGIO from 2.4 (Julian Anastasov)
o Fix error reporting in OOM cases (Julian Anastasov)
o List a 2.2 maintainer in MAINTAINERS (Keith Owens)
o Set atime on AF_UNIX sockets (Solar Designer)
o Restore SPARC MD boot configuration (Tomas Szepe)
o Multiple further sign/overflow fixes (Solar Designer)
o Fix ov511 'vfree in interrupt' (Mark McClelland)
2.2.22-rc1
o Backport 2.4 neighbour sending fix (Chris Friesen)
o Fix a sign handling slackness in apm (Silvio Cesare)
o Fix a sign handling error in rio500 (Silvio Cesare)
o Indent depca ready for cleanups (me)
o Update VIA C3 recognition (Diego Rodriguez)
o Fix a sysctl handling bug (MIYOSHI Kazuto)
o Fix a netlink error handling bug in ipfw (Alexander Atanasov)
o 3ware IDE RAID update (Adam Radford)
o Note ioctl clash on 0x5402 (Pavel Machek)
o Typo fix (Dan Aloni)
o Update Riley's contact info (Riley Williams)
o Alpha ptrace fixes (Solar Designer)
o Multiple security fix backports (Solar Designer)
next reply other threads:[~2002-08-30 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-30 14:55 Alan Cox [this message]
2002-08-30 17:54 ` Linux 2.2.22rc2 Krzysiek Taraszka
2002-08-31 23:32 ` Milton Miller
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=200208301455.g7UEtsS16348@devserv.devel.redhat.com \
--to=alan@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 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.