<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/fs/gfs2/bmap.c, branch linux-5.19.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.19.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.19.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2022-05-13T19:59:18Z</updated>
<entry>
<title>gfs2: Fix filesystem block deallocation for short writes</title>
<updated>2022-05-13T19:59:18Z</updated>
<author>
<name>Andreas Gruenbacher</name>
</author>
<published>2022-04-14T15:52:39Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d031a8866e709c9d1ee5537a321b6192b4d2dc5b'/>
<id>urn:sha1:d031a8866e709c9d1ee5537a321b6192b4d2dc5b</id>
<content type='text'>
When a write cannot be carried out in full, gfs2_iomap_end() releases
blocks that have been allocated for this write but haven't been used.

To compute the end of the allocation, gfs2_iomap_end() incorrectly
rounded the end of the attempted write down to the next block boundary
to arrive at the end of the allocation.  It would have to round up, but
the end of the allocation is also available as iomap-&gt;offset +
iomap-&gt;length, so just use that instead.

In addition, use round_up() for computing the start of the unused range.

Fixes: 64bc06bb32ee ("gfs2: iomap buffered write support")
Signed-off-by: Andreas Gruenbacher &lt;agruenba@redhat.com&gt;
</content>
</entry>
<entry>
<title>gfs2: Remove return value for gfs2_indirect_init</title>
<updated>2022-03-03T14:59:21Z</updated>
<author>
<name>Bob Peterson</name>
</author>
<published>2022-03-03T12:32:43Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b2963932346f0631c5145f656a22d4237f0956fa'/>
<id>urn:sha1:b2963932346f0631c5145f656a22d4237f0956fa</id>
<content type='text'>
The return value from function gfs2_indirect_init is never used, so
remove it.

Signed-off-by: Bob Peterson &lt;rpeterso@redhat.com&gt;
Signed-off-by: Andreas Gruenbacher &lt;agruenba@redhat.com&gt;
</content>
</entry>
<entry>
<title>gfs2: gfs2_setattr_size error path fix</title>
<updated>2022-02-15T14:01:40Z</updated>
<author>
<name>Andreas Gruenbacher</name>
</author>
<published>2021-12-10T13:43:36Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=7336905a89f19173bf9301cd50a24421162f417c'/>
<id>urn:sha1:7336905a89f19173bf9301cd50a24421162f417c</id>
<content type='text'>
When gfs2_setattr_size() fails, it calls gfs2_rs_delete(ip, NULL) to get
rid of any reservations the inode may have.  Instead, it should pass in
the inode's write count as the second parameter to allow
gfs2_rs_delete() to figure out if the inode has any writers left.

In a next step, there are two instances of gfs2_rs_delete(ip, NULL) left
where we know that there can be no other users of the inode.  Replace
those with gfs2_rs_deltree(&amp;ip-&gt;i_res) to avoid the unnecessary write
count check.

With that, gfs2_rs_delete() is only called with the inode's actual write
count, so get rid of the second parameter.

Fixes: a097dc7e24cb ("GFS2: Make rgrp reservations part of the gfs2_inode structure")
Signed-off-by: Andreas Gruenbacher &lt;agruenba@redhat.com&gt;
</content>
</entry>
<entry>
<title>gfs2: Fix length of holes reported at end-of-file</title>
<updated>2021-11-06T09:25:45Z</updated>
<author>
<name>Andreas Gruenbacher</name>
</author>
<published>2021-11-05T23:18:56Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f3506eee81d1f700d9ee2d2f4a88fddb669ec032'/>
<id>urn:sha1:f3506eee81d1f700d9ee2d2f4a88fddb669ec032</id>
<content type='text'>
Fix the length of holes reported at the end of a file: the length is
relative to the beginning of the extent, not the seek position which is
rounded down to the filesystem block size.

This bug went unnoticed for some time, but is now caught by the
following assertion in iomap_iter_done():

  WARN_ON_ONCE(iter-&gt;iomap.offset + iter-&gt;iomap.length &lt;= iter-&gt;pos)

Signed-off-by: Andreas Gruenbacher &lt;agruenba@redhat.com&gt;
</content>
</entry>
<entry>
<title>gfs2: Move the inode glock locking to gfs2_file_buffered_write</title>
<updated>2021-10-20T17:33:09Z</updated>
<author>
<name>Andreas Gruenbacher</name>
</author>
<published>2021-08-11T19:50:14Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b924bdab7445946e2ed364a0e6e249d36f1f1158'/>
<id>urn:sha1:b924bdab7445946e2ed364a0e6e249d36f1f1158</id>
<content type='text'>
So far, for buffered writes, we were taking the inode glock in
gfs2_iomap_begin and dropping it in gfs2_iomap_end with the intention of
not holding the inode glock while iomap_write_actor faults in user
pages.  It turns out that iomap_write_actor is called inside iomap_begin
... iomap_end, so the user pages were still faulted in while holding the
inode glock and the locking code in iomap_begin / iomap_end was
completely pointless.

Move the locking into gfs2_file_buffered_write instead.  We'll take care
of the potential deadlocks due to faulting in user pages while holding a
glock in a subsequent patch.

Signed-off-by: Andreas Gruenbacher &lt;agruenba@redhat.com&gt;
</content>
</entry>
<entry>
<title>iomap: remove the iomap arguments to -&gt;page_{prepare,done}</title>
<updated>2021-08-17T04:26:33Z</updated>
<author>
<name>Christoph Hellwig</name>
</author>
<published>2021-08-11T01:33:03Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1d25d0aecfcd480b1a997a709c1b37e56ddc3c38'/>
<id>urn:sha1:1d25d0aecfcd480b1a997a709c1b37e56ddc3c38</id>
<content type='text'>
These aren't actually used by the only instance implementing the methods.

Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Reviewed-by: Darrick J. Wong &lt;djwong@kernel.org&gt;
Signed-off-by: Darrick J. Wong &lt;djwong@kernel.org&gt;
</content>
</entry>
<entry>
<title>gfs2: Clean up gfs2_unstuff_dinode</title>
<updated>2021-06-29T08:56:51Z</updated>
<author>
<name>Andreas Gruenbacher</name>
</author>
<published>2021-06-17T19:36:50Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=7a607a41cdc6c6f27b8e234cb44ce57070513dac'/>
<id>urn:sha1:7a607a41cdc6c6f27b8e234cb44ce57070513dac</id>
<content type='text'>
Split __gfs2_unstuff_inode off from gfs2_unstuff_dinode and clean up the
code a little.  All remaining callers now pass NULL as the page argument
of gfs2_unstuff_dinode, so remove that argument.

Signed-off-by: Andreas Gruenbacher &lt;agruenba@redhat.com&gt;
</content>
</entry>
<entry>
<title>gfs2: Fix a number of kernel-doc warnings</title>
<updated>2021-04-09T20:14:13Z</updated>
<author>
<name>Lee Jones</name>
</author>
<published>2021-03-30T16:44:29Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c551f66c5dfefd00687f7567183fec6889ba46a3'/>
<id>urn:sha1:c551f66c5dfefd00687f7567183fec6889ba46a3</id>
<content type='text'>
Building the kernel with W=1 results in a number of kernel-doc warnings
like incorrect function names and parameter descriptions.  Fix those,
mostly by adding missing parameter descriptions, removing left-over
descriptions, and demoting some less important kernel-doc comments into
regular comments.

Originally proposed by Lee Jones; improved and combined into a single
patch by Andreas.

Signed-off-by: Lee Jones &lt;lee.jones@linaro.org&gt;
Signed-off-by: Andreas Gruenbacher &lt;agruenba@redhat.com&gt;
</content>
</entry>
<entry>
<title>gfs2: Turn gfs2_meta_indirect_buffer into gfs2_meta_buffer</title>
<updated>2021-04-03T19:38:12Z</updated>
<author>
<name>Andreas Gruenbacher</name>
</author>
<published>2021-03-25T17:48:49Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6d8da302aedf9ff32c1579cbf91705a78538cb9e'/>
<id>urn:sha1:6d8da302aedf9ff32c1579cbf91705a78538cb9e</id>
<content type='text'>
Instead of only supporting GFS2_METATYPE_DI and GFS2_METATYPE_IN blocks,
make the block type a parameter of gfs2_meta_indirect_buffer and rename
the function to gfs2_meta_buffer.

Signed-off-by: Andreas Gruenbacher &lt;agruenba@redhat.com&gt;
</content>
</entry>
<entry>
<title>gfs2: Replace gfs2_lblk_to_dblk with gfs2_get_extent</title>
<updated>2021-04-03T19:38:12Z</updated>
<author>
<name>Andreas Gruenbacher</name>
</author>
<published>2021-03-27T21:05:14Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=152f58c9af21abf913699e671b425fd38447b170'/>
<id>urn:sha1:152f58c9af21abf913699e671b425fd38447b170</id>
<content type='text'>
We don't need two very similar functions for mapping logical blocks to physical
blocks.

Signed-off-by: Andreas Gruenbacher &lt;agruenba@redhat.com&gt;
</content>
</entry>
</feed>
