Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id E612E200C01 for ; Thu, 19 Jan 2017 23:34:36 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id E4BA0160B54; Thu, 19 Jan 2017 22:34:36 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 3C074160B3A for ; Thu, 19 Jan 2017 23:34:36 +0100 (CET) Received: (qmail 97565 invoked by uid 500); 19 Jan 2017 22:34:35 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 97553 invoked by uid 99); 19 Jan 2017 22:34:35 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Jan 2017 22:34:35 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id B065AC12E5 for ; Thu, 19 Jan 2017 22:34:34 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -3.1 X-Spam-Level: X-Spam-Status: No, score=-3.1 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-2.999, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=greenbytes.de header.b=hHNG0zw3; dkim=pass (1024-bit key) header.d=greenbytes.de header.b=hHNG0zw3 Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id lKRnkLQL1Put for ; Thu, 19 Jan 2017 22:34:30 +0000 (UTC) Received: from mail.greenbytes.de (mail.greenbytes.de [5.10.171.186]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id B25D25F47E for ; Thu, 19 Jan 2017 22:34:29 +0000 (UTC) Received: by mail.greenbytes.de (Postfix, from userid 117) id F3D8D15A059A; Thu, 19 Jan 2017 23:33:58 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=greenbytes.de; s=mail; t=1484865238; bh=2wDMODAaWql+7Pjd5KfucSte1h9apTDAL2uWZtNdjPo=; h=From:Subject:Date:References:To:In-Reply-To:From; b=hHNG0zw3s5epgWTVTud+PFk2dMHpW+IFzc2vpIo17AY5whsX0DRSUCgyhDsgDLi2x 6CRa4+n05gJCCYF9hD1LZnCAmyW9c2TpvhATTIVIs9sN0bbh4y+nf2aDkVjFmEQ+yd JsNKRzrhjy6J5j/0chiH4URIkHnL7F3mne5MjwjI= Received: from [192.168.178.72] (unknown [93.211.112.192]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mail.greenbytes.de (Postfix) with ESMTPSA id AFDD115A0571 for ; Thu, 19 Jan 2017 23:33:58 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=greenbytes.de; s=mail; t=1484865238; bh=2wDMODAaWql+7Pjd5KfucSte1h9apTDAL2uWZtNdjPo=; h=From:Subject:Date:References:To:In-Reply-To:From; b=hHNG0zw3s5epgWTVTud+PFk2dMHpW+IFzc2vpIo17AY5whsX0DRSUCgyhDsgDLi2x 6CRa4+n05gJCCYF9hD1LZnCAmyW9c2TpvhATTIVIs9sN0bbh4y+nf2aDkVjFmEQ+yd JsNKRzrhjy6J5j/0chiH4URIkHnL7F3mne5MjwjI= From: Stefan Eissing Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: svn commit: r1779528 - /httpd/httpd/trunk/modules/http2/h2_mplx.c Date: Thu, 19 Jan 2017 23:33:57 +0100 References: <20170119210919.5347A3A1E65@svn01-us-west.apache.org> <4675A940-3775-430F-9875-A97585D9F02A@greenbytes.de> To: dev@httpd.apache.org In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.3259) archived-at: Thu, 19 Jan 2017 22:34:37 -0000 Have to sleep over this. But I agree that this area needs some change. > Am 19.01.2017 um 23:31 schrieb Yann Ylavic : >=20 > On Thu, Jan 19, 2017 at 10:58 PM, Yann Ylavic = wrote: >> On Thu, Jan 19, 2017 at 10:41 PM, Stefan Eissing >> wrote: >>>=20 >>> Would work. But then we could just never destroy this directly, >>> because it will always disappear via the parent h2_session pool? >>=20 >> Yes, we only need to cleanups things (or take actions) that are not >> cleaned implicitely by the pool itself. >=20 > Actually for the h2_session_cleanup() case, it seems that releasing > (and joining) the mplx should happen before anything else in (or > after) the cleanup, so you may not want to put > h2_mplx_release_and_join() in an mplx->pool cleanup that'd execute > after. >=20 > But if that's not an issue, you could do that and simply > session->mplx=3DNULL in the session cleanup. >=20 > If that's an issue, you could also register h2_session_cleanup as a > "normal" (i.e. not "pre_") cleanup, so that it exectutes after all > subpools are destroyed... >=20 > I just proposed the minimal patch... Stefan Eissing bytes GmbH Hafenstrasse 16 48155 M=C3=BCnster www.greenbytes.de