All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andres Salomon <dilinger@debian.org>
To: linux-kernel@vger.kernel.org
Subject: 2.6.10-as7
Date: Fri, 11 Mar 2005 00:18:59 -0500	[thread overview]
Message-ID: <1110518340.8577.9.camel@localhost> (raw)

[-- Attachment #1: Type: text/plain, Size: 2785 bytes --]

Hi,

2.6.10-as is now in purely maintenance mode; that is, I'll only include
security fixes or quick things that people send me (that don't require
much effort on my part :).  This includes the security fix from
2.6.11.2.  I'll have 2.6.11-as1 soon, after I sync up w/ Debian stuff
and go through about 800 more changesets.  We'll see where 2.6.x.y goes
from there; if feeding patches is easy, then there won't be much need
for -as; otherwise, I'll continue doing it as a vendor base (at least
one person who does vendor kernels has expressed the opinion that they'd
prefer 2.6.x.y to be a bit more liberal than it currently is).

Also, note the email address; I'm trying to phase out usage of my
voxel.net address, as I no longer work there.


The -as tree is intended to include only security and bugfixes, from
various sources.  I do not include hardware driver updates
(specifically, anything that changes how the hardware registers
themselves are probed/poked), large subsystem updates, cleanups, and so
on; only fixes that will not contain regressions.  The hope is that
vendors/distributors can use this tree as a base for their kernels.  It
is also what I'd want a 2.6.x.y tree to have.

The kernel patches can be grabbed from here:
http://www.acm.cs.rpi.edu/~dilinger/patches/2.6.10/as7/

86f79bd2e50963829da3c0456804df0f  ChangeLog
e852090bafa5ea4ff7c6b922d33ec1e7  linux-2.6.10-as7.tar.gz
8ca1ac89c1eac2111f146cc21d6193c2  patch-2.6.10-as7.gz

Changes from 2.6.10-as6:

2005-03-10 21:51:49 GMT	Andres Salomon <dilinger@voxel.net>	patch-155

    Summary:
      tag 2.6.10-as7
    Revision:
      linux--dilinger--0--patch-155

    
    

    modified files:
     000-extraversion.patch


2005-03-10 21:50:21 GMT	Andres Salomon <dilinger@voxel.net>	patch-154

    Summary:
      144-sys_epoll_wait_int_overflow.patch
    Revision:
      linux--dilinger--0--patch-154

    [SECURITY] sys_epoll_wait contains an integer overflow; see
    http://seclists.org/lists/fulldisclosure/2005/Mar/0293.html for
additional
    details.
    
    

    new files:
     .arch-ids/144-sys_epoll_wait_int_overflow.patch.id
     144-sys_epoll_wait_int_overflow.patch


2005-03-10 21:46:21 GMT	Andres Salomon <dilinger@voxel.net>	patch-153

    Summary:
      143-sysfs_write_file_signedness_problem.patch
    Revision:
      linux--dilinger--0--patch-153

    [SYSFS] sysfs_write_file assigns the result of fill_write_buffer
(which is
    signed and returns negative upon error) to an unsigned int.
Clearly, bad
    and wrong..
    

    new files:
     .arch-ids/143-sysfs_write_file_signedness_problem.patch.id
     143-sysfs_write_file_signedness_problem.patch


-- 
Andres Salomon <dilinger@debian.org>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

                 reply	other threads:[~2005-03-11  5:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1110518340.8577.9.camel@localhost \
    --to=dilinger@debian.org \
    --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.