linux-ext4 - Re: [PATCH] default max mount count to unused

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] [thread-next>] [day] [month] [year] [list]

Message-id: <CC1F3E6D-A4B3-42C5-A71C-259DBA73CC4C@sun.com>
Date:	Fri, 22 Jan 2010 11:35:01 -0700
From:	Andreas Dilger <adilger@....com>
To:	Eric Sandeen <sandeen@...hat.com>
Cc:	tytso@....edu, ext4 development <linux-ext4@...r.kernel.org>,
	Bill Nottingham <notting@...hat.com>,
	Alasdair G Kergon <agk@...hat.com>,
	LVM Mailing List <linux-lvm@...hat.com>
Subject: Re: [PATCH] default max mount count to unused

On 2010-01-22, at 10:42, Eric Sandeen wrote:
> tytso@....edu wrote:
>> On Thu, Jan 21, 2010 at 05:22:55PM -0700, Andreas Dilger wrote:
>>> Alasdair, any chance you can include this script into the LVM  
>>> package?
>>>
>>> Ted, this should really be added to e2fsprogs, and the e2croncheck
>>> script removed.  The existing e2croncheck script is broken in a
>>> number of ways (e.g. the force check timestamp 19000101 is invalid,
>>> the email reporting doesn't work because "$RPT-EMAIL" is never set)
>>> and is less functional in other ways (it doesn't remove stale
>>> snapshots in case of an interrupted script, it doesn't check
>>> multiple LVs, etc).
>>
>> Sure, I'd be happy to include this to e2fsprogs.  I'm not sure which
>> distro package should be installing it, but we can leave that up to
>> the distro maintainers.
>
> Last time around, we all seemed to think it should be in the lvm
> tools (though I don't remember exactly why - probably because it's
> really not ext*-specific at all)

Sure, but since there is only a semi-functional version in e2fsprogs  
we may as well replace it with a working one.

> It got forwarded to the LVM list, agk asked if anyone wanted to
> clean it up & take ownership of it, and that was the end.  :(


I guess I wasn't on that email.  I've gone ahead and fixed up the  
current script to be functional (including testing of failed-fsck  
email, force-fsck on next boot, stale snapshot cleanup, etc) so you  
may as well chalk me up as the maintainer for now.

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.

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