diff options
| author | Christoph Hellwig <hch@lst.de> | 2023-08-09 15:05:42 -0700 |
|---|---|---|
| committer | Christian Brauner <brauner@kernel.org> | 2023-08-10 10:34:55 +0200 |
| commit | 4abc9a43d99ccab7bd71742b86d2f48d8be798c3 (patch) | |
| tree | baff178dd58ff1e463d43536f9a4be6de022c4aa /tools/perf/scripts/python/bin/stackcollapse-report | |
| parent | exfat: don't RCU-free the sbi (diff) | |
| download | linux-4abc9a43d99ccab7bd71742b86d2f48d8be798c3.tar.gz linux-4abc9a43d99ccab7bd71742b86d2f48d8be798c3.zip | |
exfat: free the sbi and iocharset in ->kill_sb
As a rule of thumb everything allocated to the fs_context and moved into
the super_block should be freed by ->kill_sb so that the teardown
handling doesn't need to be duplicated between the fill_super error
path and put_super. Implement an exfat-specific kill_sb method to do
that and share the code with the mount contex free helper for the
mount error handling case.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Message-Id: <20230809220545.1308228-11-hch@lst.de>
Signed-off-by: Christian Brauner <brauner@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions