Re: [PATCH] fscrypt: move the call to fscrypt_destroy_keyring() into ->put_super()
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: Eric Biggers <ebiggers@xxxxxxxxxx>
- Subject: Re: [PATCH] fscrypt: move the call to fscrypt_destroy_keyring() into ->put_super()
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
- Date: Tue, 5 Dec 2023 23:16:33 -0800
- In-reply-to: <20231206064430.GA41771@sol.localdomain>
- References: <20231206001325.13676-1-ebiggers@kernel.org> <ZXAW1BREPtCSUz4W@infradead.org> <20231206064430.GA41771@sol.localdomain>
On Tue, Dec 05, 2023 at 10:44:30PM -0800, Eric Biggers wrote:
> There are lots of filesystems that free their ->s_fs_info in ->put_super(). Are
> they all wrong?
Wrong is the wrong word :)
For simple file systems that either don't use block devices, or just
the main one set up by the super.c code using ->put_super is perfectly
fine. Once a file system does something complicated like setting up
their own block devices, or trying to reuse super blocks using custom
rules it basically has to free ->s_fs_info in it's own ->kill_sb
handler. This whole area is a bit messy unfortunately.
[Index of Archives]
[linux Cryptography]
[Asterisk App Development]
[PJ SIP]
[Gnu Gatekeeper]
[IETF Sipping]
[Info Cyrus]
[ALSA User]
[Fedora Linux Users]
[Linux SCTP]
[DCCP]
[Gimp]
[Yosemite News]
[Deep Creek Hot Springs]
[Yosemite Campsites]
[ISDN Cause Codes]