Tejun Heo fe0f726c9f
kernfs: combine ino/id lookup functions into kernfs_find_and_get_node_by_id() ...
kernfs_find_and_get_node_by_ino() looks the kernfs_node matching the
specified ino. On top of that, kernfs_get_node_by_id() and
kernfs_fh_get_inode() implement full ID matching by testing the rest
of ID.
On surface, confusingly, the two are slightly different in that the
latter uses 0 gen as wildcard while the former doesn't - does it mean
that the latter can't uniquely identify inodes w/ 0 gen? In practice,
this is a distinction without a difference because generation number
starts at 1. There are no actual IDs with 0 gen, so it can always
safely used as wildcard.
Let's simplify the code by renaming kernfs_find_and_get_node_by_ino()
to kernfs_find_and_get_node_by_id(), moving all lookup logics into it,
and removing now unnecessary kernfs_get_node_by_id().
Signed-off-by: Tejun Heo <tj@kernel.org >
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org >
2019-11-12 08:18:04 -08:00
2019-11-12 08:18:03 -08:00
2019-11-12 08:18:04 -08:00
2019-09-25 17:51:40 -07:00
2019-10-05 10:24:17 +02:00
2019-10-01 15:45:22 +02:00
2019-09-15 21:37:13 +02:00
2019-09-17 19:15:14 -07:00
2019-08-19 13:03:37 +02:00
2019-09-25 10:22:37 +02:00
2019-09-28 08:14:15 -07:00
2019-09-16 12:54:25 +02:00
2019-09-16 17:25:49 -07:00
2019-10-04 10:36:31 -07:00
2019-09-27 14:45:55 +02:00
2019-11-12 08:18:03 -08:00
2019-04-29 16:48:03 +02:00
2019-04-04 21:04:13 -04:00
2019-06-05 17:37:17 +02:00
2019-05-30 11:26:37 -07:00
2019-04-26 13:51:03 -04:00
2019-05-30 11:26:35 -07:00
2019-07-08 18:55:42 -07:00
2019-07-08 18:55:42 -07:00
2019-07-08 18:55:42 -07:00
2019-05-28 17:46:43 -04:00
2019-06-05 17:37:17 +02:00
2019-01-25 11:22:43 -08:00
2019-06-19 17:09:55 +02:00
2019-07-30 18:34:15 +02:00
2019-05-21 10:50:45 +02:00
2019-06-05 17:36:37 +02:00
2019-09-24 13:37:28 +02:00
2019-06-19 17:09:06 +02:00
2019-05-21 10:50:45 +02:00
2019-07-25 08:36:29 -07:00
2019-05-21 11:52:39 +02:00
2019-09-25 17:51:39 -07:00
2019-09-25 17:42:29 +02:00
2019-08-21 22:23:48 +10:00
2019-06-03 15:49:06 +02:00
2019-10-04 10:36:31 -07:00
2019-05-21 10:50:45 +02:00
2019-08-01 17:43:16 +02:00
2019-10-05 15:29:49 +09:00
2019-05-21 10:50:45 +02:00
2019-07-12 11:05:40 -07:00
2019-05-21 10:50:45 +02:00
2019-08-29 15:10:10 +01:00
2019-08-27 16:19:56 +01:00
2019-05-21 10:50:46 +02:00
2019-05-21 10:50:46 +02:00
2019-05-21 10:50:46 +02:00
2019-07-22 18:05:11 +02:00
2019-03-07 18:32:02 -08:00
2019-09-25 17:51:40 -07:00
2019-09-06 23:58:44 +02:00
2019-09-28 08:14:15 -07:00
2019-08-19 21:54:15 -07:00
2019-05-24 20:16:01 +02:00
2019-09-20 11:19:48 -07:00
2019-05-30 11:26:39 -07:00
2019-05-21 10:50:45 +02:00
2019-06-05 17:37:17 +02:00
2019-09-27 19:37:27 -07:00
2019-08-05 18:39:56 -04:00
2019-08-05 18:39:56 -04:00
2019-05-24 17:27:11 +02:00
2019-09-28 08:14:15 -07:00
2019-05-21 10:50:45 +02:00
2019-06-05 17:37:17 +02:00
2019-09-13 21:15:41 +10:00
2019-09-25 17:51:41 -07:00
2019-08-19 21:54:16 -07:00
2019-07-18 17:08:07 -07:00
2019-07-16 19:23:24 -07:00
2019-05-21 10:50:45 +02:00
2019-07-16 19:23:24 -07:00
2019-05-21 10:50:45 +02:00
2019-03-12 13:27:20 -07:00
2019-09-24 15:54:09 -07:00
2019-05-27 09:36:28 -05:00
2019-05-29 09:31:44 -05:00
2019-09-16 09:28:19 -07:00
2019-07-20 11:27:16 +02:00
2019-05-21 10:50:45 +02:00
2019-07-08 11:01:13 -07:00
2019-07-25 15:43:26 +02:00
2019-08-08 09:09:30 +02:00
2019-06-21 01:54:53 +02:00
2019-09-17 12:35:15 -07:00
2019-01-04 13:13:47 -08:00
2019-09-24 15:54:11 -07:00
2019-05-30 11:26:37 -07:00
2019-05-21 11:52:39 +02:00
2019-08-01 14:30:22 -07:00
2019-07-18 11:51:00 -07:00
2019-05-30 11:26:37 -07:00
2019-07-18 17:08:07 -07:00
2019-05-21 10:50:45 +02:00
2019-06-23 14:26:26 +02:00
2019-07-08 19:36:47 -07:00
2019-05-21 10:50:45 +02:00
2019-07-08 19:36:47 -07:00
2019-06-05 17:37:17 +02:00
2019-06-05 17:37:17 +02:00
2019-04-19 09:46:05 -07:00
2019-08-01 20:51:20 +02:00
2019-04-16 16:55:15 +02:00
2019-09-13 21:15:40 +10:00
fe0f726c9f