Bug#963746: Fw: [PATCH v2] Re: Strange segmentation violations of rpc.gssd in Debian Buster

From	"Kraus, Sebastian" <sebastian.kraus@tu-berlin.de>
Newsgroups	linux.debian.bugs.dist, linux.debian.kernel
Subject	Bug#963746: Fw: [PATCH v2] Re: Strange segmentation violations of rpc.gssd in Debian Buster
Date	2020-06-29 06:40 +0200
Message-ID	<AmTKh-7v-3@gated-at.bofh.it> (permalink)
References	(8 earlier) <AmTKh-7v-21@gated-at.bofh.it> <AmTKh-7v-23@gated-at.bofh.it> <AmTKh-7v-25@gated-at.bofh.it> <AlUS6-5lp-9@gated-at.bofh.it> <AmTKh-7v-27@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

Testing upstream patch by Doug Nazar:
Manually patching gssd.c, gssd_proc.c and gssd.h wihtin nfs-utils_1.3.4 source.
Rebuilding binary package nfs-common-1.3.4-2.5 from nfs-utils_1.3.4 source.
Testing altered binary packages nfs-common_1.3.4-2.5_amd64.deb and nfs-common-dbgsym_1.3.4-2.5_amd64.deb on one machine.

ToDo:
Correctly backporting Nazar's patch to nfs-utils_1.3.4 source of Debian Stable and Oldstable.
Roll-out to all NFS file servers.

Jump into nightmare's heaven oUt
Sebastian

________________________
Sebastian Kraus
Team IT am Institut für Chemie
Gebäude C, Straße des 17. Juni 115, Raum C7

Technische Universität Berlin
Fakultät II
Institut für Chemie
Sekretariat C3
Straße des 17. Juni 135
10623 Berlin

Email: sebastian.kraus@tu-berlin.de

________________________________________
From: linux-nfs-owner@vger.kernel.org <linux-nfs-owner@vger.kernel.org> on behalf of Doug Nazar <nazard@nazar.ca>
Sent: Friday, June 26, 2020 23:30
To: J. Bruce Fields
Cc: Kraus, Sebastian; linux-nfs@vger.kernel.org; Steve Dickson; Olga Kornievskaia
Subject: [PATCH v2] Re: Strange segmentation violations of rpc.gssd in Debian Buster

On 2020-06-26 17:02, J. Bruce Fields wrote:
> Unless I'm missing something--an upcall thread could still be using this
> file descriptor.
>
> If we're particularly unlucky, we could do a new open in a moment and
> reuse this file descriptor number, and then then writes in do_downcall()
> could end up going to some other random file.
>
> I think we want these closes done by gssd_free_client() in the !refcnt
> case?

Makes sense. I was thinking more that it was an abort situation and we
shouldn't be sending any data to the kernel but re-use is definitely a
concern.

I've split it so that we are removed from the event loop in destroy()
but the close happens in free().

Doug

Back to linux.debian.kernel | Previous | Next | Find similar | Unroll thread

Thread

Bug#963746: Fw: [PATCH v2] Re: Strange segmentation violations of rpc.gssd in Debian Buster "Kraus, Sebastian" <sebastian.kraus@tu-berlin.de> - 2020-06-29 06:40 +0200

csiph-web