When dealing with multiple sub-arches (like 32- and 64-bit on x86, for
example) generating a bunch of kernel tar archives with the same name
but for different sub-arches could get confusing and error-prone. Also,
the build process could overwrite otherwise unrelated builds and you
probably don't want that. So, add the architecture to the archive name
for more clarity and less shoot-yourself-in-the-foot practices.
Signed-off-by: NBorislav Petkov <bp@suse.de>
Signed-off-by: NMichal Marek <mmarek@suse.cz>

For large kernel configurations (like a distribution kernel)
targz-pkg takes a quite long time to just do the compression.
I clocked it at 15+mins for a SUSE kernel like config on a fast
system.  And tarxz and bzip2 are even slower.

The main reason is that the script that is doing the taring sets
the highest compression level (-9).  When I change it to just
use the defaults the gzip time for the same kernel goes down
to ~3 mins. I haven't tested xz and bzip, but I expect those
to be much faster too.

I'm not willing to wait that long for a small compression
gain. So just change the script to use the defaults.
Signed-off-by: NAndi Kleen <ak@linux.intel.com>
Reviewed-by: NFengguang Wu <fengguang.wu@intel.com>
Signed-off-by: NMichal Marek <mmarek@suse.cz>

There were reports of users destroying their Fedora installs by a kernel
tarball that replaces the /lib -> /usr/lib symlink. Let's remove the
toplevel directories from the tarball to prevent this from happening.
Reported-by: NAndi Kleen <andi@firstfloor.org>
Suggested-by: NBen Hutchings <ben@decadent.org.uk>
Cc: <stable@kernel.org>
Signed-off-by: NMichal Marek <mmarek@suse.cz>

Fixes generated by 'codespell' and manually reviewed.
Signed-off-by: NLucas De Marchi <lucas.demarchi@profusion.mobi>

Signed-off-by: NZdenek Kaspar <zkaspar82@gmail.com>
Signed-off-by: NMichal Marek <mmarek@suse.cz>

Use the --owner= and --group= options to make sure the entries in
the built tar file are owned by root.  Without this change, a
careless sysadmin using the tar-pkg target can easily end up
installing a kernel that is writable by the unprivileged user
account used to build the kernel.

Test that these options are understood before using them so that
non-GNU versions of tar can still be used if the operator is
appropriately cautious.
Signed-off-by: NJonathan Nieder <jrnieder@gmail.com>
Signed-off-by: NMichal Marek <mmarek@suse.cz>

Signed-off-by: NHelge Deller <deller@gmx.de>
Signed-off-by: NKyle McMartin <kyle@mcmartin.ca>

Signed-off-by: NDaniel De Graaf <danieldegraaf@gmail.com>
Signed-off-by: NSam Ravnborg <sam@ravnborg.org>

Signed-off-by: NAndi Kleen <ak@suse.de>
Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>

Fix out-of-tree builds for the tar-pkg targets

When I wrote the buildtar script, I didn't even think about
out-of-tree builds because I didn't use these back then. This patch
throughoutly uses ${objtree} instead of `pwd`.

Also, the kernel version is no longer manually built. Instead, it will
properly use $KERNELRELEASE .  Installing modules is only done if
CONFIG_MODULES is set.
Signed-off-by: NJan-Benedict Glaw <jbglaw@lug-owl.de>
Signed-off-by: NSam Ravnborg <sam@ravnborg.org>

It adds tarball packaging, which I prefer for distribution.
Also one of the two blanks after @echo is removed. One seems to be enough :)
Signed-off-by: NJan-Benedict Glaw <jbglaw@lug-owl.de>
Signed-off-by: NSam Ravnborg <sam@ravnborg.org>