linux-ext4 - Re: [PATCH v2 0/2] ext4: Add pollable sysfs entry for block threshold events

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 for Android: free password hash cracker in your pocket

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

Message-id: <550945D5.4060805@samsung.com>
Date:	Wed, 18 Mar 2015 10:31:01 +0100
From:	Beata Michalska <b.michalska@...sung.com>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	lczerner@...hat.com, adilger.kernel@...ger.ca, tytso@....edu,
	linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org,
	kyungmin.park@...sung.com
Subject: Re: [PATCH v2 0/2] ext4: Add pollable sysfs entry for block threshold
 events

On 03/16/2015 02:28 PM, Christoph Hellwig wrote:
> Between this and the recent tmpfs discussion I really think this
> needs to be done in a generic way.  Given that the quota noticiations
> already use netlink general space notifications seem like a very
> sensible extension for them.
> 

First of all, apologies for late response.

I do agree that having a generic solution is the perfect one
though non-trivial. If I understood You correctly, You would
like to have quota being extended to cover the case in subject;
smth similar to xfs project quota and its pqnoenforce mount
option, as this would require disabling enforcing both:
soft and hard limits ?

We could also consider going back to already mentioned,
in another thread, the netlink notification interface proposal,
though this still leaves the problem on how to setup the thresholds
(as it covers only the ENOSPC case).

BR
Beata

--
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