On Wed 28-07-21 09:57:01, Steven Whitehouse wrote: > On Wed, 2021-07-28 at 08:50 +0200, Andreas Gruenbacher wrote: > > On Tue, Jul 13, 2021 at 9:34 PM Bob Peterson <rpeterso@xxxxxxxxxx> > > wrote: > > > On 7/13/21 1:26 PM, Steven Whitehouse wrote: > > > > > > Hi, > > > > > > On Tue, 2021-07-13 at 13:09 -0500, Bob Peterson wrote: > > > > > > Before this patch, gfs2 kept its own address space for rgrps, but > > > this > > > caused a lockdep problem because vfs assumes a 1:1 relationship > > > between > > > address spaces and their inode. One problematic area is this: > > > > > > I don't think that is the case. The reason that the address space > > > is a > > > separate structure in the first place is to allow them to exist > > > without > > > an inode. Maybe that has changed, but we should see why that is, in > > > that case rather than just making this change immediately. > > > > > > I can't see any reason why if we have to have an inode here that it > > > needs to be hashed... what would need to look it up via the hashes? > > > > > > Steve. > > > > > > Hi, > > > > > > The actual use case, which is easily demonstrated with lockdep, is > > > given > > > in the patch text shortly after where you placed your comment. This > > > goes > > > back to this discussion from April 2018: > > > > > > https://listman.redhat.com/archives/cluster-devel/2018-April/msg00017.html > > > > > > in which Jan Kara pointed out that: > > > > > > "The problem is we really do expect mapping->host->i_mapping == > > > mapping as > > > we pass mapping and inode interchangeably in the mm code. The > > > address_space > > > and inodes are separate structures because you can have many inodes > > > pointing to one address space (block devices). However it is not > > > allowed > > > for several address_spaces to point to one inode!" > > > > This is fundamentally at adds with how we manage inodes: we have > > inode->i_mapping which is the logical address space of the inode, and > > we have gfs2_glock2aspace(GFS2_I(inode)->i_gl) which is the metadata > > address space of the inode. The most important function of the > > metadata address space is to remove the inode's metadata from memory > > by truncating the metadata address space (inode_go_inval). We need > > that when moving an inode to another node. I don't have the faintest > > idea how we could otherwise achieve that in a somewhat efficient way. > > > > Thanks, > > Andreas > > > > In addition, I'm fairly sure also that we were told to use this > solution (i.e. a separate address space) back in the day because it was > expected that they didn't have a 1:1 relationship with inodes. I don't > think we'd have used that solution otherwise. I've not had enough time > to go digging back in my email to check, but it might be worth looking > to see when we introduced the use of the second address space (removing > a whole additional inode structure) and any discussions around that > change, AFAIK in last 20 years it has never been the case that multiple address_space structs for an inode would be handled by the VFS/MM code properly. There can be multiple 'struct inode' for one 'struct address_space'. That is handled just fine and is being used. The trouble is that once you allow multiple address_space structs pointing to one struct inode, you have some hard questions to answer (at least for VFS) - e.g. you get a request to writeback the inode, how you do that when you have multiple address spaces? Writeback them all? And how do you iterate them? And there are similar questions regarding how to determine inode's dirtiness or whether some inode's page is under writeback. Tied to that are locking questions where inode->i_mapping->i_pages->xa_lock lock is used to protect some of the inode state transitions. But when you have multiple address spaces pointing to the inode it is not clear which of these many locks would be protecting it (and the warning syzbot is hitting exactly says that these state transitions are not properly serialized). Of course all this can be decided and implemented but it is not a trivial task there needs to be good motivation for the added complexity in the code used by everybody. And AFAIU GFS2 even doesn't strictly need it. It uses a very limited subset of functions that can operate on address_space for these special address spaces. Andreas mentions you use metadata address_space for tracking and evicting cached metadata associated with the inode. Quickly checking the code, another heavy use seems to be metadata dirtiness tracking and writeback. I'd note that other filesystems traditionally use mapping->private_list for exactly these purposes (through helpers like mark_buffer_dirty_inode, sync_mapping_buffers, etc.). Any reason why you don't use these? Honza -- Jan Kara <jack@xxxxxxxx> SUSE Labs, CR
