From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4D9E7C33CA9 for ; Mon, 13 Jan 2020 22:17:59 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 094422084D for ; Mon, 13 Jan 2020 22:17:58 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="ST4aSNTT" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728641AbgAMWR6 (ORCPT ); Mon, 13 Jan 2020 17:17:58 -0500 Received: from mail-ot1-f68.google.com ([209.85.210.68]:44399 "EHLO mail-ot1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726530AbgAMWR6 (ORCPT ); Mon, 13 Jan 2020 17:17:58 -0500 Received: by mail-ot1-f68.google.com with SMTP id h9so10523523otj.11; Mon, 13 Jan 2020 14:17:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=bK5tAWYYK9RXUwEYak4dnGM+/7DX2wX/UYXB9gMajUQ=; b=ST4aSNTTlA/yd/eg+W3JhTUhV6Lymv/8pDR/NCMtzSaGxbjejrjsj5JOOrNLmLFwHS txzGWLc7LtTQZA6H/Pv6XNc+Yj9EOcL7cvnwGRpc6XJxvOiJq3cx58d8ft+HUt6C2EeE 5tkBZAWLGSOKcNV0tpGqAUSpp+x2yS4V9yBaYhcrOTz9bKAZ+8q4Sqn1s04dV2WS3OcY kM9V7JcMhFPU1A8RkJoC/BLny1iM3OC/qfL5CTrVhKenXWKqOBdNcV7c6G0z60fcLmjE +qx1uMIRkYyJB+1xarfE3iHNDSMlNrslZFTlNx5LphRGI5Ta+JQx/9q6TLTHtePJ5k7M gnxQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=bK5tAWYYK9RXUwEYak4dnGM+/7DX2wX/UYXB9gMajUQ=; b=hFgAEMWCyUWT6hLAcaz3qWAmvcMxtEjspfQe5tVGvJ9dACd+6oFEftXyR/4yfuhDRK 9dwvkZZKJRl321V+2NwHkKe7KCu/1G1yG5zjyVB8XbuPo2oSVS6XQFsQNPsWu5rfBHeD wFkEHOrthJ2Aku29i6jGQHY5UCzj44dHZknMcaKpsPNuFIXnPhZ2XqEnwdcv4R/6HQTA wqRU/aLKMdu7UXUNHueXgLEwirwKEIeTxJfFi95mFn1GBjJhJbn2GXaRYmdSdWaR3NS+ ZJRQ5eHN2rhzHlgmClHbGllpVqTgOfIkuWbRcoJti8wkIsBMO/Et9od/uUT2fAZEWilb Ilew== X-Gm-Message-State: APjAAAU1TnQp4bl3ylQ3ByAX+4ZP9IaMjiqh0Q0YyCBJSUryLdSPcOR0 c0QZSaU/7PIRJuxR+NXg2sE0ssgkOxpNW4pOU6s= X-Google-Smtp-Source: APXvYqyVdhG3hldz4ONnrT0gKc2YOBgljzMvL2rp8Bg5pF5JXB45PNzpJxFm6UCbTZB/iCUobze1pw30POKZAru7U64= X-Received: by 2002:a05:6830:155a:: with SMTP id l26mr14851212otp.339.1578953877354; Mon, 13 Jan 2020 14:17:57 -0800 (PST) MIME-Version: 1.0 References: <20191219165250.2875-1-bprotopopov@hotmail.com> <780DD595-1F92-4C34-A323-BB32748E5D07@dilger.ca> <20200113203613.GA111855@jra4> In-Reply-To: <20200113203613.GA111855@jra4> From: Boris Protopopov Date: Mon, 13 Jan 2020 17:17:46 -0500 Message-ID: Subject: Re: [PATCH] Add support for setting owner info, dos attributes, and create time To: Jeremy Allison Cc: Andreas Dilger , Steve French , CIFS , samba-technical , David Howells , linux-fsdevel Content-Type: text/plain; charset="UTF-8" Sender: linux-cifs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-cifs@vger.kernel.org OK, I will look into adding ctime-related attribute, and model it after btime. On Mon, Jan 13, 2020 at 3:36 PM Jeremy Allison wrote: > > On Mon, Jan 13, 2020 at 01:26:39PM -0700, Andreas Dilger via samba-technical wrote: > > On Jan 9, 2020, at 12:10 PM, Steve French wrote: > > > > > > One loosely related question ... > > > > > > Your patch adds the ability to set creation time (birth time) which > > > can be useful for backup/restore cases, but doesn't address the other > > > hole in Linux (the inability to restore a files ctime). > > > > > > In Linux the ability to set timestamps seems quite limited (utimes > > > only allows setting mtime and atime). > > > > The whole point of not being able to change ctime and btime as a regular > > user is so that it is possible to determine when a file was actually > > created on the filesystem and last modified. That is often useful for > > debugging or forensics reasons. > > > > I think if this is something that SMB/CIFS wants to do, it should save > > these attributes into an xattr of its own (e.g. user.dos or whatever), > > rather than using the ctime and btime(crtime) fields in the filesystem. > > FYI, we (Samba) already do this for create time to store/fetch it > on systems and filesystems that don't store a create time. It's > easy to add extra info here.