kern/106078: shmget regression in -CURRENT?
Remko Lodder
remko at elvandar.org
Thu Nov 30 10:50:21 PST 2006
The following reply was made to PR kern/106078; it has been noted by GNATS.
From: Remko Lodder <remko at elvandar.org>
To: JAroslav Suchanek <jarda at grisoft.cz>
Cc: FreeBSD-gnats-submit at FreeBSD.org, linimon at FreeBSD.org
Subject: Re: kern/106078: shmget regression in -CURRENT?
Date: Thu, 30 Nov 2006 19:45:06 +0100
On Thu, 2006-11-30 at 18:27 +0000, JAroslav Suchanek wrote:
> >Number: 106078
> >Category: kern
> >Synopsis: shmget regression in -CURRENT?
> >Confidential: no
> >Severity: non-critical
> >Priority: low
> >Responsible: freebsd-bugs
> >State: open
> >Quarter:
> >Keywords:
> >Date-Required:
> >Class: sw-bug
> >Submitter-Id: current-users
> >Arrival-Date: Thu Nov 30 18:30:12 GMT 2006
> >Closed-Date:
> >Last-Modified:
> >Originator: JAroslav Suchanek
> >Release: FreeBSD-CURRENT
> >Organization:
> >Environment:
> >Description:
> I just wonder whether there was some change in shmget behavior in current.
>
> Look at this patch to src/sys-cur/tools/regression/sysvshm/shmtest.c
>
> --- shmtest_old.c Tue Nov 28 09:59:55 2006
> +++ shmtest.c Tue Nov 28 09:58:39 2006
> @@ -126,6 +126,9 @@
> if ((sender_shmid = shmget(shmkey, pgsize, IPC_CREAT | 0640)) == -1)
> err(1, "shmget");
>
> + if ((sender_shmid = shmget(shmkey, pgsize, 0640)) == -1)
> + err(1, "shmget");
> +
> if (shmctl(sender_shmid, IPC_STAT, &s_ds) == -1)
> err(1, "shmctl IPC_STAT");
>
>
> It failed with permission denied. Is that ok? Same code does not fail on STABLE
> nor Linux.
>
> The system is:
> i386 FreeBSD 7.0-CURRENT
>
> Relevant part of conf file:
> options SYSVSHM #SYSV-style shared memory
> options SYSVMSG #SYSV-style message queues
> options SYSVSEM #SYSV-style semaphores
>
> As I searched via cvsview, there were no suspicious changes in sysv ipc code
> recently, the only change is switch to priv(9) from suser(9).
>
> Thanks for clarification,
> Jarda Suchanek
> >How-To-Repeat:
> >Fix:
> >Release-Note:
> >Audit-Trail:
> >Unformatted:
Hello, thanks for taking the time to report this issue. However I need
to disappoint you a little, this is not a PR, but a general question.
Can you please email the freebsd-bugs and/or freebsd-current
mailinglist(s) (findable via http://lists.freebsd.org/mailman/listinfo/)
and get helped that way? (People will probably help you sooner that way
as well).
Thanks and Cheers!
REmko
More information about the freebsd-bugs
mailing list