Messages in this thread |  | | From | "Theodore Ts'o" <> | | Subject | Re: [PATCH v4 0/4] jbd2/ext4/ocfs2: lockless jinode dirty range | | Date | Fri, 10 Apr 2026 11:18:37 -0400 |
| |
On Fri, 06 Mar 2026 16:56:38 +0800, Li Chen wrote: > This series makes the jbd2_inode dirty range tracking safe for lockless > reads in jbd2 and filesystem callbacks used by ext4 and ocfs2. > > Some paths access jinode fields without holding journal->j_list_lock > (e.g. fast commit helpers and ordered truncate helpers). v1 used READ_ONCE() > on i_dirty_start/end, but Matthew pointed out that loff_t can be torn on > 32-bit platforms, and Jan suggested storing the dirty range in PAGE_SIZE > units as pgoff_t. > > [...]
Applied, thanks!
[1/4] jbd2: add jinode dirty range accessors commit: 5267f6ef49cb5fba426f2d286817b1355fde31da [2/4] ext4: use jbd2 jinode dirty range accessor commit: 660d23669982202c99798658e2a15ccdd001f82b [3/4] ocfs2: use jbd2 jinode dirty range accessor commit: be81084e032c2d74f51173e30f687ce13476cb73 [4/4] jbd2: store jinode dirty range in PAGE_SIZE units commit: 4edafa81a1d6020272d0c6eb68faeb810dd083c1
Best regards, -- Theodore Ts'o <tytso@mit.edu>
|  |