In msgrcv(), set msgtyp correctly. Hardwiring 0 as the message type
yields incorrect behaviour. The hardwiring was present in the very first commit that implemented msgrcv() (revision 1.4) and hasn't been changed since. The native implementation was complete at that time, so there doesn't seem to be a reason for the hardwiring from a technical point of view. Submitted by: Reinier Bezuidenhout <rbezuide@yahoo.com>
This commit is contained in:
parent
094f6d2694
commit
b76e6a6f09
@ -358,7 +358,7 @@ linux_msgrcv(struct thread *td, struct linux_msgrcv_args *args)
|
||||
bsd_args.msqid = args->msqid;
|
||||
bsd_args.msgp = args->msgp;
|
||||
bsd_args.msgsz = args->msgsz;
|
||||
bsd_args.msgtyp = 0; /* XXX - args->msgtyp; */
|
||||
bsd_args.msgtyp = args->msgtyp;
|
||||
bsd_args.msgflg = args->msgflg;
|
||||
return msgrcv(td, &bsd_args);
|
||||
}
|
||||
|
Loading…
Reference in New Issue
Block a user