linux-kernel - Re: [PATCH] mm: strictlimit feature -v3

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: <CAJfpegtNRxacv3Lw0XOK7zuQJB0_NttNzw7p3fQE+J7T_dZHyQ@mail.gmail.com>
Date:	Mon, 15 Jul 2013 12:35:23 +0200
From:	Miklos Szeredi <miklos@...redi.hu>
To:	Maxim Patlasov <MPatlasov@...allels.com>
Cc:	Jan Kara <jack@...e.cz>, Andrew Morton <akpm@...ux-foundation.org>,
	riel@...hat.com, Kirill Korotaev <dev@...allels.com>,
	fuse-devel <fuse-devel@...ts.sourceforge.net>,
	Brian Foster <bfoster@...hat.com>,
	Pavel Emelianov <xemul@...allels.com>,
	Kernel Mailing List <linux-kernel@...r.kernel.org>,
	James Bottomley <jbottomley@...allels.com>, linux-mm@...ck.org,
	Al Viro <viro@...iv.linux.org.uk>,
	Linux-Fsdevel <linux-fsdevel@...r.kernel.org>,
	fengguang.wu@...el.com, devel@...nvz.org,
	Mel Gorman <mgorman@...e.de>
Subject: Re: [PATCH] mm: strictlimit feature -v3

On Thu, Jul 11, 2013 at 11:50 PM, Maxim Patlasov
<MPatlasov@...allels.com> wrote:
> On Thu, Jul 11, 2013 at 10:51 PM, Jan Kara <jack@...e.cz> wrote:

[snipped]

>> If I'm right in the above, then removing NR_WRITEBACK_TEMP would be a nice
>> followup patch.
>
> I'd rather introduce the notion of trusted fuse filesystem. If system
> administrator believe given fuse fs "trusted", it works w/o
> strictlimit, but fuse daemon is supposed to notify the kernel
> explicitly about threads related to processing writeback. The kernel
> would raise a per-task flag for those threads. And, calculating
> nr_dirty in balance_dirty_pages, we'd add NR_WRITEBACK_TEMP for all,
> excepting tasks with the flag set.  This is very simple and will work
> perfectly.

Yes, doing a trusted mode for fuse is a good idea, I think.  And it
should have a new filesystem type (can't think of a good name though,
"fusetrusted" is a bit too long).

Thanks,
Miklos
--
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/