2010-10-20 00:17:58 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-07-13 15:58:28 -04:00
|
|
|
|
2011-07-01 14:23:34 -04:00
|
|
|
|
2016-09-15 14:40:49 -04:00
|
|
|
|
2010-10-20 00:18:02 -04:00
|
|
|
|
2010-10-20 00:17:58 -04:00
|
|
|
|
2011-03-01 01:34:16 +00:00
|
|
|
|
2013-08-14 15:31:28 -04:00
|
|
|
|
2015-01-24 13:54:37 -05:00
|
|
|
|
2015-06-23 19:51:57 +08:00
|
|
|
|
2016-09-21 15:24:26 -04:00
|
|
|
|
2010-10-20 00:17:58 -04:00
|
|
|
|
|
|
|
|
|
2012-09-18 17:01:12 -04:00
|
|
|
|
2010-10-20 00:17:58 -04:00
|
|
|
|
2010-10-20 00:17:59 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-01-26 23:12:11 -05:00
|
|
|
|
2016-10-12 19:50:54 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-11-30 12:32:55 -05:00
|
|
|
|
|
|
|
|
|
2024-06-13 01:00:55 -04:00
|
|
|
|
2014-09-06 00:53:25 +08:00
|
|
|
|
2010-10-20 00:17:59 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-20 00:17:58 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-20 00:17:59 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-06-15 13:02:58 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-20 00:17:59 -04:00
|
|
|
|
|
|
|
|
|
2010-10-20 00:17:58 -04:00
|
|
|
|
|
|
|
|
|
2022-03-28 08:36:34 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-20 00:17:58 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-07-30 20:52:36 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-06-14 13:08:38 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-20 00:17:59 -04:00
|
|
|
|
2011-07-30 20:52:36 -04:00
|
|
|
|
2010-10-20 00:17:58 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-09-15 14:40:49 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-20 00:17:58 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-08-10 15:58:24 -04:00
|
|
|
|
2010-10-20 00:17:58 -04:00
|
|
|
|
|
|
|
|
|
2011-07-30 20:52:36 -04:00
|
|
|
|
2016-09-15 14:40:49 -04:00
|
|
|
|
2010-10-20 00:17:58 -04:00
|
|
|
|
|
|
|
|
|
2016-08-10 15:58:24 -04:00
|
|
|
|
2016-09-15 14:40:49 -04:00
|
|
|
|
2010-10-20 00:17:58 -04:00
|
|
|
|
2016-10-26 15:54:31 -04:00
|
|
|
|
|
|
|
|
|
2010-10-20 00:17:58 -04:00
|
|
|
|
|
|
|
|
|
2016-08-10 15:58:24 -04:00
|
|
|
|
|
|
|
|
|
2010-10-20 00:17:58 -04:00
|
|
|
|
|
|
|
|
|
2016-08-10 15:58:24 -04:00
|
|
|
|
2016-09-15 14:40:49 -04:00
|
|
|
|
|
|
|
|
|
2016-08-10 15:58:24 -04:00
|
|
|
|
2016-09-15 14:40:49 -04:00
|
|
|
|
|
|
|
|
|
2010-10-20 00:17:58 -04:00
|
|
|
|
2016-09-15 14:40:49 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-20 00:17:58 -04:00
|
|
|
|
2016-08-10 15:58:24 -04:00
|
|
|
|
|
|
|
|
|
2016-09-15 14:40:49 -04:00
|
|
|
|
2016-08-10 15:58:24 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-20 00:17:58 -04:00
|
|
|
|
2011-07-30 20:52:36 -04:00
|
|
|
|
|
|
|
|
|
2012-01-26 13:32:23 -05:00
|
|
|
|
|
|
|
|
|
2011-07-30 20:52:36 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-06-14 13:08:38 -04:00
|
|
|
|
|
|
|
|
|
2011-03-01 01:34:21 +00:00
|
|
|
|
2010-10-20 00:17:58 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-20 00:17:59 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-01-26 13:32:23 -05:00
|
|
|
|
2010-10-20 00:17:59 -04:00
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:03 -04:00
|
|
|
|
2012-01-26 13:32:23 -05:00
|
|
|
|
2010-10-20 00:18:03 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-20 00:17:59 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-01-26 13:32:23 -05:00
|
|
|
|
2010-10-20 00:17:59 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
2010-10-20 00:18:03 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-01-06 11:36:28 +00:00
|
|
|
|
2011-01-06 11:36:30 +00:00
|
|
|
|
2012-09-18 20:51:13 -04:00
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
2017-10-20 12:53:33 +03:00
|
|
|
|
2011-01-06 11:36:28 +00:00
|
|
|
|
|
|
|
|
|
2011-05-22 19:51:33 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-20 20:37:23 -04:00
|
|
|
|
2011-05-22 19:51:33 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-20 17:31:43 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-02-18 17:14:40 -05:00
|
|
|
|
2012-09-20 17:31:43 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-02-18 17:14:40 -05:00
|
|
|
|
2012-09-20 17:31:43 -04:00
|
|
|
|
|
|
|
|
|
2018-12-03 11:30:31 +11:00
|
|
|
|
2012-09-20 20:37:23 -04:00
|
|
|
|
2011-05-22 19:51:33 +03:00
|
|
|
|
|
|
|
|
|
2011-01-06 11:36:28 +00:00
|
|
|
|
2012-09-20 17:23:11 -04:00
|
|
|
|
2011-01-06 11:36:28 +00:00
|
|
|
|
2012-09-20 15:52:13 -04:00
|
|
|
|
2011-01-06 11:36:28 +00:00
|
|
|
|
2012-09-20 15:52:13 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:03 -04:00
|
|
|
|
2012-09-18 20:51:13 -04:00
|
|
|
|
2010-10-20 00:18:02 -04:00
|
|
|
|
2018-03-07 14:49:06 -05:00
|
|
|
|
2011-01-06 11:36:28 +00:00
|
|
|
|
2018-03-07 14:49:06 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-01-26 23:12:11 -05:00
|
|
|
|
|
|
|
|
|
2017-10-20 12:53:33 +03:00
|
|
|
|
2014-10-10 23:25:46 +08:00
|
|
|
|
|
|
|
|
|
2012-09-20 17:23:11 -04:00
|
|
|
|
2025-07-18 16:44:03 -07:00
|
|
|
|
Coccinelle-based conversion to use ->i_state accessors
All places were patched by coccinelle with the default expecting that
->i_lock is held, afterwards entries got fixed up by hand to use
unlocked variants as needed.
The script:
@@
expression inode, flags;
@@
- inode->i_state & flags
+ inode_state_read(inode) & flags
@@
expression inode, flags;
@@
- inode->i_state &= ~flags
+ inode_state_clear(inode, flags)
@@
expression inode, flag1, flag2;
@@
- inode->i_state &= ~flag1 & ~flag2
+ inode_state_clear(inode, flag1 | flag2)
@@
expression inode, flags;
@@
- inode->i_state |= flags
+ inode_state_set(inode, flags)
@@
expression inode, flags;
@@
- inode->i_state = flags
+ inode_state_assign(inode, flags)
@@
expression inode, flags;
@@
- flags = inode->i_state
+ flags = inode_state_read(inode)
@@
expression inode, flags;
@@
- READ_ONCE(inode->i_state) & flags
+ inode_state_read(inode) & flags
Signed-off-by: Mateusz Guzik <mjguzik@gmail.com>
Signed-off-by: Christian Brauner <brauner@kernel.org>
2025-10-09 09:59:18 +02:00
|
|
|
|
2025-07-18 16:44:03 -07:00
|
|
|
|
2011-01-06 11:36:28 +00:00
|
|
|
|
2012-09-20 17:23:11 -04:00
|
|
|
|
2011-01-06 11:36:28 +00:00
|
|
|
|
2010-10-20 00:18:02 -04:00
|
|
|
|
|
|
|
|
|
2020-02-18 15:58:31 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-01-21 13:51:50 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-07-23 08:57:20 -04:00
|
|
|
|
2021-01-21 13:51:50 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-11-30 10:47:48 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-07-26 07:58:49 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-11-30 10:47:48 -05:00
|
|
|
|
2021-07-26 07:58:49 -04:00
|
|
|
|
2016-11-30 10:47:48 -05:00
|
|
|
|
|
|
|
|
|
2016-11-14 14:34:18 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-05-01 17:03:44 -04:00
|
|
|
|
2016-11-14 14:34:18 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-05-01 17:03:44 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-11-14 14:34:18 -05:00
|
|
|
|
|
|
|
|
|
2016-12-05 17:33:07 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-11-30 12:32:55 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-11-06 15:28:07 -05:00
|
|
|
|
2019-09-20 07:23:45 -04:00
|
|
|
|
|
|
|
|
|
2017-11-06 15:28:07 -05:00
|
|
|
|
2019-09-20 07:23:45 -04:00
|
|
|
|
2018-08-15 21:35:46 -04:00
|
|
|
|
|
|
|
|
|
2017-11-06 15:28:07 -05:00
|
|
|
|
|
|
|
|
|
2018-07-29 22:39:15 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-11-06 15:28:07 -05:00
|
|
|
|
2018-07-29 22:39:15 -04:00
|
|
|
|
|
|
|
|
|
2017-11-06 15:28:07 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-09-20 07:23:45 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-07-29 22:39:15 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-08-15 21:35:46 -04:00
|
|
|
|
2018-07-29 22:39:15 -04:00
|
|
|
|
|
|
|
|
|
2017-11-06 15:28:07 -05:00
|
|
|
|
2019-09-20 07:23:45 -04:00
|
|
|
|
2017-11-06 15:28:07 -05:00
|
|
|
|
2018-07-29 22:39:15 -04:00
|
|
|
|
2017-11-06 15:28:07 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-22 17:34:59 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-07-22 11:25:27 -04:00
|
|
|
|
2016-02-22 17:34:59 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-11-30 12:32:55 -05:00
|
|
|
|
2016-02-22 17:34:59 -05:00
|
|
|
|
2026-01-26 14:15:39 -05:00
|
|
|
|
|
|
|
|
|
2025-11-12 18:02:42 +00:00
|
|
|
|
2016-11-30 12:32:55 -05:00
|
|
|
|
|
|
|
|
|
2017-05-01 17:03:44 -04:00
|
|
|
|
2016-10-12 19:50:54 -04:00
|
|
|
|
2022-05-31 11:03:07 -04:00
|
|
|
|
2016-12-05 17:33:07 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-11-30 12:32:55 -05:00
|
|
|
|
2016-02-22 17:34:59 -05:00
|
|
|
|
|
|
|
|
|
2024-06-13 01:00:49 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-18 16:41:18 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-24 13:07:16 -04:00
|
|
|
|
2012-09-18 16:41:18 -04:00
|
|
|
|
2012-09-18 17:01:12 -04:00
|
|
|
|
2013-01-04 20:19:49 +08:00
|
|
|
|
2017-10-20 12:53:33 +03:00
|
|
|
|
2012-09-24 13:07:16 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-10-20 12:53:33 +03:00
|
|
|
|
2012-09-24 13:07:16 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-20 21:19:43 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-24 13:07:16 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-01-20 13:40:20 -05:00
|
|
|
|
2012-09-24 13:07:16 -04:00
|
|
|
|
2012-09-20 21:19:43 -04:00
|
|
|
|
2012-09-18 16:41:18 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-18 17:01:12 -04:00
|
|
|
|
2012-09-24 13:07:16 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-18 17:01:12 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-24 13:07:16 -04:00
|
|
|
|
2012-09-18 17:01:12 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-18 16:41:18 -04:00
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:02 -04:00
|
|
|
|
2016-07-24 15:10:12 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:02 -04:00
|
|
|
|
2011-01-06 11:36:20 +00:00
|
|
|
|
2011-07-30 20:52:33 -04:00
|
|
|
|
2020-03-20 16:04:06 -04:00
|
|
|
|
2017-10-20 12:53:32 +03:00
|
|
|
|
2011-01-06 11:36:23 +00:00
|
|
|
|
2011-01-06 11:36:20 +00:00
|
|
|
|
2016-07-24 15:10:12 -04:00
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:02 -04:00
|
|
|
|
|
|
|
|
|
2012-09-20 20:46:49 -04:00
|
|
|
|
2010-10-20 00:18:02 -04:00
|
|
|
|
2016-10-12 19:50:54 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:02 -04:00
|
|
|
|
|
|
|
|
|
2011-03-01 01:34:13 +00:00
|
|
|
|
2012-09-20 16:33:30 -04:00
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:02 -04:00
|
|
|
|
2011-05-22 19:52:03 +03:00
|
|
|
|
2011-03-01 01:34:13 +00:00
|
|
|
|
2012-09-20 20:57:11 -04:00
|
|
|
|
2017-10-20 12:53:33 +03:00
|
|
|
|
2016-11-30 11:38:10 -05:00
|
|
|
|
|
|
|
|
|
2016-11-14 13:10:48 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-09-04 12:46:35 -04:00
|
|
|
|
|
|
|
|
|
2012-09-21 15:49:42 -04:00
|
|
|
|
2016-06-17 16:48:26 -04:00
|
|
|
|
2011-03-01 01:34:13 +00:00
|
|
|
|
|
|
|
|
|
2016-10-12 19:50:54 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-11-30 10:47:48 -05:00
|
|
|
|
2016-10-12 19:50:54 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-03-01 01:34:15 +00:00
|
|
|
|
2012-09-18 20:57:08 -04:00
|
|
|
|
2011-03-01 01:34:13 +00:00
|
|
|
|
2012-09-20 16:33:30 -04:00
|
|
|
|
2011-03-01 01:34:13 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-01-06 11:36:23 +00:00
|
|
|
|
2017-10-20 12:53:32 +03:00
|
|
|
|
2011-01-06 11:36:23 +00:00
|
|
|
|
2015-02-05 17:27:39 -05:00
|
|
|
|
2012-09-20 16:33:30 -04:00
|
|
|
|
|
|
|
|
|
2015-02-05 17:27:39 -05:00
|
|
|
|
2017-10-20 12:53:32 +03:00
|
|
|
|
2012-09-20 20:57:11 -04:00
|
|
|
|
2015-02-05 17:27:39 -05:00
|
|
|
|
2016-10-12 19:50:54 -04:00
|
|
|
|
|
|
|
|
|
2015-02-05 17:27:39 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-01-06 11:36:23 +00:00
|
|
|
|
2010-10-20 00:18:02 -04:00
|
|
|
|
2012-09-18 20:57:08 -04:00
|
|
|
|
2010-10-20 00:18:02 -04:00
|
|
|
|
2011-05-22 19:47:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-06-03 11:24:36 -04:00
|
|
|
|
2013-06-03 11:30:24 -04:00
|
|
|
|
2013-06-03 11:24:36 -04:00
|
|
|
|
2011-05-22 19:47:26 +03:00
|
|
|
|
|
|
|
|
|
2016-10-25 12:24:25 -04:00
|
|
|
|
2011-05-22 19:47:26 +03:00
|
|
|
|
2016-10-25 12:24:25 -04:00
|
|
|
|
2011-05-22 19:47:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-03-20 13:03:00 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-10-20 12:53:32 +03:00
|
|
|
|
2013-03-20 13:03:00 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-01-06 11:36:23 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-03-01 01:34:13 +00:00
|
|
|
|
2017-10-20 12:53:32 +03:00
|
|
|
|
2013-03-20 13:03:00 -04:00
|
|
|
|
2011-03-01 01:34:13 +00:00
|
|
|
|
2011-01-06 11:36:23 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-07-22 11:13:22 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-05-17 12:28:42 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-01-06 11:36:23 +00:00
|
|
|
|
2011-01-06 11:36:30 +00:00
|
|
|
|
2012-09-18 20:43:31 -04:00
|
|
|
|
2011-01-06 11:36:23 +00:00
|
|
|
|
2016-05-17 12:28:42 -04:00
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:02 -04:00
|
|
|
|
|
|
|
|
|
2022-10-05 15:57:38 -04:00
|
|
|
|
2016-01-04 12:41:15 -05:00
|
|
|
|
2010-10-20 00:18:02 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-21 14:48:04 -04:00
|
|
|
|
2011-02-03 18:28:50 +00:00
|
|
|
|
2011-01-06 11:36:23 +00:00
|
|
|
|
2016-07-22 11:13:22 -04:00
|
|
|
|
pnfs/blocklayout: handle transient devices
PNFS block/SCSI layouts should gracefully handle cases where block devices
are not available when a layout is retrieved, or the block devices are
removed while the client holds a layout.
While setting up a layout segment, keep a record of an unavailable or
un-parsable block device in cache with a flag so that subsequent layouts do
not spam the server with GETDEVINFO. We can reuse the current
NFS_DEVICEID_UNAVAILABLE handling with one variation: instead of reusing
the device, we will discard it and send a fresh GETDEVINFO after the
timeout, since the lookup and validation of the device occurs within the
GETDEVINFO response handling.
A lookup of a layout segment that references an unavailable device will
return a segment with the NFS_LSEG_UNAVAILABLE flag set. This will allow
the pgio layer to mark the layout with the appropriate fail bit, which
forces subsequent IO to the MDS, and prevents spamming the server with
LAYOUTGET, LAYOUTRETURN.
Finally, when IO to a block device fails, look up the block device(s)
referenced by the pgio header, and mark them as unavailable.
Signed-off-by: Benjamin Coddington <bcodding@redhat.com>
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
2017-12-08 12:52:59 -05:00
|
|
|
|
2011-01-06 11:36:23 +00:00
|
|
|
|
2016-05-17 12:28:42 -04:00
|
|
|
|
|
|
|
|
|
2022-10-05 15:57:38 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-01-06 11:36:23 +00:00
|
|
|
|
2016-01-04 12:41:15 -05:00
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:02 -04:00
|
|
|
|
|
|
|
|
|
2025-05-10 10:50:13 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-10-12 19:50:54 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-02-03 18:28:52 +00:00
|
|
|
|
2011-01-06 11:36:30 +00:00
|
|
|
|
2011-01-06 11:36:23 +00:00
|
|
|
|
2010-10-20 00:18:02 -04:00
|
|
|
|
2011-01-06 11:36:23 +00:00
|
|
|
|
2010-10-20 00:18:02 -04:00
|
|
|
|
2011-02-03 18:28:52 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-01-06 11:36:23 +00:00
|
|
|
|
2011-01-06 11:36:20 +00:00
|
|
|
|
2012-09-20 20:46:49 -04:00
|
|
|
|
2010-10-20 00:18:02 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-11-25 12:06:14 -05:00
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:02 -04:00
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-24 13:07:16 -04:00
|
|
|
|
2016-02-22 17:34:59 -05:00
|
|
|
|
2012-09-24 13:07:16 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-29 10:10:17 -04:00
|
|
|
|
2012-09-24 13:07:16 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-11-25 12:06:14 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
2012-04-27 17:53:53 -04:00
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
2020-11-25 12:06:14 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-07-18 16:44:03 -07:00
|
|
|
|
2020-11-25 12:06:14 -05:00
|
|
|
|
2025-07-18 16:44:03 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-11-25 12:06:14 -05:00
|
|
|
|
|
|
|
|
|
2013-02-12 09:48:42 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-22 14:20:27 -05:00
|
|
|
|
|
|
|
|
|
2013-02-12 09:48:42 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-02-22 14:20:27 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-11-30 18:00:07 -05:00
|
|
|
|
2019-02-22 14:20:27 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-02-18 15:58:31 -05:00
|
|
|
|
2019-02-22 14:20:27 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-12 09:48:42 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-06-13 01:00:48 -04:00
|
|
|
|
2013-02-12 09:48:42 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-04 10:32:42 -05:00
|
|
|
|
2013-02-12 09:48:42 -05:00
|
|
|
|
|
|
|
|
|
2014-09-10 08:23:29 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-12 09:48:42 -05:00
|
|
|
|
|
|
|
|
|
2024-06-13 01:00:49 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-06-13 01:00:48 -04:00
|
|
|
|
2016-02-22 17:46:34 -05:00
|
|
|
|
2013-02-12 09:48:42 -05:00
|
|
|
|
2016-02-22 17:46:34 -05:00
|
|
|
|
2013-02-12 09:48:42 -05:00
|
|
|
|
|
|
|
|
|
2015-12-31 09:28:06 -05:00
|
|
|
|
|
|
|
|
|
2013-02-12 09:48:42 -05:00
|
|
|
|
2019-02-22 14:20:27 -05:00
|
|
|
|
2013-02-12 09:48:42 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-06-13 01:00:48 -04:00
|
|
|
|
|
|
|
|
|
2013-02-12 09:48:42 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-06-13 01:00:48 -04:00
|
|
|
|
2013-02-12 09:48:42 -05:00
|
|
|
|
|
|
|
|
|
2024-06-13 01:00:55 -04:00
|
|
|
|
|
|
|
|
|
2013-02-12 09:48:42 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-06-13 01:00:55 -04:00
|
|
|
|
|
|
|
|
|
2013-02-12 09:48:42 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-06-13 01:00:55 -04:00
|
|
|
|
2013-02-12 09:48:42 -05:00
|
|
|
|
2024-06-13 01:00:55 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-12 09:48:42 -05:00
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:02 -04:00
|
|
|
|
2020-09-17 10:19:00 +08:00
|
|
|
|
2010-10-20 00:18:02 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-06-15 17:52:40 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-06-13 01:00:48 -04:00
|
|
|
|
2010-10-20 00:18:02 -04:00
|
|
|
|
|
|
|
|
|
2024-06-13 01:00:55 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-01-27 13:07:26 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-01-06 11:36:22 +00:00
|
|
|
|
2011-01-06 11:36:30 +00:00
|
|
|
|
|
|
|
|
|
2020-01-27 13:07:26 -05:00
|
|
|
|
2010-10-20 00:18:03 -04:00
|
|
|
|
2021-07-02 16:37:15 -04:00
|
|
|
|
|
|
|
|
|
2016-09-03 11:20:04 -04:00
|
|
|
|
|
|
|
|
|
2020-01-27 13:07:26 -05:00
|
|
|
|
2016-09-03 11:20:04 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-07-02 16:37:15 -04:00
|
|
|
|
|
|
|
|
|
2012-03-04 18:13:56 -05:00
|
|
|
|
2021-07-02 16:37:15 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-07-24 11:46:06 -04:00
|
|
|
|
2021-07-02 16:37:15 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:03 -04:00
|
|
|
|
|
|
|
|
|
2012-10-05 16:56:58 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-07-23 08:57:21 -04:00
|
|
|
|
2012-10-05 16:56:58 -07:00
|
|
|
|
|
|
|
|
|
2011-01-06 11:36:25 +00:00
|
|
|
|
|
|
|
|
|
2015-08-04 16:40:08 -04:00
|
|
|
|
2011-01-06 11:36:25 +00:00
|
|
|
|
2011-01-06 11:36:32 +00:00
|
|
|
|
2015-08-04 16:40:08 -04:00
|
|
|
|
2011-01-06 11:36:25 +00:00
|
|
|
|
|
|
|
|
|
2016-10-06 12:08:51 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-09-22 12:30:20 -04:00
|
|
|
|
2016-10-06 12:08:51 -04:00
|
|
|
|
2016-09-22 12:30:20 -04:00
|
|
|
|
2016-10-06 12:08:51 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-05-30 17:16:20 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
treewide: Replace kmalloc with kmalloc_obj for non-scalar types
This is the result of running the Coccinelle script from
scripts/coccinelle/api/kmalloc_objs.cocci. The script is designed to
avoid scalar types (which need careful case-by-case checking), and
instead replace kmalloc-family calls that allocate struct or union
object instances:
Single allocations: kmalloc(sizeof(TYPE), ...)
are replaced with: kmalloc_obj(TYPE, ...)
Array allocations: kmalloc_array(COUNT, sizeof(TYPE), ...)
are replaced with: kmalloc_objs(TYPE, COUNT, ...)
Flex array allocations: kmalloc(struct_size(PTR, FAM, COUNT), ...)
are replaced with: kmalloc_flex(*PTR, FAM, COUNT, ...)
(where TYPE may also be *VAR)
The resulting allocations no longer return "void *", instead returning
"TYPE *".
Signed-off-by: Kees Cook <kees@kernel.org>
2026-02-20 23:49:23 -08:00
|
|
|
|
2018-05-30 17:16:20 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-09-03 12:57:52 -04:00
|
|
|
|
2018-05-30 17:16:20 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-09-21 05:14:28 -04:00
|
|
|
|
2016-10-06 12:08:51 -04:00
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
2016-10-06 12:11:21 -04:00
|
|
|
|
2016-01-04 12:52:53 -05:00
|
|
|
|
2016-09-21 05:14:28 -04:00
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
2016-10-06 12:08:51 -04:00
|
|
|
|
2018-09-03 13:12:15 -04:00
|
|
|
|
2016-09-19 17:47:09 -04:00
|
|
|
|
2010-10-20 00:18:03 -04:00
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
2010-10-20 00:18:03 -04:00
|
|
|
|
|
|
|
|
|
treewide: Replace kmalloc with kmalloc_obj for non-scalar types
This is the result of running the Coccinelle script from
scripts/coccinelle/api/kmalloc_objs.cocci. The script is designed to
avoid scalar types (which need careful case-by-case checking), and
instead replace kmalloc-family calls that allocate struct or union
object instances:
Single allocations: kmalloc(sizeof(TYPE), ...)
are replaced with: kmalloc_obj(TYPE, ...)
Array allocations: kmalloc_array(COUNT, sizeof(TYPE), ...)
are replaced with: kmalloc_objs(TYPE, COUNT, ...)
Flex array allocations: kmalloc(struct_size(PTR, FAM, COUNT), ...)
are replaced with: kmalloc_flex(*PTR, FAM, COUNT, ...)
(where TYPE may also be *VAR)
The resulting allocations no longer return "void *", instead returning
"TYPE *".
Signed-off-by: Kees Cook <kees@kernel.org>
2026-02-20 23:49:23 -08:00
|
|
|
|
2016-05-17 12:28:46 -04:00
|
|
|
|
2016-09-21 05:14:28 -04:00
|
|
|
|
2015-11-25 13:43:14 -05:00
|
|
|
|
2018-09-03 13:12:15 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-09-19 17:47:09 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-01 20:42:44 -05:00
|
|
|
|
|
|
|
|
|
2015-11-25 13:43:14 -05:00
|
|
|
|
2016-05-17 12:28:46 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-10-06 12:08:51 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-05-17 12:28:45 -04:00
|
|
|
|
2016-05-17 12:28:46 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
pnfs: rework LAYOUTGET retry handling
There are several problems in the way a stateid is selected for a
LAYOUTGET operation:
We pick a stateid to use in the RPC prepare op, but that makes
it difficult to serialize LAYOUTGETs that use the open stateid. That
serialization is done in pnfs_update_layout, which occurs well before
the rpc_prepare operation.
Between those two events, the i_lock is dropped and reacquired.
pnfs_update_layout can find that the list has lsegs in it and not do any
serialization, but then later pnfs_choose_layoutget_stateid ends up
choosing the open stateid.
This patch changes the client to select the stateid to use in the
LAYOUTGET earlier, when we're searching for a usable layout segment.
This way we can do it all while holding the i_lock the first time, and
ensure that we serialize any LAYOUTGET call that uses a non-layout
stateid.
This also means a rework of how LAYOUTGET replies are handled, as we
must now get the latest stateid if we want to retransmit in response
to a retryable error.
Most of those errors boil down to the fact that the layout state has
changed in some fashion. Thus, what we really want to do is to re-search
for a layout when it fails with a retryable error, so that we can avoid
reissuing the RPC at all if possible.
While the LAYOUTGET RPC is async, the initiating thread always waits for
it to complete, so it's effectively synchronous anyway. Currently, when
we need to retry a LAYOUTGET because of an error, we drive that retry
via the rpc state machine.
This means that once the call has been submitted, it runs until it
completes. So, we must move the error handling for this RPC out of the
rpc_call_done operation and into the caller.
In order to handle errors like NFS4ERR_DELAY properly, we must also
pass a pointer to the sliding timeout, which is now moved to the stack
in pnfs_update_layout.
The complicating errors are -NFS4ERR_RECALLCONFLICT and
-NFS4ERR_LAYOUTTRYLATER, as those involve a timeout after which we give
up and return NULL back to the caller. So, there is some special
handling for those errors to ensure that the layers driving the retries
can handle that appropriately.
Signed-off-by: Jeff Layton <jeff.layton@primarydata.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
2016-05-17 12:28:47 -04:00
|
|
|
|
2016-05-17 12:28:46 -04:00
|
|
|
|
2020-02-07 19:40:14 -05:00
|
|
|
|
2016-09-21 05:14:28 -04:00
|
|
|
|
2010-10-20 00:18:02 -04:00
|
|
|
|
|
|
|
|
|
2018-05-30 17:16:20 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-07-02 17:24:22 -04:00
|
|
|
|
2018-05-30 17:16:20 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-03-20 13:03:00 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-06-13 01:00:50 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-05-10 11:05:36 -04:00
|
|
|
|
|
|
|
|
|
2024-06-13 01:00:50 -04:00
|
|
|
|
|
|
|
|
|
2025-05-10 11:05:36 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-06-13 01:00:50 -04:00
|
|
|
|
|
|
|
|
|
2024-06-13 01:00:52 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-05-10 11:05:36 -04:00
|
|
|
|
2024-06-13 01:00:52 -04:00
|
|
|
|
|
|
|
|
|
2025-05-10 11:05:36 -04:00
|
|
|
|
2024-06-13 01:00:52 -04:00
|
|
|
|
2025-05-10 11:05:36 -04:00
|
|
|
|
2024-06-13 01:00:52 -04:00
|
|
|
|
|
|
|
|
|
2016-10-12 19:50:54 -04:00
|
|
|
|
2016-11-20 13:13:54 -05:00
|
|
|
|
2016-10-12 19:50:54 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-08-21 14:05:01 -04:00
|
|
|
|
2016-11-20 13:13:54 -05:00
|
|
|
|
2024-08-21 14:05:01 -04:00
|
|
|
|
2016-11-20 13:13:54 -05:00
|
|
|
|
|
|
|
|
|
2016-10-12 19:50:54 -04:00
|
|
|
|
|
|
|
|
|
2020-01-27 13:07:26 -05:00
|
|
|
|
2025-05-10 10:50:13 -04:00
|
|
|
|
2016-10-12 19:50:54 -04:00
|
|
|
|
|
|
|
|
|
2016-11-20 13:13:54 -05:00
|
|
|
|
2016-10-12 19:50:54 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-01-26 23:12:11 -05:00
|
|
|
|
2016-07-21 12:44:15 -04:00
|
|
|
|
|
|
|
|
|
2020-04-02 15:37:02 -04:00
|
|
|
|
2016-07-21 12:44:15 -04:00
|
|
|
|
2016-01-26 23:12:11 -05:00
|
|
|
|
2016-09-03 10:39:51 -04:00
|
|
|
|
2024-12-16 19:28:06 -05:00
|
|
|
|
2016-09-03 10:39:51 -04:00
|
|
|
|
2016-10-17 17:54:32 -04:00
|
|
|
|
2016-01-26 23:12:11 -05:00
|
|
|
|
2016-10-17 17:54:32 -04:00
|
|
|
|
2016-01-26 23:12:11 -05:00
|
|
|
|
2021-01-21 13:51:50 -05:00
|
|
|
|
|
|
|
|
|
2016-07-21 12:44:15 -04:00
|
|
|
|
2020-04-02 15:37:02 -04:00
|
|
|
|
|
|
|
|
|
2016-07-21 12:44:15 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-01-21 13:51:50 -05:00
|
|
|
|
2016-07-21 12:44:15 -04:00
|
|
|
|
2021-01-21 13:51:50 -05:00
|
|
|
|
2016-01-26 23:12:11 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-11-15 21:47:27 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-09-06 00:53:22 +08:00
|
|
|
|
2020-04-02 15:37:02 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-06-13 01:00:53 -04:00
|
|
|
|
2014-09-06 00:53:22 +08:00
|
|
|
|
|
|
|
|
|
2016-12-02 16:12:12 -05:00
|
|
|
|
2014-09-06 00:53:22 +08:00
|
|
|
|
2020-04-02 15:37:02 -04:00
|
|
|
|
2014-09-06 00:53:22 +08:00
|
|
|
|
|
|
|
|
|
2020-04-02 15:37:02 -04:00
|
|
|
|
treewide: Replace kmalloc with kmalloc_obj for non-scalar types
This is the result of running the Coccinelle script from
scripts/coccinelle/api/kmalloc_objs.cocci. The script is designed to
avoid scalar types (which need careful case-by-case checking), and
instead replace kmalloc-family calls that allocate struct or union
object instances:
Single allocations: kmalloc(sizeof(TYPE), ...)
are replaced with: kmalloc_obj(TYPE, ...)
Array allocations: kmalloc_array(COUNT, sizeof(TYPE), ...)
are replaced with: kmalloc_objs(TYPE, COUNT, ...)
Flex array allocations: kmalloc(struct_size(PTR, FAM, COUNT), ...)
are replaced with: kmalloc_flex(*PTR, FAM, COUNT, ...)
(where TYPE may also be *VAR)
The resulting allocations no longer return "void *", instead returning
"TYPE *".
Signed-off-by: Kees Cook <kees@kernel.org>
2026-02-20 23:49:23 -08:00
|
|
|
|
2014-09-06 00:53:22 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-12-11 17:02:04 -05:00
|
|
|
|
2014-09-06 00:53:22 +08:00
|
|
|
|
2020-04-02 15:37:02 -04:00
|
|
|
|
2014-09-06 00:53:22 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-11-15 21:47:27 -05:00
|
|
|
|
2016-09-23 11:38:08 -04:00
|
|
|
|
2014-09-06 00:53:22 +08:00
|
|
|
|
2020-04-02 15:37:02 -04:00
|
|
|
|
2016-12-02 16:12:12 -05:00
|
|
|
|
|
|
|
|
|
2014-09-06 00:53:22 +08:00
|
|
|
|
2024-06-13 01:00:53 -04:00
|
|
|
|
2014-09-06 00:53:22 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-01-26 23:12:11 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-01-27 20:32:50 -05:00
|
|
|
|
2016-01-26 23:12:11 -05:00
|
|
|
|
2024-06-13 01:00:49 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-01-26 23:12:11 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-01-27 20:32:50 -05:00
|
|
|
|
2016-01-26 23:12:11 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-02 15:37:02 -04:00
|
|
|
|
2016-01-26 23:12:11 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-02 15:37:02 -04:00
|
|
|
|
2016-01-26 23:12:11 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-06-13 01:00:53 -04:00
|
|
|
|
|
|
|
|
|
2016-01-26 23:12:11 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-06-20 15:03:34 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-05-22 19:52:37 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-19 12:54:51 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-05-22 19:52:37 +03:00
|
|
|
|
2020-04-02 15:37:02 -04:00
|
|
|
|
2011-05-22 19:52:37 +03:00
|
|
|
|
2016-11-30 10:19:09 -05:00
|
|
|
|
2018-06-11 15:32:06 -04:00
|
|
|
|
2011-05-22 19:52:37 +03:00
|
|
|
|
2026-03-04 10:32:42 -05:00
|
|
|
|
2011-05-22 19:52:37 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-21 16:37:02 -04:00
|
|
|
|
2011-05-22 19:52:37 +03:00
|
|
|
|
2012-06-20 15:03:34 -04:00
|
|
|
|
|
|
|
|
|
2011-05-22 19:52:37 +03:00
|
|
|
|
|
|
|
|
|
2012-09-18 20:51:13 -04:00
|
|
|
|
2016-11-30 10:19:09 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-06-11 15:32:06 -04:00
|
|
|
|
2013-03-20 13:03:00 -04:00
|
|
|
|
2021-05-19 12:54:51 -04:00
|
|
|
|
2014-09-10 08:23:31 -07:00
|
|
|
|
|
|
|
|
|
2012-06-20 15:03:34 -04:00
|
|
|
|
2018-06-11 15:32:06 -04:00
|
|
|
|
|
|
|
|
|
2012-06-20 15:03:34 -04:00
|
|
|
|
|
|
|
|
|
2020-04-19 14:38:00 -04:00
|
|
|
|
2012-06-20 15:03:34 -04:00
|
|
|
|
2014-08-21 11:09:22 -05:00
|
|
|
|
2020-04-02 15:37:02 -04:00
|
|
|
|
2011-05-22 19:52:37 +03:00
|
|
|
|
2026-05-26 16:29:53 -07:00
|
|
|
|
|
|
|
|
|
2015-07-09 18:40:01 +02:00
|
|
|
|
2024-06-13 01:00:53 -04:00
|
|
|
|
|
|
|
|
|
2020-04-19 14:38:00 -04:00
|
|
|
|
|
|
|
|
|
2015-07-09 18:40:01 +02:00
|
|
|
|
2017-01-26 15:50:41 -05:00
|
|
|
|
2015-07-09 18:40:01 +02:00
|
|
|
|
2011-05-22 19:52:37 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-03-20 13:23:33 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-06-13 01:00:55 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-12-08 14:45:00 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-01-06 11:36:32 +00:00
|
|
|
|
2015-01-24 13:54:37 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-01-06 11:36:32 +00:00
|
|
|
|
2016-11-16 01:11:25 -05:00
|
|
|
|
2020-04-02 15:37:02 -04:00
|
|
|
|
2014-11-17 09:30:41 +08:00
|
|
|
|
2016-11-16 01:11:25 -05:00
|
|
|
|
|
|
|
|
|
2025-12-08 14:45:00 -05:00
|
|
|
|
2011-01-06 11:36:32 +00:00
|
|
|
|
2016-11-16 01:11:25 -05:00
|
|
|
|
|
|
|
|
|
2016-11-30 16:23:38 -05:00
|
|
|
|
2018-09-02 15:57:01 -04:00
|
|
|
|
2011-01-06 11:36:32 +00:00
|
|
|
|
2015-01-24 13:54:37 -05:00
|
|
|
|
2016-11-21 11:05:33 -05:00
|
|
|
|
2018-03-07 14:49:06 -05:00
|
|
|
|
|
|
|
|
|
2015-01-24 13:54:37 -05:00
|
|
|
|
2018-03-07 14:49:06 -05:00
|
|
|
|
2015-01-24 13:54:37 -05:00
|
|
|
|
2015-08-19 13:49:19 +08:00
|
|
|
|
2025-12-08 14:45:00 -05:00
|
|
|
|
2016-11-21 10:56:38 -05:00
|
|
|
|
2025-12-08 14:45:00 -05:00
|
|
|
|
|
|
|
|
|
2016-11-21 10:56:38 -05:00
|
|
|
|
2025-12-08 14:45:00 -05:00
|
|
|
|
2016-11-21 10:56:38 -05:00
|
|
|
|
|
|
|
|
|
2015-01-24 13:54:37 -05:00
|
|
|
|
2018-09-02 15:57:01 -04:00
|
|
|
|
2015-01-24 13:54:37 -05:00
|
|
|
|
2016-11-21 10:56:38 -05:00
|
|
|
|
|
|
|
|
|
2015-01-24 13:54:37 -05:00
|
|
|
|
2025-12-08 14:45:00 -05:00
|
|
|
|
|
|
|
|
|
2015-01-24 13:54:37 -05:00
|
|
|
|
2025-12-08 14:45:00 -05:00
|
|
|
|
2016-11-21 10:56:38 -05:00
|
|
|
|
|
|
|
|
|
2015-01-24 13:54:37 -05:00
|
|
|
|
|
|
|
|
|
2025-12-08 14:45:00 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-08-19 13:49:19 +08:00
|
|
|
|
2016-11-16 01:11:25 -05:00
|
|
|
|
2016-11-21 10:56:38 -05:00
|
|
|
|
|
|
|
|
|
2015-08-19 13:49:19 +08:00
|
|
|
|
2016-11-16 01:11:25 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-11-15 18:29:59 -05:00
|
|
|
|
|
|
|
|
|
2016-11-16 01:11:25 -05:00
|
|
|
|
|
|
|
|
|
2016-11-15 18:29:59 -05:00
|
|
|
|
2015-09-22 11:35:22 +08:00
|
|
|
|
2015-08-19 13:49:19 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-11-16 01:11:25 -05:00
|
|
|
|
2020-04-02 15:37:02 -04:00
|
|
|
|
2016-11-16 01:11:25 -05:00
|
|
|
|
2020-04-19 23:53:52 -04:00
|
|
|
|
2016-11-16 01:11:25 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-02 15:37:02 -04:00
|
|
|
|
2020-04-19 23:53:52 -04:00
|
|
|
|
2015-08-19 13:49:19 +08:00
|
|
|
|
2011-01-06 11:36:32 +00:00
|
|
|
|
2018-09-02 15:57:01 -04:00
|
|
|
|
2025-12-08 14:45:00 -05:00
|
|
|
|
2016-12-02 16:12:12 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-03-07 14:49:06 -05:00
|
|
|
|
2016-12-02 16:12:12 -05:00
|
|
|
|
|
|
|
|
|
2015-08-19 13:49:19 +08:00
|
|
|
|
2024-06-13 01:00:53 -04:00
|
|
|
|
2018-03-07 14:49:06 -05:00
|
|
|
|
2016-12-02 16:12:12 -05:00
|
|
|
|
2011-01-06 11:36:32 +00:00
|
|
|
|
|
|
|
|
|
2021-01-04 13:18:03 -05:00
|
|
|
|
|
|
|
|
|
2019-09-20 07:23:41 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-09-20 07:23:43 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-04-06 11:05:27 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-09-20 07:23:43 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-01-05 16:43:21 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-09-20 07:23:43 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-09-20 07:23:42 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-09-20 07:23:41 -04:00
|
|
|
|
2019-09-20 07:23:45 -04:00
|
|
|
|
2021-01-04 13:18:03 -05:00
|
|
|
|
2019-09-20 07:23:41 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-11-16 01:11:25 -05:00
|
|
|
|
2024-06-13 01:00:51 -04:00
|
|
|
|
2011-01-06 11:36:32 +00:00
|
|
|
|
2016-11-16 01:11:25 -05:00
|
|
|
|
2021-01-04 13:35:46 -05:00
|
|
|
|
2016-11-16 01:11:25 -05:00
|
|
|
|
2016-12-02 16:12:12 -05:00
|
|
|
|
2025-05-10 11:05:36 -04:00
|
|
|
|
2011-01-06 11:36:32 +00:00
|
|
|
|
2019-09-20 07:23:40 -04:00
|
|
|
|
2024-06-13 01:00:51 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-09-20 07:23:40 -04:00
|
|
|
|
2021-01-04 13:35:46 -05:00
|
|
|
|
2024-06-13 01:00:50 -04:00
|
|
|
|
2025-05-10 11:05:36 -04:00
|
|
|
|
2021-01-04 13:35:46 -05:00
|
|
|
|
2025-05-10 11:05:36 -04:00
|
|
|
|
2019-09-20 07:23:40 -04:00
|
|
|
|
|
|
|
|
|
2016-11-16 01:11:25 -05:00
|
|
|
|
|
|
|
|
|
2020-08-23 17:36:59 -05:00
|
|
|
|
2019-09-20 07:23:40 -04:00
|
|
|
|
2021-01-04 15:01:18 -05:00
|
|
|
|
|
|
|
|
|
2016-11-16 01:11:25 -05:00
|
|
|
|
2020-08-03 18:32:28 -04:00
|
|
|
|
2016-12-02 16:12:12 -05:00
|
|
|
|
|
|
|
|
|
2016-11-16 01:11:25 -05:00
|
|
|
|
2011-01-06 11:36:32 +00:00
|
|
|
|
|
|
|
|
|
2015-09-22 11:35:22 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-11-18 15:21:30 -05:00
|
|
|
|
2015-09-22 11:35:22 +08:00
|
|
|
|
2016-11-18 15:21:30 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-09-22 11:35:22 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:03 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-06-03 11:30:24 -04:00
|
|
|
|
2013-06-03 11:24:36 -04:00
|
|
|
|
2010-10-20 00:18:03 -04:00
|
|
|
|
2011-05-22 19:47:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:03 -04:00
|
|
|
|
2011-05-22 19:47:26 +03:00
|
|
|
|
2010-10-20 00:18:03 -04:00
|
|
|
|
|
|
|
|
|
2015-08-25 08:54:17 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:02 -04:00
|
|
|
|
2015-08-25 08:54:17 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:03 -04:00
|
|
|
|
2010-10-20 00:18:02 -04:00
|
|
|
|
|
|
|
|
|
2015-08-25 08:54:17 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:03 -04:00
|
|
|
|
2011-01-06 11:36:20 +00:00
|
|
|
|
2010-10-20 00:18:03 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-01-06 11:36:20 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-05-22 19:47:26 +03:00
|
|
|
|
2010-10-20 00:18:03 -04:00
|
|
|
|
2011-05-22 19:47:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-18 20:51:13 -04:00
|
|
|
|
2010-10-20 00:18:02 -04:00
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
2015-08-25 08:54:17 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
|
|
|
|
|
2011-07-30 20:52:32 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-05-22 19:51:33 +03:00
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
|
|
|
|
|
2017-10-20 12:53:33 +03:00
|
|
|
|
2011-01-06 11:36:21 +00:00
|
|
|
|
|
|
|
|
|
2016-10-12 19:50:54 -04:00
|
|
|
|
2013-02-12 09:48:42 -05:00
|
|
|
|
2011-01-06 11:36:21 +00:00
|
|
|
|
2018-12-03 11:30:31 +11:00
|
|
|
|
2016-06-17 16:48:19 -04:00
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-07-30 20:52:32 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-06-17 16:48:20 -04:00
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-10-02 15:41:05 -07:00
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
2011-07-30 20:52:32 -04:00
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
|
|
|
|
|
2012-10-02 15:41:05 -07:00
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
2012-10-02 15:41:05 -07:00
|
|
|
|
2012-10-31 16:05:48 +08:00
|
|
|
|
|
|
|
|
|
2012-10-02 15:41:05 -07:00
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:03 -04:00
|
|
|
|
|
|
|
|
|
2016-05-25 07:31:14 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:03 -04:00
|
|
|
|
2013-06-03 11:24:36 -04:00
|
|
|
|
2013-06-03 11:30:24 -04:00
|
|
|
|
2016-05-25 07:31:14 -07:00
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:03 -04:00
|
|
|
|
2011-05-22 19:47:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-05-25 07:31:14 -07:00
|
|
|
|
2017-10-07 16:02:21 +02:00
|
|
|
|
2013-06-03 11:30:24 -04:00
|
|
|
|
2018-08-01 19:55:51 -05:00
|
|
|
|
2011-05-22 19:47:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-06-03 11:30:24 -04:00
|
|
|
|
2010-10-20 00:18:03 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
2011-05-22 19:47:26 +03:00
|
|
|
|
2016-05-25 07:31:14 -07:00
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
2010-10-20 00:18:03 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-01-06 11:36:21 +00:00
|
|
|
|
2011-01-06 11:36:23 +00:00
|
|
|
|
2016-05-25 07:31:14 -07:00
|
|
|
|
|
|
|
|
|
2012-09-18 20:57:08 -04:00
|
|
|
|
2010-10-20 00:18:03 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-10-20 12:53:32 +03:00
|
|
|
|
2010-10-20 00:18:03 -04:00
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
|
|
|
|
|
2012-05-23 05:02:37 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-09-05 14:07:12 -04:00
|
|
|
|
2014-12-01 08:22:23 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-09-05 14:07:12 -04:00
|
|
|
|
2015-12-14 16:25:11 -05:00
|
|
|
|
freezer,sched: Rewrite core freezer logic
Rewrite the core freezer to behave better wrt thawing and be simpler
in general.
By replacing PF_FROZEN with TASK_FROZEN, a special block state, it is
ensured frozen tasks stay frozen until thawed and don't randomly wake
up early, as is currently possible.
As such, it does away with PF_FROZEN and PF_FREEZER_SKIP, freeing up
two PF_flags (yay!).
Specifically; the current scheme works a little like:
freezer_do_not_count();
schedule();
freezer_count();
And either the task is blocked, or it lands in try_to_freezer()
through freezer_count(). Now, when it is blocked, the freezer
considers it frozen and continues.
However, on thawing, once pm_freezing is cleared, freezer_count()
stops working, and any random/spurious wakeup will let a task run
before its time.
That is, thawing tries to thaw things in explicit order; kernel
threads and workqueues before doing bringing SMP back before userspace
etc.. However due to the above mentioned races it is entirely possible
for userspace tasks to thaw (by accident) before SMP is back.
This can be a fatal problem in asymmetric ISA architectures (eg ARMv9)
where the userspace task requires a special CPU to run.
As said; replace this with a special task state TASK_FROZEN and add
the following state transitions:
TASK_FREEZABLE -> TASK_FROZEN
__TASK_STOPPED -> TASK_FROZEN
__TASK_TRACED -> TASK_FROZEN
The new TASK_FREEZABLE can be set on any state part of TASK_NORMAL
(IOW. TASK_INTERRUPTIBLE and TASK_UNINTERRUPTIBLE) -- any such state
is already required to deal with spurious wakeups and the freezer
causes one such when thawing the task (since the original state is
lost).
The special __TASK_{STOPPED,TRACED} states *can* be restored since
their canonical state is in ->jobctl.
With this, frozen tasks need an explicit TASK_FROZEN wakeup and are
free of undue (early / spurious) wakeups.
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Reviewed-by: Ingo Molnar <mingo@kernel.org>
Acked-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Link: https://lore.kernel.org/r/20220822114649.055452969@infradead.org
2022-08-22 13:18:22 +02:00
|
|
|
|
2014-12-01 08:22:23 +08:00
|
|
|
|
|
|
|
|
|
2018-06-23 22:54:33 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-05-31 11:03:07 -04:00
|
|
|
|
2025-06-19 11:02:21 -04:00
|
|
|
|
|
|
|
|
|
2022-05-31 11:03:07 -04:00
|
|
|
|
2025-06-19 11:02:21 -04:00
|
|
|
|
2018-06-23 22:54:33 -04:00
|
|
|
|
|
|
|
|
|
2021-01-22 10:05:51 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-12-11 17:02:04 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-09-22 12:30:20 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-02-18 17:14:40 -05:00
|
|
|
|
2016-09-22 12:30:20 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-02-18 17:14:40 -05:00
|
|
|
|
2016-09-22 12:30:20 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-06-13 18:22:38 -04:00
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
|
|
|
|
|
2011-05-22 19:47:26 +03:00
|
|
|
|
|
|
|
|
|
2011-05-11 18:00:51 -04:00
|
|
|
|
2016-05-25 07:31:14 -07:00
|
|
|
|
2011-05-11 18:00:51 -04:00
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
2011-05-22 19:47:26 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-09-11 13:09:37 -04:00
|
|
|
|
2011-06-01 16:44:44 -04:00
|
|
|
|
|
|
|
|
|
pnfs: rework LAYOUTGET retry handling
There are several problems in the way a stateid is selected for a
LAYOUTGET operation:
We pick a stateid to use in the RPC prepare op, but that makes
it difficult to serialize LAYOUTGETs that use the open stateid. That
serialization is done in pnfs_update_layout, which occurs well before
the rpc_prepare operation.
Between those two events, the i_lock is dropped and reacquired.
pnfs_update_layout can find that the list has lsegs in it and not do any
serialization, but then later pnfs_choose_layoutget_stateid ends up
choosing the open stateid.
This patch changes the client to select the stateid to use in the
LAYOUTGET earlier, when we're searching for a usable layout segment.
This way we can do it all while holding the i_lock the first time, and
ensure that we serialize any LAYOUTGET call that uses a non-layout
stateid.
This also means a rework of how LAYOUTGET replies are handled, as we
must now get the latest stateid if we want to retransmit in response
to a retryable error.
Most of those errors boil down to the fact that the layout state has
changed in some fashion. Thus, what we really want to do is to re-search
for a layout when it fails with a retryable error, so that we can avoid
reissuing the RPC at all if possible.
While the LAYOUTGET RPC is async, the initiating thread always waits for
it to complete, so it's effectively synchronous anyway. Currently, when
we need to retry a LAYOUTGET because of an error, we drive that retry
via the rpc state machine.
This means that once the call has been submitted, it runs until it
completes. So, we must move the error handling for this RPC out of the
rpc_call_done operation and into the caller.
In order to handle errors like NFS4ERR_DELAY properly, we must also
pass a pointer to the sliding timeout, which is now moved to the stack
in pnfs_update_layout.
The complicating errors are -NFS4ERR_RECALLCONFLICT and
-NFS4ERR_LAYOUTTRYLATER, as those involve a timeout after which we give
up and return NULL back to the caller. So, there is some special
handling for those errors to ensure that the layers driving the retries
can handle that appropriately.
Signed-off-by: Jeff Layton <jeff.layton@primarydata.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
2016-05-17 12:28:47 -04:00
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
2016-09-21 05:14:28 -04:00
|
|
|
|
pnfs: rework LAYOUTGET retry handling
There are several problems in the way a stateid is selected for a
LAYOUTGET operation:
We pick a stateid to use in the RPC prepare op, but that makes
it difficult to serialize LAYOUTGETs that use the open stateid. That
serialization is done in pnfs_update_layout, which occurs well before
the rpc_prepare operation.
Between those two events, the i_lock is dropped and reacquired.
pnfs_update_layout can find that the list has lsegs in it and not do any
serialization, but then later pnfs_choose_layoutget_stateid ends up
choosing the open stateid.
This patch changes the client to select the stateid to use in the
LAYOUTGET earlier, when we're searching for a usable layout segment.
This way we can do it all while holding the i_lock the first time, and
ensure that we serialize any LAYOUTGET call that uses a non-layout
stateid.
This also means a rework of how LAYOUTGET replies are handled, as we
must now get the latest stateid if we want to retransmit in response
to a retryable error.
Most of those errors boil down to the fact that the layout state has
changed in some fashion. Thus, what we really want to do is to re-search
for a layout when it fails with a retryable error, so that we can avoid
reissuing the RPC at all if possible.
While the LAYOUTGET RPC is async, the initiating thread always waits for
it to complete, so it's effectively synchronous anyway. Currently, when
we need to retry a LAYOUTGET because of an error, we drive that retry
via the rpc state machine.
This means that once the call has been submitted, it runs until it
completes. So, we must move the error handling for this RPC out of the
rpc_call_done operation and into the caller.
In order to handle errors like NFS4ERR_DELAY properly, we must also
pass a pointer to the sliding timeout, which is now moved to the stack
in pnfs_update_layout.
The complicating errors are -NFS4ERR_RECALLCONFLICT and
-NFS4ERR_LAYOUTTRYLATER, as those involve a timeout after which we give
up and return NULL back to the caller. So, there is some special
handling for those errors to ensure that the layers driving the retries
can handle that appropriately.
Signed-off-by: Jeff Layton <jeff.layton@primarydata.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
2016-05-17 12:28:47 -04:00
|
|
|
|
2023-09-09 19:16:53 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-07-14 14:28:31 -04:00
|
|
|
|
2013-02-28 20:30:10 -05:00
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
2015-12-10 10:41:58 -05:00
|
|
|
|
pnfs: rework LAYOUTGET retry handling
There are several problems in the way a stateid is selected for a
LAYOUTGET operation:
We pick a stateid to use in the RPC prepare op, but that makes
it difficult to serialize LAYOUTGETs that use the open stateid. That
serialization is done in pnfs_update_layout, which occurs well before
the rpc_prepare operation.
Between those two events, the i_lock is dropped and reacquired.
pnfs_update_layout can find that the list has lsegs in it and not do any
serialization, but then later pnfs_choose_layoutget_stateid ends up
choosing the open stateid.
This patch changes the client to select the stateid to use in the
LAYOUTGET earlier, when we're searching for a usable layout segment.
This way we can do it all while holding the i_lock the first time, and
ensure that we serialize any LAYOUTGET call that uses a non-layout
stateid.
This also means a rework of how LAYOUTGET replies are handled, as we
must now get the latest stateid if we want to retransmit in response
to a retryable error.
Most of those errors boil down to the fact that the layout state has
changed in some fashion. Thus, what we really want to do is to re-search
for a layout when it fails with a retryable error, so that we can avoid
reissuing the RPC at all if possible.
While the LAYOUTGET RPC is async, the initiating thread always waits for
it to complete, so it's effectively synchronous anyway. Currently, when
we need to retry a LAYOUTGET because of an error, we drive that retry
via the rpc state machine.
This means that once the call has been submitted, it runs until it
completes. So, we must move the error handling for this RPC out of the
rpc_call_done operation and into the caller.
In order to handle errors like NFS4ERR_DELAY properly, we must also
pass a pointer to the sliding timeout, which is now moved to the stack
in pnfs_update_layout.
The complicating errors are -NFS4ERR_RECALLCONFLICT and
-NFS4ERR_LAYOUTTRYLATER, as those involve a timeout after which we give
up and return NULL back to the caller. So, there is some special
handling for those errors to ensure that the layers driving the retries
can handle that appropriately.
Signed-off-by: Jeff Layton <jeff.layton@primarydata.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
2016-05-17 12:28:47 -04:00
|
|
|
|
2015-12-10 10:41:58 -05:00
|
|
|
|
2012-09-26 11:21:40 -04:00
|
|
|
|
2015-12-10 10:41:58 -05:00
|
|
|
|
2012-05-23 05:02:37 -04:00
|
|
|
|
2015-12-10 10:41:58 -05:00
|
|
|
|
pnfs: rework LAYOUTGET retry handling
There are several problems in the way a stateid is selected for a
LAYOUTGET operation:
We pick a stateid to use in the RPC prepare op, but that makes
it difficult to serialize LAYOUTGETs that use the open stateid. That
serialization is done in pnfs_update_layout, which occurs well before
the rpc_prepare operation.
Between those two events, the i_lock is dropped and reacquired.
pnfs_update_layout can find that the list has lsegs in it and not do any
serialization, but then later pnfs_choose_layoutget_stateid ends up
choosing the open stateid.
This patch changes the client to select the stateid to use in the
LAYOUTGET earlier, when we're searching for a usable layout segment.
This way we can do it all while holding the i_lock the first time, and
ensure that we serialize any LAYOUTGET call that uses a non-layout
stateid.
This also means a rework of how LAYOUTGET replies are handled, as we
must now get the latest stateid if we want to retransmit in response
to a retryable error.
Most of those errors boil down to the fact that the layout state has
changed in some fashion. Thus, what we really want to do is to re-search
for a layout when it fails with a retryable error, so that we can avoid
reissuing the RPC at all if possible.
While the LAYOUTGET RPC is async, the initiating thread always waits for
it to complete, so it's effectively synchronous anyway. Currently, when
we need to retry a LAYOUTGET because of an error, we drive that retry
via the rpc state machine.
This means that once the call has been submitted, it runs until it
completes. So, we must move the error handling for this RPC out of the
rpc_call_done operation and into the caller.
In order to handle errors like NFS4ERR_DELAY properly, we must also
pass a pointer to the sliding timeout, which is now moved to the stack
in pnfs_update_layout.
The complicating errors are -NFS4ERR_RECALLCONFLICT and
-NFS4ERR_LAYOUTTRYLATER, as those involve a timeout after which we give
up and return NULL back to the caller. So, there is some special
handling for those errors to ensure that the layers driving the retries
can handle that appropriately.
Signed-off-by: Jeff Layton <jeff.layton@primarydata.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
2016-05-17 12:28:47 -04:00
|
|
|
|
2015-12-10 10:41:58 -05:00
|
|
|
|
2012-09-26 11:21:40 -04:00
|
|
|
|
2015-12-10 10:41:58 -05:00
|
|
|
|
2012-05-23 05:02:37 -04:00
|
|
|
|
2014-08-22 17:37:41 +08:00
|
|
|
|
2024-02-28 11:24:53 +11:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-09-05 14:07:12 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-08-22 17:37:41 +08:00
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
2011-07-30 20:52:32 -04:00
|
|
|
|
2012-09-20 21:25:19 -04:00
|
|
|
|
|
|
|
|
|
2022-05-14 10:08:11 -04:00
|
|
|
|
pnfs: rework LAYOUTGET retry handling
There are several problems in the way a stateid is selected for a
LAYOUTGET operation:
We pick a stateid to use in the RPC prepare op, but that makes
it difficult to serialize LAYOUTGETs that use the open stateid. That
serialization is done in pnfs_update_layout, which occurs well before
the rpc_prepare operation.
Between those two events, the i_lock is dropped and reacquired.
pnfs_update_layout can find that the list has lsegs in it and not do any
serialization, but then later pnfs_choose_layoutget_stateid ends up
choosing the open stateid.
This patch changes the client to select the stateid to use in the
LAYOUTGET earlier, when we're searching for a usable layout segment.
This way we can do it all while holding the i_lock the first time, and
ensure that we serialize any LAYOUTGET call that uses a non-layout
stateid.
This also means a rework of how LAYOUTGET replies are handled, as we
must now get the latest stateid if we want to retransmit in response
to a retryable error.
Most of those errors boil down to the fact that the layout state has
changed in some fashion. Thus, what we really want to do is to re-search
for a layout when it fails with a retryable error, so that we can avoid
reissuing the RPC at all if possible.
While the LAYOUTGET RPC is async, the initiating thread always waits for
it to complete, so it's effectively synchronous anyway. Currently, when
we need to retry a LAYOUTGET because of an error, we drive that retry
via the rpc state machine.
This means that once the call has been submitted, it runs until it
completes. So, we must move the error handling for this RPC out of the
rpc_call_done operation and into the caller.
In order to handle errors like NFS4ERR_DELAY properly, we must also
pass a pointer to the sliding timeout, which is now moved to the stack
in pnfs_update_layout.
The complicating errors are -NFS4ERR_RECALLCONFLICT and
-NFS4ERR_LAYOUTTRYLATER, as those involve a timeout after which we give
up and return NULL back to the caller. So, there is some special
handling for those errors to ensure that the layers driving the retries
can handle that appropriately.
Signed-off-by: Jeff Layton <jeff.layton@primarydata.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
2016-05-17 12:28:47 -04:00
|
|
|
|
2015-12-10 10:41:58 -05:00
|
|
|
|
2012-09-20 21:25:19 -04:00
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
2011-01-06 11:36:30 +00:00
|
|
|
|
2012-03-01 11:17:47 -05:00
|
|
|
|
pnfs: rework LAYOUTGET retry handling
There are several problems in the way a stateid is selected for a
LAYOUTGET operation:
We pick a stateid to use in the RPC prepare op, but that makes
it difficult to serialize LAYOUTGETs that use the open stateid. That
serialization is done in pnfs_update_layout, which occurs well before
the rpc_prepare operation.
Between those two events, the i_lock is dropped and reacquired.
pnfs_update_layout can find that the list has lsegs in it and not do any
serialization, but then later pnfs_choose_layoutget_stateid ends up
choosing the open stateid.
This patch changes the client to select the stateid to use in the
LAYOUTGET earlier, when we're searching for a usable layout segment.
This way we can do it all while holding the i_lock the first time, and
ensure that we serialize any LAYOUTGET call that uses a non-layout
stateid.
This also means a rework of how LAYOUTGET replies are handled, as we
must now get the latest stateid if we want to retransmit in response
to a retryable error.
Most of those errors boil down to the fact that the layout state has
changed in some fashion. Thus, what we really want to do is to re-search
for a layout when it fails with a retryable error, so that we can avoid
reissuing the RPC at all if possible.
While the LAYOUTGET RPC is async, the initiating thread always waits for
it to complete, so it's effectively synchronous anyway. Currently, when
we need to retry a LAYOUTGET because of an error, we drive that retry
via the rpc state machine.
This means that once the call has been submitted, it runs until it
completes. So, we must move the error handling for this RPC out of the
rpc_call_done operation and into the caller.
In order to handle errors like NFS4ERR_DELAY properly, we must also
pass a pointer to the sliding timeout, which is now moved to the stack
in pnfs_update_layout.
The complicating errors are -NFS4ERR_RECALLCONFLICT and
-NFS4ERR_LAYOUTTRYLATER, as those involve a timeout after which we give
up and return NULL back to the caller. So, there is some special
handling for those errors to ensure that the layers driving the retries
can handle that appropriately.
Signed-off-by: Jeff Layton <jeff.layton@primarydata.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
2016-05-17 12:28:47 -04:00
|
|
|
|
2015-12-10 10:41:58 -05:00
|
|
|
|
2011-01-06 11:36:30 +00:00
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-12-14 16:25:11 -05:00
|
|
|
|
pnfs: rework LAYOUTGET retry handling
There are several problems in the way a stateid is selected for a
LAYOUTGET operation:
We pick a stateid to use in the RPC prepare op, but that makes
it difficult to serialize LAYOUTGETs that use the open stateid. That
serialization is done in pnfs_update_layout, which occurs well before
the rpc_prepare operation.
Between those two events, the i_lock is dropped and reacquired.
pnfs_update_layout can find that the list has lsegs in it and not do any
serialization, but then later pnfs_choose_layoutget_stateid ends up
choosing the open stateid.
This patch changes the client to select the stateid to use in the
LAYOUTGET earlier, when we're searching for a usable layout segment.
This way we can do it all while holding the i_lock the first time, and
ensure that we serialize any LAYOUTGET call that uses a non-layout
stateid.
This also means a rework of how LAYOUTGET replies are handled, as we
must now get the latest stateid if we want to retransmit in response
to a retryable error.
Most of those errors boil down to the fact that the layout state has
changed in some fashion. Thus, what we really want to do is to re-search
for a layout when it fails with a retryable error, so that we can avoid
reissuing the RPC at all if possible.
While the LAYOUTGET RPC is async, the initiating thread always waits for
it to complete, so it's effectively synchronous anyway. Currently, when
we need to retry a LAYOUTGET because of an error, we drive that retry
via the rpc state machine.
This means that once the call has been submitted, it runs until it
completes. So, we must move the error handling for this RPC out of the
rpc_call_done operation and into the caller.
In order to handle errors like NFS4ERR_DELAY properly, we must also
pass a pointer to the sliding timeout, which is now moved to the stack
in pnfs_update_layout.
The complicating errors are -NFS4ERR_RECALLCONFLICT and
-NFS4ERR_LAYOUTTRYLATER, as those involve a timeout after which we give
up and return NULL back to the caller. So, there is some special
handling for those errors to ensure that the layers driving the retries
can handle that appropriately.
Signed-off-by: Jeff Layton <jeff.layton@primarydata.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
2016-05-17 12:28:47 -04:00
|
|
|
|
2015-12-10 10:41:58 -05:00
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
2015-12-10 10:41:58 -05:00
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
2018-06-23 22:54:33 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-05-31 11:03:07 -04:00
|
|
|
|
2018-06-23 22:54:33 -04:00
|
|
|
|
|
|
|
|
|
2022-05-31 11:03:07 -04:00
|
|
|
|
|
|
|
|
|
2019-07-18 15:33:42 -04:00
|
|
|
|
2018-06-23 22:54:33 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-01-05 06:43:45 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-05-18 13:10:36 +00:00
|
|
|
|
2021-01-05 06:43:45 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-05-25 07:31:14 -07:00
|
|
|
|
pnfs: rework LAYOUTGET retry handling
There are several problems in the way a stateid is selected for a
LAYOUTGET operation:
We pick a stateid to use in the RPC prepare op, but that makes
it difficult to serialize LAYOUTGETs that use the open stateid. That
serialization is done in pnfs_update_layout, which occurs well before
the rpc_prepare operation.
Between those two events, the i_lock is dropped and reacquired.
pnfs_update_layout can find that the list has lsegs in it and not do any
serialization, but then later pnfs_choose_layoutget_stateid ends up
choosing the open stateid.
This patch changes the client to select the stateid to use in the
LAYOUTGET earlier, when we're searching for a usable layout segment.
This way we can do it all while holding the i_lock the first time, and
ensure that we serialize any LAYOUTGET call that uses a non-layout
stateid.
This also means a rework of how LAYOUTGET replies are handled, as we
must now get the latest stateid if we want to retransmit in response
to a retryable error.
Most of those errors boil down to the fact that the layout state has
changed in some fashion. Thus, what we really want to do is to re-search
for a layout when it fails with a retryable error, so that we can avoid
reissuing the RPC at all if possible.
While the LAYOUTGET RPC is async, the initiating thread always waits for
it to complete, so it's effectively synchronous anyway. Currently, when
we need to retry a LAYOUTGET because of an error, we drive that retry
via the rpc state machine.
This means that once the call has been submitted, it runs until it
completes. So, we must move the error handling for this RPC out of the
rpc_call_done operation and into the caller.
In order to handle errors like NFS4ERR_DELAY properly, we must also
pass a pointer to the sliding timeout, which is now moved to the stack
in pnfs_update_layout.
The complicating errors are -NFS4ERR_RECALLCONFLICT and
-NFS4ERR_LAYOUTTRYLATER, as those involve a timeout after which we give
up and return NULL back to the caller. So, there is some special
handling for those errors to ensure that the layers driving the retries
can handle that appropriately.
Signed-off-by: Jeff Layton <jeff.layton@primarydata.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
2016-05-17 12:28:47 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-06-17 16:48:19 -04:00
|
|
|
|
2019-07-16 15:38:28 -04:00
|
|
|
|
pnfs: rework LAYOUTGET retry handling
There are several problems in the way a stateid is selected for a
LAYOUTGET operation:
We pick a stateid to use in the RPC prepare op, but that makes
it difficult to serialize LAYOUTGETs that use the open stateid. That
serialization is done in pnfs_update_layout, which occurs well before
the rpc_prepare operation.
Between those two events, the i_lock is dropped and reacquired.
pnfs_update_layout can find that the list has lsegs in it and not do any
serialization, but then later pnfs_choose_layoutget_stateid ends up
choosing the open stateid.
This patch changes the client to select the stateid to use in the
LAYOUTGET earlier, when we're searching for a usable layout segment.
This way we can do it all while holding the i_lock the first time, and
ensure that we serialize any LAYOUTGET call that uses a non-layout
stateid.
This also means a rework of how LAYOUTGET replies are handled, as we
must now get the latest stateid if we want to retransmit in response
to a retryable error.
Most of those errors boil down to the fact that the layout state has
changed in some fashion. Thus, what we really want to do is to re-search
for a layout when it fails with a retryable error, so that we can avoid
reissuing the RPC at all if possible.
While the LAYOUTGET RPC is async, the initiating thread always waits for
it to complete, so it's effectively synchronous anyway. Currently, when
we need to retry a LAYOUTGET because of an error, we drive that retry
via the rpc state machine.
This means that once the call has been submitted, it runs until it
completes. So, we must move the error handling for this RPC out of the
rpc_call_done operation and into the caller.
In order to handle errors like NFS4ERR_DELAY properly, we must also
pass a pointer to the sliding timeout, which is now moved to the stack
in pnfs_update_layout.
The complicating errors are -NFS4ERR_RECALLCONFLICT and
-NFS4ERR_LAYOUTTRYLATER, as those involve a timeout after which we give
up and return NULL back to the caller. So, there is some special
handling for those errors to ensure that the layers driving the retries
can handle that appropriately.
Signed-off-by: Jeff Layton <jeff.layton@primarydata.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
2016-05-17 12:28:47 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-08-22 17:37:41 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-09-05 14:07:12 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-08-22 17:37:41 +08:00
|
|
|
|
pnfs: rework LAYOUTGET retry handling
There are several problems in the way a stateid is selected for a
LAYOUTGET operation:
We pick a stateid to use in the RPC prepare op, but that makes
it difficult to serialize LAYOUTGETs that use the open stateid. That
serialization is done in pnfs_update_layout, which occurs well before
the rpc_prepare operation.
Between those two events, the i_lock is dropped and reacquired.
pnfs_update_layout can find that the list has lsegs in it and not do any
serialization, but then later pnfs_choose_layoutget_stateid ends up
choosing the open stateid.
This patch changes the client to select the stateid to use in the
LAYOUTGET earlier, when we're searching for a usable layout segment.
This way we can do it all while holding the i_lock the first time, and
ensure that we serialize any LAYOUTGET call that uses a non-layout
stateid.
This also means a rework of how LAYOUTGET replies are handled, as we
must now get the latest stateid if we want to retransmit in response
to a retryable error.
Most of those errors boil down to the fact that the layout state has
changed in some fashion. Thus, what we really want to do is to re-search
for a layout when it fails with a retryable error, so that we can avoid
reissuing the RPC at all if possible.
While the LAYOUTGET RPC is async, the initiating thread always waits for
it to complete, so it's effectively synchronous anyway. Currently, when
we need to retry a LAYOUTGET because of an error, we drive that retry
via the rpc state machine.
This means that once the call has been submitted, it runs until it
completes. So, we must move the error handling for this RPC out of the
rpc_call_done operation and into the caller.
In order to handle errors like NFS4ERR_DELAY properly, we must also
pass a pointer to the sliding timeout, which is now moved to the stack
in pnfs_update_layout.
The complicating errors are -NFS4ERR_RECALLCONFLICT and
-NFS4ERR_LAYOUTTRYLATER, as those involve a timeout after which we give
up and return NULL back to the caller. So, there is some special
handling for those errors to ensure that the layers driving the retries
can handle that appropriately.
Signed-off-by: Jeff Layton <jeff.layton@primarydata.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
2016-05-17 12:28:47 -04:00
|
|
|
|
2014-08-22 17:37:41 +08:00
|
|
|
|
|
|
|
|
|
pnfs: rework LAYOUTGET retry handling
There are several problems in the way a stateid is selected for a
LAYOUTGET operation:
We pick a stateid to use in the RPC prepare op, but that makes
it difficult to serialize LAYOUTGETs that use the open stateid. That
serialization is done in pnfs_update_layout, which occurs well before
the rpc_prepare operation.
Between those two events, the i_lock is dropped and reacquired.
pnfs_update_layout can find that the list has lsegs in it and not do any
serialization, but then later pnfs_choose_layoutget_stateid ends up
choosing the open stateid.
This patch changes the client to select the stateid to use in the
LAYOUTGET earlier, when we're searching for a usable layout segment.
This way we can do it all while holding the i_lock the first time, and
ensure that we serialize any LAYOUTGET call that uses a non-layout
stateid.
This also means a rework of how LAYOUTGET replies are handled, as we
must now get the latest stateid if we want to retransmit in response
to a retryable error.
Most of those errors boil down to the fact that the layout state has
changed in some fashion. Thus, what we really want to do is to re-search
for a layout when it fails with a retryable error, so that we can avoid
reissuing the RPC at all if possible.
While the LAYOUTGET RPC is async, the initiating thread always waits for
it to complete, so it's effectively synchronous anyway. Currently, when
we need to retry a LAYOUTGET because of an error, we drive that retry
via the rpc state machine.
This means that once the call has been submitted, it runs until it
completes. So, we must move the error handling for this RPC out of the
rpc_call_done operation and into the caller.
In order to handle errors like NFS4ERR_DELAY properly, we must also
pass a pointer to the sliding timeout, which is now moved to the stack
in pnfs_update_layout.
The complicating errors are -NFS4ERR_RECALLCONFLICT and
-NFS4ERR_LAYOUTTRYLATER, as those involve a timeout after which we give
up and return NULL back to the caller. So, there is some special
handling for those errors to ensure that the layers driving the retries
can handle that appropriately.
Signed-off-by: Jeff Layton <jeff.layton@primarydata.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
2016-05-17 12:28:47 -04:00
|
|
|
|
2020-04-13 15:55:21 -04:00
|
|
|
|
pnfs: rework LAYOUTGET retry handling
There are several problems in the way a stateid is selected for a
LAYOUTGET operation:
We pick a stateid to use in the RPC prepare op, but that makes
it difficult to serialize LAYOUTGETs that use the open stateid. That
serialization is done in pnfs_update_layout, which occurs well before
the rpc_prepare operation.
Between those two events, the i_lock is dropped and reacquired.
pnfs_update_layout can find that the list has lsegs in it and not do any
serialization, but then later pnfs_choose_layoutget_stateid ends up
choosing the open stateid.
This patch changes the client to select the stateid to use in the
LAYOUTGET earlier, when we're searching for a usable layout segment.
This way we can do it all while holding the i_lock the first time, and
ensure that we serialize any LAYOUTGET call that uses a non-layout
stateid.
This also means a rework of how LAYOUTGET replies are handled, as we
must now get the latest stateid if we want to retransmit in response
to a retryable error.
Most of those errors boil down to the fact that the layout state has
changed in some fashion. Thus, what we really want to do is to re-search
for a layout when it fails with a retryable error, so that we can avoid
reissuing the RPC at all if possible.
While the LAYOUTGET RPC is async, the initiating thread always waits for
it to complete, so it's effectively synchronous anyway. Currently, when
we need to retry a LAYOUTGET because of an error, we drive that retry
via the rpc state machine.
This means that once the call has been submitted, it runs until it
completes. So, we must move the error handling for this RPC out of the
rpc_call_done operation and into the caller.
In order to handle errors like NFS4ERR_DELAY properly, we must also
pass a pointer to the sliding timeout, which is now moved to the stack
in pnfs_update_layout.
The complicating errors are -NFS4ERR_RECALLCONFLICT and
-NFS4ERR_LAYOUTTRYLATER, as those involve a timeout after which we give
up and return NULL back to the caller. So, there is some special
handling for those errors to ensure that the layers driving the retries
can handle that appropriately.
Signed-off-by: Jeff Layton <jeff.layton@primarydata.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
2016-05-17 12:28:47 -04:00
|
|
|
|
2019-07-16 15:38:28 -04:00
|
|
|
|
2017-09-11 13:09:37 -04:00
|
|
|
|
2019-07-16 15:38:28 -04:00
|
|
|
|
|
|
|
|
|
2019-07-22 18:06:17 +01:00
|
|
|
|
2017-09-11 13:09:37 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-07-16 15:38:28 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-09-11 13:09:37 -04:00
|
|
|
|
2020-04-13 15:55:21 -04:00
|
|
|
|
2014-08-22 17:37:41 +08:00
|
|
|
|
pnfs: rework LAYOUTGET retry handling
There are several problems in the way a stateid is selected for a
LAYOUTGET operation:
We pick a stateid to use in the RPC prepare op, but that makes
it difficult to serialize LAYOUTGETs that use the open stateid. That
serialization is done in pnfs_update_layout, which occurs well before
the rpc_prepare operation.
Between those two events, the i_lock is dropped and reacquired.
pnfs_update_layout can find that the list has lsegs in it and not do any
serialization, but then later pnfs_choose_layoutget_stateid ends up
choosing the open stateid.
This patch changes the client to select the stateid to use in the
LAYOUTGET earlier, when we're searching for a usable layout segment.
This way we can do it all while holding the i_lock the first time, and
ensure that we serialize any LAYOUTGET call that uses a non-layout
stateid.
This also means a rework of how LAYOUTGET replies are handled, as we
must now get the latest stateid if we want to retransmit in response
to a retryable error.
Most of those errors boil down to the fact that the layout state has
changed in some fashion. Thus, what we really want to do is to re-search
for a layout when it fails with a retryable error, so that we can avoid
reissuing the RPC at all if possible.
While the LAYOUTGET RPC is async, the initiating thread always waits for
it to complete, so it's effectively synchronous anyway. Currently, when
we need to retry a LAYOUTGET because of an error, we drive that retry
via the rpc state machine.
This means that once the call has been submitted, it runs until it
completes. So, we must move the error handling for this RPC out of the
rpc_call_done operation and into the caller.
In order to handle errors like NFS4ERR_DELAY properly, we must also
pass a pointer to the sliding timeout, which is now moved to the stack
in pnfs_update_layout.
The complicating errors are -NFS4ERR_RECALLCONFLICT and
-NFS4ERR_LAYOUTTRYLATER, as those involve a timeout after which we give
up and return NULL back to the caller. So, there is some special
handling for those errors to ensure that the layers driving the retries
can handle that appropriately.
Signed-off-by: Jeff Layton <jeff.layton@primarydata.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
2016-05-17 12:28:47 -04:00
|
|
|
|
2014-08-22 17:37:41 +08:00
|
|
|
|
2011-03-01 01:34:22 +00:00
|
|
|
|
2015-12-10 10:41:58 -05:00
|
|
|
|
pnfs: rework LAYOUTGET retry handling
There are several problems in the way a stateid is selected for a
LAYOUTGET operation:
We pick a stateid to use in the RPC prepare op, but that makes
it difficult to serialize LAYOUTGETs that use the open stateid. That
serialization is done in pnfs_update_layout, which occurs well before
the rpc_prepare operation.
Between those two events, the i_lock is dropped and reacquired.
pnfs_update_layout can find that the list has lsegs in it and not do any
serialization, but then later pnfs_choose_layoutget_stateid ends up
choosing the open stateid.
This patch changes the client to select the stateid to use in the
LAYOUTGET earlier, when we're searching for a usable layout segment.
This way we can do it all while holding the i_lock the first time, and
ensure that we serialize any LAYOUTGET call that uses a non-layout
stateid.
This also means a rework of how LAYOUTGET replies are handled, as we
must now get the latest stateid if we want to retransmit in response
to a retryable error.
Most of those errors boil down to the fact that the layout state has
changed in some fashion. Thus, what we really want to do is to re-search
for a layout when it fails with a retryable error, so that we can avoid
reissuing the RPC at all if possible.
While the LAYOUTGET RPC is async, the initiating thread always waits for
it to complete, so it's effectively synchronous anyway. Currently, when
we need to retry a LAYOUTGET because of an error, we drive that retry
via the rpc state machine.
This means that once the call has been submitted, it runs until it
completes. So, we must move the error handling for this RPC out of the
rpc_call_done operation and into the caller.
In order to handle errors like NFS4ERR_DELAY properly, we must also
pass a pointer to the sliding timeout, which is now moved to the stack
in pnfs_update_layout.
The complicating errors are -NFS4ERR_RECALLCONFLICT and
-NFS4ERR_LAYOUTTRYLATER, as those involve a timeout after which we give
up and return NULL back to the caller. So, there is some special
handling for those errors to ensure that the layers driving the retries
can handle that appropriately.
Signed-off-by: Jeff Layton <jeff.layton@primarydata.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
2016-05-17 12:28:47 -04:00
|
|
|
|
2015-12-10 10:41:58 -05:00
|
|
|
|
2011-01-06 11:36:25 +00:00
|
|
|
|
2015-12-10 10:41:58 -05:00
|
|
|
|
2018-06-23 22:54:33 -04:00
|
|
|
|
2011-02-03 18:28:52 +00:00
|
|
|
|
2013-02-28 20:30:10 -05:00
|
|
|
|
2016-09-22 12:30:20 -04:00
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
mm, fs: get rid of PAGE_CACHE_* and page_cache_{get,release} macros
PAGE_CACHE_{SIZE,SHIFT,MASK,ALIGN} macros were introduced *long* time
ago with promise that one day it will be possible to implement page
cache with bigger chunks than PAGE_SIZE.
This promise never materialized. And unlikely will.
We have many places where PAGE_CACHE_SIZE assumed to be equal to
PAGE_SIZE. And it's constant source of confusion on whether
PAGE_CACHE_* or PAGE_* constant should be used in a particular case,
especially on the border between fs and mm.
Global switching to PAGE_CACHE_SIZE != PAGE_SIZE would cause to much
breakage to be doable.
Let's stop pretending that pages in page cache are special. They are
not.
The changes are pretty straight-forward:
- <foo> << (PAGE_CACHE_SHIFT - PAGE_SHIFT) -> <foo>;
- <foo> >> (PAGE_CACHE_SHIFT - PAGE_SHIFT) -> <foo>;
- PAGE_CACHE_{SIZE,SHIFT,MASK,ALIGN} -> PAGE_{SIZE,SHIFT,MASK,ALIGN};
- page_cache_get() -> get_page();
- page_cache_release() -> put_page();
This patch contains automated changes generated with coccinelle using
script below. For some reason, coccinelle doesn't patch header files.
I've called spatch for them manually.
The only adjustment after coccinelle is revert of changes to
PAGE_CAHCE_ALIGN definition: we are going to drop it later.
There are few places in the code where coccinelle didn't reach. I'll
fix them manually in a separate patch. Comments and documentation also
will be addressed with the separate patch.
virtual patch
@@
expression E;
@@
- E << (PAGE_CACHE_SHIFT - PAGE_SHIFT)
+ E
@@
expression E;
@@
- E >> (PAGE_CACHE_SHIFT - PAGE_SHIFT)
+ E
@@
@@
- PAGE_CACHE_SHIFT
+ PAGE_SHIFT
@@
@@
- PAGE_CACHE_SIZE
+ PAGE_SIZE
@@
@@
- PAGE_CACHE_MASK
+ PAGE_MASK
@@
expression E;
@@
- PAGE_CACHE_ALIGN(E)
+ PAGE_ALIGN(E)
@@
expression E;
@@
- page_cache_get(E)
+ get_page(E)
@@
expression E;
@@
- page_cache_release(E)
+ put_page(E)
Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
Acked-by: Michal Hocko <mhocko@suse.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2016-04-01 15:29:47 +03:00
|
|
|
|
2011-05-22 19:47:46 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-06-13 18:22:38 -04:00
|
|
|
|
mm, fs: get rid of PAGE_CACHE_* and page_cache_{get,release} macros
PAGE_CACHE_{SIZE,SHIFT,MASK,ALIGN} macros were introduced *long* time
ago with promise that one day it will be possible to implement page
cache with bigger chunks than PAGE_SIZE.
This promise never materialized. And unlikely will.
We have many places where PAGE_CACHE_SIZE assumed to be equal to
PAGE_SIZE. And it's constant source of confusion on whether
PAGE_CACHE_* or PAGE_* constant should be used in a particular case,
especially on the border between fs and mm.
Global switching to PAGE_CACHE_SIZE != PAGE_SIZE would cause to much
breakage to be doable.
Let's stop pretending that pages in page cache are special. They are
not.
The changes are pretty straight-forward:
- <foo> << (PAGE_CACHE_SHIFT - PAGE_SHIFT) -> <foo>;
- <foo> >> (PAGE_CACHE_SHIFT - PAGE_SHIFT) -> <foo>;
- PAGE_CACHE_{SIZE,SHIFT,MASK,ALIGN} -> PAGE_{SIZE,SHIFT,MASK,ALIGN};
- page_cache_get() -> get_page();
- page_cache_release() -> put_page();
This patch contains automated changes generated with coccinelle using
script below. For some reason, coccinelle doesn't patch header files.
I've called spatch for them manually.
The only adjustment after coccinelle is revert of changes to
PAGE_CAHCE_ALIGN definition: we are going to drop it later.
There are few places in the code where coccinelle didn't reach. I'll
fix them manually in a separate patch. Comments and documentation also
will be addressed with the separate patch.
virtual patch
@@
expression E;
@@
- E << (PAGE_CACHE_SHIFT - PAGE_SHIFT)
+ E
@@
expression E;
@@
- E >> (PAGE_CACHE_SHIFT - PAGE_SHIFT)
+ E
@@
@@
- PAGE_CACHE_SHIFT
+ PAGE_SHIFT
@@
@@
- PAGE_CACHE_SIZE
+ PAGE_SIZE
@@
@@
- PAGE_CACHE_MASK
+ PAGE_MASK
@@
expression E;
@@
- PAGE_CACHE_ALIGN(E)
+ PAGE_ALIGN(E)
@@
expression E;
@@
- page_cache_get(E)
+ get_page(E)
@@
expression E;
@@
- page_cache_release(E)
+ put_page(E)
Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
Acked-by: Michal Hocko <mhocko@suse.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2016-04-01 15:29:47 +03:00
|
|
|
|
2011-05-22 19:47:46 +03:00
|
|
|
|
2016-10-06 12:08:51 -04:00
|
|
|
|
2016-09-21 05:14:28 -04:00
|
|
|
|
2022-05-14 10:08:11 -04:00
|
|
|
|
2016-09-21 05:14:28 -04:00
|
|
|
|
|
|
|
|
|
2018-06-23 22:54:33 -04:00
|
|
|
|
2016-09-21 05:14:28 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-07-02 17:24:22 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-09-09 19:16:53 -04:00
|
|
|
|
pnfs: rework LAYOUTGET retry handling
There are several problems in the way a stateid is selected for a
LAYOUTGET operation:
We pick a stateid to use in the RPC prepare op, but that makes
it difficult to serialize LAYOUTGETs that use the open stateid. That
serialization is done in pnfs_update_layout, which occurs well before
the rpc_prepare operation.
Between those two events, the i_lock is dropped and reacquired.
pnfs_update_layout can find that the list has lsegs in it and not do any
serialization, but then later pnfs_choose_layoutget_stateid ends up
choosing the open stateid.
This patch changes the client to select the stateid to use in the
LAYOUTGET earlier, when we're searching for a usable layout segment.
This way we can do it all while holding the i_lock the first time, and
ensure that we serialize any LAYOUTGET call that uses a non-layout
stateid.
This also means a rework of how LAYOUTGET replies are handled, as we
must now get the latest stateid if we want to retransmit in response
to a retryable error.
Most of those errors boil down to the fact that the layout state has
changed in some fashion. Thus, what we really want to do is to re-search
for a layout when it fails with a retryable error, so that we can avoid
reissuing the RPC at all if possible.
While the LAYOUTGET RPC is async, the initiating thread always waits for
it to complete, so it's effectively synchronous anyway. Currently, when
we need to retry a LAYOUTGET because of an error, we drive that retry
via the rpc state machine.
This means that once the call has been submitted, it runs until it
completes. So, we must move the error handling for this RPC out of the
rpc_call_done operation and into the caller.
In order to handle errors like NFS4ERR_DELAY properly, we must also
pass a pointer to the sliding timeout, which is now moved to the stack
in pnfs_update_layout.
The complicating errors are -NFS4ERR_RECALLCONFLICT and
-NFS4ERR_LAYOUTTRYLATER, as those involve a timeout after which we give
up and return NULL back to the caller. So, there is some special
handling for those errors to ensure that the layers driving the retries
can handle that appropriately.
Signed-off-by: Jeff Layton <jeff.layton@primarydata.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
2016-05-17 12:28:47 -04:00
|
|
|
|
|
|
|
|
|
2018-06-23 22:54:33 -04:00
|
|
|
|
2016-05-17 12:28:46 -04:00
|
|
|
|
pnfs: rework LAYOUTGET retry handling
There are several problems in the way a stateid is selected for a
LAYOUTGET operation:
We pick a stateid to use in the RPC prepare op, but that makes
it difficult to serialize LAYOUTGETs that use the open stateid. That
serialization is done in pnfs_update_layout, which occurs well before
the rpc_prepare operation.
Between those two events, the i_lock is dropped and reacquired.
pnfs_update_layout can find that the list has lsegs in it and not do any
serialization, but then later pnfs_choose_layoutget_stateid ends up
choosing the open stateid.
This patch changes the client to select the stateid to use in the
LAYOUTGET earlier, when we're searching for a usable layout segment.
This way we can do it all while holding the i_lock the first time, and
ensure that we serialize any LAYOUTGET call that uses a non-layout
stateid.
This also means a rework of how LAYOUTGET replies are handled, as we
must now get the latest stateid if we want to retransmit in response
to a retryable error.
Most of those errors boil down to the fact that the layout state has
changed in some fashion. Thus, what we really want to do is to re-search
for a layout when it fails with a retryable error, so that we can avoid
reissuing the RPC at all if possible.
While the LAYOUTGET RPC is async, the initiating thread always waits for
it to complete, so it's effectively synchronous anyway. Currently, when
we need to retry a LAYOUTGET because of an error, we drive that retry
via the rpc state machine.
This means that once the call has been submitted, it runs until it
completes. So, we must move the error handling for this RPC out of the
rpc_call_done operation and into the caller.
In order to handle errors like NFS4ERR_DELAY properly, we must also
pass a pointer to the sliding timeout, which is now moved to the stack
in pnfs_update_layout.
The complicating errors are -NFS4ERR_RECALLCONFLICT and
-NFS4ERR_LAYOUTTRYLATER, as those involve a timeout after which we give
up and return NULL back to the caller. So, there is some special
handling for those errors to ensure that the layers driving the retries
can handle that appropriately.
Signed-off-by: Jeff Layton <jeff.layton@primarydata.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
2016-05-17 12:28:47 -04:00
|
|
|
|
2016-07-14 18:46:24 -04:00
|
|
|
|
pnfs: rework LAYOUTGET retry handling
There are several problems in the way a stateid is selected for a
LAYOUTGET operation:
We pick a stateid to use in the RPC prepare op, but that makes
it difficult to serialize LAYOUTGETs that use the open stateid. That
serialization is done in pnfs_update_layout, which occurs well before
the rpc_prepare operation.
Between those two events, the i_lock is dropped and reacquired.
pnfs_update_layout can find that the list has lsegs in it and not do any
serialization, but then later pnfs_choose_layoutget_stateid ends up
choosing the open stateid.
This patch changes the client to select the stateid to use in the
LAYOUTGET earlier, when we're searching for a usable layout segment.
This way we can do it all while holding the i_lock the first time, and
ensure that we serialize any LAYOUTGET call that uses a non-layout
stateid.
This also means a rework of how LAYOUTGET replies are handled, as we
must now get the latest stateid if we want to retransmit in response
to a retryable error.
Most of those errors boil down to the fact that the layout state has
changed in some fashion. Thus, what we really want to do is to re-search
for a layout when it fails with a retryable error, so that we can avoid
reissuing the RPC at all if possible.
While the LAYOUTGET RPC is async, the initiating thread always waits for
it to complete, so it's effectively synchronous anyway. Currently, when
we need to retry a LAYOUTGET because of an error, we drive that retry
via the rpc state machine.
This means that once the call has been submitted, it runs until it
completes. So, we must move the error handling for this RPC out of the
rpc_call_done operation and into the caller.
In order to handle errors like NFS4ERR_DELAY properly, we must also
pass a pointer to the sliding timeout, which is now moved to the stack
in pnfs_update_layout.
The complicating errors are -NFS4ERR_RECALLCONFLICT and
-NFS4ERR_LAYOUTTRYLATER, as those involve a timeout after which we give
up and return NULL back to the caller. So, there is some special
handling for those errors to ensure that the layers driving the retries
can handle that appropriately.
Signed-off-by: Jeff Layton <jeff.layton@primarydata.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
2016-05-17 12:28:47 -04:00
|
|
|
|
|
|
|
|
|
2016-07-14 14:28:31 -04:00
|
|
|
|
|
|
|
|
|
pnfs: rework LAYOUTGET retry handling
There are several problems in the way a stateid is selected for a
LAYOUTGET operation:
We pick a stateid to use in the RPC prepare op, but that makes
it difficult to serialize LAYOUTGETs that use the open stateid. That
serialization is done in pnfs_update_layout, which occurs well before
the rpc_prepare operation.
Between those two events, the i_lock is dropped and reacquired.
pnfs_update_layout can find that the list has lsegs in it and not do any
serialization, but then later pnfs_choose_layoutget_stateid ends up
choosing the open stateid.
This patch changes the client to select the stateid to use in the
LAYOUTGET earlier, when we're searching for a usable layout segment.
This way we can do it all while holding the i_lock the first time, and
ensure that we serialize any LAYOUTGET call that uses a non-layout
stateid.
This also means a rework of how LAYOUTGET replies are handled, as we
must now get the latest stateid if we want to retransmit in response
to a retryable error.
Most of those errors boil down to the fact that the layout state has
changed in some fashion. Thus, what we really want to do is to re-search
for a layout when it fails with a retryable error, so that we can avoid
reissuing the RPC at all if possible.
While the LAYOUTGET RPC is async, the initiating thread always waits for
it to complete, so it's effectively synchronous anyway. Currently, when
we need to retry a LAYOUTGET because of an error, we drive that retry
via the rpc state machine.
This means that once the call has been submitted, it runs until it
completes. So, we must move the error handling for this RPC out of the
rpc_call_done operation and into the caller.
In order to handle errors like NFS4ERR_DELAY properly, we must also
pass a pointer to the sliding timeout, which is now moved to the stack
in pnfs_update_layout.
The complicating errors are -NFS4ERR_RECALLCONFLICT and
-NFS4ERR_LAYOUTTRYLATER, as those involve a timeout after which we give
up and return NULL back to the caller. So, there is some special
handling for those errors to ensure that the layers driving the retries
can handle that appropriately.
Signed-off-by: Jeff Layton <jeff.layton@primarydata.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
2016-05-17 12:28:47 -04:00
|
|
|
|
2016-07-14 18:34:12 -04:00
|
|
|
|
2022-05-31 11:03:06 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
pnfs: rework LAYOUTGET retry handling
There are several problems in the way a stateid is selected for a
LAYOUTGET operation:
We pick a stateid to use in the RPC prepare op, but that makes
it difficult to serialize LAYOUTGETs that use the open stateid. That
serialization is done in pnfs_update_layout, which occurs well before
the rpc_prepare operation.
Between those two events, the i_lock is dropped and reacquired.
pnfs_update_layout can find that the list has lsegs in it and not do any
serialization, but then later pnfs_choose_layoutget_stateid ends up
choosing the open stateid.
This patch changes the client to select the stateid to use in the
LAYOUTGET earlier, when we're searching for a usable layout segment.
This way we can do it all while holding the i_lock the first time, and
ensure that we serialize any LAYOUTGET call that uses a non-layout
stateid.
This also means a rework of how LAYOUTGET replies are handled, as we
must now get the latest stateid if we want to retransmit in response
to a retryable error.
Most of those errors boil down to the fact that the layout state has
changed in some fashion. Thus, what we really want to do is to re-search
for a layout when it fails with a retryable error, so that we can avoid
reissuing the RPC at all if possible.
While the LAYOUTGET RPC is async, the initiating thread always waits for
it to complete, so it's effectively synchronous anyway. Currently, when
we need to retry a LAYOUTGET because of an error, we drive that retry
via the rpc state machine.
This means that once the call has been submitted, it runs until it
completes. So, we must move the error handling for this RPC out of the
rpc_call_done operation and into the caller.
In order to handle errors like NFS4ERR_DELAY properly, we must also
pass a pointer to the sliding timeout, which is now moved to the stack
in pnfs_update_layout.
The complicating errors are -NFS4ERR_RECALLCONFLICT and
-NFS4ERR_LAYOUTTRYLATER, as those involve a timeout after which we give
up and return NULL back to the caller. So, there is some special
handling for those errors to ensure that the layers driving the retries
can handle that appropriately.
Signed-off-by: Jeff Layton <jeff.layton@primarydata.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
2016-05-17 12:28:47 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-07-14 18:34:12 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-09-09 19:16:53 -04:00
|
|
|
|
|
|
|
|
|
2016-07-14 18:34:12 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-05-17 12:28:46 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-20 21:25:19 -04:00
|
|
|
|
2014-12-11 17:02:04 -05:00
|
|
|
|
|
|
|
|
|
2019-07-18 09:32:17 -04:00
|
|
|
|
|
|
|
|
|
2012-09-18 20:51:13 -04:00
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
2012-09-26 11:21:40 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-05-12 12:12:44 -04:00
|
|
|
|
2015-12-04 02:57:48 +08:00
|
|
|
|
2012-09-26 11:21:40 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-20 21:25:19 -04:00
|
|
|
|
2010-10-20 00:18:01 -04:00
|
|
|
|
2011-06-13 18:22:38 -04:00
|
|
|
|
2010-10-20 00:18:03 -04:00
|
|
|
|
2015-08-25 11:16:13 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-09-22 12:30:20 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-03-21 15:32:09 -04:00
|
|
|
|
2016-09-22 12:30:20 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-06-23 22:54:33 -04:00
|
|
|
|
2016-09-22 12:30:20 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-10-06 12:11:21 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-09-22 12:30:20 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-02 12:26:38 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-09-22 12:30:20 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-03-21 15:32:09 -04:00
|
|
|
|
|
|
|
|
|
2016-09-22 12:30:20 -04:00
|
|
|
|
|
|
|
|
|
2021-01-06 14:13:22 -05:00
|
|
|
|
2016-09-22 12:30:20 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-07-02 17:24:22 -04:00
|
|
|
|
2016-09-22 12:30:20 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-10-06 12:11:21 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-07-02 17:24:22 -04:00
|
|
|
|
2016-10-06 12:11:21 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2022-03-21 15:32:09 -04:00
|
|
|
|
|
|
|
|
|
2016-10-06 12:11:21 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-10-04 15:26:41 -04:00
|
|
|
|
|
|
|
|
|
2021-07-02 17:24:22 -04:00
|
|
|
|
|
|
|
|
|
2016-10-06 12:11:21 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-10-05 09:37:12 -04:00
|
|
|
|
2016-10-06 12:11:21 -04:00
|
|
|
|
|
|
|
|
|
2016-10-04 15:26:41 -04:00
|
|
|
|
2016-10-06 12:11:21 -04:00
|
|
|
|
2016-10-04 15:26:41 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-01 21:02:07 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-10-05 09:37:12 -04:00
|
|
|
|
2016-10-04 15:26:41 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-07-02 17:24:22 -04:00
|
|
|
|
2016-09-22 12:30:20 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-07-02 17:24:22 -04:00
|
|
|
|
2016-10-06 12:11:21 -04:00
|
|
|
|
2021-07-02 17:24:22 -04:00
|
|
|
|
2016-10-06 12:11:21 -04:00
|
|
|
|
|
|
|
|
|
2018-05-22 11:15:32 -04:00
|
|
|
|
2016-10-06 12:11:21 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-10-18 13:39:51 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-07-02 17:24:22 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-10-18 13:39:51 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-10-06 12:11:21 -04:00
|
|
|
|
|
|
|
|
|
2012-09-17 17:12:15 -04:00
|
|
|
|
2010-10-20 00:18:03 -04:00
|
|
|
|
|
|
|
|
|
2021-07-02 17:24:22 -04:00
|
|
|
|
2010-10-20 00:18:03 -04:00
|
|
|
|
|
|
|
|
|
2011-01-06 11:36:21 +00:00
|
|
|
|
2014-02-12 10:02:27 -05:00
|
|
|
|
2015-08-25 11:16:13 -04:00
|
|
|
|
|
|
|
|
|
2016-05-17 12:28:48 -04:00
|
|
|
|
2010-10-20 00:18:03 -04:00
|
|
|
|
|
|
|
|
|
2011-05-11 18:00:51 -04:00
|
|
|
|
2016-05-17 12:28:48 -04:00
|
|
|
|
2010-10-20 00:18:03 -04:00
|
|
|
|
2016-05-17 12:28:48 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:03 -04:00
|
|
|
|
|
|
|
|
|
2016-07-24 15:10:12 -04:00
|
|
|
|
2014-08-21 11:09:18 -05:00
|
|
|
|
2010-10-20 00:18:03 -04:00
|
|
|
|
2015-08-04 16:40:08 -04:00
|
|
|
|
2011-01-06 11:36:30 +00:00
|
|
|
|
2016-05-17 12:28:48 -04:00
|
|
|
|
2011-01-06 11:36:30 +00:00
|
|
|
|
2012-10-02 16:38:41 -07:00
|
|
|
|
2022-05-31 11:03:07 -04:00
|
|
|
|
|
|
|
|
|
2021-07-02 19:48:41 -04:00
|
|
|
|
|
|
|
|
|
2021-01-22 10:05:51 -05:00
|
|
|
|
2014-08-21 11:09:20 -05:00
|
|
|
|
|
|
|
|
|
2021-07-02 19:48:41 -04:00
|
|
|
|
2021-01-22 10:05:51 -05:00
|
|
|
|
2014-08-21 11:09:20 -05:00
|
|
|
|
2016-05-17 12:28:48 -04:00
|
|
|
|
2014-08-21 11:09:20 -05:00
|
|
|
|
2020-01-27 13:07:26 -05:00
|
|
|
|
2021-01-22 10:05:51 -05:00
|
|
|
|
2014-08-21 11:09:20 -05:00
|
|
|
|
|
|
|
|
|
2016-11-23 12:36:04 -05:00
|
|
|
|
2014-08-21 11:09:20 -05:00
|
|
|
|
2021-01-21 17:11:42 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-04-15 17:33:07 -04:00
|
|
|
|
2016-11-23 12:36:04 -05:00
|
|
|
|
2021-01-22 10:05:51 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-08-21 11:09:20 -05:00
|
|
|
|
2012-10-02 16:38:41 -07:00
|
|
|
|
2012-09-18 20:57:08 -04:00
|
|
|
|
2015-08-25 08:54:17 -04:00
|
|
|
|
2016-07-21 11:53:29 -04:00
|
|
|
|
2010-10-20 00:18:03 -04:00
|
|
|
|
2015-08-21 12:49:44 +08:00
|
|
|
|
2011-01-06 11:36:32 +00:00
|
|
|
|
|
|
|
|
|
2010-10-20 00:18:03 -04:00
|
|
|
|
2014-02-12 10:02:27 -05:00
|
|
|
|
2012-09-17 17:12:15 -04:00
|
|
|
|
2011-01-06 11:36:30 +00:00
|
|
|
|
2016-05-17 12:28:48 -04:00
|
|
|
|
2011-01-06 11:36:30 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-05-17 12:28:48 -04:00
|
|
|
|
2010-10-20 00:18:03 -04:00
|
|
|
|
|
|
|
|
|
2016-02-15 12:36:04 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-06-23 10:28:40 -04:00
|
|
|
|
2016-02-15 12:36:04 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-06-23 10:28:40 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-15 12:36:04 -05:00
|
|
|
|
2016-01-04 11:23:52 -05:00
|
|
|
|
2014-09-06 00:53:23 +08:00
|
|
|
|
|
|
|
|
|
2016-05-17 12:28:42 -04:00
|
|
|
|
|
|
|
|
|
2014-09-06 00:53:23 +08:00
|
|
|
|
|
|
|
|
|
2022-10-05 15:57:38 -04:00
|
|
|
|
2016-01-04 11:23:52 -05:00
|
|
|
|
2014-09-06 00:53:23 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-12-28 10:28:59 -05:00
|
|
|
|
2014-09-06 00:53:23 +08:00
|
|
|
|
2021-04-15 15:41:57 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-09-06 00:53:23 +08:00
|
|
|
|
2016-07-22 11:13:22 -04:00
|
|
|
|
2014-09-06 00:53:23 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-04-15 15:41:57 -04:00
|
|
|
|
|
|
|
|
|
2020-08-04 16:30:30 -04:00
|
|
|
|
2016-02-15 12:36:04 -05:00
|
|
|
|
|
|
|
|
|
2014-09-06 00:53:23 +08:00
|
|
|
|
2022-10-05 15:57:38 -04:00
|
|
|
|
2014-09-06 00:53:23 +08:00
|
|
|
|
2016-05-17 12:28:42 -04:00
|
|
|
|
2018-06-23 10:28:40 -04:00
|
|
|
|
2016-05-17 12:28:42 -04:00
|
|
|
|
2018-06-23 10:28:40 -04:00
|
|
|
|
|
|
|
|
|
2016-05-17 12:28:42 -04:00
|
|
|
|
2018-06-23 10:28:40 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-09-06 00:53:23 +08:00
|
|
|
|
|
|
|
|
|
2020-02-18 15:58:31 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-09-06 00:53:23 +08:00
|
|
|
|
2020-02-18 15:58:31 -05:00
|
|
|
|
2016-01-04 11:23:52 -05:00
|
|
|
|
2014-09-06 00:53:23 +08:00
|
|
|
|
|
|
|
|
|
2020-02-18 15:58:31 -05:00
|
|
|
|
2017-04-27 15:30:00 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-02-18 15:58:31 -05:00
|
|
|
|
2014-09-06 00:53:23 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-02-18 15:58:31 -05:00
|
|
|
|
2020-04-02 15:37:02 -04:00
|
|
|
|
2016-01-04 11:23:52 -05:00
|
|
|
|
2016-07-21 12:44:15 -04:00
|
|
|
|
2016-01-04 11:23:52 -05:00
|
|
|
|
2020-04-02 15:37:02 -04:00
|
|
|
|
2016-01-04 11:23:52 -05:00
|
|
|
|
|
|
|
|
|
2024-06-13 01:00:53 -04:00
|
|
|
|
|
|
|
|
|
2016-01-04 11:23:52 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-09-06 00:53:23 +08:00
|
|
|
|
2020-02-18 15:58:31 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-09-06 00:53:23 +08:00
|
|
|
|
|
|
|
|
|
2020-02-18 15:58:31 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-10-08 14:20:19 -04:00
|
|
|
|
|
|
|
|
|
2020-02-18 15:58:31 -05:00
|
|
|
|
|
|
|
|
|
2023-10-08 14:20:19 -04:00
|
|
|
|
2020-02-18 15:58:31 -05:00
|
|
|
|
|
|
|
|
|
2023-10-08 14:20:19 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-02-18 15:58:31 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-10-08 14:20:19 -04:00
|
|
|
|
|
|
|
|
|
2020-02-18 15:58:31 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-10-08 14:20:19 -04:00
|
|
|
|
|
|
|
|
|
2020-02-18 15:58:31 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-10-08 14:20:19 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-02-18 15:58:31 -05:00
|
|
|
|
|
|
|
|
|
2024-06-13 01:00:53 -04:00
|
|
|
|
|
|
|
|
|
2023-10-08 14:20:19 -04:00
|
|
|
|
2020-02-18 15:58:31 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2024-05-10 15:07:43 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-04-25 10:56:19 -04:00
|
|
|
|
2024-05-10 15:07:43 -04:00
|
|
|
|
|
|
|
|
|
2017-04-25 10:56:19 -04:00
|
|
|
|
|
|
|
|
|
2024-05-10 15:07:43 -04:00
|
|
|
|
|
|
|
|
|
2017-04-25 10:56:19 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-06-10 13:30:23 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-05-12 17:20:04 +08:00
|
|
|
|
2012-09-25 14:55:57 +08:00
|
|
|
|
2024-05-10 15:07:43 -04:00
|
|
|
|
2015-01-24 22:14:52 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-11-17 06:25:13 -05:00
|
|
|
|
|
|
|
|
|
2011-06-10 13:30:23 -04:00
|
|
|
|
2022-03-21 15:32:09 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-12-04 02:57:48 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-01-24 22:14:52 +08:00
|
|
|
|
2011-06-10 13:30:23 -04:00
|
|
|
|
|
|
|
|
|
2011-07-13 15:59:57 -04:00
|
|
|
|
2011-06-10 13:30:23 -04:00
|
|
|
|
2011-06-10 13:30:23 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-25 14:55:57 +08:00
|
|
|
|
|
|
|
|
|
2011-06-10 13:30:23 -04:00
|
|
|
|
2024-05-10 15:07:43 -04:00
|
|
|
|
2015-12-04 02:57:48 +08:00
|
|
|
|
2022-03-21 15:32:09 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-12-04 02:57:48 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-06-10 13:30:23 -04:00
|
|
|
|
|
|
|
|
|
2011-07-13 15:59:57 -04:00
|
|
|
|
2011-06-10 13:30:23 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-09-10 15:48:01 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-05-15 11:56:43 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-09-19 10:55:07 -04:00
|
|
|
|
|
|
|
|
|
2011-03-01 01:34:15 +00:00
|
|
|
|
2014-05-15 11:56:51 -04:00
|
|
|
|
2014-06-09 17:47:26 -04:00
|
|
|
|
2014-05-15 11:56:51 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-05-25 20:54:40 +03:00
|
|
|
|
2011-06-10 13:30:23 -04:00
|
|
|
|
2014-06-09 17:47:26 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-06-10 13:30:23 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-05-15 11:56:55 -04:00
|
|
|
|
2016-10-25 12:24:25 -04:00
|
|
|
|
2014-06-09 17:47:26 -04:00
|
|
|
|
|
|
|
|
|
2017-05-22 20:20:23 -04:00
|
|
|
|
2014-06-09 17:47:26 -04:00
|
|
|
|
2017-05-22 20:20:23 -04:00
|
|
|
|
2014-05-15 11:56:55 -04:00
|
|
|
|
2014-06-09 17:47:26 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-05-15 11:56:55 -04:00
|
|
|
|
2014-05-15 11:56:51 -04:00
|
|
|
|
2014-05-15 11:56:55 -04:00
|
|
|
|
2011-03-01 01:34:15 +00:00
|
|
|
|
2011-05-25 20:54:40 +03:00
|
|
|
|
2011-03-01 01:34:15 +00:00
|
|
|
|
2014-06-09 11:48:38 -04:00
|
|
|
|
2012-01-06 08:57:46 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-06-09 11:48:38 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-01-06 08:57:46 -05:00
|
|
|
|
2012-04-27 17:53:46 -04:00
|
|
|
|
2012-01-06 08:57:46 -05:00
|
|
|
|
2014-06-09 11:48:35 -04:00
|
|
|
|
2012-04-20 14:47:37 -04:00
|
|
|
|
2012-04-20 14:47:44 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-04-20 14:47:37 -04:00
|
|
|
|
2012-04-20 14:47:44 -04:00
|
|
|
|
2012-04-20 14:47:37 -04:00
|
|
|
|
2012-04-20 14:47:47 -04:00
|
|
|
|
2014-06-09 11:48:38 -04:00
|
|
|
|
2012-04-20 14:47:37 -04:00
|
|
|
|
|
|
|
|
|
2011-05-22 19:52:03 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-06-09 11:48:35 -04:00
|
|
|
|
2011-03-01 01:34:14 +00:00
|
|
|
|
2015-10-16 17:23:29 +08:00
|
|
|
|
2015-03-25 20:40:38 -04:00
|
|
|
|
|
|
|
|
|
2014-06-09 11:48:35 -04:00
|
|
|
|
2015-10-16 17:23:29 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-06-09 11:48:35 -04:00
|
|
|
|
|
|
|
|
|
2011-03-03 15:13:44 +00:00
|
|
|
|
2011-05-22 19:52:03 +03:00
|
|
|
|
2011-03-03 15:13:44 +00:00
|
|
|
|
2011-07-13 15:59:19 -04:00
|
|
|
|
|
|
|
|
|
2014-06-09 11:48:35 -04:00
|
|
|
|
2011-07-13 15:59:19 -04:00
|
|
|
|
2014-11-10 08:35:35 +08:00
|
|
|
|
2014-09-19 10:55:07 -04:00
|
|
|
|
2012-04-20 14:47:47 -04:00
|
|
|
|
2014-09-19 10:55:07 -04:00
|
|
|
|
2012-04-20 14:47:47 -04:00
|
|
|
|
2014-09-19 10:55:07 -04:00
|
|
|
|
2012-04-20 14:47:47 -04:00
|
|
|
|
2017-12-15 16:12:32 -05:00
|
|
|
|
2011-07-13 15:59:19 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-06-09 11:48:35 -04:00
|
|
|
|
2011-07-13 15:59:19 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-03-03 15:13:45 +00:00
|
|
|
|
2012-04-20 14:47:44 -04:00
|
|
|
|
2011-03-03 15:13:45 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-04-20 14:47:44 -04:00
|
|
|
|
2011-03-03 15:13:45 +00:00
|
|
|
|
2026-03-04 10:32:42 -05:00
|
|
|
|
2014-06-09 11:48:35 -04:00
|
|
|
|
|
|
|
|
|
2012-04-20 14:47:47 -04:00
|
|
|
|
2011-03-03 15:13:45 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-07-13 15:59:19 -04:00
|
|
|
|
2014-05-15 11:56:53 -04:00
|
|
|
|
|
|
|
|
|
2011-07-13 15:59:19 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-05-15 11:56:53 -04:00
|
|
|
|
2011-07-13 15:59:19 -04:00
|
|
|
|
2014-06-09 11:48:35 -04:00
|
|
|
|
2017-04-29 00:02:37 -04:00
|
|
|
|
|
|
|
|
|
2014-06-09 11:48:35 -04:00
|
|
|
|
2020-11-20 12:26:46 -06:00
|
|
|
|
2017-04-29 00:02:37 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-07-13 15:59:19 -04:00
|
|
|
|
|
|
|
|
|
2012-04-20 14:47:47 -04:00
|
|
|
|
|
|
|
|
|
2012-09-18 20:57:08 -04:00
|
|
|
|
2014-06-09 11:48:33 -04:00
|
|
|
|
2012-04-20 14:47:47 -04:00
|
|
|
|
|
|
|
|
|
2011-07-13 15:59:19 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-04-20 14:47:47 -04:00
|
|
|
|
2011-07-13 15:59:19 -04:00
|
|
|
|
|
|
|
|
|
2014-06-09 11:48:33 -04:00
|
|
|
|
|
|
|
|
|
2015-12-05 02:03:17 +08:00
|
|
|
|
|
|
|
|
|
2012-04-20 14:47:47 -04:00
|
|
|
|
|
|
|
|
|
2014-09-10 15:48:01 -04:00
|
|
|
|
2012-09-18 20:57:08 -04:00
|
|
|
|
2014-05-06 09:12:36 -04:00
|
|
|
|
2014-09-10 15:48:01 -04:00
|
|
|
|
2014-05-15 11:56:53 -04:00
|
|
|
|
2014-09-19 10:55:07 -04:00
|
|
|
|
2012-04-20 14:47:47 -04:00
|
|
|
|
2011-07-13 15:59:19 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-06-09 11:48:38 -04:00
|
|
|
|
2011-11-10 14:30:37 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-04-20 14:47:37 -04:00
|
|
|
|
2014-06-09 11:48:38 -04:00
|
|
|
|
|
|
|
|
|
2012-04-20 14:47:37 -04:00
|
|
|
|
2012-04-27 17:53:46 -04:00
|
|
|
|
2012-04-20 14:47:37 -04:00
|
|
|
|
2014-06-09 11:48:35 -04:00
|
|
|
|
2012-04-20 14:47:37 -04:00
|
|
|
|
2012-04-20 14:47:44 -04:00
|
|
|
|
|
|
|
|
|
2012-04-20 14:47:37 -04:00
|
|
|
|
2012-04-20 14:47:44 -04:00
|
|
|
|
2012-04-20 14:47:37 -04:00
|
|
|
|
2012-04-20 14:47:46 -04:00
|
|
|
|
2014-06-09 11:48:38 -04:00
|
|
|
|
2011-11-10 14:30:37 -05:00
|
|
|
|
|
|
|
|
|
2011-05-22 19:52:03 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-06-09 11:48:35 -04:00
|
|
|
|
2011-05-22 19:52:03 +03:00
|
|
|
|
2016-09-15 18:26:05 -04:00
|
|
|
|
2014-06-09 11:48:35 -04:00
|
|
|
|
2015-10-16 17:23:29 +08:00
|
|
|
|
|
|
|
|
|
2014-06-09 11:48:35 -04:00
|
|
|
|
|
|
|
|
|
2011-05-22 19:52:03 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-07-13 15:58:28 -04:00
|
|
|
|
|
|
|
|
|
2014-06-09 11:48:35 -04:00
|
|
|
|
2011-07-13 15:58:28 -04:00
|
|
|
|
2014-11-10 08:35:35 +08:00
|
|
|
|
2014-09-19 10:55:07 -04:00
|
|
|
|
2012-04-20 14:47:46 -04:00
|
|
|
|
2014-09-19 10:55:07 -04:00
|
|
|
|
2012-04-20 14:47:46 -04:00
|
|
|
|
2014-09-19 10:55:07 -04:00
|
|
|
|
2012-04-20 14:47:46 -04:00
|
|
|
|
2017-12-15 16:12:32 -05:00
|
|
|
|
2011-07-13 15:58:28 -04:00
|
|
|
|
|
|
|
|
|
2011-03-01 01:34:16 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-07-13 15:58:28 -04:00
|
|
|
|
2014-06-09 11:48:35 -04:00
|
|
|
|
2011-07-13 15:58:28 -04:00
|
|
|
|
|
|
|
|
|
2011-03-01 01:34:16 +00:00
|
|
|
|
2012-04-20 14:47:44 -04:00
|
|
|
|
2011-03-01 01:34:16 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-04-20 14:47:44 -04:00
|
|
|
|
2011-03-01 01:34:16 +00:00
|
|
|
|
2026-03-04 10:32:42 -05:00
|
|
|
|
2014-06-09 11:48:35 -04:00
|
|
|
|
2011-03-01 01:34:16 +00:00
|
|
|
|
2014-06-09 11:48:35 -04:00
|
|
|
|
2012-04-20 14:47:46 -04:00
|
|
|
|
2011-03-01 01:34:16 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-03-23 13:27:54 +00:00
|
|
|
|
2014-11-10 08:35:38 +08:00
|
|
|
|
2020-08-11 13:36:32 -04:00
|
|
|
|
|
|
|
|
|
2014-11-10 08:35:38 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-04-01 11:42:28 -04:00
|
|
|
|
2016-11-27 15:12:39 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-04-01 11:42:28 -04:00
|
|
|
|
|
|
|
|
|
2020-08-11 13:36:32 -04:00
|
|
|
|
2016-04-01 11:42:28 -04:00
|
|
|
|
|
|
|
|
|
2014-11-10 08:35:38 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-07-13 15:58:28 -04:00
|
|
|
|
2014-05-15 11:56:53 -04:00
|
|
|
|
2011-07-13 15:58:28 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-05-15 11:56:53 -04:00
|
|
|
|
2011-07-13 15:58:28 -04:00
|
|
|
|
2014-06-09 11:48:35 -04:00
|
|
|
|
2017-04-25 11:26:53 -04:00
|
|
|
|
|
|
|
|
|
2014-06-09 11:48:35 -04:00
|
|
|
|
2020-11-20 12:26:46 -06:00
|
|
|
|
2017-04-25 11:26:53 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-07-13 15:58:28 -04:00
|
|
|
|
|
|
|
|
|
2012-04-20 14:47:46 -04:00
|
|
|
|
|
|
|
|
|
2012-09-18 20:57:08 -04:00
|
|
|
|
2014-06-09 11:48:33 -04:00
|
|
|
|
2012-04-20 14:47:46 -04:00
|
|
|
|
|
|
|
|
|
2011-07-13 15:58:28 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-04-20 14:47:46 -04:00
|
|
|
|
2011-07-13 15:58:28 -04:00
|
|
|
|
|
|
|
|
|
2014-06-09 11:48:33 -04:00
|
|
|
|
|
|
|
|
|
2015-12-05 02:03:17 +08:00
|
|
|
|
|
|
|
|
|
2011-07-13 15:58:28 -04:00
|
|
|
|
2012-04-20 14:47:46 -04:00
|
|
|
|
2012-09-18 20:57:08 -04:00
|
|
|
|
2014-05-06 09:12:36 -04:00
|
|
|
|
2014-09-10 15:48:01 -04:00
|
|
|
|
2014-05-15 11:56:53 -04:00
|
|
|
|
2012-04-20 14:47:46 -04:00
|
|
|
|
2011-07-13 15:58:28 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-01-13 13:34:36 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-03-17 18:06:10 +01:00
|
|
|
|
2014-01-13 13:34:36 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-03-23 13:27:54 +00:00
|
|
|
|
2011-07-30 20:52:33 -04:00
|
|
|
|
2011-03-23 13:27:54 +00:00
|
|
|
|
2011-07-30 20:52:33 -04:00
|
|
|
|
2011-03-23 13:27:54 +00:00
|
|
|
|
2011-07-30 20:52:33 -04:00
|
|
|
|
2011-03-23 13:27:54 +00:00
|
|
|
|
2011-07-30 20:52:33 -04:00
|
|
|
|
|
|
|
|
|
2013-03-20 12:34:32 -04:00
|
|
|
|
2011-07-30 20:52:33 -04:00
|
|
|
|
|
|
|
|
|
2011-03-23 13:27:54 +00:00
|
|
|
|
|
|
|
|
|
2013-03-20 12:34:32 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-01-13 13:34:36 -05:00
|
|
|
|
2013-03-20 12:34:32 -04:00
|
|
|
|
|
|
|
|
|
2011-09-22 21:50:12 -04:00
|
|
|
|
|
|
|
|
|
2012-09-18 16:41:18 -04:00
|
|
|
|
2011-09-22 21:50:12 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-03-23 13:27:54 +00:00
|
|
|
|
2015-03-25 20:40:38 -04:00
|
|
|
|
|
|
|
|
|
2011-03-23 13:27:54 +00:00
|
|
|
|
2012-04-20 14:47:44 -04:00
|
|
|
|
2011-04-13 10:53:51 -04:00
|
|
|
|
2011-03-23 13:27:54 +00:00
|
|
|
|
2012-04-20 14:47:44 -04:00
|
|
|
|
2011-03-23 13:27:54 +00:00
|
|
|
|
2015-03-25 20:10:20 -04:00
|
|
|
|
2011-04-13 10:53:51 -04:00
|
|
|
|
2026-03-04 10:32:42 -05:00
|
|
|
|
2012-04-20 14:47:44 -04:00
|
|
|
|
2015-03-25 20:10:20 -04:00
|
|
|
|
|
|
|
|
|
2015-03-25 20:40:38 -04:00
|
|
|
|
2011-07-30 20:52:33 -04:00
|
|
|
|
2015-03-25 20:40:38 -04:00
|
|
|
|
2011-07-30 20:52:33 -04:00
|
|
|
|
2012-04-20 14:47:44 -04:00
|
|
|
|
2011-07-30 20:52:31 -04:00
|
|
|
|
2015-03-25 20:40:38 -04:00
|
|
|
|
2011-04-13 10:53:51 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-04-20 14:47:44 -04:00
|
|
|
|
2011-03-23 13:27:54 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-07-30 20:52:38 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-03-20 12:34:32 -04:00
|
|
|
|
2011-07-30 20:52:38 -04:00
|
|
|
|
|
|
|
|
|
2011-03-12 02:58:09 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-03-23 13:27:54 +00:00
|
|
|
|
2011-03-12 02:58:10 -05:00
|
|
|
|
2011-03-23 13:27:54 +00:00
|
|
|
|
2014-08-21 11:09:25 -05:00
|
|
|
|
2011-03-23 13:27:54 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-01-13 13:34:36 -05:00
|
|
|
|
2025-06-30 21:35:29 +03:00
|
|
|
|
2014-01-13 13:34:36 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-03-23 13:27:54 +00:00
|
|
|
|
2026-03-04 10:32:42 -05:00
|
|
|
|
2011-03-23 13:27:54 +00:00
|
|
|
|
2014-01-13 13:34:36 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
sched: Remove proliferation of wait_on_bit() action functions
The current "wait_on_bit" interface requires an 'action'
function to be provided which does the actual waiting.
There are over 20 such functions, many of them identical.
Most cases can be satisfied by one of just two functions, one
which uses io_schedule() and one which just uses schedule().
So:
Rename wait_on_bit and wait_on_bit_lock to
wait_on_bit_action and wait_on_bit_lock_action
to make it explicit that they need an action function.
Introduce new wait_on_bit{,_lock} and wait_on_bit{,_lock}_io
which are *not* given an action function but implicitly use
a standard one.
The decision to error-out if a signal is pending is now made
based on the 'mode' argument rather than being encoded in the action
function.
All instances of the old wait_on_bit and wait_on_bit_lock which
can use the new version have been changed accordingly and their
action functions have been discarded.
wait_on_bit{_lock} does not return any specific error code in the
event of a signal so the caller must check for non-zero and
interpolate their own error code as appropriate.
The wait_on_bit() call in __fscache_wait_on_invalidate() was
ambiguous as it specified TASK_UNINTERRUPTIBLE but used
fscache_wait_bit_interruptible as an action function.
David Howells confirms this should be uniformly
"uninterruptible"
The main remaining user of wait_on_bit{,_lock}_action is NFS
which needs to use a freezer-aware schedule() call.
A comment in fs/gfs2/glock.c notes that having multiple 'action'
functions is useful as they display differently in the 'wchan'
field of 'ps'. (and /proc/$PID/wchan).
As the new bit_wait{,_io} functions are tagged "__sched", they
will not show up at all, but something higher in the stack. So
the distinction will still be visible, only with different
function names (gds2_glock_wait versus gfs2_glock_dq_wait in the
gfs2/glock.c case).
Since first version of this patch (against 3.15) two new action
functions appeared, on in NFS and one in CIFS. CIFS also now
uses an action function that makes the same freezer aware
schedule call as NFS.
Signed-off-by: NeilBrown <neilb@suse.de>
Acked-by: David Howells <dhowells@redhat.com> (fscache, keys)
Acked-by: Steven Whitehouse <swhiteho@redhat.com> (gfs2)
Acked-by: Peter Zijlstra <peterz@infradead.org>
Cc: Oleg Nesterov <oleg@redhat.com>
Cc: Steve French <sfrench@samba.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Link: http://lkml.kernel.org/r/20140707051603.28027.72349.stgit@notabene.brown
Signed-off-by: Ingo Molnar <mingo@kernel.org>
2014-07-07 15:16:04 +10:00
|
|
|
|
2014-01-13 13:34:36 -05:00
|
|
|
|
|
|
|
|
|
freezer,sched: Rewrite core freezer logic
Rewrite the core freezer to behave better wrt thawing and be simpler
in general.
By replacing PF_FROZEN with TASK_FROZEN, a special block state, it is
ensured frozen tasks stay frozen until thawed and don't randomly wake
up early, as is currently possible.
As such, it does away with PF_FROZEN and PF_FREEZER_SKIP, freeing up
two PF_flags (yay!).
Specifically; the current scheme works a little like:
freezer_do_not_count();
schedule();
freezer_count();
And either the task is blocked, or it lands in try_to_freezer()
through freezer_count(). Now, when it is blocked, the freezer
considers it frozen and continues.
However, on thawing, once pm_freezing is cleared, freezer_count()
stops working, and any random/spurious wakeup will let a task run
before its time.
That is, thawing tries to thaw things in explicit order; kernel
threads and workqueues before doing bringing SMP back before userspace
etc.. However due to the above mentioned races it is entirely possible
for userspace tasks to thaw (by accident) before SMP is back.
This can be a fatal problem in asymmetric ISA architectures (eg ARMv9)
where the userspace task requires a special CPU to run.
As said; replace this with a special task state TASK_FROZEN and add
the following state transitions:
TASK_FREEZABLE -> TASK_FROZEN
__TASK_STOPPED -> TASK_FROZEN
__TASK_TRACED -> TASK_FROZEN
The new TASK_FREEZABLE can be set on any state part of TASK_NORMAL
(IOW. TASK_INTERRUPTIBLE and TASK_UNINTERRUPTIBLE) -- any such state
is already required to deal with spurious wakeups and the freezer
causes one such when thawing the task (since the original state is
lost).
The special __TASK_{STOPPED,TRACED} states *can* be restored since
their canonical state is in ->jobctl.
With this, frozen tasks need an explicit TASK_FROZEN wakeup and are
free of undue (early / spurious) wakeups.
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Reviewed-by: Ingo Molnar <mingo@kernel.org>
Acked-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Link: https://lore.kernel.org/r/20220822114649.055452969@infradead.org
2022-08-22 13:18:22 +02:00
|
|
|
|
2014-01-13 13:34:36 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-03-12 02:58:09 -05:00
|
|
|
|
2014-01-13 13:34:36 -05:00
|
|
|
|
2011-03-23 13:27:54 +00:00
|
|
|
|
treewide: Replace kmalloc with kmalloc_obj for non-scalar types
This is the result of running the Coccinelle script from
scripts/coccinelle/api/kmalloc_objs.cocci. The script is designed to
avoid scalar types (which need careful case-by-case checking), and
instead replace kmalloc-family calls that allocate struct or union
object instances:
Single allocations: kmalloc(sizeof(TYPE), ...)
are replaced with: kmalloc_obj(TYPE, ...)
Array allocations: kmalloc_array(COUNT, sizeof(TYPE), ...)
are replaced with: kmalloc_objs(TYPE, COUNT, ...)
Flex array allocations: kmalloc(struct_size(PTR, FAM, COUNT), ...)
are replaced with: kmalloc_flex(*PTR, FAM, COUNT, ...)
(where TYPE may also be *VAR)
The resulting allocations no longer return "void *", instead returning
"TYPE *".
Signed-off-by: Kees Cook <kees@kernel.org>
2026-02-20 23:49:23 -08:00
|
|
|
|
2014-01-13 13:34:36 -05:00
|
|
|
|
|
|
|
|
|
2011-03-23 13:27:54 +00:00
|
|
|
|
2014-01-13 13:34:36 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-10-23 20:21:17 -07:00
|
|
|
|
2011-07-30 20:52:33 -04:00
|
|
|
|
|
|
|
|
|
2011-03-23 13:27:54 +00:00
|
|
|
|
2011-07-30 20:52:31 -04:00
|
|
|
|
2011-03-23 13:27:54 +00:00
|
|
|
|
2012-03-04 18:13:56 -05:00
|
|
|
|
2020-04-02 15:47:08 -04:00
|
|
|
|
2011-03-23 13:27:54 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-06-26 18:54:58 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-03-23 13:27:54 +00:00
|
|
|
|
|
|
|
|
|
2014-08-21 11:09:25 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-06-30 21:35:29 +03:00
|
|
|
|
|
|
|
|
|
2014-08-21 11:09:25 -05:00
|
|
|
|
2015-03-25 20:10:20 -04:00
|
|
|
|
|
|
|
|
|
2014-08-21 11:09:25 -05:00
|
|
|
|
2025-06-30 21:35:29 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-08-21 11:09:25 -05:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-03-23 13:27:54 +00:00
|
|
|
|
|
|
|
|
|
2025-06-30 21:35:29 +03:00
|
|
|
|
2011-10-23 20:21:17 -07:00
|
|
|
|
2011-03-23 13:27:54 +00:00
|
|
|
|
|
|
|
|
|
2014-01-13 13:34:36 -05:00
|
|
|
|
|
|
|
|
|
2011-10-23 20:21:17 -07:00
|
|
|
|
2014-01-13 13:34:36 -05:00
|
|
|
|
|
|
|
|
|
2011-10-23 20:21:17 -07:00
|
|
|
|
2011-03-23 13:27:54 +00:00
|
|
|
|
2014-08-07 10:12:38 +08:00
|
|
|
|
2012-05-23 05:02:35 -04:00
|
|
|
|
2015-03-25 14:14:42 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-05-23 05:02:35 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
treewide: Replace kmalloc with kmalloc_obj for non-scalar types
This is the result of running the Coccinelle script from
scripts/coccinelle/api/kmalloc_objs.cocci. The script is designed to
avoid scalar types (which need careful case-by-case checking), and
instead replace kmalloc-family calls that allocate struct or union
object instances:
Single allocations: kmalloc(sizeof(TYPE), ...)
are replaced with: kmalloc_obj(TYPE, ...)
Array allocations: kmalloc_array(COUNT, sizeof(TYPE), ...)
are replaced with: kmalloc_objs(TYPE, COUNT, ...)
Flex array allocations: kmalloc(struct_size(PTR, FAM, COUNT), ...)
are replaced with: kmalloc_flex(*PTR, FAM, COUNT, ...)
(where TYPE may also be *VAR)
The resulting allocations no longer return "void *", instead returning
"TYPE *".
Signed-off-by: Kees Cook <kees@kernel.org>
2026-02-20 23:49:23 -08:00
|
|
|
|
2012-05-23 05:02:35 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-06-23 19:51:57 +08:00
|
|
|
|
2015-06-25 18:19:32 +08:00
|
|
|
|
2015-06-23 19:51:57 +08:00
|
|
|
|
2015-08-05 17:31:58 -04:00
|
|
|
|
2015-06-23 19:51:57 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-06-23 19:52:03 +08:00
|
|
|
|
2015-06-23 19:51:57 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-06-27 11:45:46 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-06-23 19:52:03 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-06-23 19:51:57 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-05-16 14:41:14 -04:00
|
|
|
|
2015-06-23 19:51:57 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
treewide: Replace kmalloc with kmalloc_obj for non-scalar types
This is the result of running the Coccinelle script from
scripts/coccinelle/api/kmalloc_objs.cocci. The script is designed to
avoid scalar types (which need careful case-by-case checking), and
instead replace kmalloc-family calls that allocate struct or union
object instances:
Single allocations: kmalloc(sizeof(TYPE), ...)
are replaced with: kmalloc_obj(TYPE, ...)
Array allocations: kmalloc_array(COUNT, sizeof(TYPE), ...)
are replaced with: kmalloc_objs(TYPE, COUNT, ...)
Flex array allocations: kmalloc(struct_size(PTR, FAM, COUNT), ...)
are replaced with: kmalloc_flex(*PTR, FAM, COUNT, ...)
(where TYPE may also be *VAR)
The resulting allocations no longer return "void *", instead returning
"TYPE *".
Signed-off-by: Kees Cook <kees@kernel.org>
2026-02-20 23:49:23 -08:00
|
|
|
|
2015-06-23 19:51:57 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-05-16 14:41:14 -04:00
|
|
|
|
2015-06-23 19:52:03 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-06-23 19:51:57 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-06-25 18:19:32 +08:00
|
|
|
|
2015-08-24 20:39:18 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|