public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: ecos-bugs@ecos.sourceware.org Subject: [Bug 1001591] New: Bogus pseudo-randomness in garbage collect Date: Mon, 21 May 2012 13:02:00 -0000 [thread overview] Message-ID: <bug-1001591-13@http.bugs.ecos.sourceware.org/> (raw) Please do not reply to this email. Use the web interface provided at: http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001591 Summary: Bogus pseudo-randomness in garbage collect Product: eCos Version: CVS Platform: All OS/Version: All Status: UNCONFIRMED Severity: major Priority: low Component: Filesystem support AssignedTo: unassigned@bugs.ecos.sourceware.org ReportedBy: stano@meduna.org CC: ecos-bugs@ecos.sourceware.org Class: Advice Request The jffs2_find_gc_block function in fs/jffs2/current/src/gc.c and jffs2_mark_node_obsolete in nodemgmt.c try to do pseudo-random stuff by computing jiffies % 128 and making probability decisions on the result. First I think that this kind of pseudo-randomness is not really correct for embedded systems that often have very predictable execution times. But what is much worse, compat/linux/current/include/linux/kernel.h defines jiffies as #define jiffies 100 I am no expert at jffs2 and cannot say whether this can lead to major problems or not, so I'd like someone with better understanding of jffs2 to look at it. Also check other usage of jiffies - I found one more in io/usb/eth/slave/current/host/ecos_usbeth.c -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2012-05-21 13:02 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-21 13:02 bugzilla-daemon [this message] 2012-05-21 13:02 ` [Bug 1001591] Bogus pseudo-randomness in jffs2 " bugzilla-daemon 2012-05-26 15:46 ` bugzilla-daemon 2012-05-27 0:53 ` bugzilla-daemon 2012-05-27 0:53 ` bugzilla-daemon 2012-05-21 13:02 [Bug 1001591] New: Bogus pseudo-randomness in " bugzilla-daemon
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-1001591-13@http.bugs.ecos.sourceware.org/ \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=ecos-bugs@ecos.sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).