search for: undelay

...files in the same time, 'cat /sys/class/misc/hw_random/rng_*' Result: cat process will get stuck, it will return if we kill dd process. We have some static variables (eg, current_rng, data_avail, etc) in hw_random/core.c, they are protected by rng_mutex. I try to workaround this issue by undelay(100) after mutex_unlock() in rng_dev_read(). This gives chance for hwrng_attr_*_show() to get mutex. This patch also contains some cleanup, moving some code out of mutex protection. Do you have some suggestion? Thanks. diff --git a/drivers/char/hw_random/core.c b/drivers/char/hw_random/core.c i...

...files in the same time, 'cat /sys/class/misc/hw_random/rng_*' Result: cat process will get stuck, it will return if we kill dd process. We have some static variables (eg, current_rng, data_avail, etc) in hw_random/core.c, they are protected by rng_mutex. I try to workaround this issue by undelay(100) after mutex_unlock() in rng_dev_read(). This gives chance for hwrng_attr_*_show() to get mutex. This patch also contains some cleanup, moving some code out of mutex protection. Do you have some suggestion? Thanks. diff --git a/drivers/char/hw_random/core.c b/drivers/char/hw_random/core.c i...

...ad, reading from /dev/hwrng isn't required -- just use /dev/random? (This doesn't mean we shouldn't fix the issue here...) > We have some static variables (eg, current_rng, data_avail, etc) in hw_random/core.c, > they are protected by rng_mutex. I try to workaround this issue by undelay(100) > after mutex_unlock() in rng_dev_read(). This gives chance for hwrng_attr_*_show() > to get mutex. > > This patch also contains some cleanup, moving some code out of mutex > protection. > > Do you have some suggestion? Thanks. > > > diff --git a/drivers/char/...

...ad, reading from /dev/hwrng isn't required -- just use /dev/random? (This doesn't mean we shouldn't fix the issue here...) > We have some static variables (eg, current_rng, data_avail, etc) in hw_random/core.c, > they are protected by rng_mutex. I try to workaround this issue by undelay(100) > after mutex_unlock() in rng_dev_read(). This gives chance for hwrng_attr_*_show() > to get mutex. > > This patch also contains some cleanup, moving some code out of mutex > protection. > > Do you have some suggestion? Thanks. > > > diff --git a/drivers/char/...

...files in the same time, 'cat /sys/class/misc/hw_random/rng_*' Result: cat process will get stuck, it will return if we kill dd process. We have some static variables (eg, current_rng, data_avail, etc) in hw_random/core.c, they are protected by rng_mutex. I try to workaround this issue by undelay(100) after mutex_unlock() in rng_dev_read(). This gives chance for hwrng_attr_*_show() to get mutex. This patch also contains some cleanup, moving some code out of mutex protection. Do you have some suggestion? Thanks. diff --git a/drivers/char/hw_random/core.c b/drivers/char/hw_random/core.c i...

...d -- just use /dev/random? Yes. > (This doesn't mean we shouldn't fix the issue here...) Completely agree :-) > > We have some static variables (eg, current_rng, data_avail, etc) in hw_random/core.c, > > they are protected by rng_mutex. I try to workaround this issue by undelay(100) > > after mutex_unlock() in rng_dev_read(). This gives chance for hwrng_attr_*_show() > > to get mutex. > > > > This patch also contains some cleanup, moving some code out of mutex > > protection. > > > > Do you have some suggestion? Thanks. > &gt...

...inutes ago Terr-AIS 3.3 37.63586 -9.282853 116 17 149976051014997605102 hours, 53 minutes ago Terr-AIS 3.2 37.6392 -9.291157 118 18 149975870414997587043 hours, 23 minutes ago Sat-AIS Add to SAT Fleet for undelayed data <NA> <NA> <NA> 19 149975631414997563144 hours, 3 minutes ago Terr-AIS 3.0 37.68459 -9.321658 159 20 149975598814997559884 hours, 8 minutes ago Terr-AIS 3.3 37.68881 -9.3241...

...s ago Terr-AIS 3.3 37.63586 -9.282853 116 > 17 149976051014997605102 hours, 53 minutes ago Terr-AIS 3.2 37.6392 -9.291157 118 > 18 149975870414997587043 hours, 23 minutes ago Sat-AIS Add to SAT Fleet for undelayed data <NA> <NA> <NA> > 19 149975631414997563144 hours, 3 minutes ago Terr-AIS 3.0 37.68459 -9.321658 159 > 20 149975598814997559884 hours, 8 minutes ago Terr-AIS 3.3 37.68881 -...

Not reproducible. [1][2][3] If our answers don't seem to apply to your situation, it will likely be because you did not explain your question clearly. Not plain text. This is a plain text mailing list, and the best-case scenario when you let your email program send HTML is that what you saw is not what we see (worst case is your email is scrambled on our end). Have you read the

...; 3.3 37.63586 -9.282853 116 >> 17 149976051014997605102 hours, 53 minutes ago Terr-AIS >> 3.2 37.6392 -9.291157 118 >> 18 149975870414997587043 hours, 23 minutes ago Sat-AIS Add to SAT >> Fleet for undelayed data <NA> <NA> <NA> >> 19 149975631414997563144 hours, 3 minutes ago Terr-AIS >> 3.0 37.68459 -9.321658 159 >> 20 149975598814997559884 hours, 8 minutes ago Terr-AIS >>...

Hi, I am extracting positions data from the marine traffic website. The table has a "Timestamp" column which, in the browser, appears with the format yyyy-mm-dd HH:MM (UTC), e.g. 2017-07-10 14:04 (UTC). When I import the table, the same date "2017-07-10 14:04 (UTC)" appears as "1499696500149969650021 minutes ago", This is the more recent date and time. Older