linux-ext4 - question on sync()

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

Message-ID: <1270052957.26517.24.camel@subu>
Date:	Wed, 31 Mar 2010 19:29:17 +0300
From:	Surbhi Palande <Surbhi.Palande@...onical.com>
To:	ext4 development <linux-ext4@...r.kernel.org>
Subject: question on sync()

Hie,

While looking at fs/sync.c :: sync(), I found out that:

1) sync() first calls wakeup_flusher_threads() which ultimately calls
bdi_alloc_queue_work() with WB_SYNC_NONE for every bdi in the bdi_list.

2) sync() immediate then calls sync_filesystems(0) which does the same
thing - it calls writeback_inodes_sb() which finally calls
bdi_alloc_queue_work() with WB_SYNC_NONE for every bdi corresponding to
every filesystem.

If it is possible, then I wanted to know why there are effectively two
calls which ultimately call bdi_alloc_queue_work() with WB_SYNC_NONE
twice?

Thanks!

Warm Regards,
Surbhi.

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