Al Viro 4a378d8a0d
gfs2: be careful with inode refresh ...
1) gfs2_dinode_in() should *not* touch ->i_rdev on live inodes; even
"zero and immediately reread the same value from dinode" is broken -
have it overlap with ->release() of char device and you can get all
kinds of bogus behaviour.
2) mismatch on inode type on live inodes should be treated as fs
corruption rather than blindly setting ->i_mode.
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk >
2021-03-12 22:15:19 -05:00
2021-01-24 14:27:20 +01:00
2021-01-24 14:27:20 +01:00
2020-11-12 18:55:20 +01:00
2019-07-03 14:45:18 +02:00
2021-02-23 18:54:22 +01:00
2020-10-14 23:54:42 +02:00
2019-09-03 09:42:41 +02:00
2020-06-02 10:59:11 -07:00
2019-09-04 20:22:17 +02:00
2020-06-05 20:19:21 +02:00
2021-02-23 14:04:04 -08:00
2019-06-05 17:37:12 +02:00
2021-02-17 19:30:28 +01:00
2021-02-17 19:30:28 +01:00
2021-03-12 22:15:19 -05:00
2020-10-29 22:16:46 +01:00
2021-02-23 18:54:22 +01:00
2021-02-27 08:07:12 -08:00
2021-01-24 14:27:20 +01:00
2019-05-21 10:50:46 +02:00
2021-02-05 20:08:47 +01:00
2021-02-23 19:01:42 +01:00
2021-02-22 21:16:23 +01:00
2021-02-23 18:54:22 +01:00
2021-02-23 18:54:22 +01:00
2021-01-22 12:19:17 -05:00
2017-11-02 11:10:55 +01:00
2020-10-15 14:29:03 +02:00
2020-10-15 14:29:03 +02:00
2021-02-23 18:54:22 +01:00
2020-08-23 17:36:59 -05:00
2020-05-08 18:47:58 +02:00
2021-02-05 18:18:57 +01:00
2019-06-05 17:37:12 +02:00
2021-02-17 19:30:28 +01:00
2021-02-17 19:30:28 +01:00
2021-02-23 14:04:04 -08:00
2021-02-08 13:01:24 +01:00
2020-10-14 23:54:43 +02:00
2019-06-05 17:37:12 +02:00
2021-02-17 19:30:26 +01:00
2021-02-22 21:16:23 +01:00
2021-02-23 18:54:22 +01:00
2021-01-25 08:08:44 -05:00
2020-12-23 00:54:13 +01:00
2021-02-23 14:04:04 -08:00
2019-06-05 17:37:12 +02:00
4a378d8a0d