2017-11-07 14:58:43 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2015-01-28 18:41:45 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-01-28 18:41:45 +00:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2014-07-17 12:27:32 -07:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-02 19:15:33 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-11-17 12:05:59 +00:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2008-11-13 17:05:58 -08:00
|
|
|
|
|
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2012-06-19 10:17:44 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2015-09-18 15:46:23 +01:00
|
|
|
|
2015-04-21 13:18:11 +01:00
|
|
|
|
2015-09-18 15:46:23 +01:00
|
|
|
|
|
|
|
|
|
2015-04-21 13:18:11 +01:00
|
|
|
|
2015-09-18 15:46:23 +01:00
|
|
|
|
2025-10-23 14:28:18 +01:00
|
|
|
|
2015-09-18 15:46:23 +01:00
|
|
|
|
2015-04-21 13:18:11 +01:00
|
|
|
|
2015-09-18 15:46:23 +01:00
|
|
|
|
2015-04-21 13:18:11 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-10-23 14:28:18 +01:00
|
|
|
|
2015-04-21 13:18:11 +01:00
|
|
|
|
|
|
|
|
|
2025-10-23 14:28:18 +01:00
|
|
|
|
|
|
|
|
|
2015-04-21 13:18:11 +01:00
|
|
|
|
2014-11-04 18:09:00 +00:00
|
|
|
|
2015-09-23 16:33:27 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-11-04 18:09:00 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-06-12 16:50:28 +02:00
|
|
|
|
2014-11-04 18:09:00 +00:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:02 +01:00
|
|
|
|
2013-04-04 14:59:04 +01:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:02 +01:00
|
|
|
|
2017-03-08 02:13:58 +08:00
|
|
|
|
|
|
|
|
|
2012-04-13 14:12:53 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-04-13 14:12:54 +01:00
|
|
|
|
2016-09-12 10:18:59 -03:00
|
|
|
|
2012-04-13 14:12:53 +01:00
|
|
|
|
|
|
|
|
|
2012-04-13 14:12:54 +01:00
|
|
|
|
2012-04-13 14:12:53 +01:00
|
|
|
|
2018-07-14 21:14:58 +05:30
|
|
|
|
|
|
|
|
|
2016-09-12 10:18:59 -03:00
|
|
|
|
2012-04-13 14:12:53 +01:00
|
|
|
|
|
|
|
|
|
2012-04-13 14:12:54 +01:00
|
|
|
|
2008-12-08 23:30:13 +00:00
|
|
|
|
2013-04-04 14:59:04 +01:00
|
|
|
|
2013-04-04 14:59:16 +01:00
|
|
|
|
2013-04-04 14:59:04 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:15 +01:00
|
|
|
|
2013-04-04 14:59:04 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2013-04-04 14:58:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-11-08 15:03:32 +00:00
|
|
|
|
2013-04-04 14:58:55 +01:00
|
|
|
|
|
|
|
|
|
2013-11-08 15:03:24 +00:00
|
|
|
|
2013-04-04 14:58:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-11-08 15:03:32 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-12-11 14:51:02 +00:00
|
|
|
|
2013-11-08 15:03:32 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-01-28 18:41:46 +00:00
|
|
|
|
2015-09-23 16:33:27 +01:00
|
|
|
|
|
|
|
|
|
2015-01-28 18:41:46 +00:00
|
|
|
|
2015-09-23 16:33:27 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-01-28 18:41:46 +00:00
|
|
|
|
2015-09-23 16:33:27 +01:00
|
|
|
|
|
|
|
|
|
2015-01-28 18:41:46 +00:00
|
|
|
|
|
|
|
|
|
2013-11-08 15:03:32 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-11-08 15:03:33 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-11-08 15:03:32 +00:00
|
|
|
|
2013-04-04 14:58:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-03-04 12:15:28 -07:00
|
|
|
|
2013-04-04 14:58:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-12-11 14:51:03 +00:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:58:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:18 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-04-17 15:39:29 +01:00
|
|
|
|
2013-04-04 14:59:18 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-03-21 09:18:35 -04:00
|
|
|
|
2013-04-04 14:58:55 +01:00
|
|
|
|
2013-04-04 14:59:16 +01:00
|
|
|
|
2013-04-04 14:58:55 +01:00
|
|
|
|
2013-04-04 14:59:04 +01:00
|
|
|
|
2013-04-04 14:59:16 +01:00
|
|
|
|
2013-04-04 14:59:04 +01:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:16 +01:00
|
|
|
|
2013-04-04 14:58:55 +01:00
|
|
|
|
|
|
|
|
|
2016-03-29 10:49:04 +01:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:04 +01:00
|
|
|
|
2013-04-04 14:59:15 +01:00
|
|
|
|
2013-04-04 14:59:04 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:15 +01:00
|
|
|
|
2013-11-08 15:03:42 +00:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:04 +01:00
|
|
|
|
2013-04-04 14:59:15 +01:00
|
|
|
|
2013-04-04 14:59:04 +01:00
|
|
|
|
|
|
|
|
|
2016-03-21 09:18:35 -04:00
|
|
|
|
2013-11-08 15:03:33 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-03-29 10:49:04 +01:00
|
|
|
|
|
|
|
|
|
2013-11-08 15:03:33 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-01-28 18:41:46 +00:00
|
|
|
|
2015-09-23 16:33:27 +01:00
|
|
|
|
|
|
|
|
|
2015-01-28 18:41:46 +00:00
|
|
|
|
2015-09-23 16:33:27 +01:00
|
|
|
|
|
|
|
|
|
2015-01-28 18:41:46 +00:00
|
|
|
|
|
|
|
|
|
2015-09-23 16:33:27 +01:00
|
|
|
|
|
|
|
|
|
2015-01-28 18:41:46 +00:00
|
|
|
|
|
|
|
|
|
2016-03-21 09:18:35 -04:00
|
|
|
|
2013-11-08 15:03:33 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-07-15 23:11:02 +08:00
|
|
|
|
|
|
|
|
|
2013-11-08 15:03:33 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-12-19 15:33:29 -07:00
|
|
|
|
2013-04-04 14:59:10 +01:00
|
|
|
|
2012-12-19 15:33:29 -07:00
|
|
|
|
2013-04-04 14:59:15 +01:00
|
|
|
|
2013-04-04 14:59:10 +01:00
|
|
|
|
2019-04-17 15:39:29 +01:00
|
|
|
|
2013-04-04 14:59:10 +01:00
|
|
|
|
2013-11-08 15:03:42 +00:00
|
|
|
|
2015-03-04 12:15:28 -07:00
|
|
|
|
2013-04-04 14:59:15 +01:00
|
|
|
|
2013-04-04 14:59:10 +01:00
|
|
|
|
|
|
|
|
|
2012-12-19 15:33:29 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:10 +01:00
|
|
|
|
2012-12-19 15:33:29 -07:00
|
|
|
|
2013-04-04 14:59:15 +01:00
|
|
|
|
2013-04-04 14:59:10 +01:00
|
|
|
|
2019-04-17 15:39:29 +01:00
|
|
|
|
2013-04-04 14:59:10 +01:00
|
|
|
|
2013-11-08 15:03:42 +00:00
|
|
|
|
2015-03-04 12:15:28 -07:00
|
|
|
|
2013-04-04 14:59:15 +01:00
|
|
|
|
2013-04-04 14:59:10 +01:00
|
|
|
|
|
|
|
|
|
2012-12-19 15:33:29 -07:00
|
|
|
|
|
|
|
|
|
2014-11-04 18:09:00 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-03-04 12:15:28 -07:00
|
|
|
|
2014-11-04 18:09:00 +00:00
|
|
|
|
2015-03-04 12:15:28 -07:00
|
|
|
|
2014-11-04 18:09:00 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-05-10 21:21:07 +05:30
|
|
|
|
|
|
|
|
|
2014-11-04 18:09:00 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-05-10 21:21:07 +05:30
|
|
|
|
2014-11-04 18:09:00 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-05-10 21:21:07 +05:30
|
|
|
|
2014-11-04 18:09:00 +00:00
|
|
|
|
|
|
|
|
|
2009-04-14 11:21:41 -04:00
|
|
|
|
2016-03-29 10:49:04 +01:00
|
|
|
|
|
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2014-05-02 13:50:14 +01:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2009-04-14 11:21:41 -04:00
|
|
|
|
2019-04-17 15:39:29 +01:00
|
|
|
|
|
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-11-26 10:21:11 -07:00
|
|
|
|
|
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
|
|
|
|
|
2014-05-06 13:12:11 +01:00
|
|
|
|
2013-11-26 10:21:11 -07:00
|
|
|
|
|
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-01-28 18:41:50 +00:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-07-21 11:48:32 -07:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-11-26 10:21:11 -07:00
|
|
|
|
|
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-07-24 15:05:25 -07:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:09 +01:00
|
|
|
|
2013-04-04 14:59:08 +01:00
|
|
|
|
|
|
|
|
|
2012-06-05 10:18:02 -07:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2013-11-08 15:03:37 +00:00
|
|
|
|
2013-04-04 14:59:11 +01:00
|
|
|
|
2013-04-04 14:59:09 +01:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:08 +01:00
|
|
|
|
2013-04-04 14:59:10 +01:00
|
|
|
|
2012-06-05 10:18:02 -07:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:08 +01:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2013-11-08 15:03:37 +00:00
|
|
|
|
2022-09-01 09:34:23 +08:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
|
|
|
|
|
2013-07-24 15:05:25 -07:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:09 +01:00
|
|
|
|
2013-04-04 14:59:08 +01:00
|
|
|
|
|
|
|
|
|
2012-06-05 10:18:02 -07:00
|
|
|
|
|
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2012-06-05 10:18:02 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2012-06-05 10:18:02 -07:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2013-11-08 15:03:37 +00:00
|
|
|
|
2013-04-04 14:59:11 +01:00
|
|
|
|
2013-04-04 14:59:09 +01:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:08 +01:00
|
|
|
|
2013-04-04 14:59:10 +01:00
|
|
|
|
2012-06-05 10:18:02 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:08 +01:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2013-11-08 15:03:37 +00:00
|
|
|
|
2012-06-05 10:18:02 -07:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2013-07-24 15:05:25 -07:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2013-07-24 15:05:25 -07:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:09 +01:00
|
|
|
|
2013-04-04 14:59:08 +01:00
|
|
|
|
|
|
|
|
|
2012-06-05 10:18:02 -07:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2013-11-08 15:03:37 +00:00
|
|
|
|
2013-04-04 14:59:11 +01:00
|
|
|
|
2013-04-04 14:59:09 +01:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:08 +01:00
|
|
|
|
2013-04-04 14:59:10 +01:00
|
|
|
|
2012-06-05 10:18:02 -07:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:08 +01:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2013-11-08 15:03:37 +00:00
|
|
|
|
2022-09-01 09:34:23 +08:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
|
|
|
|
|
2013-07-24 15:05:25 -07:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:09 +01:00
|
|
|
|
2013-04-04 14:59:08 +01:00
|
|
|
|
|
|
|
|
|
2012-06-05 10:18:02 -07:00
|
|
|
|
|
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2012-06-05 10:18:02 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2012-06-05 10:18:02 -07:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2013-11-08 15:03:37 +00:00
|
|
|
|
2013-04-04 14:59:11 +01:00
|
|
|
|
2013-04-04 14:59:09 +01:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:08 +01:00
|
|
|
|
2013-04-04 14:59:10 +01:00
|
|
|
|
2012-06-05 10:18:02 -07:00
|
|
|
|
2014-05-02 13:50:14 +01:00
|
|
|
|
2012-06-05 10:18:02 -07:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:08 +01:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2013-11-08 15:03:37 +00:00
|
|
|
|
2012-06-05 10:18:02 -07:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2013-07-24 15:05:25 -07:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2013-07-24 15:05:25 -07:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:09 +01:00
|
|
|
|
2013-04-04 14:59:08 +01:00
|
|
|
|
|
|
|
|
|
2012-06-05 10:18:02 -07:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2013-11-08 15:03:37 +00:00
|
|
|
|
2013-04-04 14:59:11 +01:00
|
|
|
|
2013-04-04 14:59:09 +01:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:08 +01:00
|
|
|
|
2013-04-04 14:59:10 +01:00
|
|
|
|
2012-06-05 10:18:02 -07:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:08 +01:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2013-11-08 15:03:37 +00:00
|
|
|
|
2022-09-01 09:34:23 +08:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
|
|
|
|
|
2013-07-24 15:05:25 -07:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:09 +01:00
|
|
|
|
2013-04-04 14:59:08 +01:00
|
|
|
|
|
|
|
|
|
2012-06-05 10:18:02 -07:00
|
|
|
|
|
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2012-06-05 10:18:02 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2012-06-05 10:18:02 -07:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2013-11-08 15:03:37 +00:00
|
|
|
|
2013-04-04 14:59:11 +01:00
|
|
|
|
2013-04-04 14:59:09 +01:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:08 +01:00
|
|
|
|
2013-04-04 14:59:10 +01:00
|
|
|
|
2012-06-05 10:18:02 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:08 +01:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2013-11-08 15:03:37 +00:00
|
|
|
|
2012-06-05 10:18:02 -07:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2013-07-24 15:05:25 -07:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2013-07-24 15:05:25 -07:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:09 +01:00
|
|
|
|
2013-04-04 14:59:08 +01:00
|
|
|
|
|
|
|
|
|
2012-06-05 10:18:02 -07:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2013-11-08 15:03:37 +00:00
|
|
|
|
2013-04-04 14:59:11 +01:00
|
|
|
|
2013-04-04 14:59:09 +01:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:08 +01:00
|
|
|
|
2013-04-04 14:59:10 +01:00
|
|
|
|
2012-06-05 10:18:02 -07:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:08 +01:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2013-11-08 15:03:37 +00:00
|
|
|
|
2022-09-01 09:34:23 +08:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
|
|
|
|
|
2013-07-24 15:05:25 -07:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:09 +01:00
|
|
|
|
2013-04-04 14:59:08 +01:00
|
|
|
|
|
|
|
|
|
2012-06-05 10:18:02 -07:00
|
|
|
|
|
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2012-06-05 10:18:02 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2012-06-05 10:18:02 -07:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2013-11-08 15:03:37 +00:00
|
|
|
|
2013-04-04 14:59:11 +01:00
|
|
|
|
2013-04-04 14:59:09 +01:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:08 +01:00
|
|
|
|
2013-04-04 14:59:10 +01:00
|
|
|
|
2012-06-05 10:18:02 -07:00
|
|
|
|
2014-05-02 13:50:14 +01:00
|
|
|
|
2012-06-05 10:18:02 -07:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:08 +01:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2013-11-08 15:03:37 +00:00
|
|
|
|
2012-06-05 10:18:02 -07:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2013-07-24 15:05:25 -07:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2013-07-24 15:05:25 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2013-07-24 15:05:25 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2023-06-20 16:41:38 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-03-27 15:13:06 +00:00
|
|
|
|
2016-03-21 09:18:35 -04:00
|
|
|
|
2015-03-27 15:13:06 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-03-21 09:18:35 -04:00
|
|
|
|
2015-03-27 15:13:06 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-03-27 15:13:00 +00:00
|
|
|
|
2016-03-29 10:49:04 +01:00
|
|
|
|
|
|
|
|
|
2012-12-19 15:31:57 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-03-27 15:13:06 +00:00
|
|
|
|
|
|
|
|
|
2012-12-19 15:31:57 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-03-21 09:18:35 -04:00
|
|
|
|
2015-03-27 15:13:06 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-03-21 09:18:35 -04:00
|
|
|
|
2012-12-19 15:42:26 -07:00
|
|
|
|
|
|
|
|
|
2016-03-21 09:18:35 -04:00
|
|
|
|
2012-12-19 15:42:26 -07:00
|
|
|
|
|
|
|
|
|
2015-03-27 15:13:06 +00:00
|
|
|
|
2012-12-19 15:42:26 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-03-21 09:18:35 -04:00
|
|
|
|
2015-03-27 15:13:01 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-03-21 09:18:35 -04:00
|
|
|
|
2015-03-27 15:13:01 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-10-23 14:28:18 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-01-28 18:41:46 +00:00
|
|
|
|
2015-09-23 16:33:27 +01:00
|
|
|
|
|
|
|
|
|
2015-01-28 18:41:46 +00:00
|
|
|
|
2015-09-23 16:33:27 +01:00
|
|
|
|
|
|
|
|
|
2015-01-28 18:41:46 +00:00
|
|
|
|
2012-12-19 15:42:47 -07:00
|
|
|
|
|
|
|
|
|
2016-03-21 09:18:35 -04:00
|
|
|
|
2012-12-19 15:42:47 -07:00
|
|
|
|
2015-03-27 15:13:01 +00:00
|
|
|
|
2012-12-19 15:42:47 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-03-27 15:13:06 +00:00
|
|
|
|
|
|
|
|
|
2016-03-21 09:18:35 -04:00
|
|
|
|
2015-03-27 15:13:06 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-10-23 14:28:18 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-04-21 13:18:10 +01:00
|
|
|
|
|
|
|
|
|
2016-03-21 09:18:35 -04:00
|
|
|
|
2015-04-21 13:18:10 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-06-11 11:32:29 -07:00
|
|
|
|
2015-09-23 16:33:27 +01:00
|
|
|
|
|
|
|
|
|
2015-04-21 13:18:10 +01:00
|
|
|
|
|
|
|
|
|
2015-09-23 16:33:27 +01:00
|
|
|
|
|
|
|
|
|
2015-04-21 13:18:10 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-09-23 16:33:27 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-06-11 11:32:29 -07:00
|
|
|
|
2015-09-23 16:33:27 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-06-11 11:32:29 -07:00
|
|
|
|
2013-06-19 15:24:36 -07:00
|
|
|
|
2013-06-11 11:32:29 -07:00
|
|
|
|
2013-06-19 15:24:36 -07:00
|
|
|
|
|
|
|
|
|
2015-04-21 13:18:10 +01:00
|
|
|
|
2013-06-19 15:24:36 -07:00
|
|
|
|
2013-06-11 11:32:29 -07:00
|
|
|
|
2013-06-19 15:24:36 -07:00
|
|
|
|
2013-06-11 11:32:29 -07:00
|
|
|
|
2012-12-19 15:31:57 -07:00
|
|
|
|
2015-01-28 18:41:50 +00:00
|
|
|
|
2012-12-19 15:31:57 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-10-23 14:28:18 +01:00
|
|
|
|
|
|
|
|
|
2012-12-19 15:31:57 -07:00
|
|
|
|
2019-04-17 15:39:29 +01:00
|
|
|
|
2025-10-23 14:28:18 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-10 11:11:04 +00:00
|
|
|
|
2025-10-23 14:28:18 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-03-10 11:11:04 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-05-06 13:12:10 +01:00
|
|
|
|
2012-12-19 15:31:57 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-11-08 15:03:27 +00:00
|
|
|
|
2015-03-27 15:13:03 +00:00
|
|
|
|
2012-12-19 15:31:57 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-04-17 15:39:29 +01:00
|
|
|
|
2012-12-19 15:43:18 -07:00
|
|
|
|
2012-12-19 15:31:57 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-11-08 15:03:28 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-04-17 15:39:29 +01:00
|
|
|
|
2013-11-08 15:03:28 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-12-19 15:31:57 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-07-22 16:53:16 +01:00
|
|
|
|
2019-04-17 15:39:29 +01:00
|
|
|
|
2012-12-19 15:31:57 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-07-22 16:53:16 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-12-19 15:31:57 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2015-01-28 18:41:47 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-06-08 21:04:41 +05:30
|
|
|
|
2010-05-03 16:32:28 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2009-03-16 22:06:20 -04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2019-04-17 15:39:29 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-03-04 12:15:28 -07:00
|
|
|
|
2025-07-22 16:53:16 +01:00
|
|
|
|
2014-05-01 13:53:12 +05:30
|
|
|
|
2025-07-22 16:53:16 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2025-07-22 16:53:16 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2012-12-19 15:42:02 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-01-09 09:46:10 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:58:54 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-04-04 14:58:56 +01:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-01-28 18:41:47 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-05-03 16:32:28 -07:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2009-03-16 22:06:37 -04:00
|
|
|
|
2009-03-16 22:05:20 -04:00
|
|
|
|
2009-03-16 22:05:14 -04:00
|
|
|
|
2009-04-14 11:21:41 -04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2019-04-17 15:39:29 +01:00
|
|
|
|
2012-12-19 15:42:02 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2013-06-07 21:29:49 +03:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2012-09-05 18:20:58 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-11-26 10:21:11 -07:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-05-02 13:50:14 +01:00
|
|
|
|
2009-04-14 11:21:41 -04:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-13 17:05:58 -08:00
|
|
|
|
2012-12-19 15:42:02 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-01-28 18:41:47 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-06-08 21:04:41 +05:30
|
|
|
|
2010-05-03 16:32:28 -07:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2012-12-19 15:39:18 -07:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2019-04-17 15:39:29 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-01-31 22:58:22 +05:30
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2014-11-04 18:09:00 +00:00
|
|
|
|
2012-12-19 15:39:18 -07:00
|
|
|
|
2012-12-19 17:27:02 -07:00
|
|
|
|
2008-11-13 17:05:58 -08:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2008-11-13 17:05:58 -08:00
|
|
|
|
2014-11-04 18:09:00 +00:00
|
|
|
|
2012-12-19 15:39:18 -07:00
|
|
|
|
2012-12-19 17:27:02 -07:00
|
|
|
|
2008-11-13 17:05:58 -08:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2012-12-19 15:42:02 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-01-28 18:41:47 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-06-08 21:04:41 +05:30
|
|
|
|
2010-05-03 16:32:28 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2009-03-16 22:06:09 -04:00
|
|
|
|
2009-03-16 22:05:14 -04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2019-04-17 15:39:29 +01:00
|
|
|
|
2026-02-21 16:37:42 -08:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-05 18:20:58 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-12-19 15:43:18 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-13 17:05:58 -08:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-12-19 15:42:02 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-01-28 18:41:47 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-06-08 21:04:41 +05:30
|
|
|
|
2020-04-25 18:35:03 -04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2009-03-16 22:05:14 -04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2019-04-17 15:39:29 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2020-04-25 18:35:03 -04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2020-04-25 18:35:03 -04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2020-04-25 18:35:03 -04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2020-04-25 18:35:03 -04:00
|
|
|
|
2009-03-16 22:05:02 -04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 18:35:03 -04:00
|
|
|
|
2013-10-07 16:50:05 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2020-04-25 18:35:03 -04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
comedi: Fix getting range information for subdevices 16 to 255
The `COMEDI_RANGEINFO` ioctl does not work properly for subdevice
indices above 15. Currently, the only in-tree COMEDI drivers that
support more than 16 subdevices are the "8255" driver and the
"comedi_bond" driver. Making the ioctl work for subdevice indices up to
255 is achievable. It needs minor changes to the handling of the
`COMEDI_RANGEINFO` and `COMEDI_CHANINFO` ioctls that should be mostly
harmless to user-space, apart from making them less broken. Details
follow...
The `COMEDI_RANGEINFO` ioctl command gets the list of supported ranges
(usually with units of volts or milliamps) for a COMEDI subdevice or
channel. (Only some subdevices have per-channel range tables, indicated
by the `SDF_RANGETYPE` flag in the subdevice information.) It uses a
`range_type` value and a user-space pointer, both supplied by
user-space, but the `range_type` value should match what was obtained
using the `COMEDI_CHANINFO` ioctl (if the subdevice has per-channel
range tables) or `COMEDI_SUBDINFO` ioctl (if the subdevice uses a
single range table for all channels). Bits 15 to 0 of the `range_type`
value contain the length of the range table, which is the only part that
user-space should care about (so it can use a suitably sized buffer to
fetch the range table). Bits 23 to 16 store the channel index, which is
assumed to be no more than 255 if the subdevice has per-channel range
tables, and is set to 0 if the subdevice has a single range table. For
`range_type` values produced by the `COMEDI_SUBDINFO` ioctl, bits 31 to
24 contain the subdevice index, which is assumed to be no more than 255.
But for `range_type` values produced by the `COMEDI_CHANINFO` ioctl,
bits 27 to 24 contain the subdevice index, which is assumed to be no
more than 15, and bits 31 to 28 contain the COMEDI device's minor device
number for some unknown reason lost in the mists of time. The
`COMEDI_RANGEINFO` ioctl extract the length from bits 15 to 0 of the
user-supplied `range_type` value, extracts the channel index from bits
23 to 16 (only used if the subdevice has per-channel range tables),
extracts the subdevice index from bits 27 to 24, and ignores bits 31 to
28. So for subdevice indices 16 to 255, the `COMEDI_SUBDINFO` or
`COMEDI_CHANINFO` ioctl will report a `range_type` value that doesn't
work with the `COMEDI_RANGEINFO` ioctl. It will either get the range
table for the subdevice index modulo 16, or will fail with `-EINVAL`.
To fix this, always use bits 31 to 24 of the `range_type` value to hold
the subdevice index (assumed to be no more than 255). This affects the
`COMEDI_CHANINFO` and `COMEDI_RANGEINFO` ioctls. There should not be
anything in user-space that depends on the old, broken usage, although
it may now see different values in bits 31 to 28 of the `range_type`
values reported by the `COMEDI_CHANINFO` ioctl for subdevices that have
per-channel subdevices. User-space should not be trying to decode bits
31 to 16 of the `range_type` values anyway.
Fixes: ed9eccbe8970 ("Staging: add comedi core")
Cc: stable@vger.kernel.org #5.17+
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Link: https://patch.msgid.link/20251203162438.176841-1-abbotti@mev.co.uk
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2025-12-03 16:24:38 +00:00
|
|
|
|
2008-11-13 17:05:58 -08:00
|
|
|
|
2020-04-25 18:35:03 -04:00
|
|
|
|
2010-09-05 22:32:33 +04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-01-28 18:41:47 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
comedi: don't use mutex for COMEDI_BUFINFO ioctl
The main mutex in a comedi device can get held for quite a while when
processing comedi instructions, so for performance reasons, the "read",
"write", and "poll" file operations do not use it; they use the
`attach_lock` rwsemaphore to protect against the comedi device becoming
detached at an inopportune moment. As an alternative to using the
"read" and "write" operations, user-space can mmap the data buffer and
use the `COMEDI_BUFINFO` ioctl to manage data transfer through the
buffer. However, the "ioctl" file handler currently locks the main
mutex for all ioctl commands. Make the handling of the `COMEDI_BUFINFO`
an exception, using the `attach_lock` rwsemaphore during normal
operation. However, before it calls `do_become_nonbusy()` at the end of
acquisition, it does need to lock the main mutex, but it needs to unlock
the `attach_lock` rwsemaphore first to avoid deadlock. After locking
the main mutex, it needs to check that it is still in a suitable state
to become non-busy, because things may have changed while unlocked.
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Link: https://patch.msgid.link/20251205131332.16672-1-abbotti@mev.co.uk
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2025-12-05 13:13:32 +00:00
|
|
|
|
|
|
|
|
|
2015-01-28 18:41:47 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-05-03 16:32:28 -07:00
|
|
|
|
2010-05-19 18:09:50 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2009-03-16 22:06:42 -04:00
|
|
|
|
2009-03-16 22:05:14 -04:00
|
|
|
|
2009-03-16 22:05:20 -04:00
|
|
|
|
2016-02-19 16:13:56 +00:00
|
|
|
|
|
|
|
|
|
comedi: don't use mutex for COMEDI_BUFINFO ioctl
The main mutex in a comedi device can get held for quite a while when
processing comedi instructions, so for performance reasons, the "read",
"write", and "poll" file operations do not use it; they use the
`attach_lock` rwsemaphore to protect against the comedi device becoming
detached at an inopportune moment. As an alternative to using the
"read" and "write" operations, user-space can mmap the data buffer and
use the `COMEDI_BUFINFO` ioctl to manage data transfer through the
buffer. However, the "ioctl" file handler currently locks the main
mutex for all ioctl commands. Make the handling of the `COMEDI_BUFINFO`
an exception, using the `attach_lock` rwsemaphore during normal
operation. However, before it calls `do_become_nonbusy()` at the end of
acquisition, it does need to lock the main mutex, but it needs to unlock
the `attach_lock` rwsemaphore first to avoid deadlock. After locking
the main mutex, it needs to check that it is still in a suitable state
to become non-busy, because things may have changed while unlocked.
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Link: https://patch.msgid.link/20251205131332.16672-1-abbotti@mev.co.uk
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2025-12-05 13:13:32 +00:00
|
|
|
|
|
|
|
|
|
2016-02-19 16:13:52 +00:00
|
|
|
|
comedi: don't use mutex for COMEDI_BUFINFO ioctl
The main mutex in a comedi device can get held for quite a while when
processing comedi instructions, so for performance reasons, the "read",
"write", and "poll" file operations do not use it; they use the
`attach_lock` rwsemaphore to protect against the comedi device becoming
detached at an inopportune moment. As an alternative to using the
"read" and "write" operations, user-space can mmap the data buffer and
use the `COMEDI_BUFINFO` ioctl to manage data transfer through the
buffer. However, the "ioctl" file handler currently locks the main
mutex for all ioctl commands. Make the handling of the `COMEDI_BUFINFO`
an exception, using the `attach_lock` rwsemaphore during normal
operation. However, before it calls `do_become_nonbusy()` at the end of
acquisition, it does need to lock the main mutex, but it needs to unlock
the `attach_lock` rwsemaphore first to avoid deadlock. After locking
the main mutex, it needs to check that it is still in a suitable state
to become non-busy, because things may have changed while unlocked.
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Link: https://patch.msgid.link/20251205131332.16672-1-abbotti@mev.co.uk
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2025-12-05 13:13:32 +00:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2012-12-19 15:42:02 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
comedi: don't use mutex for COMEDI_BUFINFO ioctl
The main mutex in a comedi device can get held for quite a while when
processing comedi instructions, so for performance reasons, the "read",
"write", and "poll" file operations do not use it; they use the
`attach_lock` rwsemaphore to protect against the comedi device becoming
detached at an inopportune moment. As an alternative to using the
"read" and "write" operations, user-space can mmap the data buffer and
use the `COMEDI_BUFINFO` ioctl to manage data transfer through the
buffer. However, the "ioctl" file handler currently locks the main
mutex for all ioctl commands. Make the handling of the `COMEDI_BUFINFO`
an exception, using the `attach_lock` rwsemaphore during normal
operation. However, before it calls `do_become_nonbusy()` at the end of
acquisition, it does need to lock the main mutex, but it needs to unlock
the `attach_lock` rwsemaphore first to avoid deadlock. After locking
the main mutex, it needs to check that it is still in a suitable state
to become non-busy, because things may have changed while unlocked.
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Link: https://patch.msgid.link/20251205131332.16672-1-abbotti@mev.co.uk
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2025-12-05 13:13:32 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2012-09-05 18:20:58 -07:00
|
|
|
|
2010-05-19 18:09:50 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
comedi: don't use mutex for COMEDI_BUFINFO ioctl
The main mutex in a comedi device can get held for quite a while when
processing comedi instructions, so for performance reasons, the "read",
"write", and "poll" file operations do not use it; they use the
`attach_lock` rwsemaphore to protect against the comedi device becoming
detached at an inopportune moment. As an alternative to using the
"read" and "write" operations, user-space can mmap the data buffer and
use the `COMEDI_BUFINFO` ioctl to manage data transfer through the
buffer. However, the "ioctl" file handler currently locks the main
mutex for all ioctl commands. Make the handling of the `COMEDI_BUFINFO`
an exception, using the `attach_lock` rwsemaphore during normal
operation. However, before it calls `do_become_nonbusy()` at the end of
acquisition, it does need to lock the main mutex, but it needs to unlock
the `attach_lock` rwsemaphore first to avoid deadlock. After locking
the main mutex, it needs to check that it is still in a suitable state
to become non-busy, because things may have changed while unlocked.
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Link: https://patch.msgid.link/20251205131332.16672-1-abbotti@mev.co.uk
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2025-12-05 13:13:32 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2016-02-19 16:13:57 +00:00
|
|
|
|
comedi: don't use mutex for COMEDI_BUFINFO ioctl
The main mutex in a comedi device can get held for quite a while when
processing comedi instructions, so for performance reasons, the "read",
"write", and "poll" file operations do not use it; they use the
`attach_lock` rwsemaphore to protect against the comedi device becoming
detached at an inopportune moment. As an alternative to using the
"read" and "write" operations, user-space can mmap the data buffer and
use the `COMEDI_BUFINFO` ioctl to manage data transfer through the
buffer. However, the "ioctl" file handler currently locks the main
mutex for all ioctl commands. Make the handling of the `COMEDI_BUFINFO`
an exception, using the `attach_lock` rwsemaphore during normal
operation. However, before it calls `do_become_nonbusy()` at the end of
acquisition, it does need to lock the main mutex, but it needs to unlock
the `attach_lock` rwsemaphore first to avoid deadlock. After locking
the main mutex, it needs to check that it is still in a suitable state
to become non-busy, because things may have changed while unlocked.
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Link: https://patch.msgid.link/20251205131332.16672-1-abbotti@mev.co.uk
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2025-12-05 13:13:32 +00:00
|
|
|
|
|
|
|
|
|
2016-02-19 16:13:51 +00:00
|
|
|
|
|
|
|
|
|
comedi: Use reference count for asynchronous command functions
For interrupts from badly behaved hardware (as emulated by Syzbot), it
is possible for the Comedi core functions that manage the progress of
asynchronous data acquisition to be called from driver ISRs while no
asynchronous command has been set up, which can cause problems such as
invalid pointer dereferencing or dividing by zero.
Change those functions in the Comedi core to use this pattern: if
`comedi_get_is_subdevice_running(s)` returns `true` then call a safe
version of the function with the same name prefixed with an underscore,
followed by a call to `comedi_put_is_subdevice_running(s)`, otherwise
take some default action.
`comedi_get_is_subdevice_running(s)` returning `true` ensures that the
details of the asynchronous command will not be destroyed before the
matching call to `comedi_put_is_subdevice_running(s)`.
Replace calls to those functions from elsewhere in the Comedi core with
calls to the safe versions of the functions.
The modified functions are: `comedi_buf_read_alloc()`,
`comedi_buf_read_free()`, `comedi_buf_read_n_available()`,
`comedi_buf_read_samples()`, `comedi_buf_write_alloc()`,
`comedi_buf_write_free()`, `comedi_buf_write_samples()`,
`comedi_bytes_per_scan()`, `comedi_event()`, `comedi_handle_events()`,
`comedi_inc_scan_progress()`, `comedi_nsamples_left()`,
`comedi_nscans_left()`.
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Link: https://patch.msgid.link/20251023133001.8439-3-abbotti@mev.co.uk
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2025-10-23 14:28:19 +01:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2016-02-19 16:13:56 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
comedi: Use reference count for asynchronous command functions
For interrupts from badly behaved hardware (as emulated by Syzbot), it
is possible for the Comedi core functions that manage the progress of
asynchronous data acquisition to be called from driver ISRs while no
asynchronous command has been set up, which can cause problems such as
invalid pointer dereferencing or dividing by zero.
Change those functions in the Comedi core to use this pattern: if
`comedi_get_is_subdevice_running(s)` returns `true` then call a safe
version of the function with the same name prefixed with an underscore,
followed by a call to `comedi_put_is_subdevice_running(s)`, otherwise
take some default action.
`comedi_get_is_subdevice_running(s)` returning `true` ensures that the
details of the asynchronous command will not be destroyed before the
matching call to `comedi_put_is_subdevice_running(s)`.
Replace calls to those functions from elsewhere in the Comedi core with
calls to the safe versions of the functions.
The modified functions are: `comedi_buf_read_alloc()`,
`comedi_buf_read_free()`, `comedi_buf_read_n_available()`,
`comedi_buf_read_samples()`, `comedi_buf_write_alloc()`,
`comedi_buf_write_free()`, `comedi_buf_write_samples()`,
`comedi_bytes_per_scan()`, `comedi_event()`, `comedi_handle_events()`,
`comedi_inc_scan_progress()`, `comedi_nsamples_left()`,
`comedi_nscans_left()`.
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Link: https://patch.msgid.link/20251023133001.8439-3-abbotti@mev.co.uk
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2025-10-23 14:28:19 +01:00
|
|
|
|
2016-02-19 16:13:56 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-19 16:13:55 +00:00
|
|
|
|
2016-02-19 16:13:56 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-19 16:13:51 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-19 16:13:57 +00:00
|
|
|
|
2016-02-19 16:13:53 +00:00
|
|
|
|
2016-02-19 16:13:57 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
comedi: Use reference count for asynchronous command functions
For interrupts from badly behaved hardware (as emulated by Syzbot), it
is possible for the Comedi core functions that manage the progress of
asynchronous data acquisition to be called from driver ISRs while no
asynchronous command has been set up, which can cause problems such as
invalid pointer dereferencing or dividing by zero.
Change those functions in the Comedi core to use this pattern: if
`comedi_get_is_subdevice_running(s)` returns `true` then call a safe
version of the function with the same name prefixed with an underscore,
followed by a call to `comedi_put_is_subdevice_running(s)`, otherwise
take some default action.
`comedi_get_is_subdevice_running(s)` returning `true` ensures that the
details of the asynchronous command will not be destroyed before the
matching call to `comedi_put_is_subdevice_running(s)`.
Replace calls to those functions from elsewhere in the Comedi core with
calls to the safe versions of the functions.
The modified functions are: `comedi_buf_read_alloc()`,
`comedi_buf_read_free()`, `comedi_buf_read_n_available()`,
`comedi_buf_read_samples()`, `comedi_buf_write_alloc()`,
`comedi_buf_write_free()`, `comedi_buf_write_samples()`,
`comedi_bytes_per_scan()`, `comedi_event()`, `comedi_handle_events()`,
`comedi_inc_scan_progress()`, `comedi_nsamples_left()`,
`comedi_nscans_left()`.
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Link: https://patch.msgid.link/20251023133001.8439-3-abbotti@mev.co.uk
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2025-10-23 14:28:19 +01:00
|
|
|
|
2016-02-19 16:13:51 +00:00
|
|
|
|
comedi: Use reference count for asynchronous command functions
For interrupts from badly behaved hardware (as emulated by Syzbot), it
is possible for the Comedi core functions that manage the progress of
asynchronous data acquisition to be called from driver ISRs while no
asynchronous command has been set up, which can cause problems such as
invalid pointer dereferencing or dividing by zero.
Change those functions in the Comedi core to use this pattern: if
`comedi_get_is_subdevice_running(s)` returns `true` then call a safe
version of the function with the same name prefixed with an underscore,
followed by a call to `comedi_put_is_subdevice_running(s)`, otherwise
take some default action.
`comedi_get_is_subdevice_running(s)` returning `true` ensures that the
details of the asynchronous command will not be destroyed before the
matching call to `comedi_put_is_subdevice_running(s)`.
Replace calls to those functions from elsewhere in the Comedi core with
calls to the safe versions of the functions.
The modified functions are: `comedi_buf_read_alloc()`,
`comedi_buf_read_free()`, `comedi_buf_read_n_available()`,
`comedi_buf_read_samples()`, `comedi_buf_write_alloc()`,
`comedi_buf_write_free()`, `comedi_buf_write_samples()`,
`comedi_bytes_per_scan()`, `comedi_event()`, `comedi_handle_events()`,
`comedi_inc_scan_progress()`, `comedi_nsamples_left()`,
`comedi_nscans_left()`.
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Link: https://patch.msgid.link/20251023133001.8439-3-abbotti@mev.co.uk
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2025-10-23 14:28:19 +01:00
|
|
|
|
2016-02-19 16:13:51 +00:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
comedi: don't use mutex for COMEDI_BUFINFO ioctl
The main mutex in a comedi device can get held for quite a while when
processing comedi instructions, so for performance reasons, the "read",
"write", and "poll" file operations do not use it; they use the
`attach_lock` rwsemaphore to protect against the comedi device becoming
detached at an inopportune moment. As an alternative to using the
"read" and "write" operations, user-space can mmap the data buffer and
use the `COMEDI_BUFINFO` ioctl to manage data transfer through the
buffer. However, the "ioctl" file handler currently locks the main
mutex for all ioctl commands. Make the handling of the `COMEDI_BUFINFO`
an exception, using the `attach_lock` rwsemaphore during normal
operation. However, before it calls `do_become_nonbusy()` at the end of
acquisition, it does need to lock the main mutex, but it needs to unlock
the `attach_lock` rwsemaphore first to avoid deadlock. After locking
the main mutex, it needs to check that it is still in a suitable state
to become non-busy, because things may have changed while unlocked.
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Link: https://patch.msgid.link/20251205131332.16672-1-abbotti@mev.co.uk
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2025-12-05 13:13:32 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-02-19 16:13:52 +00:00
|
|
|
|
2016-02-19 16:13:56 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-12-19 15:42:02 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-06-08 21:04:41 +05:30
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2008-11-13 17:05:58 -08:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-01-03 15:11:27 +00:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-10-30 14:17:13 +00:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-11-14 11:22:57 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-09-19 10:51:03 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-01-28 18:41:50 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2014-07-17 12:27:32 -07:00
|
|
|
|
2012-08-16 14:38:05 +01:00
|
|
|
|
2014-07-17 12:27:32 -07:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-10-03 14:56:02 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-04-17 15:39:29 +01:00
|
|
|
|
2018-10-03 14:56:02 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-06-08 21:04:41 +05:30
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2009-03-16 22:05:14 -04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-04-17 15:39:29 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-06-17 21:56:15 +02:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-06-17 21:56:15 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-11-26 10:21:11 -07:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-05 18:20:58 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2013-11-26 10:21:11 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-11-26 10:21:11 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-18 19:46:58 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-10-03 14:56:02 -06:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2013-11-26 10:21:11 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-03-16 22:05:02 -04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2013-11-26 10:21:11 -07:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-05 18:20:58 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2013-11-26 10:21:11 -07:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-11-26 10:21:11 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-05-01 12:33:17 -07:00
|
|
|
|
2008-11-13 17:05:58 -08:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2013-11-26 10:21:11 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-10-13 21:07:47 +05:30
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-02-10 11:49:45 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-13 17:05:58 -08:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-11-26 10:21:11 -07:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-02-10 11:49:45 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2014-02-10 11:49:45 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-01-18 17:44:33 +00:00
|
|
|
|
2015-01-28 18:41:50 +00:00
|
|
|
|
|
|
|
|
|
2011-01-18 17:44:33 +00:00
|
|
|
|
2015-01-28 18:41:50 +00:00
|
|
|
|
|
|
|
|
|
2014-07-18 14:28:14 -07:00
|
|
|
|
|
|
|
|
|
2011-01-18 17:44:33 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-07-18 14:28:14 -07:00
|
|
|
|
2011-01-18 17:44:33 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-13 17:05:58 -08:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-01-21 14:02:59 -07:00
|
|
|
|
2015-01-28 18:41:47 +00:00
|
|
|
|
|
|
|
|
|
2013-01-21 14:02:59 -07:00
|
|
|
|
2015-01-28 18:41:47 +00:00
|
|
|
|
|
|
|
|
|
2013-01-21 14:02:59 -07:00
|
|
|
|
2015-01-28 18:41:47 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-01-21 14:02:59 -07:00
|
|
|
|
2015-01-28 18:41:47 +00:00
|
|
|
|
|
|
|
|
|
2013-01-21 14:02:59 -07:00
|
|
|
|
|
|
|
|
|
2018-12-04 12:07:50 -07:00
|
|
|
|
|
|
|
|
|
2013-01-21 14:02:59 -07:00
|
|
|
|
2020-04-25 20:33:04 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-01-21 14:02:59 -07:00
|
|
|
|
|
|
|
|
|
2018-12-04 12:07:50 -07:00
|
|
|
|
2013-01-21 14:02:59 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-04-17 15:39:29 +01:00
|
|
|
|
2013-01-21 14:02:59 -07:00
|
|
|
|
2018-12-04 12:07:50 -07:00
|
|
|
|
2020-04-25 20:33:04 -04:00
|
|
|
|
2013-01-21 14:02:59 -07:00
|
|
|
|
2013-11-26 10:21:11 -07:00
|
|
|
|
|
|
|
|
|
2013-01-21 14:02:59 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2018-12-04 12:07:50 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 20:33:04 -04:00
|
|
|
|
2025-07-07 17:14:39 +01:00
|
|
|
|
|
|
|
|
|
2013-01-21 14:02:59 -07:00
|
|
|
|
|
|
|
|
|
2025-07-07 17:14:39 +01:00
|
|
|
|
2013-11-26 10:21:11 -07:00
|
|
|
|
|
|
|
|
|
2013-01-21 14:02:59 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-07-07 17:14:39 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-07-25 13:53:24 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-01-21 14:02:59 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-07-07 17:14:39 +01:00
|
|
|
|
2013-11-26 10:21:11 -07:00
|
|
|
|
|
|
|
|
|
2013-01-21 14:02:59 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-07-04 13:04:05 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2015-01-28 18:41:47 +00:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2015-01-28 18:41:47 +00:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2015-01-28 18:41:47 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2015-01-28 18:41:47 +00:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2010-05-03 16:32:28 -07:00
|
|
|
|
2020-04-25 20:11:57 -04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2009-03-16 22:05:02 -04:00
|
|
|
|
2018-12-04 12:07:50 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2019-04-17 15:39:29 +01:00
|
|
|
|
2019-01-15 21:06:56 +05:30
|
|
|
|
2020-04-25 20:11:57 -04:00
|
|
|
|
2018-12-04 12:07:50 -07:00
|
|
|
|
|
|
|
|
|
2020-04-25 20:11:57 -04:00
|
|
|
|
|
|
|
|
|
2018-12-04 12:07:50 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 20:11:57 -04:00
|
|
|
|
2010-05-13 17:44:39 +08:00
|
|
|
|
2020-04-25 20:11:57 -04:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-07-07 17:14:39 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-07-25 13:53:24 +01:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2020-04-25 20:11:57 -04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2020-04-25 20:11:57 -04:00
|
|
|
|
|
|
|
|
|
2010-05-13 17:44:39 +08:00
|
|
|
|
2020-04-25 20:11:57 -04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 20:11:57 -04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2008-11-13 17:05:58 -08:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-03-06 12:02:56 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-04-17 15:39:29 +01:00
|
|
|
|
2014-03-06 12:02:56 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-03-31 22:55:39 +02:00
|
|
|
|
|
|
|
|
|
2014-03-06 12:02:56 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-03-31 22:55:39 +02:00
|
|
|
|
|
|
|
|
|
2014-03-06 12:02:56 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-10-30 12:42:26 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-03-06 12:02:56 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-03-06 12:02:57 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-04-17 15:39:29 +01:00
|
|
|
|
2014-10-20 15:10:40 +01:00
|
|
|
|
2023-11-03 12:29:33 +01:00
|
|
|
|
|
|
|
|
|
2014-03-06 12:02:57 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-01-28 18:41:47 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-05-03 16:32:28 -07:00
|
|
|
|
2020-04-26 09:01:49 -04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2009-03-16 22:05:14 -04:00
|
|
|
|
2009-03-16 22:05:20 -04:00
|
|
|
|
2012-09-18 11:43:52 -07:00
|
|
|
|
2014-03-06 12:02:56 -07:00
|
|
|
|
|
|
|
|
|
2019-04-17 15:39:29 +01:00
|
|
|
|
|
|
|
|
|
2020-04-26 09:01:49 -04:00
|
|
|
|
|
|
|
|
|
2014-03-06 12:02:56 -07:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2008-11-13 17:05:58 -08:00
|
|
|
|
2020-04-26 09:01:49 -04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2020-04-26 09:01:49 -04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-11-26 10:21:11 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-11-26 10:21:11 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-26 09:01:49 -04:00
|
|
|
|
2013-11-26 10:21:11 -07:00
|
|
|
|
2020-04-26 09:01:49 -04:00
|
|
|
|
2013-07-05 16:49:34 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2020-04-26 09:01:49 -04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2014-03-06 12:02:57 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-09-03 13:45:44 +01:00
|
|
|
|
2013-11-26 10:21:11 -07:00
|
|
|
|
2020-04-26 09:01:49 -04:00
|
|
|
|
2008-11-13 17:05:58 -08:00
|
|
|
|
2020-04-26 09:01:49 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-11-26 10:21:11 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-05-06 13:12:10 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2014-10-13 09:56:08 -07:00
|
|
|
|
2014-09-03 13:45:30 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2025-10-23 14:28:18 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-03-27 15:13:00 +00:00
|
|
|
|
2025-10-23 14:28:18 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2015-01-20 12:06:00 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-07-05 16:49:34 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-13 17:05:58 -08:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-01-28 18:41:47 +00:00
|
|
|
|
2015-04-24 09:40:42 -04:00
|
|
|
|
2015-01-28 18:41:47 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-05-03 16:32:28 -07:00
|
|
|
|
2020-04-26 08:56:55 -04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2009-03-16 22:05:14 -04:00
|
|
|
|
2012-09-18 11:43:52 -07:00
|
|
|
|
2014-03-06 12:02:56 -07:00
|
|
|
|
|
|
|
|
|
2019-04-17 15:39:29 +01:00
|
|
|
|
|
|
|
|
|
2020-04-26 08:56:55 -04:00
|
|
|
|
|
|
|
|
|
2014-03-06 12:02:56 -07:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2008-11-13 17:05:58 -08:00
|
|
|
|
2020-04-26 08:56:55 -04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2020-04-26 08:56:55 -04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2014-10-08 16:09:14 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-26 08:56:55 -04:00
|
|
|
|
2014-10-08 16:09:14 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2020-04-26 08:56:55 -04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2020-04-26 08:56:55 -04:00
|
|
|
|
2014-10-20 15:10:40 +01:00
|
|
|
|
2008-11-13 17:05:58 -08:00
|
|
|
|
2020-04-26 08:56:55 -04:00
|
|
|
|
|
|
|
|
|
2014-03-06 12:02:57 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-01-28 18:41:47 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-10-28 17:15:47 +00:00
|
|
|
|
2009-06-08 21:04:41 +05:30
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2009-03-16 22:05:14 -04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2019-04-17 15:39:29 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2012-09-05 18:20:58 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2009-04-27 14:44:31 -07:00
|
|
|
|
2008-11-13 17:05:58 -08:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2008-11-13 17:05:58 -08:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2009-04-27 14:44:31 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-01-28 18:41:47 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-10-28 17:15:47 +00:00
|
|
|
|
2009-06-08 21:04:41 +05:30
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2009-03-16 22:05:14 -04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2019-04-17 15:39:29 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2012-09-05 18:20:58 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-07-21 11:01:26 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-01-28 18:41:47 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-10-28 17:15:47 +00:00
|
|
|
|
2009-06-08 21:04:41 +05:30
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2009-03-16 22:05:14 -04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2019-04-17 15:39:29 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2012-09-05 18:20:58 -07:00
|
|
|
|
2015-03-04 12:15:28 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-10-06 13:46:09 +05:30
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-01-28 18:41:47 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-10-28 17:15:47 +00:00
|
|
|
|
2009-06-08 21:04:41 +05:30
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2009-03-16 22:05:14 -04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2019-04-17 15:39:29 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2012-09-05 18:20:58 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-11-04 18:09:01 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-04-17 15:39:29 +01:00
|
|
|
|
2014-11-04 18:09:01 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-05-10 21:21:07 +05:30
|
|
|
|
2014-11-04 18:09:01 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2019-04-17 15:39:29 +01:00
|
|
|
|
2014-11-04 18:09:01 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-05-10 21:21:07 +05:30
|
|
|
|
2014-11-04 18:09:01 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-06-07 17:05:27 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-03-21 09:18:35 -04:00
|
|
|
|
2014-11-04 18:09:00 +00:00
|
|
|
|
|
|
|
|
|
2012-06-07 17:05:27 -07:00
|
|
|
|
|
|
|
|
|
comedi: don't use mutex for COMEDI_BUFINFO ioctl
The main mutex in a comedi device can get held for quite a while when
processing comedi instructions, so for performance reasons, the "read",
"write", and "poll" file operations do not use it; they use the
`attach_lock` rwsemaphore to protect against the comedi device becoming
detached at an inopportune moment. As an alternative to using the
"read" and "write" operations, user-space can mmap the data buffer and
use the `COMEDI_BUFINFO` ioctl to manage data transfer through the
buffer. However, the "ioctl" file handler currently locks the main
mutex for all ioctl commands. Make the handling of the `COMEDI_BUFINFO`
an exception, using the `attach_lock` rwsemaphore during normal
operation. However, before it calls `do_become_nonbusy()` at the end of
acquisition, it does need to lock the main mutex, but it needs to unlock
the `attach_lock` rwsemaphore first to avoid deadlock. After locking
the main mutex, it needs to check that it is still in a suitable state
to become non-busy, because things may have changed while unlocked.
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Link: https://patch.msgid.link/20251205131332.16672-1-abbotti@mev.co.uk
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2025-12-05 13:13:32 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-06-07 17:05:27 -07:00
|
|
|
|
|
|
|
|
|
2015-01-28 18:41:50 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-06-07 17:05:27 -07:00
|
|
|
|
2013-01-28 16:14:31 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-06-07 17:05:27 -07:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:58:54 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-01-28 18:41:50 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:18 +01:00
|
|
|
|
2013-04-04 14:58:54 +01:00
|
|
|
|
2013-04-04 14:59:16 +01:00
|
|
|
|
2013-04-04 14:58:54 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-06-07 17:05:27 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-11-26 10:21:11 -07:00
|
|
|
|
2012-06-07 17:05:27 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 18:35:03 -04:00
|
|
|
|
|
|
|
|
|
2020-06-05 08:51:40 +05:30
|
|
|
|
2020-04-25 18:35:03 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-06-07 17:05:27 -07:00
|
|
|
|
2020-04-25 18:35:03 -04:00
|
|
|
|
2020-04-25 18:44:30 -04:00
|
|
|
|
|
|
|
|
|
2020-06-05 08:51:40 +05:30
|
|
|
|
2020-04-25 18:44:30 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-06-07 17:05:27 -07:00
|
|
|
|
2020-04-25 18:44:30 -04:00
|
|
|
|
2012-06-07 17:05:27 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-26 09:01:49 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-06-07 17:05:27 -07:00
|
|
|
|
2020-04-26 09:01:49 -04:00
|
|
|
|
2020-04-26 08:56:55 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-06-07 17:05:27 -07:00
|
|
|
|
2020-04-26 08:56:55 -04:00
|
|
|
|
2020-04-25 20:33:04 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-07-04 13:04:05 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-09-17 15:13:47 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 20:33:04 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-06-07 17:05:27 -07:00
|
|
|
|
2020-04-25 20:33:04 -04:00
|
|
|
|
2020-04-25 20:11:57 -04:00
|
|
|
|
|
|
|
|
|
2020-06-05 08:51:40 +05:30
|
|
|
|
2020-04-25 20:11:57 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-06-07 17:05:27 -07:00
|
|
|
|
2020-04-25 20:11:57 -04:00
|
|
|
|
2012-06-07 17:05:27 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-11-04 18:09:01 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-06-07 17:05:27 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-10-29 09:45:39 +02:00
|
|
|
|
|
|
|
|
|
2013-11-08 15:03:43 +00:00
|
|
|
|
2011-10-29 09:45:39 +02:00
|
|
|
|
2013-11-08 15:03:43 +00:00
|
|
|
|
|
|
|
|
|
2011-10-29 09:45:39 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2013-11-08 15:03:43 +00:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2013-11-08 15:03:43 +00:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2017-04-20 19:05:14 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-09-09 15:39:26 -07:00
|
|
|
|
2011-10-29 09:45:39 +02:00
|
|
|
|
|
|
|
|
|
2017-04-20 19:05:14 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-11-04 18:09:00 +00:00
|
|
|
|
|
|
|
|
|
2012-12-19 15:45:12 -07:00
|
|
|
|
|
|
|
|
|
staging: comedi: fix circular locking dependency in comedi_mmap()
Mmapping a comedi data buffer with lockdep checking enabled produced the
following kernel debug messages:
======================================================
[ INFO: possible circular locking dependency detected ]
3.5.0-rc3-ija1+ #9 Tainted: G C
-------------------------------------------------------
comedi_test/4160 is trying to acquire lock:
(&dev->mutex#2){+.+.+.}, at: [<ffffffffa00313f4>] comedi_mmap+0x57/0x1d9 [comedi]
but task is already holding lock:
(&mm->mmap_sem){++++++}, at: [<ffffffff810c96fe>] vm_mmap_pgoff+0x41/0x76
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #1 (&mm->mmap_sem){++++++}:
[<ffffffff8106d0e8>] lock_acquire+0x97/0x105
[<ffffffff810ce3bc>] might_fault+0x6d/0x90
[<ffffffffa0031ffb>] do_devinfo_ioctl.isra.7+0x11e/0x14c [comedi]
[<ffffffffa003227f>] comedi_unlocked_ioctl+0x256/0xe48 [comedi]
[<ffffffff810f7fcd>] vfs_ioctl+0x18/0x34
[<ffffffff810f87fd>] do_vfs_ioctl+0x382/0x43c
[<ffffffff810f88f9>] sys_ioctl+0x42/0x65
[<ffffffff81415c62>] system_call_fastpath+0x16/0x1b
-> #0 (&dev->mutex#2){+.+.+.}:
[<ffffffff8106c528>] __lock_acquire+0x101d/0x1591
[<ffffffff8106d0e8>] lock_acquire+0x97/0x105
[<ffffffff8140c894>] mutex_lock_nested+0x46/0x2a4
[<ffffffffa00313f4>] comedi_mmap+0x57/0x1d9 [comedi]
[<ffffffff810d5816>] mmap_region+0x281/0x492
[<ffffffff810d5c92>] do_mmap_pgoff+0x26b/0x2a7
[<ffffffff810c971a>] vm_mmap_pgoff+0x5d/0x76
[<ffffffff810d493f>] sys_mmap_pgoff+0xc7/0x10d
[<ffffffff81004d36>] sys_mmap+0x16/0x20
[<ffffffff81415c62>] system_call_fastpath+0x16/0x1b
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(&mm->mmap_sem);
lock(&dev->mutex#2);
lock(&mm->mmap_sem);
lock(&dev->mutex#2);
*** DEADLOCK ***
To avoid the circular dependency, just try to get the lock in
`comedi_mmap()` instead of blocking. Since the comedi device's main mutex
is heavily used, do a down-read of its `attach_lock` rwsemaphore
instead. Trying to down-read `attach_lock` should only fail if
some task has down-write locked it, and that is only done while the
comedi device is being attached to or detached from a low-level hardware
device.
Unfortunately, acquiring the `attach_lock` doesn't prevent another
task replacing the comedi data buffer we are trying to mmap. The
details of the buffer are held in a `struct comedi_buf_map` and pointed
to by `s->async->buf_map` where `s` is the comedi subdevice whose buffer
we are trying to map. The `struct comedi_buf_map` is already reference
counted with a `struct kref`, so we can stop it being freed prematurely.
Modify `comedi_mmap()` to call new function
`comedi_buf_map_from_subdev_get()` to read the subdevice's current
buffer map pointer and increment its reference instead of accessing
`async->buf_map` directly. Call `comedi_buf_map_put()` to decrement the
reference once the buffer map structure has been dealt with. (Note that
`comedi_buf_map_put()` does nothing if passed a NULL pointer.)
`comedi_buf_map_from_subdev_get()` checks the subdevice's buffer map
pointer has been set and the buffer map has been initialized enough for
`comedi_mmap()` to deal with it (specifically, check the `n_pages`
member has been set to a non-zero value). If all is well, the buffer
map's reference is incremented and a pointer to it is returned. The
comedi subdevice's spin-lock is used to protect the checks. Also use
the spin-lock in `__comedi_buf_alloc()` and `__comedi_buf_free()` to
protect changes to the subdevice's buffer map structure pointer and the
buffer map structure's `n_pages` member. (This checking of `n_pages` is
a bit clunky and I [Ian Abbott] plan to deal with it in the future.)
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Cc: <stable@vger.kernel.org> # 3.14.x, 3.15.x
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2014-04-10 19:41:57 +01:00
|
|
|
|
staging: comedi: use dma_mmap_coherent for DMA-able buffer mmap
Comedi's acquisition buffer allocation code can allocate the buffer from
normal kernel memory or from DMA coherent memory depending on the
`dma_async_dir` value in the comedi subdevice. (A value of `DMA_NONE`
causes the buffer to be allocated from normal kernel memory. Other
values cause the buffer to be allocated from DMA coherent memory.) The
buffer currently consists of a bunch of page-sized blocks that are
vmap'ed into a contiguous range of virtual addresses. The pages are also
mmap'able into user address space. For DMA'able buffers, these
page-sized blocks are allocated by `dma_alloc_coherent()`.
For DMA-able buffers, the DMA API is currently abused in various ways,
the most serious abuse being the calling of `virt_to_page()` on the
blocks allocated by `dma_alloc_coherent()` and passing those pages to
`vmap()` (for mapping to the kernels vmalloc address space) and via
`page_to_pfn()` to `remap_pfn_range()` (for mmap'ing to user space). it
also uses the `__GFP_COMP` flag when allocating the blocks, and marks
the allocated pages as reserved (which is unnecessary for DMA coherent
allocations).
The code can be changed to get rid of the vmap'ed address altogether if
necessary, since there are only a few places in the comedi code that use
the vmap'ed address directly and we also keep a list of the kernel
addresses for the individual pages prior to the vmap operation. This
would add some run-time overhead to buffer accesses. The real killer is
the mmap operation.
For mmap, the address range specified in the VMA needs to be mmap'ed to
the individually allocated page-sized blocks. That is not a problem
when the pages are allocated from normal kernel memory as the individual
pages can be remapped by `remap_pfn_range()`, but it is a problem when
the page-sized blocks are allocated by `dma_alloc_coherent()` because
the DMA API currently has no support for splitting a VMA across multiple
blocks of DMA coherent memory (or rather, no support for mapping part of
a VMA range to a single block of DMA coherent memory).
In order to comply with the DMA API and allow the buffer to be mmap'ed,
the buffer needs to be allocated as a single block by a single call to
`dma_alloc_coherent()`, freed by a single call to `dma_free_coherent()`,
and mmap'ed to user space by a single call to `dma_mmap_coherent()`.
This patch changes the buffer allocation, freeing, and mmap'ing code to
do that, with the unfortunate consequence that buffer allocation is more
likely to fail. It also no longer uses the `__GFP_COMP` flag when
allocating DMA coherent memory, no longer marks the
allocated pages of DMA coherent memory as reserved, and no longer vmap's
the DMA coherent memory pages (since they are contiguous anyway).
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2019-06-25 12:26:59 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
staging: comedi: use dma_mmap_coherent for DMA-able buffer mmap
Comedi's acquisition buffer allocation code can allocate the buffer from
normal kernel memory or from DMA coherent memory depending on the
`dma_async_dir` value in the comedi subdevice. (A value of `DMA_NONE`
causes the buffer to be allocated from normal kernel memory. Other
values cause the buffer to be allocated from DMA coherent memory.) The
buffer currently consists of a bunch of page-sized blocks that are
vmap'ed into a contiguous range of virtual addresses. The pages are also
mmap'able into user address space. For DMA'able buffers, these
page-sized blocks are allocated by `dma_alloc_coherent()`.
For DMA-able buffers, the DMA API is currently abused in various ways,
the most serious abuse being the calling of `virt_to_page()` on the
blocks allocated by `dma_alloc_coherent()` and passing those pages to
`vmap()` (for mapping to the kernels vmalloc address space) and via
`page_to_pfn()` to `remap_pfn_range()` (for mmap'ing to user space). it
also uses the `__GFP_COMP` flag when allocating the blocks, and marks
the allocated pages as reserved (which is unnecessary for DMA coherent
allocations).
The code can be changed to get rid of the vmap'ed address altogether if
necessary, since there are only a few places in the comedi code that use
the vmap'ed address directly and we also keep a list of the kernel
addresses for the individual pages prior to the vmap operation. This
would add some run-time overhead to buffer accesses. The real killer is
the mmap operation.
For mmap, the address range specified in the VMA needs to be mmap'ed to
the individually allocated page-sized blocks. That is not a problem
when the pages are allocated from normal kernel memory as the individual
pages can be remapped by `remap_pfn_range()`, but it is a problem when
the page-sized blocks are allocated by `dma_alloc_coherent()` because
the DMA API currently has no support for splitting a VMA across multiple
blocks of DMA coherent memory (or rather, no support for mapping part of
a VMA range to a single block of DMA coherent memory).
In order to comply with the DMA API and allow the buffer to be mmap'ed,
the buffer needs to be allocated as a single block by a single call to
`dma_alloc_coherent()`, freed by a single call to `dma_free_coherent()`,
and mmap'ed to user space by a single call to `dma_mmap_coherent()`.
This patch changes the buffer allocation, freeing, and mmap'ing code to
do that, with the unfortunate consequence that buffer allocation is more
likely to fail. It also no longer uses the `__GFP_COMP` flag when
allocating DMA coherent memory, no longer marks the
allocated pages of DMA coherent memory as reserved, and no longer vmap's
the DMA coherent memory pages (since they are contiguous anyway).
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2019-06-25 12:26:59 +01:00
|
|
|
|
2011-11-08 21:23:03 +00:00
|
|
|
|
staging: comedi: fix circular locking dependency in comedi_mmap()
Mmapping a comedi data buffer with lockdep checking enabled produced the
following kernel debug messages:
======================================================
[ INFO: possible circular locking dependency detected ]
3.5.0-rc3-ija1+ #9 Tainted: G C
-------------------------------------------------------
comedi_test/4160 is trying to acquire lock:
(&dev->mutex#2){+.+.+.}, at: [<ffffffffa00313f4>] comedi_mmap+0x57/0x1d9 [comedi]
but task is already holding lock:
(&mm->mmap_sem){++++++}, at: [<ffffffff810c96fe>] vm_mmap_pgoff+0x41/0x76
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #1 (&mm->mmap_sem){++++++}:
[<ffffffff8106d0e8>] lock_acquire+0x97/0x105
[<ffffffff810ce3bc>] might_fault+0x6d/0x90
[<ffffffffa0031ffb>] do_devinfo_ioctl.isra.7+0x11e/0x14c [comedi]
[<ffffffffa003227f>] comedi_unlocked_ioctl+0x256/0xe48 [comedi]
[<ffffffff810f7fcd>] vfs_ioctl+0x18/0x34
[<ffffffff810f87fd>] do_vfs_ioctl+0x382/0x43c
[<ffffffff810f88f9>] sys_ioctl+0x42/0x65
[<ffffffff81415c62>] system_call_fastpath+0x16/0x1b
-> #0 (&dev->mutex#2){+.+.+.}:
[<ffffffff8106c528>] __lock_acquire+0x101d/0x1591
[<ffffffff8106d0e8>] lock_acquire+0x97/0x105
[<ffffffff8140c894>] mutex_lock_nested+0x46/0x2a4
[<ffffffffa00313f4>] comedi_mmap+0x57/0x1d9 [comedi]
[<ffffffff810d5816>] mmap_region+0x281/0x492
[<ffffffff810d5c92>] do_mmap_pgoff+0x26b/0x2a7
[<ffffffff810c971a>] vm_mmap_pgoff+0x5d/0x76
[<ffffffff810d493f>] sys_mmap_pgoff+0xc7/0x10d
[<ffffffff81004d36>] sys_mmap+0x16/0x20
[<ffffffff81415c62>] system_call_fastpath+0x16/0x1b
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(&mm->mmap_sem);
lock(&dev->mutex#2);
lock(&mm->mmap_sem);
lock(&dev->mutex#2);
*** DEADLOCK ***
To avoid the circular dependency, just try to get the lock in
`comedi_mmap()` instead of blocking. Since the comedi device's main mutex
is heavily used, do a down-read of its `attach_lock` rwsemaphore
instead. Trying to down-read `attach_lock` should only fail if
some task has down-write locked it, and that is only done while the
comedi device is being attached to or detached from a low-level hardware
device.
Unfortunately, acquiring the `attach_lock` doesn't prevent another
task replacing the comedi data buffer we are trying to mmap. The
details of the buffer are held in a `struct comedi_buf_map` and pointed
to by `s->async->buf_map` where `s` is the comedi subdevice whose buffer
we are trying to map. The `struct comedi_buf_map` is already reference
counted with a `struct kref`, so we can stop it being freed prematurely.
Modify `comedi_mmap()` to call new function
`comedi_buf_map_from_subdev_get()` to read the subdevice's current
buffer map pointer and increment its reference instead of accessing
`async->buf_map` directly. Call `comedi_buf_map_put()` to decrement the
reference once the buffer map structure has been dealt with. (Note that
`comedi_buf_map_put()` does nothing if passed a NULL pointer.)
`comedi_buf_map_from_subdev_get()` checks the subdevice's buffer map
pointer has been set and the buffer map has been initialized enough for
`comedi_mmap()` to deal with it (specifically, check the `n_pages`
member has been set to a non-zero value). If all is well, the buffer
map's reference is incremented and a pointer to it is returned. The
comedi subdevice's spin-lock is used to protect the checks. Also use
the spin-lock in `__comedi_buf_alloc()` and `__comedi_buf_free()` to
protect changes to the subdevice's buffer map structure pointer and the
buffer map structure's `n_pages` member. (This checking of `n_pages` is
a bit clunky and I [Ian Abbott] plan to deal with it in the future.)
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Cc: <stable@vger.kernel.org> # 3.14.x, 3.15.x
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2014-04-10 19:41:57 +01:00
|
|
|
|
2020-06-08 21:33:54 -07:00
|
|
|
|
staging: comedi: fix circular locking dependency in comedi_mmap()
Mmapping a comedi data buffer with lockdep checking enabled produced the
following kernel debug messages:
======================================================
[ INFO: possible circular locking dependency detected ]
3.5.0-rc3-ija1+ #9 Tainted: G C
-------------------------------------------------------
comedi_test/4160 is trying to acquire lock:
(&dev->mutex#2){+.+.+.}, at: [<ffffffffa00313f4>] comedi_mmap+0x57/0x1d9 [comedi]
but task is already holding lock:
(&mm->mmap_sem){++++++}, at: [<ffffffff810c96fe>] vm_mmap_pgoff+0x41/0x76
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #1 (&mm->mmap_sem){++++++}:
[<ffffffff8106d0e8>] lock_acquire+0x97/0x105
[<ffffffff810ce3bc>] might_fault+0x6d/0x90
[<ffffffffa0031ffb>] do_devinfo_ioctl.isra.7+0x11e/0x14c [comedi]
[<ffffffffa003227f>] comedi_unlocked_ioctl+0x256/0xe48 [comedi]
[<ffffffff810f7fcd>] vfs_ioctl+0x18/0x34
[<ffffffff810f87fd>] do_vfs_ioctl+0x382/0x43c
[<ffffffff810f88f9>] sys_ioctl+0x42/0x65
[<ffffffff81415c62>] system_call_fastpath+0x16/0x1b
-> #0 (&dev->mutex#2){+.+.+.}:
[<ffffffff8106c528>] __lock_acquire+0x101d/0x1591
[<ffffffff8106d0e8>] lock_acquire+0x97/0x105
[<ffffffff8140c894>] mutex_lock_nested+0x46/0x2a4
[<ffffffffa00313f4>] comedi_mmap+0x57/0x1d9 [comedi]
[<ffffffff810d5816>] mmap_region+0x281/0x492
[<ffffffff810d5c92>] do_mmap_pgoff+0x26b/0x2a7
[<ffffffff810c971a>] vm_mmap_pgoff+0x5d/0x76
[<ffffffff810d493f>] sys_mmap_pgoff+0xc7/0x10d
[<ffffffff81004d36>] sys_mmap+0x16/0x20
[<ffffffff81415c62>] system_call_fastpath+0x16/0x1b
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(&mm->mmap_sem);
lock(&dev->mutex#2);
lock(&mm->mmap_sem);
lock(&dev->mutex#2);
*** DEADLOCK ***
To avoid the circular dependency, just try to get the lock in
`comedi_mmap()` instead of blocking. Since the comedi device's main mutex
is heavily used, do a down-read of its `attach_lock` rwsemaphore
instead. Trying to down-read `attach_lock` should only fail if
some task has down-write locked it, and that is only done while the
comedi device is being attached to or detached from a low-level hardware
device.
Unfortunately, acquiring the `attach_lock` doesn't prevent another
task replacing the comedi data buffer we are trying to mmap. The
details of the buffer are held in a `struct comedi_buf_map` and pointed
to by `s->async->buf_map` where `s` is the comedi subdevice whose buffer
we are trying to map. The `struct comedi_buf_map` is already reference
counted with a `struct kref`, so we can stop it being freed prematurely.
Modify `comedi_mmap()` to call new function
`comedi_buf_map_from_subdev_get()` to read the subdevice's current
buffer map pointer and increment its reference instead of accessing
`async->buf_map` directly. Call `comedi_buf_map_put()` to decrement the
reference once the buffer map structure has been dealt with. (Note that
`comedi_buf_map_put()` does nothing if passed a NULL pointer.)
`comedi_buf_map_from_subdev_get()` checks the subdevice's buffer map
pointer has been set and the buffer map has been initialized enough for
`comedi_mmap()` to deal with it (specifically, check the `n_pages`
member has been set to a non-zero value). If all is well, the buffer
map's reference is incremented and a pointer to it is returned. The
comedi subdevice's spin-lock is used to protect the checks. Also use
the spin-lock in `__comedi_buf_alloc()` and `__comedi_buf_free()` to
protect changes to the subdevice's buffer map structure pointer and the
buffer map structure's `n_pages` member. (This checking of `n_pages` is
a bit clunky and I [Ian Abbott] plan to deal with it in the future.)
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Cc: <stable@vger.kernel.org> # 3.14.x, 3.15.x
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2014-04-10 19:41:57 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-12-19 15:45:12 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2013-11-26 10:21:11 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-12-19 15:45:12 -07:00
|
|
|
|
2008-11-13 17:05:58 -08:00
|
|
|
|
2014-11-04 18:09:00 +00:00
|
|
|
|
2008-11-13 17:05:58 -08:00
|
|
|
|
2014-11-04 18:09:00 +00:00
|
|
|
|
2012-12-19 15:45:12 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-12-19 15:45:12 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2012-12-19 15:45:12 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-11-26 10:21:11 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-03-06 12:35:29 +05:30
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-09-20 03:21:38 +05:30
|
|
|
|
staging: comedi: fix circular locking dependency in comedi_mmap()
Mmapping a comedi data buffer with lockdep checking enabled produced the
following kernel debug messages:
======================================================
[ INFO: possible circular locking dependency detected ]
3.5.0-rc3-ija1+ #9 Tainted: G C
-------------------------------------------------------
comedi_test/4160 is trying to acquire lock:
(&dev->mutex#2){+.+.+.}, at: [<ffffffffa00313f4>] comedi_mmap+0x57/0x1d9 [comedi]
but task is already holding lock:
(&mm->mmap_sem){++++++}, at: [<ffffffff810c96fe>] vm_mmap_pgoff+0x41/0x76
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #1 (&mm->mmap_sem){++++++}:
[<ffffffff8106d0e8>] lock_acquire+0x97/0x105
[<ffffffff810ce3bc>] might_fault+0x6d/0x90
[<ffffffffa0031ffb>] do_devinfo_ioctl.isra.7+0x11e/0x14c [comedi]
[<ffffffffa003227f>] comedi_unlocked_ioctl+0x256/0xe48 [comedi]
[<ffffffff810f7fcd>] vfs_ioctl+0x18/0x34
[<ffffffff810f87fd>] do_vfs_ioctl+0x382/0x43c
[<ffffffff810f88f9>] sys_ioctl+0x42/0x65
[<ffffffff81415c62>] system_call_fastpath+0x16/0x1b
-> #0 (&dev->mutex#2){+.+.+.}:
[<ffffffff8106c528>] __lock_acquire+0x101d/0x1591
[<ffffffff8106d0e8>] lock_acquire+0x97/0x105
[<ffffffff8140c894>] mutex_lock_nested+0x46/0x2a4
[<ffffffffa00313f4>] comedi_mmap+0x57/0x1d9 [comedi]
[<ffffffff810d5816>] mmap_region+0x281/0x492
[<ffffffff810d5c92>] do_mmap_pgoff+0x26b/0x2a7
[<ffffffff810c971a>] vm_mmap_pgoff+0x5d/0x76
[<ffffffff810d493f>] sys_mmap_pgoff+0xc7/0x10d
[<ffffffff81004d36>] sys_mmap+0x16/0x20
[<ffffffff81415c62>] system_call_fastpath+0x16/0x1b
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(&mm->mmap_sem);
lock(&dev->mutex#2);
lock(&mm->mmap_sem);
lock(&dev->mutex#2);
*** DEADLOCK ***
To avoid the circular dependency, just try to get the lock in
`comedi_mmap()` instead of blocking. Since the comedi device's main mutex
is heavily used, do a down-read of its `attach_lock` rwsemaphore
instead. Trying to down-read `attach_lock` should only fail if
some task has down-write locked it, and that is only done while the
comedi device is being attached to or detached from a low-level hardware
device.
Unfortunately, acquiring the `attach_lock` doesn't prevent another
task replacing the comedi data buffer we are trying to mmap. The
details of the buffer are held in a `struct comedi_buf_map` and pointed
to by `s->async->buf_map` where `s` is the comedi subdevice whose buffer
we are trying to map. The `struct comedi_buf_map` is already reference
counted with a `struct kref`, so we can stop it being freed prematurely.
Modify `comedi_mmap()` to call new function
`comedi_buf_map_from_subdev_get()` to read the subdevice's current
buffer map pointer and increment its reference instead of accessing
`async->buf_map` directly. Call `comedi_buf_map_put()` to decrement the
reference once the buffer map structure has been dealt with. (Note that
`comedi_buf_map_put()` does nothing if passed a NULL pointer.)
`comedi_buf_map_from_subdev_get()` checks the subdevice's buffer map
pointer has been set and the buffer map has been initialized enough for
`comedi_mmap()` to deal with it (specifically, check the `n_pages`
member has been set to a non-zero value). If all is well, the buffer
map's reference is incremented and a pointer to it is returned. The
comedi subdevice's spin-lock is used to protect the checks. Also use
the spin-lock in `__comedi_buf_alloc()` and `__comedi_buf_free()` to
protect changes to the subdevice's buffer map structure pointer and the
buffer map structure's `n_pages` member. (This checking of `n_pages` is
a bit clunky and I [Ian Abbott] plan to deal with it in the future.)
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Cc: <stable@vger.kernel.org> # 3.14.x, 3.15.x
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2014-04-10 19:41:57 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-11-08 15:03:43 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
staging: comedi: use dma_mmap_coherent for DMA-able buffer mmap
Comedi's acquisition buffer allocation code can allocate the buffer from
normal kernel memory or from DMA coherent memory depending on the
`dma_async_dir` value in the comedi subdevice. (A value of `DMA_NONE`
causes the buffer to be allocated from normal kernel memory. Other
values cause the buffer to be allocated from DMA coherent memory.) The
buffer currently consists of a bunch of page-sized blocks that are
vmap'ed into a contiguous range of virtual addresses. The pages are also
mmap'able into user address space. For DMA'able buffers, these
page-sized blocks are allocated by `dma_alloc_coherent()`.
For DMA-able buffers, the DMA API is currently abused in various ways,
the most serious abuse being the calling of `virt_to_page()` on the
blocks allocated by `dma_alloc_coherent()` and passing those pages to
`vmap()` (for mapping to the kernels vmalloc address space) and via
`page_to_pfn()` to `remap_pfn_range()` (for mmap'ing to user space). it
also uses the `__GFP_COMP` flag when allocating the blocks, and marks
the allocated pages as reserved (which is unnecessary for DMA coherent
allocations).
The code can be changed to get rid of the vmap'ed address altogether if
necessary, since there are only a few places in the comedi code that use
the vmap'ed address directly and we also keep a list of the kernel
addresses for the individual pages prior to the vmap operation. This
would add some run-time overhead to buffer accesses. The real killer is
the mmap operation.
For mmap, the address range specified in the VMA needs to be mmap'ed to
the individually allocated page-sized blocks. That is not a problem
when the pages are allocated from normal kernel memory as the individual
pages can be remapped by `remap_pfn_range()`, but it is a problem when
the page-sized blocks are allocated by `dma_alloc_coherent()` because
the DMA API currently has no support for splitting a VMA across multiple
blocks of DMA coherent memory (or rather, no support for mapping part of
a VMA range to a single block of DMA coherent memory).
In order to comply with the DMA API and allow the buffer to be mmap'ed,
the buffer needs to be allocated as a single block by a single call to
`dma_alloc_coherent()`, freed by a single call to `dma_free_coherent()`,
and mmap'ed to user space by a single call to `dma_mmap_coherent()`.
This patch changes the buffer allocation, freeing, and mmap'ing code to
do that, with the unfortunate consequence that buffer allocation is more
likely to fail. It also no longer uses the `__GFP_COMP` flag when
allocating DMA coherent memory, no longer marks the
allocated pages of DMA coherent memory as reserved, and no longer vmap's
the DMA coherent memory pages (since they are contiguous anyway).
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2019-06-25 12:26:59 +01:00
|
|
|
|
comedi: allocate DMA coherent buffer as individual pages
Depending on the driver, the acquisition buffer is allocated either from
normal memory, or from DMA coherent memory. For normal memory, the
buffer is allocated as individual pages, but for DMA coherent memory, it
is allocated as a single block. Prior to commit e36472145aa7 ("staging:
comedi: use dma_mmap_coherent for DMA-able buffer mmap"), the buffer was
allocated as individual pages for DMA coherent memory too, but that was
changed to allocate it as a single block to allow `dma_mmap_coherent()`
to be used to mmap it, because that requires the pages being mmap'ed to
be contiguous.
This patch allocates the buffer from DMA coherent memory a page at a
time again, and works around the limitation of `dma_mmap_coherent()` by
calling it in a loop for each page, with temporarily modified `vm_start`
and `vm_end` values in the VMA. (The `vm_pgoff` value is 0.)
Cc: Christoph Hellwig <hch@lst.de>
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Link: https://lore.kernel.org/r/20250415114008.5977-5-abbotti@mev.co.uk
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2025-04-15 12:35:59 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
staging: comedi: use dma_mmap_coherent for DMA-able buffer mmap
Comedi's acquisition buffer allocation code can allocate the buffer from
normal kernel memory or from DMA coherent memory depending on the
`dma_async_dir` value in the comedi subdevice. (A value of `DMA_NONE`
causes the buffer to be allocated from normal kernel memory. Other
values cause the buffer to be allocated from DMA coherent memory.) The
buffer currently consists of a bunch of page-sized blocks that are
vmap'ed into a contiguous range of virtual addresses. The pages are also
mmap'able into user address space. For DMA'able buffers, these
page-sized blocks are allocated by `dma_alloc_coherent()`.
For DMA-able buffers, the DMA API is currently abused in various ways,
the most serious abuse being the calling of `virt_to_page()` on the
blocks allocated by `dma_alloc_coherent()` and passing those pages to
`vmap()` (for mapping to the kernels vmalloc address space) and via
`page_to_pfn()` to `remap_pfn_range()` (for mmap'ing to user space). it
also uses the `__GFP_COMP` flag when allocating the blocks, and marks
the allocated pages as reserved (which is unnecessary for DMA coherent
allocations).
The code can be changed to get rid of the vmap'ed address altogether if
necessary, since there are only a few places in the comedi code that use
the vmap'ed address directly and we also keep a list of the kernel
addresses for the individual pages prior to the vmap operation. This
would add some run-time overhead to buffer accesses. The real killer is
the mmap operation.
For mmap, the address range specified in the VMA needs to be mmap'ed to
the individually allocated page-sized blocks. That is not a problem
when the pages are allocated from normal kernel memory as the individual
pages can be remapped by `remap_pfn_range()`, but it is a problem when
the page-sized blocks are allocated by `dma_alloc_coherent()` because
the DMA API currently has no support for splitting a VMA across multiple
blocks of DMA coherent memory (or rather, no support for mapping part of
a VMA range to a single block of DMA coherent memory).
In order to comply with the DMA API and allow the buffer to be mmap'ed,
the buffer needs to be allocated as a single block by a single call to
`dma_alloc_coherent()`, freed by a single call to `dma_free_coherent()`,
and mmap'ed to user space by a single call to `dma_mmap_coherent()`.
This patch changes the buffer allocation, freeing, and mmap'ing code to
do that, with the unfortunate consequence that buffer allocation is more
likely to fail. It also no longer uses the `__GFP_COMP` flag when
allocating DMA coherent memory, no longer marks the
allocated pages of DMA coherent memory as reserved, and no longer vmap's
the DMA coherent memory pages (since they are contiguous anyway).
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2019-06-25 12:26:59 +01:00
|
|
|
|
comedi: allocate DMA coherent buffer as individual pages
Depending on the driver, the acquisition buffer is allocated either from
normal memory, or from DMA coherent memory. For normal memory, the
buffer is allocated as individual pages, but for DMA coherent memory, it
is allocated as a single block. Prior to commit e36472145aa7 ("staging:
comedi: use dma_mmap_coherent for DMA-able buffer mmap"), the buffer was
allocated as individual pages for DMA coherent memory too, but that was
changed to allocate it as a single block to allow `dma_mmap_coherent()`
to be used to mmap it, because that requires the pages being mmap'ed to
be contiguous.
This patch allocates the buffer from DMA coherent memory a page at a
time again, and works around the limitation of `dma_mmap_coherent()` by
calling it in a loop for each page, with temporarily modified `vm_start`
and `vm_end` values in the VMA. (The `vm_pgoff` value is 0.)
Cc: Christoph Hellwig <hch@lst.de>
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Link: https://lore.kernel.org/r/20250415114008.5977-5-abbotti@mev.co.uk
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2025-04-15 12:35:59 +01:00
|
|
|
|
|
|
|
|
|
staging: comedi: use dma_mmap_coherent for DMA-able buffer mmap
Comedi's acquisition buffer allocation code can allocate the buffer from
normal kernel memory or from DMA coherent memory depending on the
`dma_async_dir` value in the comedi subdevice. (A value of `DMA_NONE`
causes the buffer to be allocated from normal kernel memory. Other
values cause the buffer to be allocated from DMA coherent memory.) The
buffer currently consists of a bunch of page-sized blocks that are
vmap'ed into a contiguous range of virtual addresses. The pages are also
mmap'able into user address space. For DMA'able buffers, these
page-sized blocks are allocated by `dma_alloc_coherent()`.
For DMA-able buffers, the DMA API is currently abused in various ways,
the most serious abuse being the calling of `virt_to_page()` on the
blocks allocated by `dma_alloc_coherent()` and passing those pages to
`vmap()` (for mapping to the kernels vmalloc address space) and via
`page_to_pfn()` to `remap_pfn_range()` (for mmap'ing to user space). it
also uses the `__GFP_COMP` flag when allocating the blocks, and marks
the allocated pages as reserved (which is unnecessary for DMA coherent
allocations).
The code can be changed to get rid of the vmap'ed address altogether if
necessary, since there are only a few places in the comedi code that use
the vmap'ed address directly and we also keep a list of the kernel
addresses for the individual pages prior to the vmap operation. This
would add some run-time overhead to buffer accesses. The real killer is
the mmap operation.
For mmap, the address range specified in the VMA needs to be mmap'ed to
the individually allocated page-sized blocks. That is not a problem
when the pages are allocated from normal kernel memory as the individual
pages can be remapped by `remap_pfn_range()`, but it is a problem when
the page-sized blocks are allocated by `dma_alloc_coherent()` because
the DMA API currently has no support for splitting a VMA across multiple
blocks of DMA coherent memory (or rather, no support for mapping part of
a VMA range to a single block of DMA coherent memory).
In order to comply with the DMA API and allow the buffer to be mmap'ed,
the buffer needs to be allocated as a single block by a single call to
`dma_alloc_coherent()`, freed by a single call to `dma_free_coherent()`,
and mmap'ed to user space by a single call to `dma_mmap_coherent()`.
This patch changes the buffer allocation, freeing, and mmap'ing code to
do that, with the unfortunate consequence that buffer allocation is more
likely to fail. It also no longer uses the `__GFP_COMP` flag when
allocating DMA coherent memory, no longer marks the
allocated pages of DMA coherent memory as reserved, and no longer vmap's
the DMA coherent memory pages (since they are contiguous anyway).
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2019-06-25 12:26:59 +01:00
|
|
|
|
comedi: allocate DMA coherent buffer as individual pages
Depending on the driver, the acquisition buffer is allocated either from
normal memory, or from DMA coherent memory. For normal memory, the
buffer is allocated as individual pages, but for DMA coherent memory, it
is allocated as a single block. Prior to commit e36472145aa7 ("staging:
comedi: use dma_mmap_coherent for DMA-able buffer mmap"), the buffer was
allocated as individual pages for DMA coherent memory too, but that was
changed to allocate it as a single block to allow `dma_mmap_coherent()`
to be used to mmap it, because that requires the pages being mmap'ed to
be contiguous.
This patch allocates the buffer from DMA coherent memory a page at a
time again, and works around the limitation of `dma_mmap_coherent()` by
calling it in a loop for each page, with temporarily modified `vm_start`
and `vm_end` values in the VMA. (The `vm_pgoff` value is 0.)
Cc: Christoph Hellwig <hch@lst.de>
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Link: https://lore.kernel.org/r/20250415114008.5977-5-abbotti@mev.co.uk
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2025-04-15 12:35:59 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
staging: comedi: use dma_mmap_coherent for DMA-able buffer mmap
Comedi's acquisition buffer allocation code can allocate the buffer from
normal kernel memory or from DMA coherent memory depending on the
`dma_async_dir` value in the comedi subdevice. (A value of `DMA_NONE`
causes the buffer to be allocated from normal kernel memory. Other
values cause the buffer to be allocated from DMA coherent memory.) The
buffer currently consists of a bunch of page-sized blocks that are
vmap'ed into a contiguous range of virtual addresses. The pages are also
mmap'able into user address space. For DMA'able buffers, these
page-sized blocks are allocated by `dma_alloc_coherent()`.
For DMA-able buffers, the DMA API is currently abused in various ways,
the most serious abuse being the calling of `virt_to_page()` on the
blocks allocated by `dma_alloc_coherent()` and passing those pages to
`vmap()` (for mapping to the kernels vmalloc address space) and via
`page_to_pfn()` to `remap_pfn_range()` (for mmap'ing to user space). it
also uses the `__GFP_COMP` flag when allocating the blocks, and marks
the allocated pages as reserved (which is unnecessary for DMA coherent
allocations).
The code can be changed to get rid of the vmap'ed address altogether if
necessary, since there are only a few places in the comedi code that use
the vmap'ed address directly and we also keep a list of the kernel
addresses for the individual pages prior to the vmap operation. This
would add some run-time overhead to buffer accesses. The real killer is
the mmap operation.
For mmap, the address range specified in the VMA needs to be mmap'ed to
the individually allocated page-sized blocks. That is not a problem
when the pages are allocated from normal kernel memory as the individual
pages can be remapped by `remap_pfn_range()`, but it is a problem when
the page-sized blocks are allocated by `dma_alloc_coherent()` because
the DMA API currently has no support for splitting a VMA across multiple
blocks of DMA coherent memory (or rather, no support for mapping part of
a VMA range to a single block of DMA coherent memory).
In order to comply with the DMA API and allow the buffer to be mmap'ed,
the buffer needs to be allocated as a single block by a single call to
`dma_alloc_coherent()`, freed by a single call to `dma_free_coherent()`,
and mmap'ed to user space by a single call to `dma_mmap_coherent()`.
This patch changes the buffer allocation, freeing, and mmap'ing code to
do that, with the unfortunate consequence that buffer allocation is more
likely to fail. It also no longer uses the `__GFP_COMP` flag when
allocating DMA coherent memory, no longer marks the
allocated pages of DMA coherent memory as reserved, and no longer vmap's
the DMA coherent memory pages (since they are contiguous anyway).
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2019-06-25 12:26:59 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-12-19 15:45:12 -07:00
|
|
|
|
staging: comedi: use dma_mmap_coherent for DMA-able buffer mmap
Comedi's acquisition buffer allocation code can allocate the buffer from
normal kernel memory or from DMA coherent memory depending on the
`dma_async_dir` value in the comedi subdevice. (A value of `DMA_NONE`
causes the buffer to be allocated from normal kernel memory. Other
values cause the buffer to be allocated from DMA coherent memory.) The
buffer currently consists of a bunch of page-sized blocks that are
vmap'ed into a contiguous range of virtual addresses. The pages are also
mmap'able into user address space. For DMA'able buffers, these
page-sized blocks are allocated by `dma_alloc_coherent()`.
For DMA-able buffers, the DMA API is currently abused in various ways,
the most serious abuse being the calling of `virt_to_page()` on the
blocks allocated by `dma_alloc_coherent()` and passing those pages to
`vmap()` (for mapping to the kernels vmalloc address space) and via
`page_to_pfn()` to `remap_pfn_range()` (for mmap'ing to user space). it
also uses the `__GFP_COMP` flag when allocating the blocks, and marks
the allocated pages as reserved (which is unnecessary for DMA coherent
allocations).
The code can be changed to get rid of the vmap'ed address altogether if
necessary, since there are only a few places in the comedi code that use
the vmap'ed address directly and we also keep a list of the kernel
addresses for the individual pages prior to the vmap operation. This
would add some run-time overhead to buffer accesses. The real killer is
the mmap operation.
For mmap, the address range specified in the VMA needs to be mmap'ed to
the individually allocated page-sized blocks. That is not a problem
when the pages are allocated from normal kernel memory as the individual
pages can be remapped by `remap_pfn_range()`, but it is a problem when
the page-sized blocks are allocated by `dma_alloc_coherent()` because
the DMA API currently has no support for splitting a VMA across multiple
blocks of DMA coherent memory (or rather, no support for mapping part of
a VMA range to a single block of DMA coherent memory).
In order to comply with the DMA API and allow the buffer to be mmap'ed,
the buffer needs to be allocated as a single block by a single call to
`dma_alloc_coherent()`, freed by a single call to `dma_free_coherent()`,
and mmap'ed to user space by a single call to `dma_mmap_coherent()`.
This patch changes the buffer allocation, freeing, and mmap'ing code to
do that, with the unfortunate consequence that buffer allocation is more
likely to fail. It also no longer uses the `__GFP_COMP` flag when
allocating DMA coherent memory, no longer marks the
allocated pages of DMA coherent memory as reserved, and no longer vmap's
the DMA coherent memory pages (since they are contiguous anyway).
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2019-06-25 12:26:59 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
comedi: allocate DMA coherent buffer as individual pages
Depending on the driver, the acquisition buffer is allocated either from
normal memory, or from DMA coherent memory. For normal memory, the
buffer is allocated as individual pages, but for DMA coherent memory, it
is allocated as a single block. Prior to commit e36472145aa7 ("staging:
comedi: use dma_mmap_coherent for DMA-able buffer mmap"), the buffer was
allocated as individual pages for DMA coherent memory too, but that was
changed to allocate it as a single block to allow `dma_mmap_coherent()`
to be used to mmap it, because that requires the pages being mmap'ed to
be contiguous.
This patch allocates the buffer from DMA coherent memory a page at a
time again, and works around the limitation of `dma_mmap_coherent()` by
calling it in a loop for each page, with temporarily modified `vm_start`
and `vm_end` values in the VMA. (The `vm_pgoff` value is 0.)
Cc: Christoph Hellwig <hch@lst.de>
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Link: https://lore.kernel.org/r/20250415114008.5977-5-abbotti@mev.co.uk
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2025-04-15 12:35:59 +01:00
|
|
|
|
2024-10-17 21:07:45 +02:00
|
|
|
|
|
|
|
|
|
comedi: allocate DMA coherent buffer as individual pages
Depending on the driver, the acquisition buffer is allocated either from
normal memory, or from DMA coherent memory. For normal memory, the
buffer is allocated as individual pages, but for DMA coherent memory, it
is allocated as a single block. Prior to commit e36472145aa7 ("staging:
comedi: use dma_mmap_coherent for DMA-able buffer mmap"), the buffer was
allocated as individual pages for DMA coherent memory too, but that was
changed to allocate it as a single block to allow `dma_mmap_coherent()`
to be used to mmap it, because that requires the pages being mmap'ed to
be contiguous.
This patch allocates the buffer from DMA coherent memory a page at a
time again, and works around the limitation of `dma_mmap_coherent()` by
calling it in a loop for each page, with temporarily modified `vm_start`
and `vm_end` values in the VMA. (The `vm_pgoff` value is 0.)
Cc: Christoph Hellwig <hch@lst.de>
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Link: https://lore.kernel.org/r/20250415114008.5977-5-abbotti@mev.co.uk
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2025-04-15 12:35:59 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-02-27 21:08:46 +01:00
|
|
|
|
2024-10-17 21:07:45 +02:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
staging: comedi: use dma_mmap_coherent for DMA-able buffer mmap
Comedi's acquisition buffer allocation code can allocate the buffer from
normal kernel memory or from DMA coherent memory depending on the
`dma_async_dir` value in the comedi subdevice. (A value of `DMA_NONE`
causes the buffer to be allocated from normal kernel memory. Other
values cause the buffer to be allocated from DMA coherent memory.) The
buffer currently consists of a bunch of page-sized blocks that are
vmap'ed into a contiguous range of virtual addresses. The pages are also
mmap'able into user address space. For DMA'able buffers, these
page-sized blocks are allocated by `dma_alloc_coherent()`.
For DMA-able buffers, the DMA API is currently abused in various ways,
the most serious abuse being the calling of `virt_to_page()` on the
blocks allocated by `dma_alloc_coherent()` and passing those pages to
`vmap()` (for mapping to the kernels vmalloc address space) and via
`page_to_pfn()` to `remap_pfn_range()` (for mmap'ing to user space). it
also uses the `__GFP_COMP` flag when allocating the blocks, and marks
the allocated pages as reserved (which is unnecessary for DMA coherent
allocations).
The code can be changed to get rid of the vmap'ed address altogether if
necessary, since there are only a few places in the comedi code that use
the vmap'ed address directly and we also keep a list of the kernel
addresses for the individual pages prior to the vmap operation. This
would add some run-time overhead to buffer accesses. The real killer is
the mmap operation.
For mmap, the address range specified in the VMA needs to be mmap'ed to
the individually allocated page-sized blocks. That is not a problem
when the pages are allocated from normal kernel memory as the individual
pages can be remapped by `remap_pfn_range()`, but it is a problem when
the page-sized blocks are allocated by `dma_alloc_coherent()` because
the DMA API currently has no support for splitting a VMA across multiple
blocks of DMA coherent memory (or rather, no support for mapping part of
a VMA range to a single block of DMA coherent memory).
In order to comply with the DMA API and allow the buffer to be mmap'ed,
the buffer needs to be allocated as a single block by a single call to
`dma_alloc_coherent()`, freed by a single call to `dma_free_coherent()`,
and mmap'ed to user space by a single call to `dma_mmap_coherent()`.
This patch changes the buffer allocation, freeing, and mmap'ing code to
do that, with the unfortunate consequence that buffer allocation is more
likely to fail. It also no longer uses the `__GFP_COMP` flag when
allocating DMA coherent memory, no longer marks the
allocated pages of DMA coherent memory as reserved, and no longer vmap's
the DMA coherent memory pages (since they are contiguous anyway).
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2019-06-25 12:26:59 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
staging: comedi: use dma_mmap_coherent for DMA-able buffer mmap
Comedi's acquisition buffer allocation code can allocate the buffer from
normal kernel memory or from DMA coherent memory depending on the
`dma_async_dir` value in the comedi subdevice. (A value of `DMA_NONE`
causes the buffer to be allocated from normal kernel memory. Other
values cause the buffer to be allocated from DMA coherent memory.) The
buffer currently consists of a bunch of page-sized blocks that are
vmap'ed into a contiguous range of virtual addresses. The pages are also
mmap'able into user address space. For DMA'able buffers, these
page-sized blocks are allocated by `dma_alloc_coherent()`.
For DMA-able buffers, the DMA API is currently abused in various ways,
the most serious abuse being the calling of `virt_to_page()` on the
blocks allocated by `dma_alloc_coherent()` and passing those pages to
`vmap()` (for mapping to the kernels vmalloc address space) and via
`page_to_pfn()` to `remap_pfn_range()` (for mmap'ing to user space). it
also uses the `__GFP_COMP` flag when allocating the blocks, and marks
the allocated pages as reserved (which is unnecessary for DMA coherent
allocations).
The code can be changed to get rid of the vmap'ed address altogether if
necessary, since there are only a few places in the comedi code that use
the vmap'ed address directly and we also keep a list of the kernel
addresses for the individual pages prior to the vmap operation. This
would add some run-time overhead to buffer accesses. The real killer is
the mmap operation.
For mmap, the address range specified in the VMA needs to be mmap'ed to
the individually allocated page-sized blocks. That is not a problem
when the pages are allocated from normal kernel memory as the individual
pages can be remapped by `remap_pfn_range()`, but it is a problem when
the page-sized blocks are allocated by `dma_alloc_coherent()` because
the DMA API currently has no support for splitting a VMA across multiple
blocks of DMA coherent memory (or rather, no support for mapping part of
a VMA range to a single block of DMA coherent memory).
In order to comply with the DMA API and allow the buffer to be mmap'ed,
the buffer needs to be allocated as a single block by a single call to
`dma_alloc_coherent()`, freed by a single call to `dma_free_coherent()`,
and mmap'ed to user space by a single call to `dma_mmap_coherent()`.
This patch changes the buffer allocation, freeing, and mmap'ing code to
do that, with the unfortunate consequence that buffer allocation is more
likely to fail. It also no longer uses the `__GFP_COMP` flag when
allocating DMA coherent memory, no longer marks the
allocated pages of DMA coherent memory as reserved, and no longer vmap's
the DMA coherent memory pages (since they are contiguous anyway).
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2019-06-25 12:26:59 +01:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2008-11-13 17:05:58 -08:00
|
|
|
|
staging: comedi: fix circular locking dependency in comedi_mmap()
Mmapping a comedi data buffer with lockdep checking enabled produced the
following kernel debug messages:
======================================================
[ INFO: possible circular locking dependency detected ]
3.5.0-rc3-ija1+ #9 Tainted: G C
-------------------------------------------------------
comedi_test/4160 is trying to acquire lock:
(&dev->mutex#2){+.+.+.}, at: [<ffffffffa00313f4>] comedi_mmap+0x57/0x1d9 [comedi]
but task is already holding lock:
(&mm->mmap_sem){++++++}, at: [<ffffffff810c96fe>] vm_mmap_pgoff+0x41/0x76
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #1 (&mm->mmap_sem){++++++}:
[<ffffffff8106d0e8>] lock_acquire+0x97/0x105
[<ffffffff810ce3bc>] might_fault+0x6d/0x90
[<ffffffffa0031ffb>] do_devinfo_ioctl.isra.7+0x11e/0x14c [comedi]
[<ffffffffa003227f>] comedi_unlocked_ioctl+0x256/0xe48 [comedi]
[<ffffffff810f7fcd>] vfs_ioctl+0x18/0x34
[<ffffffff810f87fd>] do_vfs_ioctl+0x382/0x43c
[<ffffffff810f88f9>] sys_ioctl+0x42/0x65
[<ffffffff81415c62>] system_call_fastpath+0x16/0x1b
-> #0 (&dev->mutex#2){+.+.+.}:
[<ffffffff8106c528>] __lock_acquire+0x101d/0x1591
[<ffffffff8106d0e8>] lock_acquire+0x97/0x105
[<ffffffff8140c894>] mutex_lock_nested+0x46/0x2a4
[<ffffffffa00313f4>] comedi_mmap+0x57/0x1d9 [comedi]
[<ffffffff810d5816>] mmap_region+0x281/0x492
[<ffffffff810d5c92>] do_mmap_pgoff+0x26b/0x2a7
[<ffffffff810c971a>] vm_mmap_pgoff+0x5d/0x76
[<ffffffff810d493f>] sys_mmap_pgoff+0xc7/0x10d
[<ffffffff81004d36>] sys_mmap+0x16/0x20
[<ffffffff81415c62>] system_call_fastpath+0x16/0x1b
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(&mm->mmap_sem);
lock(&dev->mutex#2);
lock(&mm->mmap_sem);
lock(&dev->mutex#2);
*** DEADLOCK ***
To avoid the circular dependency, just try to get the lock in
`comedi_mmap()` instead of blocking. Since the comedi device's main mutex
is heavily used, do a down-read of its `attach_lock` rwsemaphore
instead. Trying to down-read `attach_lock` should only fail if
some task has down-write locked it, and that is only done while the
comedi device is being attached to or detached from a low-level hardware
device.
Unfortunately, acquiring the `attach_lock` doesn't prevent another
task replacing the comedi data buffer we are trying to mmap. The
details of the buffer are held in a `struct comedi_buf_map` and pointed
to by `s->async->buf_map` where `s` is the comedi subdevice whose buffer
we are trying to map. The `struct comedi_buf_map` is already reference
counted with a `struct kref`, so we can stop it being freed prematurely.
Modify `comedi_mmap()` to call new function
`comedi_buf_map_from_subdev_get()` to read the subdevice's current
buffer map pointer and increment its reference instead of accessing
`async->buf_map` directly. Call `comedi_buf_map_put()` to decrement the
reference once the buffer map structure has been dealt with. (Note that
`comedi_buf_map_put()` does nothing if passed a NULL pointer.)
`comedi_buf_map_from_subdev_get()` checks the subdevice's buffer map
pointer has been set and the buffer map has been initialized enough for
`comedi_mmap()` to deal with it (specifically, check the `n_pages`
member has been set to a non-zero value). If all is well, the buffer
map's reference is incremented and a pointer to it is returned. The
comedi subdevice's spin-lock is used to protect the checks. Also use
the spin-lock in `__comedi_buf_alloc()` and `__comedi_buf_free()` to
protect changes to the subdevice's buffer map structure pointer and the
buffer map structure's `n_pages` member. (This checking of `n_pages` is
a bit clunky and I [Ian Abbott] plan to deal with it in the future.)
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Cc: <stable@vger.kernel.org> # 3.14.x, 3.15.x
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2014-04-10 19:41:57 +01:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-07-03 06:39:46 -04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2017-07-03 06:39:46 -04:00
|
|
|
|
2014-11-04 18:09:00 +00:00
|
|
|
|
|
|
|
|
|
2015-10-09 12:26:47 +01:00
|
|
|
|
2011-11-08 21:23:03 +00:00
|
|
|
|
2015-10-09 12:26:52 +01:00
|
|
|
|
2012-12-19 15:39:44 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2013-11-26 10:21:11 -07:00
|
|
|
|
2012-12-19 15:39:44 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2014-11-04 18:09:00 +00:00
|
|
|
|
2015-10-09 12:26:47 +01:00
|
|
|
|
2013-02-05 12:50:40 +00:00
|
|
|
|
2012-12-19 15:39:44 -07:00
|
|
|
|
2015-10-09 12:26:51 +01:00
|
|
|
|
2014-10-30 12:42:31 +00:00
|
|
|
|
comedi: Use reference count for asynchronous command functions
For interrupts from badly behaved hardware (as emulated by Syzbot), it
is possible for the Comedi core functions that manage the progress of
asynchronous data acquisition to be called from driver ISRs while no
asynchronous command has been set up, which can cause problems such as
invalid pointer dereferencing or dividing by zero.
Change those functions in the Comedi core to use this pattern: if
`comedi_get_is_subdevice_running(s)` returns `true` then call a safe
version of the function with the same name prefixed with an underscore,
followed by a call to `comedi_put_is_subdevice_running(s)`, otherwise
take some default action.
`comedi_get_is_subdevice_running(s)` returning `true` ensures that the
details of the asynchronous command will not be destroyed before the
matching call to `comedi_put_is_subdevice_running(s)`.
Replace calls to those functions from elsewhere in the Comedi core with
calls to the safe versions of the functions.
The modified functions are: `comedi_buf_read_alloc()`,
`comedi_buf_read_free()`, `comedi_buf_read_n_available()`,
`comedi_buf_read_samples()`, `comedi_buf_write_alloc()`,
`comedi_buf_write_free()`, `comedi_buf_write_samples()`,
`comedi_bytes_per_scan()`, `comedi_event()`, `comedi_handle_events()`,
`comedi_inc_scan_progress()`, `comedi_nsamples_left()`,
`comedi_nscans_left()`.
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Link: https://patch.msgid.link/20251023133001.8439-3-abbotti@mev.co.uk
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2025-10-23 14:28:19 +01:00
|
|
|
|
2018-02-11 14:34:03 -08:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2014-11-04 18:09:00 +00:00
|
|
|
|
2013-02-05 12:50:40 +00:00
|
|
|
|
2014-10-31 12:04:28 -07:00
|
|
|
|
2012-12-19 15:39:44 -07:00
|
|
|
|
2015-10-09 12:26:47 +01:00
|
|
|
|
|
|
|
|
|
2015-10-09 12:26:51 +01:00
|
|
|
|
2014-10-30 12:42:31 +00:00
|
|
|
|
2015-10-09 12:26:50 +01:00
|
|
|
|
2018-02-11 14:34:03 -08:00
|
|
|
|
2012-12-19 15:39:44 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-10-09 12:26:52 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-04-15 12:35:57 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-05-03 16:32:28 -07:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2009-03-16 22:05:14 -04:00
|
|
|
|
2009-03-16 22:05:20 -04:00
|
|
|
|
2015-11-18 17:55:06 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2014-11-04 18:09:00 +00:00
|
|
|
|
|
|
|
|
|
2015-11-18 17:55:04 +00:00
|
|
|
|
2013-11-08 15:03:30 +00:00
|
|
|
|
|
|
|
|
|
2011-11-08 21:23:03 +00:00
|
|
|
|
2013-11-08 15:03:30 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2013-11-26 10:21:11 -07:00
|
|
|
|
2013-11-08 15:03:30 +00:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2014-11-04 18:09:00 +00:00
|
|
|
|
2013-11-08 15:03:30 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-12-19 15:40:34 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2015-11-18 17:55:10 +00:00
|
|
|
|
2014-10-30 12:42:30 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-12-19 15:40:34 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2015-11-18 17:55:04 +00:00
|
|
|
|
2016-03-21 09:18:35 -04:00
|
|
|
|
2015-03-27 15:13:01 +00:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2015-03-27 15:13:01 +00:00
|
|
|
|
|
|
|
|
|
2015-11-18 17:55:04 +00:00
|
|
|
|
|
|
|
|
|
2015-11-18 17:55:11 +00:00
|
|
|
|
|
|
|
|
|
2010-05-19 17:22:41 +01:00
|
|
|
|
|
|
|
|
|
2015-11-18 17:55:11 +00:00
|
|
|
|
|
|
|
|
|
2010-05-19 17:22:41 +01:00
|
|
|
|
2015-11-18 17:55:07 +00:00
|
|
|
|
comedi: Use reference count for asynchronous command functions
For interrupts from badly behaved hardware (as emulated by Syzbot), it
is possible for the Comedi core functions that manage the progress of
asynchronous data acquisition to be called from driver ISRs while no
asynchronous command has been set up, which can cause problems such as
invalid pointer dereferencing or dividing by zero.
Change those functions in the Comedi core to use this pattern: if
`comedi_get_is_subdevice_running(s)` returns `true` then call a safe
version of the function with the same name prefixed with an underscore,
followed by a call to `comedi_put_is_subdevice_running(s)`, otherwise
take some default action.
`comedi_get_is_subdevice_running(s)` returning `true` ensures that the
details of the asynchronous command will not be destroyed before the
matching call to `comedi_put_is_subdevice_running(s)`.
Replace calls to those functions from elsewhere in the Comedi core with
calls to the safe versions of the functions.
The modified functions are: `comedi_buf_read_alloc()`,
`comedi_buf_read_free()`, `comedi_buf_read_n_available()`,
`comedi_buf_read_samples()`, `comedi_buf_write_alloc()`,
`comedi_buf_write_free()`, `comedi_buf_write_samples()`,
`comedi_bytes_per_scan()`, `comedi_event()`, `comedi_handle_events()`,
`comedi_inc_scan_progress()`, `comedi_nsamples_left()`,
`comedi_nscans_left()`.
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Link: https://patch.msgid.link/20251023133001.8439-3-abbotti@mev.co.uk
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2025-10-23 14:28:19 +01:00
|
|
|
|
2015-11-18 17:55:07 +00:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-10-29 09:47:39 +02:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-11-18 17:55:10 +00:00
|
|
|
|
|
|
|
|
|
2014-10-30 12:42:30 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-07-28 16:22:31 +01:00
|
|
|
|
2025-04-15 12:35:57 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
comedi: Use reference count for asynchronous command functions
For interrupts from badly behaved hardware (as emulated by Syzbot), it
is possible for the Comedi core functions that manage the progress of
asynchronous data acquisition to be called from driver ISRs while no
asynchronous command has been set up, which can cause problems such as
invalid pointer dereferencing or dividing by zero.
Change those functions in the Comedi core to use this pattern: if
`comedi_get_is_subdevice_running(s)` returns `true` then call a safe
version of the function with the same name prefixed with an underscore,
followed by a call to `comedi_put_is_subdevice_running(s)`, otherwise
take some default action.
`comedi_get_is_subdevice_running(s)` returning `true` ensures that the
details of the asynchronous command will not be destroyed before the
matching call to `comedi_put_is_subdevice_running(s)`.
Replace calls to those functions from elsewhere in the Comedi core with
calls to the safe versions of the functions.
The modified functions are: `comedi_buf_read_alloc()`,
`comedi_buf_read_free()`, `comedi_buf_read_n_available()`,
`comedi_buf_read_samples()`, `comedi_buf_write_alloc()`,
`comedi_buf_write_free()`, `comedi_buf_write_samples()`,
`comedi_bytes_per_scan()`, `comedi_event()`, `comedi_handle_events()`,
`comedi_inc_scan_progress()`, `comedi_nsamples_left()`,
`comedi_nscans_left()`.
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Link: https://patch.msgid.link/20251023133001.8439-3-abbotti@mev.co.uk
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2025-10-23 14:28:19 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-11-18 17:55:04 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-11-18 17:55:05 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-11-18 17:55:04 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-11-18 17:55:05 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-11-18 17:55:04 +00:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2013-11-08 15:03:30 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2008-11-13 17:05:58 -08:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2010-05-03 16:32:28 -07:00
|
|
|
|
2014-07-18 14:28:14 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2009-03-16 22:05:14 -04:00
|
|
|
|
2009-03-16 22:05:20 -04:00
|
|
|
|
2015-10-12 17:21:23 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2014-11-04 18:09:00 +00:00
|
|
|
|
|
|
|
|
|
2013-11-08 15:03:31 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-08 21:23:03 +00:00
|
|
|
|
2013-11-08 15:03:31 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2013-11-26 10:21:11 -07:00
|
|
|
|
2013-11-08 15:03:31 +00:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2014-11-04 18:09:00 +00:00
|
|
|
|
2013-11-08 15:03:31 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-12-19 15:40:08 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2015-10-12 17:21:28 +01:00
|
|
|
|
2014-10-30 12:42:29 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2015-10-12 17:21:29 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
comedi: Use reference count for asynchronous command functions
For interrupts from badly behaved hardware (as emulated by Syzbot), it
is possible for the Comedi core functions that manage the progress of
asynchronous data acquisition to be called from driver ISRs while no
asynchronous command has been set up, which can cause problems such as
invalid pointer dereferencing or dividing by zero.
Change those functions in the Comedi core to use this pattern: if
`comedi_get_is_subdevice_running(s)` returns `true` then call a safe
version of the function with the same name prefixed with an underscore,
followed by a call to `comedi_put_is_subdevice_running(s)`, otherwise
take some default action.
`comedi_get_is_subdevice_running(s)` returning `true` ensures that the
details of the asynchronous command will not be destroyed before the
matching call to `comedi_put_is_subdevice_running(s)`.
Replace calls to those functions from elsewhere in the Comedi core with
calls to the safe versions of the functions.
The modified functions are: `comedi_buf_read_alloc()`,
`comedi_buf_read_free()`, `comedi_buf_read_n_available()`,
`comedi_buf_read_samples()`, `comedi_buf_write_alloc()`,
`comedi_buf_write_free()`, `comedi_buf_write_samples()`,
`comedi_bytes_per_scan()`, `comedi_event()`, `comedi_handle_events()`,
`comedi_inc_scan_progress()`, `comedi_nsamples_left()`,
`comedi_nscans_left()`.
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Link: https://patch.msgid.link/20251023133001.8439-3-abbotti@mev.co.uk
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2025-10-23 14:28:19 +01:00
|
|
|
|
2015-10-12 17:21:24 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2016-03-29 10:49:04 +01:00
|
|
|
|
|
|
|
|
|
2015-03-27 15:13:01 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2015-10-12 17:21:29 +01:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2015-10-12 17:21:29 +01:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-10-29 09:47:39 +02:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-10-12 17:21:28 +01:00
|
|
|
|
|
|
|
|
|
2014-10-30 12:42:29 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2017-07-28 16:22:31 +01:00
|
|
|
|
|
|
|
|
|
2025-04-15 12:35:57 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
comedi: Use reference count for asynchronous command functions
For interrupts from badly behaved hardware (as emulated by Syzbot), it
is possible for the Comedi core functions that manage the progress of
asynchronous data acquisition to be called from driver ISRs while no
asynchronous command has been set up, which can cause problems such as
invalid pointer dereferencing or dividing by zero.
Change those functions in the Comedi core to use this pattern: if
`comedi_get_is_subdevice_running(s)` returns `true` then call a safe
version of the function with the same name prefixed with an underscore,
followed by a call to `comedi_put_is_subdevice_running(s)`, otherwise
take some default action.
`comedi_get_is_subdevice_running(s)` returning `true` ensures that the
details of the asynchronous command will not be destroyed before the
matching call to `comedi_put_is_subdevice_running(s)`.
Replace calls to those functions from elsewhere in the Comedi core with
calls to the safe versions of the functions.
The modified functions are: `comedi_buf_read_alloc()`,
`comedi_buf_read_free()`, `comedi_buf_read_n_available()`,
`comedi_buf_read_samples()`, `comedi_buf_write_alloc()`,
`comedi_buf_write_free()`, `comedi_buf_write_samples()`,
`comedi_bytes_per_scan()`, `comedi_event()`, `comedi_handle_events()`,
`comedi_inc_scan_progress()`, `comedi_nsamples_left()`,
`comedi_nscans_left()`.
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Link: https://patch.msgid.link/20251023133001.8439-3-abbotti@mev.co.uk
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2025-10-23 14:28:19 +01:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-11-08 15:03:31 +00:00
|
|
|
|
|
|
|
|
|
2015-10-12 17:21:20 +01:00
|
|
|
|
2013-11-08 15:03:31 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-07-05 16:49:34 +01:00
|
|
|
|
2013-11-08 15:03:31 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-10-12 17:21:22 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-11-08 15:03:31 +00:00
|
|
|
|
2014-11-04 18:09:00 +00:00
|
|
|
|
2013-11-08 15:03:31 +00:00
|
|
|
|
2015-10-12 17:21:22 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
comedi: Use reference count for asynchronous command functions
For interrupts from badly behaved hardware (as emulated by Syzbot), it
is possible for the Comedi core functions that manage the progress of
asynchronous data acquisition to be called from driver ISRs while no
asynchronous command has been set up, which can cause problems such as
invalid pointer dereferencing or dividing by zero.
Change those functions in the Comedi core to use this pattern: if
`comedi_get_is_subdevice_running(s)` returns `true` then call a safe
version of the function with the same name prefixed with an underscore,
followed by a call to `comedi_put_is_subdevice_running(s)`, otherwise
take some default action.
`comedi_get_is_subdevice_running(s)` returning `true` ensures that the
details of the asynchronous command will not be destroyed before the
matching call to `comedi_put_is_subdevice_running(s)`.
Replace calls to those functions from elsewhere in the Comedi core with
calls to the safe versions of the functions.
The modified functions are: `comedi_buf_read_alloc()`,
`comedi_buf_read_free()`, `comedi_buf_read_n_available()`,
`comedi_buf_read_samples()`, `comedi_buf_write_alloc()`,
`comedi_buf_write_free()`, `comedi_buf_write_samples()`,
`comedi_bytes_per_scan()`, `comedi_event()`, `comedi_handle_events()`,
`comedi_inc_scan_progress()`, `comedi_nsamples_left()`,
`comedi_nscans_left()`.
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Link: https://patch.msgid.link/20251023133001.8439-3-abbotti@mev.co.uk
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2025-10-23 14:28:19 +01:00
|
|
|
|
2015-10-12 17:21:22 +01:00
|
|
|
|
2013-07-05 16:49:34 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2013-11-08 15:03:31 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2008-11-13 17:05:58 -08:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2016-03-21 09:18:35 -04:00
|
|
|
|
2014-11-04 18:09:00 +00:00
|
|
|
|
2013-11-08 15:03:34 +00:00
|
|
|
|
|
|
|
|
|
2009-02-09 16:51:38 +00:00
|
|
|
|
2012-12-19 15:35:23 -07:00
|
|
|
|
2013-11-26 10:21:11 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-02-21 16:37:42 -08:00
|
|
|
|
2020-04-20 13:44:16 +08:00
|
|
|
|
|
|
|
|
|
2014-11-04 18:09:00 +00:00
|
|
|
|
2020-04-20 13:44:16 +08:00
|
|
|
|
2014-11-04 18:09:00 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2015-07-07 17:06:52 +01:00
|
|
|
|
|
|
|
|
|
2013-11-08 15:03:34 +00:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2013-12-11 14:51:03 +00:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2015-06-29 10:44:03 +01:00
|
|
|
|
2013-11-08 15:03:34 +00:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2013-12-11 14:51:03 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-05-19 14:10:00 +01:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2014-11-04 18:09:00 +00:00
|
|
|
|
|
|
|
|
|
2013-11-08 15:03:34 +00:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2013-11-08 15:03:34 +00:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2014-11-04 18:09:00 +00:00
|
|
|
|
2013-11-08 15:03:34 +00:00
|
|
|
|
2014-11-04 18:09:00 +00:00
|
|
|
|
|
|
|
|
|
2013-11-08 15:03:34 +00:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2012-12-19 15:31:57 -07:00
|
|
|
|
|
|
|
|
|
2014-11-04 18:09:00 +00:00
|
|
|
|
|
|
|
|
|
2012-12-19 15:31:57 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2014-11-04 18:09:00 +00:00
|
|
|
|
|
|
|
|
|
2009-03-16 22:05:14 -04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2011-11-08 21:23:03 +00:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-09-05 18:20:58 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2008-11-13 17:05:58 -08:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2008-11-13 17:05:58 -08:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-12-11 14:51:03 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2013-12-11 14:51:03 +00:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-11-08 15:03:34 +00:00
|
|
|
|
2014-11-04 18:09:00 +00:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 18:35:03 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
|
|
|
|
|
2020-04-25 18:35:03 -04:00
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
|
|
|
|
|
2020-04-25 18:35:03 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
2020-04-25 18:35:03 -04:00
|
|
|
|
comedi: check device's attached status in compat ioctls
Syzbot identified an issue [1] that crashes kernel, seemingly due to
unexistent callback dev->get_valid_routes(). By all means, this should
not occur as said callback must always be set to
get_zero_valid_routes() in __comedi_device_postconfig().
As the crash seems to appear exclusively in i386 kernels, at least,
judging from [1] reports, the blame lies with compat versions
of standard IOCTL handlers. Several of them are modified and
do not use comedi_unlocked_ioctl(). While functionality of these
ioctls essentially copy their original versions, they do not
have required sanity check for device's attached status. This,
in turn, leads to a possibility of calling select IOCTLs on a
device that has not been properly setup, even via COMEDI_DEVCONFIG.
Doing so on unconfigured devices means that several crucial steps
are missed, for instance, specifying dev->get_valid_routes()
callback.
Fix this somewhat crudely by ensuring device's attached status before
performing any ioctls, improving logic consistency between modern
and compat functions.
[1] Syzbot report:
BUG: kernel NULL pointer dereference, address: 0000000000000000
...
CR2: ffffffffffffffd6 CR3: 000000006c717000 CR4: 0000000000352ef0
Call Trace:
<TASK>
get_valid_routes drivers/comedi/comedi_fops.c:1322 [inline]
parse_insn+0x78c/0x1970 drivers/comedi/comedi_fops.c:1401
do_insnlist_ioctl+0x272/0x700 drivers/comedi/comedi_fops.c:1594
compat_insnlist drivers/comedi/comedi_fops.c:3208 [inline]
comedi_compat_ioctl+0x810/0x990 drivers/comedi/comedi_fops.c:3273
__do_compat_sys_ioctl fs/ioctl.c:695 [inline]
__se_compat_sys_ioctl fs/ioctl.c:638 [inline]
__ia32_compat_sys_ioctl+0x242/0x370 fs/ioctl.c:638
do_syscall_32_irqs_on arch/x86/entry/syscall_32.c:83 [inline]
...
Reported-by: syzbot+ab8008c24e84adee93ff@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=ab8008c24e84adee93ff
Fixes: 3fbfd2223a27 ("comedi: get rid of compat_alloc_user_space() mess in COMEDI_CHANINFO compat")
Cc: stable <stable@kernel.org>
Reviewed-by: Ian Abbott <abbotti@mev.co.uk>
Signed-off-by: Nikita Zhandarovich <n.zhandarovich@fintech.ru>
Link: https://patch.msgid.link/20251023132234.395794-1-n.zhandarovich@fintech.ru
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2025-10-23 16:22:32 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 18:35:03 -04:00
|
|
|
|
|
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 18:44:30 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
|
|
|
|
|
2020-04-25 18:44:30 -04:00
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
2020-04-25 18:44:30 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
2020-04-25 18:44:30 -04:00
|
|
|
|
comedi: check device's attached status in compat ioctls
Syzbot identified an issue [1] that crashes kernel, seemingly due to
unexistent callback dev->get_valid_routes(). By all means, this should
not occur as said callback must always be set to
get_zero_valid_routes() in __comedi_device_postconfig().
As the crash seems to appear exclusively in i386 kernels, at least,
judging from [1] reports, the blame lies with compat versions
of standard IOCTL handlers. Several of them are modified and
do not use comedi_unlocked_ioctl(). While functionality of these
ioctls essentially copy their original versions, they do not
have required sanity check for device's attached status. This,
in turn, leads to a possibility of calling select IOCTLs on a
device that has not been properly setup, even via COMEDI_DEVCONFIG.
Doing so on unconfigured devices means that several crucial steps
are missed, for instance, specifying dev->get_valid_routes()
callback.
Fix this somewhat crudely by ensuring device's attached status before
performing any ioctls, improving logic consistency between modern
and compat functions.
[1] Syzbot report:
BUG: kernel NULL pointer dereference, address: 0000000000000000
...
CR2: ffffffffffffffd6 CR3: 000000006c717000 CR4: 0000000000352ef0
Call Trace:
<TASK>
get_valid_routes drivers/comedi/comedi_fops.c:1322 [inline]
parse_insn+0x78c/0x1970 drivers/comedi/comedi_fops.c:1401
do_insnlist_ioctl+0x272/0x700 drivers/comedi/comedi_fops.c:1594
compat_insnlist drivers/comedi/comedi_fops.c:3208 [inline]
comedi_compat_ioctl+0x810/0x990 drivers/comedi/comedi_fops.c:3273
__do_compat_sys_ioctl fs/ioctl.c:695 [inline]
__se_compat_sys_ioctl fs/ioctl.c:638 [inline]
__ia32_compat_sys_ioctl+0x242/0x370 fs/ioctl.c:638
do_syscall_32_irqs_on arch/x86/entry/syscall_32.c:83 [inline]
...
Reported-by: syzbot+ab8008c24e84adee93ff@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=ab8008c24e84adee93ff
Fixes: 3fbfd2223a27 ("comedi: get rid of compat_alloc_user_space() mess in COMEDI_CHANINFO compat")
Cc: stable <stable@kernel.org>
Reviewed-by: Ian Abbott <abbotti@mev.co.uk>
Signed-off-by: Nikita Zhandarovich <n.zhandarovich@fintech.ru>
Link: https://patch.msgid.link/20251023132234.395794-1-n.zhandarovich@fintech.ru
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2025-10-23 16:22:32 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 18:44:30 -04:00
|
|
|
|
|
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-26 09:27:23 -04:00
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
|
|
|
|
|
2020-04-26 09:27:23 -04:00
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
2020-04-26 09:27:23 -04:00
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
|
|
|
|
|
2020-04-26 09:27:23 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-07-17 06:30:31 -04:00
|
|
|
|
2020-04-26 09:27:23 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-26 09:27:23 -04:00
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
2020-04-26 09:27:23 -04:00
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
2020-04-26 09:27:23 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
2020-07-17 06:30:31 -04:00
|
|
|
|
2020-04-26 09:27:23 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-12-02 09:43:49 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-26 09:27:23 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
|
|
|
|
|
2020-04-26 09:27:23 -04:00
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-26 09:27:23 -04:00
|
|
|
|
comedi: check device's attached status in compat ioctls
Syzbot identified an issue [1] that crashes kernel, seemingly due to
unexistent callback dev->get_valid_routes(). By all means, this should
not occur as said callback must always be set to
get_zero_valid_routes() in __comedi_device_postconfig().
As the crash seems to appear exclusively in i386 kernels, at least,
judging from [1] reports, the blame lies with compat versions
of standard IOCTL handlers. Several of them are modified and
do not use comedi_unlocked_ioctl(). While functionality of these
ioctls essentially copy their original versions, they do not
have required sanity check for device's attached status. This,
in turn, leads to a possibility of calling select IOCTLs on a
device that has not been properly setup, even via COMEDI_DEVCONFIG.
Doing so on unconfigured devices means that several crucial steps
are missed, for instance, specifying dev->get_valid_routes()
callback.
Fix this somewhat crudely by ensuring device's attached status before
performing any ioctls, improving logic consistency between modern
and compat functions.
[1] Syzbot report:
BUG: kernel NULL pointer dereference, address: 0000000000000000
...
CR2: ffffffffffffffd6 CR3: 000000006c717000 CR4: 0000000000352ef0
Call Trace:
<TASK>
get_valid_routes drivers/comedi/comedi_fops.c:1322 [inline]
parse_insn+0x78c/0x1970 drivers/comedi/comedi_fops.c:1401
do_insnlist_ioctl+0x272/0x700 drivers/comedi/comedi_fops.c:1594
compat_insnlist drivers/comedi/comedi_fops.c:3208 [inline]
comedi_compat_ioctl+0x810/0x990 drivers/comedi/comedi_fops.c:3273
__do_compat_sys_ioctl fs/ioctl.c:695 [inline]
__se_compat_sys_ioctl fs/ioctl.c:638 [inline]
__ia32_compat_sys_ioctl+0x242/0x370 fs/ioctl.c:638
do_syscall_32_irqs_on arch/x86/entry/syscall_32.c:83 [inline]
...
Reported-by: syzbot+ab8008c24e84adee93ff@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=ab8008c24e84adee93ff
Fixes: 3fbfd2223a27 ("comedi: get rid of compat_alloc_user_space() mess in COMEDI_CHANINFO compat")
Cc: stable <stable@kernel.org>
Reviewed-by: Ian Abbott <abbotti@mev.co.uk>
Signed-off-by: Nikita Zhandarovich <n.zhandarovich@fintech.ru>
Link: https://patch.msgid.link/20251023132234.395794-1-n.zhandarovich@fintech.ru
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2025-10-23 16:22:32 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-26 09:27:23 -04:00
|
|
|
|
|
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
2020-04-26 09:27:23 -04:00
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-26 09:27:23 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
|
|
|
|
|
2020-04-26 09:27:23 -04:00
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-26 09:27:23 -04:00
|
|
|
|
comedi: check device's attached status in compat ioctls
Syzbot identified an issue [1] that crashes kernel, seemingly due to
unexistent callback dev->get_valid_routes(). By all means, this should
not occur as said callback must always be set to
get_zero_valid_routes() in __comedi_device_postconfig().
As the crash seems to appear exclusively in i386 kernels, at least,
judging from [1] reports, the blame lies with compat versions
of standard IOCTL handlers. Several of them are modified and
do not use comedi_unlocked_ioctl(). While functionality of these
ioctls essentially copy their original versions, they do not
have required sanity check for device's attached status. This,
in turn, leads to a possibility of calling select IOCTLs on a
device that has not been properly setup, even via COMEDI_DEVCONFIG.
Doing so on unconfigured devices means that several crucial steps
are missed, for instance, specifying dev->get_valid_routes()
callback.
Fix this somewhat crudely by ensuring device's attached status before
performing any ioctls, improving logic consistency between modern
and compat functions.
[1] Syzbot report:
BUG: kernel NULL pointer dereference, address: 0000000000000000
...
CR2: ffffffffffffffd6 CR3: 000000006c717000 CR4: 0000000000352ef0
Call Trace:
<TASK>
get_valid_routes drivers/comedi/comedi_fops.c:1322 [inline]
parse_insn+0x78c/0x1970 drivers/comedi/comedi_fops.c:1401
do_insnlist_ioctl+0x272/0x700 drivers/comedi/comedi_fops.c:1594
compat_insnlist drivers/comedi/comedi_fops.c:3208 [inline]
comedi_compat_ioctl+0x810/0x990 drivers/comedi/comedi_fops.c:3273
__do_compat_sys_ioctl fs/ioctl.c:695 [inline]
__se_compat_sys_ioctl fs/ioctl.c:638 [inline]
__ia32_compat_sys_ioctl+0x242/0x370 fs/ioctl.c:638
do_syscall_32_irqs_on arch/x86/entry/syscall_32.c:83 [inline]
...
Reported-by: syzbot+ab8008c24e84adee93ff@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=ab8008c24e84adee93ff
Fixes: 3fbfd2223a27 ("comedi: get rid of compat_alloc_user_space() mess in COMEDI_CHANINFO compat")
Cc: stable <stable@kernel.org>
Reviewed-by: Ian Abbott <abbotti@mev.co.uk>
Signed-off-by: Nikita Zhandarovich <n.zhandarovich@fintech.ru>
Link: https://patch.msgid.link/20251023132234.395794-1-n.zhandarovich@fintech.ru
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2025-10-23 16:22:32 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-26 09:27:23 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 20:11:57 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 20:33:04 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
2020-04-25 20:33:04 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
2020-04-25 20:33:04 -04:00
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
|
|
|
|
|
2025-07-04 13:04:05 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2026-02-21 16:37:42 -08:00
|
|
|
|
2020-04-25 20:33:04 -04:00
|
|
|
|
|
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
|
|
|
|
|
2020-04-25 20:33:04 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
2020-04-25 20:33:04 -04:00
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
|
|
|
|
|
2020-04-25 20:33:04 -04:00
|
|
|
|
comedi: check device's attached status in compat ioctls
Syzbot identified an issue [1] that crashes kernel, seemingly due to
unexistent callback dev->get_valid_routes(). By all means, this should
not occur as said callback must always be set to
get_zero_valid_routes() in __comedi_device_postconfig().
As the crash seems to appear exclusively in i386 kernels, at least,
judging from [1] reports, the blame lies with compat versions
of standard IOCTL handlers. Several of them are modified and
do not use comedi_unlocked_ioctl(). While functionality of these
ioctls essentially copy their original versions, they do not
have required sanity check for device's attached status. This,
in turn, leads to a possibility of calling select IOCTLs on a
device that has not been properly setup, even via COMEDI_DEVCONFIG.
Doing so on unconfigured devices means that several crucial steps
are missed, for instance, specifying dev->get_valid_routes()
callback.
Fix this somewhat crudely by ensuring device's attached status before
performing any ioctls, improving logic consistency between modern
and compat functions.
[1] Syzbot report:
BUG: kernel NULL pointer dereference, address: 0000000000000000
...
CR2: ffffffffffffffd6 CR3: 000000006c717000 CR4: 0000000000352ef0
Call Trace:
<TASK>
get_valid_routes drivers/comedi/comedi_fops.c:1322 [inline]
parse_insn+0x78c/0x1970 drivers/comedi/comedi_fops.c:1401
do_insnlist_ioctl+0x272/0x700 drivers/comedi/comedi_fops.c:1594
compat_insnlist drivers/comedi/comedi_fops.c:3208 [inline]
comedi_compat_ioctl+0x810/0x990 drivers/comedi/comedi_fops.c:3273
__do_compat_sys_ioctl fs/ioctl.c:695 [inline]
__se_compat_sys_ioctl fs/ioctl.c:638 [inline]
__ia32_compat_sys_ioctl+0x242/0x370 fs/ioctl.c:638
do_syscall_32_irqs_on arch/x86/entry/syscall_32.c:83 [inline]
...
Reported-by: syzbot+ab8008c24e84adee93ff@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=ab8008c24e84adee93ff
Fixes: 3fbfd2223a27 ("comedi: get rid of compat_alloc_user_space() mess in COMEDI_CHANINFO compat")
Cc: stable <stable@kernel.org>
Reviewed-by: Ian Abbott <abbotti@mev.co.uk>
Signed-off-by: Nikita Zhandarovich <n.zhandarovich@fintech.ru>
Link: https://patch.msgid.link/20251023132234.395794-1-n.zhandarovich@fintech.ru
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2025-10-23 16:22:32 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 20:33:04 -04:00
|
|
|
|
2021-09-16 15:50:23 +01:00
|
|
|
|
2020-04-25 20:33:04 -04:00
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 20:11:57 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
|
|
|
|
|
2020-04-25 20:11:57 -04:00
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 20:11:57 -04:00
|
|
|
|
comedi: check device's attached status in compat ioctls
Syzbot identified an issue [1] that crashes kernel, seemingly due to
unexistent callback dev->get_valid_routes(). By all means, this should
not occur as said callback must always be set to
get_zero_valid_routes() in __comedi_device_postconfig().
As the crash seems to appear exclusively in i386 kernels, at least,
judging from [1] reports, the blame lies with compat versions
of standard IOCTL handlers. Several of them are modified and
do not use comedi_unlocked_ioctl(). While functionality of these
ioctls essentially copy their original versions, they do not
have required sanity check for device's attached status. This,
in turn, leads to a possibility of calling select IOCTLs on a
device that has not been properly setup, even via COMEDI_DEVCONFIG.
Doing so on unconfigured devices means that several crucial steps
are missed, for instance, specifying dev->get_valid_routes()
callback.
Fix this somewhat crudely by ensuring device's attached status before
performing any ioctls, improving logic consistency between modern
and compat functions.
[1] Syzbot report:
BUG: kernel NULL pointer dereference, address: 0000000000000000
...
CR2: ffffffffffffffd6 CR3: 000000006c717000 CR4: 0000000000352ef0
Call Trace:
<TASK>
get_valid_routes drivers/comedi/comedi_fops.c:1322 [inline]
parse_insn+0x78c/0x1970 drivers/comedi/comedi_fops.c:1401
do_insnlist_ioctl+0x272/0x700 drivers/comedi/comedi_fops.c:1594
compat_insnlist drivers/comedi/comedi_fops.c:3208 [inline]
comedi_compat_ioctl+0x810/0x990 drivers/comedi/comedi_fops.c:3273
__do_compat_sys_ioctl fs/ioctl.c:695 [inline]
__se_compat_sys_ioctl fs/ioctl.c:638 [inline]
__ia32_compat_sys_ioctl+0x242/0x370 fs/ioctl.c:638
do_syscall_32_irqs_on arch/x86/entry/syscall_32.c:83 [inline]
...
Reported-by: syzbot+ab8008c24e84adee93ff@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=ab8008c24e84adee93ff
Fixes: 3fbfd2223a27 ("comedi: get rid of compat_alloc_user_space() mess in COMEDI_CHANINFO compat")
Cc: stable <stable@kernel.org>
Reviewed-by: Ian Abbott <abbotti@mev.co.uk>
Signed-off-by: Nikita Zhandarovich <n.zhandarovich@fintech.ru>
Link: https://patch.msgid.link/20251023132234.395794-1-n.zhandarovich@fintech.ru
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2025-10-23 16:22:32 +03:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 20:11:57 -04:00
|
|
|
|
|
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 18:23:17 -04:00
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 18:23:17 -04:00
|
|
|
|
2020-04-25 18:19:30 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-06-19 10:17:43 +01:00
|
|
|
|
2009-06-08 21:04:41 +05:30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
llseek: automatically add .llseek fop
All file_operations should get a .llseek operation so we can make
nonseekable_open the default for future file operations without a
.llseek pointer.
The three cases that we can automatically detect are no_llseek, seq_lseek
and default_llseek. For cases where we can we can automatically prove that
the file offset is always ignored, we use noop_llseek, which maintains
the current behavior of not returning an error from a seek.
New drivers should normally not use noop_llseek but instead use no_llseek
and call nonseekable_open at open time. Existing drivers can be converted
to do the same when the maintainer knows for certain that no user code
relies on calling seek on the device file.
The generated code is often incorrectly indented and right now contains
comments that clarify for each added line why a specific variant was
chosen. In the version that gets submitted upstream, the comments will
be gone and I will manually fix the indentation, because there does not
seem to be a way to do that using coccinelle.
Some amount of new code is currently sitting in linux-next that should get
the same modifications, which I will do at the end of the merge window.
Many thanks to Julia Lawall for helping me learn to write a semantic
patch that does all this.
===== begin semantic patch =====
// This adds an llseek= method to all file operations,
// as a preparation for making no_llseek the default.
//
// The rules are
// - use no_llseek explicitly if we do nonseekable_open
// - use seq_lseek for sequential files
// - use default_llseek if we know we access f_pos
// - use noop_llseek if we know we don't access f_pos,
// but we still want to allow users to call lseek
//
@ open1 exists @
identifier nested_open;
@@
nested_open(...)
{
<+...
nonseekable_open(...)
...+>
}
@ open exists@
identifier open_f;
identifier i, f;
identifier open1.nested_open;
@@
int open_f(struct inode *i, struct file *f)
{
<+...
(
nonseekable_open(...)
|
nested_open(...)
)
...+>
}
@ read disable optional_qualifier exists @
identifier read_f;
identifier f, p, s, off;
type ssize_t, size_t, loff_t;
expression E;
identifier func;
@@
ssize_t read_f(struct file *f, char *p, size_t s, loff_t *off)
{
<+...
(
*off = E
|
*off += E
|
func(..., off, ...)
|
E = *off
)
...+>
}
@ read_no_fpos disable optional_qualifier exists @
identifier read_f;
identifier f, p, s, off;
type ssize_t, size_t, loff_t;
@@
ssize_t read_f(struct file *f, char *p, size_t s, loff_t *off)
{
... when != off
}
@ write @
identifier write_f;
identifier f, p, s, off;
type ssize_t, size_t, loff_t;
expression E;
identifier func;
@@
ssize_t write_f(struct file *f, const char *p, size_t s, loff_t *off)
{
<+...
(
*off = E
|
*off += E
|
func(..., off, ...)
|
E = *off
)
...+>
}
@ write_no_fpos @
identifier write_f;
identifier f, p, s, off;
type ssize_t, size_t, loff_t;
@@
ssize_t write_f(struct file *f, const char *p, size_t s, loff_t *off)
{
... when != off
}
@ fops0 @
identifier fops;
@@
struct file_operations fops = {
...
};
@ has_llseek depends on fops0 @
identifier fops0.fops;
identifier llseek_f;
@@
struct file_operations fops = {
...
.llseek = llseek_f,
...
};
@ has_read depends on fops0 @
identifier fops0.fops;
identifier read_f;
@@
struct file_operations fops = {
...
.read = read_f,
...
};
@ has_write depends on fops0 @
identifier fops0.fops;
identifier write_f;
@@
struct file_operations fops = {
...
.write = write_f,
...
};
@ has_open depends on fops0 @
identifier fops0.fops;
identifier open_f;
@@
struct file_operations fops = {
...
.open = open_f,
...
};
// use no_llseek if we call nonseekable_open
////////////////////////////////////////////
@ nonseekable1 depends on !has_llseek && has_open @
identifier fops0.fops;
identifier nso ~= "nonseekable_open";
@@
struct file_operations fops = {
... .open = nso, ...
+.llseek = no_llseek, /* nonseekable */
};
@ nonseekable2 depends on !has_llseek @
identifier fops0.fops;
identifier open.open_f;
@@
struct file_operations fops = {
... .open = open_f, ...
+.llseek = no_llseek, /* open uses nonseekable */
};
// use seq_lseek for sequential files
/////////////////////////////////////
@ seq depends on !has_llseek @
identifier fops0.fops;
identifier sr ~= "seq_read";
@@
struct file_operations fops = {
... .read = sr, ...
+.llseek = seq_lseek, /* we have seq_read */
};
// use default_llseek if there is a readdir
///////////////////////////////////////////
@ fops1 depends on !has_llseek && !nonseekable1 && !nonseekable2 && !seq @
identifier fops0.fops;
identifier readdir_e;
@@
// any other fop is used that changes pos
struct file_operations fops = {
... .readdir = readdir_e, ...
+.llseek = default_llseek, /* readdir is present */
};
// use default_llseek if at least one of read/write touches f_pos
/////////////////////////////////////////////////////////////////
@ fops2 depends on !fops1 && !has_llseek && !nonseekable1 && !nonseekable2 && !seq @
identifier fops0.fops;
identifier read.read_f;
@@
// read fops use offset
struct file_operations fops = {
... .read = read_f, ...
+.llseek = default_llseek, /* read accesses f_pos */
};
@ fops3 depends on !fops1 && !fops2 && !has_llseek && !nonseekable1 && !nonseekable2 && !seq @
identifier fops0.fops;
identifier write.write_f;
@@
// write fops use offset
struct file_operations fops = {
... .write = write_f, ...
+ .llseek = default_llseek, /* write accesses f_pos */
};
// Use noop_llseek if neither read nor write accesses f_pos
///////////////////////////////////////////////////////////
@ fops4 depends on !fops1 && !fops2 && !fops3 && !has_llseek && !nonseekable1 && !nonseekable2 && !seq @
identifier fops0.fops;
identifier read_no_fpos.read_f;
identifier write_no_fpos.write_f;
@@
// write fops use offset
struct file_operations fops = {
...
.write = write_f,
.read = read_f,
...
+.llseek = noop_llseek, /* read and write both use no f_pos */
};
@ depends on has_write && !has_read && !fops1 && !fops2 && !has_llseek && !nonseekable1 && !nonseekable2 && !seq @
identifier fops0.fops;
identifier write_no_fpos.write_f;
@@
struct file_operations fops = {
... .write = write_f, ...
+.llseek = noop_llseek, /* write uses no f_pos */
};
@ depends on has_read && !has_write && !fops1 && !fops2 && !has_llseek && !nonseekable1 && !nonseekable2 && !seq @
identifier fops0.fops;
identifier read_no_fpos.read_f;
@@
struct file_operations fops = {
... .read = read_f, ...
+.llseek = noop_llseek, /* read uses no f_pos */
};
@ depends on !has_read && !has_write && !fops1 && !fops2 && !has_llseek && !nonseekable1 && !nonseekable2 && !seq @
identifier fops0.fops;
@@
struct file_operations fops = {
...
+.llseek = noop_llseek, /* no read or write fn */
};
===== End semantic patch =====
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Cc: Julia Lawall <julia@diku.dk>
Cc: Christoph Hellwig <hch@infradead.org>
2010-08-15 18:52:59 +02:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
comedi: Use reference count for asynchronous command functions
For interrupts from badly behaved hardware (as emulated by Syzbot), it
is possible for the Comedi core functions that manage the progress of
asynchronous data acquisition to be called from driver ISRs while no
asynchronous command has been set up, which can cause problems such as
invalid pointer dereferencing or dividing by zero.
Change those functions in the Comedi core to use this pattern: if
`comedi_get_is_subdevice_running(s)` returns `true` then call a safe
version of the function with the same name prefixed with an underscore,
followed by a call to `comedi_put_is_subdevice_running(s)`, otherwise
take some default action.
`comedi_get_is_subdevice_running(s)` returning `true` ensures that the
details of the asynchronous command will not be destroyed before the
matching call to `comedi_put_is_subdevice_running(s)`.
Replace calls to those functions from elsewhere in the Comedi core with
calls to the safe versions of the functions.
The modified functions are: `comedi_buf_read_alloc()`,
`comedi_buf_read_free()`, `comedi_buf_read_n_available()`,
`comedi_buf_read_samples()`, `comedi_buf_write_alloc()`,
`comedi_buf_write_free()`, `comedi_buf_write_samples()`,
`comedi_bytes_per_scan()`, `comedi_event()`, `comedi_handle_events()`,
`comedi_inc_scan_progress()`, `comedi_nsamples_left()`,
`comedi_nscans_left()`.
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Link: https://patch.msgid.link/20251023133001.8439-3-abbotti@mev.co.uk
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2025-10-23 14:28:19 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2009-03-16 22:05:20 -04:00
|
|
|
|
2015-03-27 15:13:06 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2015-03-27 15:13:06 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-03-27 15:13:04 +00:00
|
|
|
|
2015-03-27 15:13:06 +00:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2015-03-27 15:13:06 +00:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2015-03-27 15:13:04 +00:00
|
|
|
|
2015-03-27 15:13:06 +00:00
|
|
|
|
2014-10-13 09:56:08 -07:00
|
|
|
|
|
|
|
|
|
2015-03-27 15:13:06 +00:00
|
|
|
|
|
|
|
|
|
2014-10-13 09:56:08 -07:00
|
|
|
|
2015-03-27 15:13:06 +00:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2015-03-27 15:13:04 +00:00
|
|
|
|
2013-11-08 15:03:22 +00:00
|
|
|
|
2015-03-27 15:13:05 +00:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2015-03-27 15:13:06 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
comedi: Use reference count for asynchronous command functions
For interrupts from badly behaved hardware (as emulated by Syzbot), it
is possible for the Comedi core functions that manage the progress of
asynchronous data acquisition to be called from driver ISRs while no
asynchronous command has been set up, which can cause problems such as
invalid pointer dereferencing or dividing by zero.
Change those functions in the Comedi core to use this pattern: if
`comedi_get_is_subdevice_running(s)` returns `true` then call a safe
version of the function with the same name prefixed with an underscore,
followed by a call to `comedi_put_is_subdevice_running(s)`, otherwise
take some default action.
`comedi_get_is_subdevice_running(s)` returning `true` ensures that the
details of the asynchronous command will not be destroyed before the
matching call to `comedi_put_is_subdevice_running(s)`.
Replace calls to those functions from elsewhere in the Comedi core with
calls to the safe versions of the functions.
The modified functions are: `comedi_buf_read_alloc()`,
`comedi_buf_read_free()`, `comedi_buf_read_n_available()`,
`comedi_buf_read_samples()`, `comedi_buf_write_alloc()`,
`comedi_buf_write_free()`, `comedi_buf_write_samples()`,
`comedi_bytes_per_scan()`, `comedi_event()`, `comedi_handle_events()`,
`comedi_inc_scan_progress()`, `comedi_nsamples_left()`,
`comedi_nscans_left()`.
Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
Link: https://patch.msgid.link/20251023133001.8439-3-abbotti@mev.co.uk
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2025-10-23 14:28:19 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-04-12 10:11:54 -07:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2013-04-04 14:58:51 +01:00
|
|
|
|
2013-04-04 14:58:50 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2013-04-04 14:58:50 +01:00
|
|
|
|
2009-03-16 22:05:36 -04:00
|
|
|
|
2016-03-21 09:18:35 -04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2026-02-21 16:37:42 -08:00
|
|
|
|
2015-03-04 12:15:28 -07:00
|
|
|
|
2013-04-04 14:58:50 +01:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:00 +01:00
|
|
|
|
2013-04-04 14:58:51 +01:00
|
|
|
|
2013-04-04 14:59:04 +01:00
|
|
|
|
2013-04-04 14:58:52 +01:00
|
|
|
|
|
|
|
|
|
2015-03-04 12:15:28 -07:00
|
|
|
|
2013-04-04 14:59:16 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:04 +01:00
|
|
|
|
2008-11-13 17:05:58 -08:00
|
|
|
|
2013-04-04 14:58:51 +01:00
|
|
|
|
2013-04-04 14:58:50 +01:00
|
|
|
|
2013-11-08 15:03:32 +00:00
|
|
|
|
2015-03-17 08:33:51 +03:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:58:50 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2013-04-04 14:58:50 +01:00
|
|
|
|
2023-06-20 16:41:38 +02:00
|
|
|
|
2011-07-06 10:15:44 -04:00
|
|
|
|
2008-11-13 17:05:58 -08:00
|
|
|
|
2013-12-11 14:51:02 +00:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2013-04-04 14:58:51 +01:00
|
|
|
|
2013-04-04 14:58:50 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:58:47 +01:00
|
|
|
|
2012-03-30 17:14:58 +01:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:16 +01:00
|
|
|
|
2012-03-30 17:14:58 +01:00
|
|
|
|
2013-04-04 14:58:52 +01:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:04 +01:00
|
|
|
|
2013-04-04 14:59:16 +01:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:04 +01:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:16 +01:00
|
|
|
|
2013-04-04 14:58:47 +01:00
|
|
|
|
2012-03-30 17:14:58 +01:00
|
|
|
|
2013-04-04 14:59:04 +01:00
|
|
|
|
2012-03-30 17:14:58 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-02-01 10:20:30 +00:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2013-02-01 10:20:30 +00:00
|
|
|
|
2009-03-16 22:05:36 -04:00
|
|
|
|
2016-03-21 09:18:35 -04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2013-04-04 14:59:04 +01:00
|
|
|
|
|
|
|
|
|
2015-03-04 12:15:28 -07:00
|
|
|
|
2013-04-04 14:59:15 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:04 +01:00
|
|
|
|
|
|
|
|
|
2015-03-17 08:33:51 +03:00
|
|
|
|
|
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:04 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2023-06-20 16:41:38 +02:00
|
|
|
|
2011-07-06 10:15:44 -04:00
|
|
|
|
2012-12-19 17:27:02 -07:00
|
|
|
|
2008-11-13 17:05:58 -08:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2012-05-09 09:20:08 -07:00
|
|
|
|
2013-02-07 16:03:00 +00:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
2009-03-16 22:05:14 -04:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2013-04-04 14:59:13 +01:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2015-03-04 12:15:28 -07:00
|
|
|
|
2008-11-13 17:05:58 -08:00
|
|
|
|
2015-08-10 13:14:01 -07:00
|
|
|
|
|
|
|
|
|
2008-11-13 17:05:58 -08:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
2013-04-04 14:59:13 +01:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:15 +01:00
|
|
|
|
|
|
|
|
|
2013-04-04 14:59:13 +01:00
|
|
|
|
2008-11-13 17:05:58 -08:00
|
|
|
|
2023-06-20 16:41:38 +02:00
|
|
|
|
2008-11-04 20:29:31 -08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-12-19 15:40:59 -07:00
|
|
|
|
2013-01-28 17:07:39 +00:00
|
|
|
|
2012-12-19 15:41:42 -07:00
|
|
|
|
2015-08-10 13:13:59 -07:00
|
|
|
|
2016-03-21 09:18:35 -04:00
|
|
|
|
2012-12-19 15:41:42 -07:00
|
|
|
|
2015-08-10 13:13:59 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-12-19 15:41:42 -07:00
|
|
|
|
|
|
|
|
|
2012-12-19 15:41:19 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-07-17 12:27:32 -07:00
|
|
|
|
2012-12-19 15:41:19 -07:00
|
|
|
|
2017-03-08 02:13:58 +08:00
|
|
|
|
2014-07-17 12:27:32 -07:00
|
|
|
|
2012-12-19 15:41:19 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-06-16 19:35:35 +01:00
|
|
|
|
|
|
|
|
|
2012-12-19 15:41:19 -07:00
|
|
|
|
|
|
|
|
|
2014-07-09 09:12:37 +04:00
|
|
|
|
|
|
|
|
|
2017-06-16 19:35:35 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-07-09 09:12:37 +04:00
|
|
|
|
2023-06-20 16:41:38 +02:00
|
|
|
|
|
|
|
|
|
2014-07-17 12:27:32 -07:00
|
|
|
|
2017-06-16 19:35:35 +01:00
|
|
|
|
2012-12-19 15:41:19 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-04-04 14:58:50 +01:00
|
|
|
|
2014-05-01 13:53:12 +05:30
|
|
|
|
2013-04-04 14:58:50 +01:00
|
|
|
|
|
|
|
|
|
2017-06-16 19:35:35 +01:00
|
|
|
|
|
|
|
|
|
2012-12-19 15:41:19 -07:00
|
|
|
|
2014-07-15 23:11:02 +08:00
|
|
|
|
2019-04-17 15:39:29 +01:00
|
|
|
|
2014-07-15 23:11:02 +08:00
|
|
|
|
2012-12-19 15:41:19 -07:00
|
|
|
|
|
|
|
|
|
2016-12-30 19:25:52 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-12-19 15:41:19 -07:00
|
|
|
|
2017-06-16 19:35:35 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2023-06-20 16:41:38 +02:00
|
|
|
|
2017-06-16 19:35:35 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-12-19 15:41:19 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-01-28 17:07:39 +00:00
|
|
|
|
2023-06-20 16:41:38 +02:00
|
|
|
|
2012-12-19 15:41:19 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-07-23 21:40:53 +02:00
|
|
|
|
2012-12-19 15:40:59 -07:00
|
|
|
|
|
|
|
|
|