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]
Date:	Mon, 17 Sep 2012 19:37:46 +0900
From:	OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
To:	Jan Kara <jack@...e.cz>
Cc:	Fengguang Wu <fengguang.wu@...el.com>, viro@...iv.linux.org.uk,
	hch@....de, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Fix queueing work if !bdi_cap_writeback_dirty()

Jan Kara <jack@...e.cz> writes:

> On Mon 17-09-12 18:39:05, OGAWA Hirofumi wrote:
>> Jan Kara <jack@...e.cz> writes:
>> 
>> >> I think you know how to solve it though. You can add the periodic flush
>> >> in own task. And you can check bdi->dirty_exceeded in any handlers.
>> >   Sure, you can have your private thread. That is possible but you will
>> > have to duplicate flusher logic and you will still get odd behavior e.g.
>> > when your filesystem is on one partition and another filesystem is on a
>> > different partition of the same disk.
>> 
>> Right. But it is what current FSes are doing more or less.
>   It's not. Page writeback is respected by all filesystems in most cases
> AFAIK. Inode writeback is a different issue but that's not so interesting
> from mm point of view...

Duplicate flusher - many FSes has own task to flush.  Odd behavior in
the case of partition - agree, but I'm not sure why metadata is ok, and
it is not odd behavior.

Sorry, I'm not sure your point in latest comment. You are just saying FS
must flush pages on writepages()?

And if alternative plan is acceptable, maybe I will not have interest to
this anymore.

Thanks.
-- 
OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ