public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@openedhand.com>
To: akpm <akpm@linux-foundation.org>, LKML <linux-kernel@vger.kernel.org>
Cc: Hugh Dickins <hugh@veritas.com>,
	Nick Piggin <nickpiggin@yahoo.com.au>,
	David Woodhouse <dwmw2@infradead.org>,
	Nitin Gupta <nitingupta910@gmail.com>
Subject: [PATCH -mm 0/5] LZO and swap write failure patches for -mm
Date: Mon, 04 Jun 2007 16:36:18 +0100	[thread overview]
Message-ID: <1180971378.6313.72.camel@localhost.localdomain> (raw)

The following series contains several patches which I'm hoping could see
some testing in -mm. They're all been seen before at some point. The LZO
ones are important due to the dependent patches, the swap write failure
ones have just fallen off the radar.

LZO
===

We've seen a lot of activity in attempts to rewrite this in a
CodingStyle compatible 'clean' kernel style. The last update I read has
convinced me this is not ready for kernel usage at this time,
particularly due to the memory alignment issues.

I would like to see a version merged in the next merge window so other
patches depending on it can follow. If a better LZO implementation is
eventually sorted out, it can replace the lzo core in due course, the
API will be interchangeable. 

I've trimmed my patch down to only contain the "safe" decompression
function, pruned the headers a little further and merged in the cleanup
patch I submitted to -mm previously. I've also included an updated
version of the patch to make resier4 use the shared LZO functions
(fixing a security hole in the process).

Swap Write Failures
===================

Currently write failures to swap are handled badly and these patches
allow more graceful handling. 

These have been looked at before by various people and have no known
issues I'm aware of. I don't think Hugh has time to review these so if
anyone else familiar with the appropriate code area could look over
them, I'd appreciate it.

-- 
Richard







             reply	other threads:[~2007-06-04 15:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-04 15:36 Richard Purdie [this message]
2007-06-04 16:14 ` [PATCH -mm 0/5] LZO and swap write failure patches for -mm Daniel Hazelton
2007-06-04 16:52   ` Richard Purdie
2007-06-04 17:37     ` Daniel Hazelton
2007-06-04 18:34       ` Nitin Gupta
2007-06-04 20:45       ` Richard Purdie
2007-06-04 22:13         ` Daniel Hazelton
2007-06-04 18:26     ` Nitin Gupta
2007-06-04 20:06       ` Adrian Bunk
2007-06-05  5:30         ` Nitin Gupta
2007-06-05  5:50           ` Andrew Morton
2007-06-05  8:56             ` Richard Purdie
2007-06-04 20:58       ` Richard Purdie
2007-06-05  6:15         ` Christoph Hellwig

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=1180971378.6313.72.camel@localhost.localdomain \
    --to=rpurdie@openedhand.com \
    --cc=akpm@linux-foundation.org \
    --cc=dwmw2@infradead.org \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=nitingupta910@gmail.com \
    /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