linux-kernel - Re: [PATCH 0/4] Improve swap page error handling

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <1168473175.14261.23.camel@localhost.localdomain>
Date:	Wed, 10 Jan 2007 23:52:55 +0000
From:	Richard Purdie <richard@...nedhand.com>
To:	Nick Piggin <nickpiggin@...oo.com.au>
Cc:	Hugh Dickins <hugh@...itas.com>,
	kernel list <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...l.org>
Subject: Re: [PATCH 0/4] Improve swap page error handling

On Thu, 2007-01-11 at 09:32 +1100, Nick Piggin wrote:
> Richard Purdie wrote: 
> > I think you were cc'd on some of it but you never commented. Anyhow,
> > I've reworked this patch series based on your comments. The hints were
> > appreciated, thanks. This was the way I'd originally hoped to be able to
> > work things, I just couldn't find the right way to do it.
> 
> IMO it seems a bit complex for so small a benefit. Last time I was
> working on this, I thought it would be almost as good to do something
> simple like stop trying to write out the page if PG_error is set (and
> clear that bit in delete_from_swap_cache or try_to_unusesomewhere).
> This way the admin could swapoff and scan the swap device at some
> point.

FWIW, the patches have got a lot less invasive and I was pleased with
the way the last set I posted worked out. 

1/4 is a lot of noise adding the page parameter to swap_free but doesn't
actually change much. 
2/4 is the guts of the solution in the form of two new functions. 
3/4 just hooks it in. 
4/4 is an optional cleanup.

I guess the key point for me is that the lack of proper handling of this
was bringing one of my systems to its knees due to IO loops before these
patches. Yes, there are ways to minimise the impact but why not fix it
properly? This proposal is certainly nowhere near as invasive as the
previous ones and since its got this far...

> > You can't proceed to do that until you're able to identify the bad pages
> > so this would be a necessary first step towards that, yes.
> 
> Agreed here, FWIW. I think that might be just as well done in
> userspace?

Maybe, I haven't made my mind up about that yet. I'd have to see how the
code looked I guess.

Cheers,

Richard

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/