Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Wed, 14 Oct 2020 17:06:22 -0700
From:   Jakub Kicinski <kuba@kernel.org>
To:     Srujana Challa <schalla@marvell.com>
Cc:     <herbert@gondor.apana.org.au>, <davem@davemloft.net>,
        <netdev@vger.kernel.org>, <linux-crypto@vger.kernel.org>,
        <sgoutham@marvell.com>, <gakula@marvell.com>,
        <sbhatta@marvell.com>, <schandran@marvell.com>,
        <pathreya@marvell.com>
Subject: Re: [PATCH v7,net-next,07/13] crypto: octeontx2: load microcode and
 create engine groups
Message-ID: <20201014170622.6de93e9a@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net>
In-Reply-To: <20201012105719.12492-8-schalla@marvell.com>
References: <20201012105719.12492-1-schalla@marvell.com>
        <20201012105719.12492-8-schalla@marvell.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Mon, 12 Oct 2020 16:27:13 +0530 Srujana Challa wrote:
> +/* tar header as defined in POSIX 1003.1-1990. */
> +struct tar_hdr_t {
> +	char name[100];
> +	char mode[8];
> +	char uid[8];
> +	char gid[8];
> +	char size[12];
> +	char mtime[12];
> +	char chksum[8];
> +	char typeflag;
> +	char linkname[100];
> +	char magic[6];
> +	char version[2];
> +	char uname[32];
> +	char gname[32];
> +	char devmajor[8];
> +	char devminor[8];
> +	char prefix[155];
> +};
> +
> +struct tar_blk_t {
> +	union {
> +		struct tar_hdr_t hdr;
> +		char block[TAR_BLOCK_LEN];
> +	};
> +};

In networking we've been pushing back on parsing firmware files 
in the kernel. Why do you need to parse tar archives?