Age | Commit message (Collapse) | Author |
|
On MIPS64, "__u64" is "unsigned long" type, so the "%llu" specifier will cause
build error on MIPS64.
Convert __u64 to unsigned long long in those sprintf calls to avoid the build
error.
Signed-off-by: Yang Shi <yang.shi@windriver.com>
|
|
Taken from: https://lkml.org/lkml/2013/6/20/80
Fix the following errors on gcc 4.8.1 / x86:
bench/numa.c: In function worker_thread:
bench/numa.c:1113:20: error: comparison between signed and unsigned integer expressions [-Werror=sign-compare]
if (diff.tv_sec >= g->p.nr_secs) {
^
bench/numa.c:1161:6: error: format %lx expects argument of type long unsigned int, but argument 5 has type u64 [-Werror=format=]
process_nr, thread_nr, runtime_ns_max / bytes_done, val);
^
Signed-off-by: Riccardo Magliocchetti <riccardo.magliocchetti@gmail.com>
Signed-off-by: Yang Shi <yang.shi@windriver.com>
|
|
We don't have 'expand' in our userspace so we need to accomplish the
same thing using 'sed', which we do have.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
CFLAGS was previously hard coded to contain "-I/usr/include/slang" to
work with hosts that have "/usr/include/slang/slang.h" as well as hosts
that have "/usr/include/slang.h". This path can cause compile warnings
like:
cc1: warning: '/usr/include/slang' doesn't exists.
or
cc1: warning: include location "/usr/include/slang" is unsafe for
cross-compilation [-Wpoison-system-directories]
Then in some cases warnings become errors if WERROR is enabled hence
build errors.
To fix this issue, we can use -idirafter to downgrade the priority of the
default hard coded path. We can also make the slang include directory
a variable, to allow the user to specify SLANG_INC and set their own
include location. And add a '=' prefix to indicate better
compatibility with sysroot/cross compile cases.
Signed-off-by: Liang Li <liang.li@windriver.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
|
|
Allow Python.h to find the definitions it needs on mips i.e. get rid
of the error: "_ABIN32" is not defined.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
Otherwise we get the sysroot path appended to the build path, not what
we want.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
If libperl isn't found, display a message to that effect along with
some hints on how to fix it.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
Python has build flags available via pkg-config, use those at
build-time instead.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
Large parts of perf use bool variables and assignments.
Rather than depending on transient includes, we force it
by including <stdbool.h> directly in perf.h
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Introduce the ability to limit the limit the uptime of a kernel.
When enabled, these options set a maximum uptime on the kernel, and
(optionally) trigger a clean reboot at expiration.
This functionality may appear to be very close to the softdog watchdog
implementation. It is. But can't be the softdog for several reasons:
- The soft watchdog should be available while this functionality is active
- The duration range is different between this and the softdog. The
timeout available here is potentially quite a bit longer.
- At expiration, there are different expiration requirements and actions.
- This functionality is specific to a particular use case and should
not impact mainline functionality
To cleanly restart the kernel after one minute of uptime, the following
config items would be required:
CONFIG_UPTIME_LIMITED_KERNEL=y
CONFIG_UPTIME_LIMIT_DURATION=1
CONFIG_UPTIME_LIMIT_KERNEL_REBOOT=y
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Introduced in commit 16b6ba6d7f6b0e8a2baeb14b128df0bb0a0a5680
("FAT: Add CONFIG_VFAT_FS_NO_DUALNAMES option"), the use of
random32 is no longer allowed.
The compatibility wrappers have been removed, so we have to
align the additions from this older patch to match upstream
commit 496f2f93b1cc286f5a4f4f9acdc1e5314978683f ("random32: rename
random32 to prandom") which does:
This renames all random32 functions to have 'prandom_' prefix as follows:
void prandom_seed(u32 seed); /* rename from srandom32() */
u32 prandom_u32(void); /* rename from random32() */
[...]
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
|
|
This patch adds a new flag field 'FAT_NO_83NAME' for FAT files. When
this flag is set on an 8.3 FAT entry, both the MSDOS and VFAT
filesystems will skip the entry. For MSDOS this makes the file
inaccessible. For VFAT it makes the file only accessible by the long
filename.
Signed-off-by: Andrew Tridgell <tridge@samba.org>
|
|
When this option is enabled this will refuse to create new files with
long names. Accessing existing files with long names will continue to
work.
File names to be created must conform to the 8.3 format. Mixed case is
not allowed in either the prefix or the suffix.
Signed-off-by: Andrew Tridgell <tridge@samba.org>
Signed-off-by: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
Signed-off-by: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
|
|
This patch adds a new config option VFAT_FS_NO_DUALNAMES. When
VFAT_FS_NO_DUALNAMES is enabled, VFAT will never create a file with
both a long and a short filename. If a long filename is needed, then
dummy bytes are stored in the 8.3 entry, and the 8.3 entry is marked
as having no short name using the FAT_NO_83NAME flag.
Signed-off-by: Andrew Tridgell <tridge@samba.org>
|
|
Hook cryptodev-linux into the kernel build as a tristate option.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Jianchuan Wang <jianchuan.wang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
|
|
|
|
Calculate tag and destination buffer length in a single place to avoid
code duplication. The TLS case is fixed by rounding the destination
length to cipher block size.
Signed-off-by: Cristian Stoica <cristian.stoica@freescale.com>
|
|
|
|
- block and stream ciphers have their keys copied from userspace
just like before
- for aead composite ciphers, the cipher and hmac keys are
combined into a single key
Signed-off-by: Cristian Stoica <cristian.stoica@freescale.com>
Signed-off-by: Phil Sutter <phil@nwl.cc>
|
|
The enclosing structure refers to both keys either as individuals
or as a group. For block ciphers and hmacs, both keys are used
independently. For composite ciphers the whole structure will be
used as a single key.
Signed-off-by: Cristian Stoica <cristian.stoica@freescale.com>
Signed-off-by: Phil Sutter <phil@nwl.cc>
|
|
Composite ciphers (cipher + hmac) use both keys at the same time. This
patch is the first in a series that adds support for composite ciphers
keys.
Signed-off-by: Cristian Stoica <cristian.stoica@freescale.com>
Signed-off-by: Phil Sutter <phil@nwl.cc>
|
|
That is because in AEAD modes we need to write more data than we read
(the tag value).
Reported and investigated by Dian Nguyen.
Signed-off-by: Nikos Mavrogiannopoulos <nmav@redhat.com>
|
|
If 'open /dev/crypto' fails, all allocated resources must be freed
before "open" returns; "close" can't be called to clean-up since
there is no file descriptor after a failed "open".
Signed-off-by: Cristian Stoica <cristian.stoica@freescale.com>
Signed-off-by: Phil Sutter <phil@nwl.cc>
|
|
This makes the test complain if the output fields were not altered at
all.
Signed-off-by: Phil Sutter <phil@nwl.cc>
|
|
Signed-off-by: Phil Sutter <phil@nwl.cc>
|
|
Signed-off-by: Phil Sutter <phil@nwl.cc>
|
|
Signed-off-by: Phil Sutter <phil@nwl.cc>
|
|
Signed-off-by: Phil Sutter <phil@nwl.cc>
|
|
Use them instead of directly calling dprintk. Also, line continuations
are to be indented with two tabs, unless there is good reason not to.
Signed-off-by: Phil Sutter <phil@nwl.cc>
|
|
Signed-off-by: Phil Sutter <phil@nwl.cc>
|
|
Normally we use dprintk which respects the module's own log level, but
at this early stage (driver registration), being noisy should be fine.
Signed-off-by: Phil Sutter <phil@nwl.cc>
|
|
Signed-off-by: Phil Sutter <phil@nwl.cc>
|
|
Signed-off-by: Phil Sutter <phil@nwl.cc>
|
|
Signed-off-by: Phil Sutter <phil@nwl.cc>
|
|
Signed-off-by: Phil Sutter <phil@nwl.cc>
|
|
Signed-off-by: Phil Sutter <phil@nwl.cc>
|
|
Signed-off-by: Phil Sutter <phil@nwl.cc>
|
|
Signed-off-by: Phil Sutter <phil@nwl.cc>
|
|
Signed-off-by: Phil Sutter <phil@nwl.cc>
|
|
Signed-off-by: Phil Sutter <phil@nwl.cc>
|
|
Signed-off-by: Phil Sutter <phil@nwl.cc>
|
|
Signed-off-by: Phil Sutter <phil@nwl.cc>
|
|
currently using the 3.13-rc3 Linux kernel, which leads to the following error:
cryptlib.c:279:2: error: implicit declaration of function 'INIT_COMPLETION' [-Werror=implicit-function-declaration]
INIT_COMPLETION(cdata->async.result->completion);
[1] https://github.com/torvalds/linux/commit/c32f74ab2872994bc8336ed367313da3139350ca
[2] https://github.com/torvalds/linux/commit/62026aedaacedbe1ffe94a3599ad4acd8ecdf587
Signed-off-by: Cosmin Paraschiv <cosmin.paraschiv@freescale.com>
Reviewed-by: Cristian Stoica <cristian.stoica@freescale.com>
Tested-by: Cristian Stoica <cristian.stoica@freescale.com>
Signed-off-by: Horia Geanta <horia.geanta@freescale.com>
Signed-off-by: Phil Sutter <phil@nwl.cc>
|
|
|
|
This slows down processing but prevents failures due to the driver
refusing to operate on unaligned data.
|
|
Add check for "atmel-" HW accelerator.
Signed-off-by: Karl Hiramoto <karl@hiramoto.org>
|
|
|
|
- for completion destroy also &pcr->fcrypt_sem and session mutexes
during shutdown
Signed-off-by: Cristian Stoica <cristian.stoica@freescale.com>
|
|
Signed-off-by: Cristian Stoica <cristian.stoica@freescale.com>
|