summaryrefslogtreecommitdiffstats
path: root/cpukit/libblock (follow)
Commit message (Collapse)AuthorAgeFilesLines
* libblock: Avoid NULL pointer accessSebastian Huber2015-11-021-1/+3
|
* libblock: Fix warningSebastian Huber2015-03-051-2/+1
|
* IMFS: Replace node union with individual structSebastian Huber2015-01-271-11/+10
| | | | | | This reduces the average node size. Add and use IMFS_GENERIC_INITIALIZER().
* bdbuf: Fix race condition with sync active flagSebastian Huber2014-11-281-5/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Bug report by Oleg Kravtsov: In rtems_bdbuf_swapout_processing() function there is the following lines: if (bdbuf_cache.sync_active && !transfered_buffers) { rtems_id sync_requester; rtems_bdbuf_lock_cache (); ... } Here access to bdbuf_cache.sync_active is not protected with anything. Imagine the following test case: 1. Task1 releases buffer(s) with bdbuf_release_modified() calls; 2. After a while swapout task starts and flushes all buffers; 3. In the end of that swapout flush we are before that part of code, and assume there is task switching (just before "if (bdbuf_cache.sync_active && !transfered_buffers)"); 4. Some other task (with higher priority) does bdbuf_release_modified and rtems_bdbuf_syncdev(). This task successfully gets both locks sync and pool (in rtems_bdbuf_syncdev() function), sets sync_active to true and starts waiting for RTEMS_BDBUF_TRANSFER_SYNC event with only sync lock got. 5. Task switching happens again and we are again before "if (bdbuf_cache.sync_active && !transfered_buffers)". As the result we check sync_active and we come inside that "if" statement. 6. The result is that we send RTEMS_BDBUF_TRANSFER_SYNC event! Though ALL modified messages of that task are not flushed yet! close #1485
* bdbuf: Use rtems_cache_aligned_malloc()Sebastian Huber2014-11-251-9/+6
|
* bdbuf: Use rtems_cache_get_data_line_size()Sebastian Huber2014-11-201-9/+1
|
* Add and use RTEMS_CONTAINER_OF()Sebastian Huber2014-08-051-2/+2
|
* libblock: Avoid recursive mutexSebastian Huber2014-06-031-9/+10
|
* libblock: Add RTEMS_BDBUF_USE_PTHREADRalf Kirchner2014-06-022-62/+190
| | | | | | Use the PTHREAD mutexes and condition variables if available. This helps on SMP configurations to avoid the home grown condition variables via disabled preemption.
* libblock: Use pthread_once() for initializationRalf Kirchner2014-06-021-29/+25
| | | | | | Enabling and disabling preemption as done for single core will not work for SMP. In the bdbuf initialization preemption handling can be avoided in general by using pthread_once().
* score: Add and use RTEMS_ZERO_LENGTH_ARRAYSebastian Huber2014-04-152-2/+2
|
* Change all references of rtems.com to rtems.org.Chris Johns2014-03-2130-30/+30
|
* score: Add SMP lock profiling supportSebastian Huber2014-03-141-1/+2
|
* score: Add local context to SMP lock APISebastian Huber2014-03-111-7/+7
| | | | | | | | | | | Add a local context structure to the SMP lock API for acquire and release pairs. This context can be used to store the ISR level and profiling information. It may be later used to enable more sophisticated lock algorithms, e.g. MCS locks. There is only one lock that cannot be used with a local context. This is the per-CPU lock since here we would have to transfer the local context through a context switch which is very complicated.
* Filesystem: Use default kqfilter and poll handlerSebastian Huber2013-12-201-0/+2
|
* Filesystem: Add readv/writev handlersSebastian Huber2013-12-201-1/+3
| | | | | | | | | The readv() and writev() support was implemented in terms of multiple calls to the read and write handlers. This imposes a problem on device files which use an IO vector as single request entity. For example a low-level network device (e.g. BPF(4)) may use an IO vector to create one frame from multiple protocol layers each with its own IO vector entry.
* libblock: Use LAST for the last partition blockSebastian Huber2013-12-041-1/+1
|
* PR2157: fdisk partition table dump improvementWendell P Silva2013-12-031-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Show the correct index of partition's last block (partition end). The documentation of struct rtems_bdpart_partition (P) says that the member 'end' is the "Block index for partition end (this block is not a part of the partition)". Then, the fdisk's partition table dump should print ((P)->end - 1). Currently, one can think that the last block of a partition P is superposing the beginning of the partition (P + 1). Example: ---------------------------------------- PARTITION TABLE ------------+------------+-------------- BEGIN | END | TYPE ------------+------------+-------------- 2048 | 133120 | FAT 32 133120 | 15628032 | FAT 32 ------------+------------+-------------- With be proposed patch, it would be: ---------------------------------------- PARTITION TABLE ------------+------------+-------------- BEGIN | END | TYPE ------------+------------+-------------- 2048 | 133119 | FAT 32 133120 | 15628031 | FAT 32 ------------+------------+--------------
* Remove double count of start offsetRic Claus2013-10-171-5/+5
|
* libblock: PR2145: Limit maximum read-ahead blocksSebastian Huber2013-09-162-3/+14
| | | | This helps to prevent stack overflows due to configuration errors.
* flashdisk: swap arguments to checksum helperGedare Bloom2013-09-051-1/+1
| | | | | | | The arguments to rtems_fdisk_calc_crc16() are reversed when called from rtems_fdisk_page_checksum(). 26052 Operands don't affect result
* nvdisk: swap arguments to checksum helperGedare Bloom2013-09-051-1/+1
| | | | | | | The arguments to rtems_nvdisk_calc_crc16() are reversed when called from rtems_nvdisk_page_checksum(). 26053 Operands don't affect result
* sparse-disk: check return value from semaphore_obtain/releaseGedare Bloom2013-09-051-2/+9
| | | | In case obtain/release is unsuccessful, cause a fatal error.
* bdpart: Argument cannot be negativeGedare Bloom2013-09-051-2/+3
| | | | If open(fd) fails then avoid the error path that calls close(fd).
* libblock: Use unprotected chain extractSebastian Huber2013-08-271-1/+1
| | | | This area is protected by the media mutex.
* libblock: Avoid uninitialized variableSebastian Huber2013-08-261-2/+1
|
* libblock: PR2040: Avoid NULL pointer accessSebastian Huber2013-08-231-6/+16
| | | | | | | This partly reverts commit 08b9d534604fbf437743a9925ef28eb1b848510d. Avoid a NULL pointer access and perform the source segment erase if necessary.
* libblock: Add missing initializerSebastian Huber2013-08-141-1/+1
|
* libblock: Add SMP supportSebastian Huber2013-08-141-5/+7
|
* score: Merge tod implementation into one fileSebastian Huber2013-07-261-1/+1
| | | | | Delete TOD_MICROSECONDS_PER_SECOND, TOD_MICROSECONDS_TO_TICKS() and TOD_MILLISECONDS_TO_TICKS().
* Include missing <string.h>Sebastian Huber2013-07-234-0/+5
|
* libblock: Use UTF-8 converter in media managerSebastian Huber2013-06-041-3/+10
|
* ramdisk: Fix device name generationSebastian Huber2013-03-221-1/+1
|
* libblock: Do resource allocation in one placeSebastian Huber2013-02-211-115/+153
| | | | | | | All resource allocations take place in rtems_bdbuf_init() now. After rtems_bdbuf_init() no fatal errors can happen due to configuration errors or resource limits. This makes it easier to detect configuration errors for users.
* cpukit: Use Consistent Beginning of Doxygen Group NotationJoel Sherrill2013-01-108-39/+21
| | | | | This is the result of a sed script which converts all uses of @{ into a consistent form.
* Header File Doxygen Enhancement Task #1Alex Ivanov2012-12-283-8/+5
|
* Header File Doxygen Enhancement Task #7Mathew Kallada2012-12-281-1/+1
|
* Header File Doxygen Enhancement Task #2Mathew Kallada2012-12-284-6/+8
|
* libblock: Use @brief in documentationSebastian Huber2012-12-211-22/+22
|
* libblock: Doxygen Enhancement Task #1 correctionsJennifer Averett2012-12-212-6/+5
|
* libblock: Doxygen Enhancement Task #1Mathew Kallada2012-12-2120-70/+97
|
* libblock: Use rtems_blkdev_create_partition()Sebastian Huber2012-12-211-53/+82
| | | | | Use rtems_blkdev_create_partition() instead of rtems_disk_create_log() to avoid problems with the huge IMFS_GENERIC_DEVICE_MAJOR_NUMBER.
* Fix spellingSebastian Huber2012-12-141-1/+1
|
* libblock: Add sparse diskRalf Kirchner2012-12-053-0/+525
|
* libblock: DocumentationRalf Kirchner2012-11-291-1/+1
|
* score: Add RTEMS_FATAL_SOURCE_BDBUFSebastian Huber2012-11-151-78/+73
| | | | | | Add rtems_bdbuf_fatal_code as a replacement for the previous fatal error codes. Remove unused error codes. Add new error codes. Use rtems_fatal() with RTEMS_FATAL_SOURCE_BDBUF as source.
* libblock: DocumentationSebastian Huber2012-11-022-98/+125
|
* libblock: Block device transfer request API changeSebastian Huber2012-11-025-48/+63
| | | | | | | | | | | | | | Add and use rtems_blkdev_request_done(). Block device transfer requests must signal the completion status now with rtems_blkdev_request_done(). The return value of the block device IO control will be ignored for transfer requests. The first parameter of rtems_blkdev_request_cb is now the transfer request structure. Renamed rtems_blkdev_request::req_done to rtems_blkdev_request::done to break third party drivers at compile time, otherwise this API change would result in runtime errors.
* libblock: Use transient eventSebastian Huber2012-10-301-5/+15
|
* libblock: rtems_bdbuf_set_block_size() API changeSebastian Huber2012-10-264-9/+28
| | | | | | | The set block size must synchronize and purge the disk to avoid an inconsistent cache state and data corruption. The synchronization is optional depending on the new sync parameter. In some contexts a synchronization must not be performed, e.g. during disk creation.
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-27 21:48:40 +0000