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.9 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS autolearn=unavailable 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 97997C04A6B for ; Sun, 12 May 2019 04:12:20 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 62F49208C0 for ; Sun, 12 May 2019 04:12:20 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=landley-net.20150623.gappssmtp.com header.i=@landley-net.20150623.gappssmtp.com header.b="qU7Hwxn3" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726332AbfELEMQ (ORCPT ); Sun, 12 May 2019 00:12:16 -0400 Received: from mail-oi1-f196.google.com ([209.85.167.196]:35900 "EHLO mail-oi1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726232AbfELEMP (ORCPT ); Sun, 12 May 2019 00:12:15 -0400 Received: by mail-oi1-f196.google.com with SMTP id l203so7162033oia.3 for ; Sat, 11 May 2019 21:12:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=landley-net.20150623.gappssmtp.com; s=20150623; h=subject:from:to:cc:references:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=zJ70OMmVoSATwQY41e9CXbzi4KY/zdWtiMcMVM3Rwn8=; b=qU7Hwxn3IxhowOOfu6iETyWGYZ8uOWfxuuJuPTlmL+Y03uBkhDUwgp5bUKfrX/epWo 0uww+l5p/OJ8Z4Ih/GofL/hTS4N6CFyXva8Cw+THf7cRng8DBNDnknXZVkSgD/VCtNN6 Ib2SNx1i1Lf3l8B55YnzhcUXLzMUKfaps9/FMIBo36Qn/Q2KdhfvKi3hND8n6m5SQnM8 lDpAWVA4AJyuBfKTvjV3vFKRtu62eysICpVmEnKYNlK43xBzSH5evomPGQGUU3c5ks4p 3Lq/W3QCCg2HPCN5iG70FeC1ww0vMcsAEYEGJ6XnpLO+E7AAq4u1sE6TNEmiZcQ/tL5x NhUg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:cc:references:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=zJ70OMmVoSATwQY41e9CXbzi4KY/zdWtiMcMVM3Rwn8=; b=k8vsvgn+QTR1G+dkYhZSd9jY5hy15mv3PtMv5bmW6BPlHqgEcO1UMXNh/iurUzgnTC KtToLe1jHyrCVW02mxW3YvKQ5H5Im+CcsGzYWObRIeJgvzxDagn13Dej/J3SMC/XDtkI /M0P1M+AFx3sGu0RgAzyjXwPTZK/LFdosHf+OVQR7/M84fNOr5XVfhOLm/n2gbv0wfSj bCQSKs4T/qqWD5qL+1EyqI6WaUKnyILDA39wO0zJjTZ7JvexfyqXBQIyp8MNjo2rob0n iBL3Z794p+eNzS7TL+/Niu6lk1oL5c/MV94dEXcR9pKb47/WOSbBEbCVfDWczVf94vh3 WjIg== X-Gm-Message-State: APjAAAX+8d0gvP7y3Lvcan8AIBi0mvTsVEIyJewgGirbI0ahQcPtMBMm oa5ARhSsaYqcON9OO6XVo0bSVg== X-Google-Smtp-Source: APXvYqwsz1sNEYQulaiAcNJtkVRe/vEPL7OP4OCFtAhzvdsHDEjbLD4uem3wP21mCcmLHlq8eNmslg== X-Received: by 2002:aca:3093:: with SMTP id w141mr10501165oiw.173.1557634334937; Sat, 11 May 2019 21:12:14 -0700 (PDT) Received: from [192.168.1.5] (072-182-052-210.res.spectrum.com. [72.182.52.210]) by smtp.googlemail.com with ESMTPSA id t7sm3206053otq.16.2019.05.11.21.12.13 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 11 May 2019 21:12:14 -0700 (PDT) Subject: Re: [PATCH v2 0/3] initramfs: add support for xattrs in the initial ram disk From: Rob Landley To: Andy Lutomirski , Roberto Sassu Cc: Al Viro , LSM List , linux-integrity , initramfs@vger.kernel.org, Linux API , Linux FS Devel , LKML , Mimi Zohar , silviu.vlasceanu@huawei.com, dmitry.kasatkin@huawei.com, takondra@cisco.com, kamensky@cisco.com, "H. Peter Anvin" , Arnd Bergmann , james.w.mcmechan@gmail.com References: <20190509112420.15671-1-roberto.sassu@huawei.com> <4aee6e10-0eec-1d76-af66-dc8c7b68b766@landley.net> Message-ID: Date: Sat, 11 May 2019 23:12:44 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <4aee6e10-0eec-1d76-af66-dc8c7b68b766@landley.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: owner-linux-security-module@vger.kernel.org Precedence: bulk List-ID: On 5/11/19 11:04 PM, Rob Landley wrote: > P.P.S. Sadly, if you want an actually standardized standard format where > implementations adhere to the standard: IETF RFC 1991 was published in 1996 and Nope, darn it, checked my notes and that wasn't it. I thought zip had an RFC, it's just zlib, deflate, and gzip, and that's not the number of any of them. I still think sticking with a lightly modified cpio makes the most sense, just... in band signalling that _doesn't_ solve the y2038 problem, the file size limit, or address sparse files seems kinda silly. Rob