DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 50MA0H1R3180897 Authentication-Results: delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com Authentication-Results: delorie.com; spf=pass smtp.mailfrom=cygwin.com DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 50MA0H1R3180897 Authentication-Results: delorie.com; dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=uraV8wzq X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 99CC7385781B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1737540015; bh=tpYpOj6fvz5OpEsfHO8ydPZGEZ+wplvfVpIMCZp2GMk=; h=References:In-Reply-To:Date:Subject:To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=uraV8wzqxJOetjF+1pBXhC2kr9vedCJ9f0PUB3Bg0FrD0V+MUMdc1/kOYl86fMTFu hWooaBj/4dNJ8MH7bn28S5gHJpk8qfLGCFtgdy+SNfyo3t2u2Lmmm/7XMUzGxSZgbR Z1UOpRLeSGh6BPXbUfl8tmc90lnF6OAjHqkoR6Lk= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 8C0223857720 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 8C0223857720 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1737539936; cv=none; b=W0RkkzI72TcAa1vhWUW5+5164+kQ6OSFprETgn0W+gbwdYSc1J008/WG3UjjHVwx7NYX6fzxrwNgo0+0g5541w47qZzlkiHnVI6Vh9aRUEe0iNIwfBW9A6TGOmfdmzRhmAC4HrF0R3LHM8r0UxrP8cecXr0lx2Kkl8Bl/LluzAU= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1737539936; c=relaxed/simple; bh=UBW8/9kjenuc3Q+jDIgq2owCgttqR66r57woCmuFnOI=; h=DKIM-Signature:MIME-Version:From:Date:Message-ID:Subject:To; b=GqCLlcGlspURYsl+rcoKnJXxJU3kA6wlQPDoKdxqh/Rjf277qhW+AxyEg8MerzF2L4dAJd/k0U4GU/ZosRSD3nY9pnpKySmOftxQf6s0VlN1uD8n2IvOfeeIiVHlLh8a5qikssfFfv38i/gIkSZKzbsnYavXFo/+y8KIoOwIqGM= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8C0223857720 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1737539935; x=1738144735; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=KUytTNchWhFYxfLxZFtJKJiCVuZ2t5NRFWPxqP9l24w=; b=eanSlnQ+03tKe3DWiixBkA/HbJUrOM1M/N125CJoUdxmaHV9921JvKPiBfh4YLh5cV eow7mwBgzgNvSlAUo2xCaFdSurtueIYDMOshSZV5CzI5K5R2Dm1gdnJr4lb2r61n431k zRT+ixbXgU543mcNa4M1N+MNRfmAcfFxroc9vihkgKN53cknVoORvIdCrO8qXiIaAmdn e6kBfcM3yjCL1f6VUJTxTzngxcRLrFA5UCAhBPLgmeVlXUl+fyvh6DkpDbGTSXrnWTjq +UkIzCMYKr0+AHc1hqWu9Z7L2NhqAUvILfcDmSh96fsh9durYM5XEpgWDuc2wbUody5r rXBg== X-Gm-Message-State: AOJu0YyjuycQtIF5VvlRPNdfChu1BfKEeu8zlTqbPggMFr7cr56+uQRP mKDkou7Q2cDiweEDjdks1bWp+9Gk1ZDncWhJ65XfYnFbl74uKNuw7MNuc1B+ycmt3ED4CdDGcLe JseXW24M9I9Hl+LA1wLZ5z251rD2TKg== X-Gm-Gg: ASbGncthjJV+HCmgEuHheR8IuMHiN7a80a0Hkk9B+FlshVnJVmvW7tQzmojEk7jXcQU Pn9/TTeJcr60BNADAyWDPTQ++z8JYOrwxV0fEA051raQdS7SvUGI= X-Google-Smtp-Source: AGHT+IHBKuVFD3rjCPQUAqwSllydymL1Uv1g55d81lOjDmfFqWBYXi61WPkrWeWxXsUensQY5yYQSepzLElF0OYepZo= X-Received: by 2002:a17:90b:1c91:b0:2f5:63a:44f8 with SMTP id 98e67ed59e1d1-2f728dc073emr46969795a91.8.1737539935224; Wed, 22 Jan 2025 01:58:55 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Wed, 22 Jan 2025 10:58:17 +0100 X-Gm-Features: AbW1kvYy9Rd_kq2OxhmWT2eUXTeS4HWdwJM6fUm6CCjRcEgbVeMljydzuCRuiLQ Message-ID: Subject: Re: Handing filesystems which do not support some timestamp fields in |FILE_BASIC_INFO| and Microsoft NFSv3 driver "NfsV3Attributes" EA ... To: cygwin AT cygwin DOT com X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.30 List-Id: General Cygwin discussions and problem reports List-Archive: List-Post: List-Help: List-Subscribe: , From: Cedric Blancher via Cygwin Reply-To: Cedric Blancher Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "Cygwin" On Wed, 22 Jan 2025 at 00:38, Roland Mainz via Cygwin wrote: > > Hi! > > ---- > > If a Windows filesystem does not support a type of timestamp it sets > the matching timestamp field in |FILE_BASIC_INFO| to |0LL| (e.g. see > Windows-driver-samples/filesys/cdfs/fileinfo.c: > |Buffer->LastAccessTime.QuadPart = 0| ; typically this can affect > |FILE_BASIC_INFO.CreationTime| and/or > |FILE_BASIC_INFO.LastAccessTime|, but formally any combination of > timestamp fields can be unsupported(==|0LL|)), and the Microsoft NFSv3 > driver sets the matching > |nfs_timestruc_t.tv_sec|+|nfs_timestruc_t.tv_nsec| to a negative value > (traditional UNIX uses -1, see > https://github.com/gagern/gnulib/blob/master/lib/stat-time.h#L173 - > and this value is then propagated via NFS), but I can't find a place > in Cygwin where this is explicitly handled - is this missing, or is > this code handling this somehow implicitly ? > What should Cygwin stat() return if a timestamp field is not supported by the file system? Return tv_sec=-1? Ced -- Cedric Blancher [https://plus.google.com/u/0/+CedricBlancher/] Institute Pasteur -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple