Notice: We have migrated to GitLab launching 2024-05-01 see here: https://gitlab.rtems.org/

Timeline



11/10/21:

17:00 Ticket #4546 (A thread restart does not update the priority of related threads) created by Sebastian Huber
Consider the following scenario. Let a high priority task H wait on a …
08:27 Ticket #4545 (The SMP EDF scheduler can only support more restricted affinity sets ...) created by Sebastian Huber
The SMP EDF scheduler supports a one-to-one and one-to-all thread to …

11/09/21:

17:06 Ticket #4145 (rtems-source-builder: Update RTEMS Kernel Recipe to Use waf for RTEMS) closed by Ryan Long <ryan.long@…>
fixed: In [changeset:"def934785d4ae3c4b90733e8d5c443d61368268f/rtems-source-builder" def9347/rtems-source-builder]: […]

11/08/21:

09:44 Ticket #4544 (The last processor must not be removed if it is owned by a helping ...) created by Sebastian Huber
The following error condition is currently not checked by …

11/04/21:

15:43 Ticket #4501 (TraceConverter.cc: Uncaught exception issue spotted by Coverity) closed by Ryan Long <ryan.long@…>
fixed: In [changeset:"d1df4f6e02fe22d2cb542adbd6ba4248ee077892/rtems-tools" d1df4f6/rtems-tools]: […]
03:39 Ticket #4104 (RSB Tools newlib patch checksum fails.) reopened by Benjamin Garner
Checksum has broken again for this patch, 4.11 branch failing to build.

11/03/21:

14:22 Ticket #4543 (cannot build multiprocessor application on eclipse) created by mohamedosama94
Hi, hope my mail finds you well, i have an issue as i am using rtems6 …
01:23 Ticket #4542 (filename length problem in JFFS2 with RTEMS4.11.3/RTEMS5.1) created by chenjin_zhong
Hi, the MACRO JFFS2_MAX_NAME_LEN defines the maximum length of …

11/01/21:

14:54 Ticket #4541 (rtems_jffs2_rmnod function problem) created by chenjin_zhong
Hi, the dir_i->i_mode must be S_IFDIR in this situation.therefore, I …

10/29/21:

17:12 Ticket #4540 (Healthcare Mailing Lists) closed by Joel Sherrill
invalid
17:08 Ticket #4540 (Healthcare Mailing Lists) created by Albert
Removed all links as spam.
06:27 Ticket #4539 (rtems_filesystem_table compile) created by chenjin_zhong
Hi, when the macro CONFIGURE_APPLICATION_DISABLE_FILESYSTEM is …

10/28/21:

18:29 Ticket #4536 (acess JFFS2 sb->s_root) closed by Sebastian Huber
invalid: Replying to chenjin_zhong: > Replying to Sebastian Huber: > > Thanks for your interest in the RTEMS port of JFFS2. If you have questions, then you could also ask them on the devel@… mailing list. The RTEMS port of JFFS2 does not use a file system internal locking. There is a global lock for each JFFS2 instance: > > {{{#!c > > static void rtems_jffs2_do_lock(struct super_block *sb) > > { > > rtems_recursive_mutex_lock(&sb->s_mutex); > > } > > > > static void rtems_jffs2_do_unlock(struct super_block *sb) > > { > > rtems_recursive_mutex_unlock(&sb->s_mutex); > > } > > }}} > > Suppose that a GC thread or other thread/task calls jffs2_garbage_collect_pass, and then operates sb->s_root by jffs2_iget.meanwhile, the main task accesing sb->s_root. a global lock for each JFFS2 instance can't work. It is not a high performance approach, but it works. See testsuites/fstests/fsjffs2gc01/init.c.
18:26 Ticket #4538 (mutex is not initilaized in jffs2_read_inode) closed by Sebastian Huber
invalid: Replying to chenjin_zhong: > Replying to Sebastian Huber: > > Yes, the f->sem is an empty structure, it is not initialized, it is not used, locked or whatever in RTEMS. This is intentional and not a bug. I repeat: The RTEMS port of JFFS2 does not use a file system internal locking. There is a global lock for each JFFS2 instance. > > Thank you! I got it. but we Suppose that a GC thread or other thread/task and main task calls jffs2_do_readinode simultaneous. a global lock for each JFFS2 instance can't work. It is not a high performance approach, but it works. See testsuites/fstests/fsjffs2gc01/init.c.
15:07 Ticket #4538 (mutex is not initilaized in jffs2_read_inode) reopened by chenjin_zhong
14:53 Ticket #4536 (acess JFFS2 sb->s_root) reopened by chenjin_zhong
Replying to Sebastian Huber: > Thanks for your interest in the RTEMS port of JFFS2. If you have questions, then you could also ask them on the devel@… mailing list. The RTEMS port of JFFS2 does not use a file system internal locking. There is a global lock for each JFFS2 instance: > {{{#!c > static void rtems_jffs2_do_lock(struct super_block *sb) > { > rtems_recursive_mutex_lock(&sb->s_mutex); > } > > static void rtems_jffs2_do_unlock(struct super_block *sb) > { > rtems_recursive_mutex_unlock(&sb->s_mutex); > } > }}} Suppose that a GC thread or other thread/task calls jffs2_garbage_collect_pass, and then operates sb->s_root by jffs2_iget.meanwhile, the main task accesing sb->s_root. a global lock for each JFFS2 instance can't work.
14:45 Ticket #4537 (mutex is not initilaized in jffs2_new_inode) closed by Sebastian Huber
invalid: Yes, the f->sem is an empty structure, it is not initialized, it is not used, locked or whatever in RTEMS. This is intentional and not a bug. I repeat: The RTEMS port of JFFS2 does not use a file system internal locking. There is a global lock for each JFFS2 instance.
14:43 Ticket #4538 (mutex is not initilaized in jffs2_read_inode) closed by Sebastian Huber
invalid: Yes, the f->sem is an empty structure, it is not initialized, it is not used, locked or whatever in RTEMS. This is intentional and not a bug. I repeat: The RTEMS port of JFFS2 does not use a file system internal locking. There is a global lock for each JFFS2 instance.
14:42 Ticket #4537 (mutex is not initilaized in jffs2_new_inode) reopened by chenjin_zhong
14:40 Ticket #4538 (mutex is not initilaized in jffs2_read_inode) reopened by chenjin_zhong
Replying to Sebastian Huber: > Thanks for your interest in the RTEMS port of JFFS2. If you have questions, then you could also ask them on the devel@… mailing list. The RTEMS port of JFFS2 does not use a file system internal locking. There is a global lock for each JFFS2 instance: > {{{#!c > static void rtems_jffs2_do_lock(struct super_block *sb) > { > rtems_recursive_mutex_lock(&sb->s_mutex); > } > > static void rtems_jffs2_do_unlock(struct super_block *sb) > { > rtems_recursive_mutex_unlock(&sb->s_mutex); > } > }}} I have compared it with Linux JFFS2. The peice of source code in Linux is as follows,As shown in black-body section, the f->sem is not be initialized and locked in RTEMS. […]
05:20 Ticket #4538 (mutex is not initilaized in jffs2_read_inode) closed by Sebastian Huber
invalid: Thanks for your interest in the RTEMS port of JFFS2. If you have questions, then you could also ask them on the devel@… mailing list. The RTEMS port of JFFS2 does not use a file system internal locking. There is a global lock for each JFFS2 instance: […]
05:20 Ticket #4537 (mutex is not initilaized in jffs2_new_inode) closed by Sebastian Huber
invalid: Thanks for your interest in the RTEMS port of JFFS2. If you have questions, then you could also ask them on the devel@… mailing list. The RTEMS port of JFFS2 does not use a file system internal locking. There is a global lock for each JFFS2 instance: […]
05:19 Ticket #4536 (acess JFFS2 sb->s_root) closed by Sebastian Huber
invalid: Thanks for your interest in the RTEMS port of JFFS2. If you have questions, then you could also ask them on the devel@… mailing list. The RTEMS port of JFFS2 does not use a file system internal locking. There is a global lock for each JFFS2 instance: […]
05:19 Ticket #4535 (acess JFFS2 sb->s_root question) closed by Sebastian Huber
invalid: Thanks for your interest in the RTEMS port of JFFS2. If you have questions, then you could also ask them on the devel@… mailing list. The RTEMS port of JFFS2 does not use a file system internal locking. There is a global lock for each JFFS2 instance: […]

10/27/21:

15:13 Ticket #4538 (mutex is not initilaized in jffs2_read_inode) created by chenjin_zhong
HI, I have found when call jffs2_read_inode to read inode. the f->sem …
14:59 Ticket #4537 (mutex is not initilaized in jffs2_new_inode) created by chenjin_zhong
HI, I have found when call jffs2_new_inode to create inode. the f->sem …
14:47 Ticket #4536 (acess JFFS2 sb->s_root) created by chenjin_zhong
Hi, I have found when access global structure without mutex or …
14:34 Ticket #4535 (acess JFFS2 sb->s_root question) created by chenjin_zhong
Hi, I have found when access global structure without mutex or …
07:40 Ticket #4534 (SMP EDF scheduler violates priority group ordering) created by Sebastian Huber
The SMP EDF scheduler supports one-to-one and one-to-all thread to …
Note: See TracTimeline for information about the timeline view.