Make sure CALLOUT_PROCESSED is not used

This flag is only used in combination with the callout expire list,
which we do not use in libbsd.
This commit is contained in:
Sebastian Huber 2018-07-26 14:35:56 +02:00
parent 6d9d7b1956
commit e37f03e47a
2 changed files with 3 additions and 1 deletions

View File

@ -681,7 +681,9 @@ callout_cc_add(struct callout *c, struct callout_cpu *cc,
sbt = cc->cc_lastscan;
c->c_arg = arg;
c->c_iflags |= CALLOUT_PENDING;
#ifndef __rtems__
c->c_iflags &= ~CALLOUT_PROCESSED;
#endif /* __rtems__ */
c->c_flags |= CALLOUT_ACTIVE;
#ifndef __rtems__
if (flags & C_DIRECT_EXEC)

View File

@ -47,8 +47,8 @@
#define CALLOUT_RETURNUNLOCKED 0x0010 /* handler returns with mtx unlocked */
#define CALLOUT_SHAREDLOCK 0x0020 /* callout lock held in shared mode */
#define CALLOUT_DFRMIGRATION 0x0040 /* callout in deferred migration mode */
#define CALLOUT_PROCESSED 0x0080 /* callout in wheel or processing list? */
#ifndef __rtems__
#define CALLOUT_PROCESSED 0x0080 /* callout in wheel or processing list? */
#define CALLOUT_DIRECT 0x0100 /* allow exec from hw int context */
#endif /* __rtems__ */