From owner-freebsd-hackers@freebsd.org  Wed Aug 23 06:49:57 2017
Return-Path: <owner-freebsd-hackers@freebsd.org>
Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 98D12DDFEE5
 for <freebsd-hackers@mailman.ysv.freebsd.org>;
 Wed, 23 Aug 2017 06:49:57 +0000 (UTC)
 (envelope-from kostikbel@gmail.com)
Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 1EC0A649EE
 for <freebsd-hackers@freebsd.org>; Wed, 23 Aug 2017 06:49:56 +0000 (UTC)
 (envelope-from kostikbel@gmail.com)
Received: from tom.home (kib@localhost [127.0.0.1])
 by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id v7N6nprk057293
 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
 Wed, 23 Aug 2017 09:49:52 +0300 (EEST)
 (envelope-from kostikbel@gmail.com)
DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua v7N6nprk057293
Received: (from kostik@localhost)
 by tom.home (8.15.2/8.15.2/Submit) id v7N6nou6057292;
 Wed, 23 Aug 2017 09:49:50 +0300 (EEST)
 (envelope-from kostikbel@gmail.com)
X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com
 using -f
Date: Wed, 23 Aug 2017 09:49:50 +0300
From: Konstantin Belousov <kostikbel@gmail.com>
To: Yuri <yuri@rawbw.com>
Cc: Freebsd hackers list <freebsd-hackers@freebsd.org>
Subject: Re: How can the shared memory object be undeletable when all shared
 memory segments belong to the same user?
Message-ID: <20170823064950.GM1700@kib.kiev.ua>
References: <b959b884-c362-5d93-39bb-6d9c9fd4f6bf@rawbw.com>
 <20170812090308.GH1700@kib.kiev.ua>
 <c8bf3688-6afb-8876-c9a4-5e1b8bfb4528@rawbw.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <c8bf3688-6afb-8876-c9a4-5e1b8bfb4528@rawbw.com>
User-Agent: Mutt/1.8.3 (2017-05-23)
X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00,
 DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no
 autolearn_force=no version=3.4.1
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Aug 2017 06:49:57 -0000

On Tue, Aug 22, 2017 at 06:10:14PM -0700, Yuri wrote:
> On 08/12/17 02:03, Konstantin Belousov wrote:
> >> Only renaming of the shared memory object in the code or reboot helped.
> > Root should be able to unlink it.
> 
> 
> Isn't shared memory supposed to be deleted when the last app that used 
> it quits, gracefully or not?

Yes for anonymous, no for named.