Re: [PATCH] CPU Jitter RNG: inclusion into kernel crypto API and /dev/random

Am Samstag, 2. November 2013, 12:01:13 schrieb Pavel Machek: Hi Pavel, >Hi! > >> >sense of where the unpredictability might be coming from, and >> >whether >> >the unpredictability is coming from something which is fundamentally >> >arising from something which is chaotic or quantum effect, or ju

[PATCH] ARM: S3C24XX: remove unused Kconfig parameter

This removes the MACH_S3C2413 Kconfig parameter, which was no longer used anywhere in the source code and Makefiles. Signed-off-by: Michael Opdenacker --- arch/arm/mach-s3c24xx/Kconfig | 7 --- 1 file changed, 7 deletions(-) diff --git a/arch/arm/mach-s3c24xx/Kconfig b/arch/arm/mach-s3c24xx

RE: mei: cancel stall timers in mei_reset

> -Original Message- > From: Eugene Shatokhin [mailto:eugene.shatok...@rosalab.ru] > Sent: Friday, November 01, 2013 14:27 > To: Winkler, Tomas > Cc: Usyskin, Alexander; Nicolò Costanza; Alex Burmashev; LKML > Subject: Re: mei: cancel stall timers in mei_reset > > Hi, > > In case my pre

Re: [PATCH] Staging: ft1000: fixed coding style issues

Dan Carpenter wrote: > On Sat, Nov 02, 2013 at 11:18:20PM +0200, Aldo Iljazi wrote: > > Aldo Iljazi wrote: > > > > > Fixed a few coding style issues that checkpatch reported. > > > > > > Specifically: > > > > > > 1. line over 80 characters issue on the lines 9 and 10. > > > 2. space prohibite

Re: [PATCH 1/2] ipc, msg: fix message length check for negative values

On 3 November 2013 01:35, Linus Torvalds wrote: > On Sat, Nov 2, 2013 at 2:26 PM, Mathias Krause wrote: >> On 64 bit systems the test for negative message sizes is bogus as the >> size, which may be positive when evaluated as a long, will get truncated >> to an int when passed to load_msg(). > >

[PATCH 1/2] ARM: sun6i: dt: Add IP needed to bring up the additional cores

Add the PRCM and CPU configuration units needed for SMP in the A31 DTSI. Signed-off-by: Maxime Ripard --- arch/arm/boot/dts/sun6i-a31.dtsi | 10 ++ 1 file changed, 10 insertions(+) diff --git a/arch/arm/boot/dts/sun6i-a31.dtsi b/arch/arm/boot/dts/sun6i-a31.dtsi index c1751a64889a..a0646

[PATCH 2/2] ARM: sun6i: Add SMP support for the Allwinner A31

The A31 is a quad Cortex-A7. Add the logic to use the IPs used to control the CPU configuration and the CPU power so that we can bring up secondary CPUs at boot. Signed-off-by: Maxime Ripard --- arch/arm/mach-sunxi/Makefile | 1 + arch/arm/mach-sunxi/common.h | 19 +++ arch/arm/mach-sun

[PATCH 0/2] Add SMP support for the Allwinner A31 SoCs

Hi everyone, The Allwinner A31 is a quad-Cortex-A7 SoC. This patchset adds support for the bringup of the others CPUs at startup. Thanks, Maxime Maxime Ripard (2): ARM: sun6i: dt: Add IP needed to bring up the additional cores ARM: sun6i: Add SMP support for the Allwinner A31 arch/arm/boot

Re: [PATCH] mm: cache largest vma

* Davidlohr Bueso wrote: > On Fri, 2013-11-01 at 16:38 -0400, KOSAKI Motohiro wrote: > > (11/1/13 4:17 PM), Davidlohr Bueso wrote: > > > > > While caching the last used vma already does a nice job avoiding > > > having to iterate the rbtree in find_vma, we can improve. After > > > studying the

[PATCHSET driver-core-next] sysfs: separate out kernfs, take #2

Hello, guys. (This is for 3.14-rc1. Posting early for review. Will refresh and repost once the next driver-core-next opens.) This is the second take of the patchset to separate out kernfs from sysfs. Changes from the last take[L] are, * Patches applied to driver-core-next are dropped and the

[PATCH 02/39] sysfs, kernfs: add skeletons for kernfs

Core sysfs implementation will be separated into kernfs so that it can be used by other non-kobject users. This patch creates fs/kernfs/ directory and makes boilerplate changes. kernfs interface will be directly based on sysfs_dirent and its forward declaration is moved to include/linux/kernfs.h w

[PATCH 07/39] sysfs, kernfs: replace sysfs_dirent->s_dir.kobj and ->s_attr.[bin_]attr with ->priv

A directory sysfs_dirent points to the associated kobj. A regular or bin file points to the associated [bin_]attribute. This patch replaces sysfs_dirent->s_dir.kobj and ->s_attr.[bin_]attr with void * ->priv. This is to prepare for kernfs interface so that sysfs can specify the private data in t

[PATCH 08/39] sysfs, kernfs: introduce kernfs_create_dir[_ns]()

Introduce kernfs interface to create a directory which takes and returns sysfs_dirents. create_dir() is renamed to kernfs_create_dir_ns() and its argumantes and return value are updated. create_dir() usages are replaced with kernfs_create_dir_ns() and sysfs_create_subdir() usages are replaced wit

[PATCH 36/39] sysfs, kernfs: prepare mount path for kernfs

We're in the process of separating out core sysfs functionality into kernfs which will deal with sysfs_dirents directly. This patch rearranges mount path so that the kernfs and sysfs parts are separate. * As sysfs_super_info won't be visible outside kernfs proper, kernfs_super_ns() is added to

[PATCH 37/39] sysfs, kernfs: move mount core code to fs/kernfs/mount.c

Move core mount code to fs/kernfs/mount.c. The respective declarations in fs/sysfs/sysfs.h are moved to fs/kernfs/kernfs-internal.h. This is pure relocation. Signed-off-by: Tejun Heo --- fs/kernfs/kernfs-internal.h | 22 +++ fs/kernfs/mount.c | 156 ++

[PATCH 32/39] sysfs, kernfs: introduce sysfs_root_sd

Currently, it's assumed that there's a single kernfs hierarchy in the system anchored at sysfs_root which is defined as a global struct. To allow other users of kernfs, this will be made dynamic. Introduce a new global variable sysfs_root_sd which points to &sysfs_root and convert all &sysfs_root

[PATCH 39/39] sysfs, kernfs: remove cross inclusions of internal headers

fs/kernfs/kernfs-internal.h needed to include fs/sysfs/sysfs.h because part of kernfs core implementation was living in sysfs. fs/sysfs/sysfs.h needed to include fs/kernfs/kernfs-internal.h because include/linux/kernfs.h didn't expose enough interface. The separation is complete and neither is tr

[PATCH 38/39] sysfs, kernfs: make sysfs_dirent definition public

sysfs_dirent includes some information which should be available to kernfs users - the type, name and parent pointer. This patch moves sysfs_dirent definition from kernfs/kernfs-internal.h to include/linux/kernfs.h so that kernfs users can access them. The type part of flags is exported as enum k

[PATCH 31/39] sysfs, kernfs: no need to kern_mount() sysfs from sysfs_init()

It has been very long since sysfs depended on vfs to keep track of internal states and whether sysfs is mounted or not doesn't make any difference to sysfs's internal operation. In addition to init and filesystem type registration, sysfs_init() invokes kern_mount() to create in-kernel mount of sys

[PATCH 13/39] sysfs, kernfs: move sysfs_open_file to include/linux/kernfs.h

sysfs_open_file will be used as the primary handle for kernfs methods. Move its definition from fs/sysfs/file.c to include/linux/kernfs.h and mark the public and private fields. This is pure relocation. Signed-off-by: Tejun Heo --- fs/sysfs/file.c| 11 --- include/linux/kernfs.h

[PATCH 34/39] sysfs, kernfs: make inode number ida per kernfs_root

kernfs is being updated to allow multiple sysfs_dirent hierarchies so that it can also be used by other users. Currently, inode number is allocated using a global ida, sysfs_ino_ida; however, inos for different hierarchies should be handled separately. This patch makes ino allocation per kernfs_r

[PATCH 33/39] sysfs, kernfs: implement kernfs_create/destroy_root()

There currently is single kernfs hierarchy in the whole system which is used for sysfs. kernfs needs to support multiple hierarchies to allow other users. This patch introduces struct kernfs_root which serves as the root of each kernfs hierarchy and implements kernfs_create/destroy_root(). * Eac

[PATCH 30/39] sysfs, kernfs: make sysfs_super_info->ns const

Add const qualifier to sysfs_super_info->ns so that it's consistent with other namespace tag usages in sysfs. Because kobject doesn't use const qualifier for namespace tags, this ends up requiring an explicit cast to drop const qualifier in free_sysfs_super_info(). Signed-off-by: Tejun Heo ---

[PATCH 35/39] sysfs, kernfs: make super_blocks bind to different kernfs_roots

kernfs is being updated to allow multiple sysfs_dirent hierarchies so that it can also be used by other users. Currently, sysfs super_blocks are always attached to one kernfs_root - sysfs_root - and distinguished only by their namespace tags. This patch adds sysfs_super_info->root and update sysf

[PATCH 12/39] sysfs, kernfs: prepare open, release, poll paths for kernfs

We're in the process of separating out core sysfs functionality into kernfs which will deal with sysfs_dirents directly. This patch prepares the rest - open, release and poll. There isn't much to do. Just renaming is enough. As sysfs_file_operations and sysfs_bin_operations are identical now, us

[PATCH 29/39] sysfs, kernfs: drop unused params from sysfs_fill_super()

sysfs_fill_super() takes three params - @sb, @data and @silent - but uses only @sb. Drop the latter two. Signed-off-by: Tejun Heo --- fs/sysfs/mount.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fs/sysfs/mount.c b/fs/sysfs/mount.c index 852d115..21070c2 100644 --- a/

[PATCH 28/39] sysfs, kernfs: move symlink core code to fs/kernfs/symlink.c

Move core symlink code to fs/kernfs/symlink.c. fs/sysfs/symlink.c now only contains sysfs wrappers around kernfs interfaces. The respective declarations in fs/sysfs/sysfs.h are moved to fs/kernfs/kernfs-internal.h. This is pure relocation. Signed-off-by: Tejun Heo --- fs/kernfs/kernfs-interna

[PATCH 11/39] sysfs, kernfs: prepare mmap path for kernfs

We're in the process of separating out core sysfs functionality into kernfs which will deal with sysfs_dirents directly. This patch rearranges mmap path so that the kernfs and sysfs parts are separate. sysfs_kf_bin_mmap() which handles the interaction with bin_attribute mmap method is factored ou

[PATCH 27/39] sysfs, kernfs: move file core code to fs/kernfs/file.c

Move core file code to fs/kernfs/file.c. fs/sysfs/file.c now contains sysfs kernfs_ops callbacks, sysfs wrappers around kernfs interfaces, and sysfs_schedule_callback(). The respective declarations in fs/sysfs/sysfs.h are moved to fs/kernfs/kernfs-internal.h. This is pure relocation. v2: Refres

[PATCH 10/39] sysfs, kernfs: prepare write path for kernfs

We're in the process of separating out core sysfs functionality into kernfs which will deal with sysfs_dirents directly. This patch rearranges write path so that the kernfs and sysfs parts are separate. kernfs_file_write() handles all boilerplate work including buffer management and locking and i

[PATCH 23/39] sysfs, kernfs: introduce kernfs[_find_and]_get() and kernfs_put()

Introduce kernfs interface for finding, getting and putting sysfs_dirents. * sysfs_find_dirent() is renamed to kernfs_find_ns() and lockdep assertion for sysfs_mutex is added. * sysfs_get_dirent_ns() is renamed to kernfs_find_and_get(). * Macro inline dancing around __sysfs_get/put() are remov

[PATCH 09/39] sysfs, kernfs: prepare read path for kernfs

We're in the process of separating out core sysfs functionality into kernfs which will deal with sysfs_dirents directly. This patch rearranges read path so that the kernfs and sysfs parts are separate. * Regular file read path is refactored such that kernfs_seq_start/next/stop/show() handle all

[PATCH 24/39] sysfs, kernfs: move internal decls to fs/kernfs/kernfs-internal.h

Move data structure, constant and basic accessor declarations from fs/sysfs/sysfs.h to fs/kernfs/kernfs-internal.h. The two files currently include each other. Once kernfs / sysfs separation is complete, the cross inclusions will be removed. Inclusion protectors are added to fs/sysfs/sysfs.h to

[PATCH 26/39] sysfs, kernfs: move dir core code to fs/kernfs/dir.c

Move core dir code to fs/kernfs/dir.c. fs/sysfs/dir.c now only contains sysfs_warn_dup() and sysfs wrappers around kernfs interfaces. The respective declarations in fs/sysfs/sysfs.h are moved to fs/kernfs/kernfs-internal.h. This is pure relocation. v2: sysfs_symlink_target_lock was mistakenly re

[PATCH 25/39] sysfs, kernfs: move inode code to fs/kernfs/inode.c

There's nothing sysfs-specific in fs/sysfs/inode.c. Move everything in it to fs/kernfs/inode.c. The respective declarations in fs/sysfs/sysfs.h are moved to fs/kernfs/kernfs-internal.h. This is pure relocation. Signed-off-by: Tejun Heo --- fs/kernfs/inode.c | 327 +++

[PATCH 20/39] sysfs, kernfs: introduce kernfs_notify()

Introduce kernfs interface to wake up poll(2) which takes and returns sysfs_dirents. sysfs_notify_dirent() is renamed to kernfs_notify() and sysfs_notify() is updated so that it doesn't directly grab sysfs_mutex but acquires the target sysfs_dirents using sysfs_get_dirent(). sysfs_notify_dirent()

[PATCH 05/39] sysfs, kernfs: introduce kernfs_rename[_ns]()

Introduce kernfs rename interface, krenfs_rename[_ns](). This is just rename of sysfs_rename(). No functional changes. Function comment is added to kernfs_rename_ns() and @new_parent_sd is renamed to @new_parent for consistency with other kernfs interfaces. v2: Dummy implementation for !CONFIG_S

[PATCH 06/39] sysfs, kernfs: introduce kernfs_setattr()

Introduce kernfs setattr interface - kernfs_setattr(). sysfs_sd_setattr() is renamed to __kernfs_setattr() and kernfs_setattr() is a simple wrapper around it with sysfs_mutex locking. sysfs_chmod_file() is updated to get an explicit ref on kobj->sd and then invoke kernfs_setattr() so that it does

[PATCH 21/39] sysfs, kernfs: reorganize SYSFS_* constants

We want to add one more SYSFS_FLAG_* but we can't use the next higher bit, 0x1, as the flag field is 16bits wide. The flags are currently arranged weirdly - 8 bits are set aside for the type flags when there are only three three used, the first flag starts at 0x1000 instead of 0x0100 and flag

[PATCH 22/39] sysfs, kernfs: revamp sysfs_dirent active_ref lockdep annotation

Currently, sysfs_dirent active_ref lockdep annotation uses attribute->[s]key as the lockdep key, which forces kernfs_create_file_ns() to assume that sysfs_dirent->priv is pointing to a struct attribute which may not be true for non-sysfs users. This patch restructures the lockdep annotation such t

[PATCH 19/39] sysfs, kernfs: add kernfs_ops->seq_{start|next|stop}()

kernfs_ops currently only supports single_open() behavior which is pretty restrictive. Add optional callbacks ->seq_{start|next|stop}() which, when implemented, are invoked for seq_file traversal. This allows full seq_file functionality for kernfs users. This currently doesn't have any user and

[PATCH 03/39] sysfs, kernfs: introduce kernfs_remove[_by_name[_ns]]()

Introduce kernfs removal interfaces - kernfs_remove() and kernfs_remove_by_name[_ns](). These are just renames of sysfs_remove() and sysfs_hash_and_remove(). No functional changes. v2: Dummy kernfs_remove_by_name_ns() for !CONFIG_SYSFS updated to return -ENOSYS instead of 0. Signed-off-by: T

[PATCH 18/39] sysfs, kernfs: remove sysfs_add_one()

sysfs_add_one() is a wrapper around __sysfs_add_one() which prints out duplicate name warning if __sysfs_add_one() fails with -EEXIST. The previous kernfs conversions moved all dup warnings to sysfs interface functions and sysfs_add_one() doesn't have any user left. Remove sysfs_add_one() and upd

[PATCH 04/39] sysfs, kernfs: introduce kernfs_create_link()

Separate out kernfs symlink interface - kernfs_create_link() - which takes and returns sysfs_dirents, from sysfs_do_create_link_sd(). sysfs_do_create_link_sd() now just determines the parent and target sysfs_dirents and invokes the new interface and handles dup warning. This patch doesn't introduc

[PATCH 17/39] sysfs, kernfs: introduce kernfs_create_file[_ns]()

Introduce kernfs interface to create a file which takes and returns sysfs_dirents. The actual file creation part is separated out from sysfs_add_file_mode_ns() into kernfs_create_file_ns(). The former now only decides the kernfs_ops to use and the file's size and invokes the latter. This patch d

[PATCH 16/39] sysfs, kernfs: remove SYSFS_KOBJ_BIN_ATTR

After kernfs_ops and sysfs_dirent->s_attr.size addition, the distinction between SYSFS_KOBJ_BIN_ATTR and SYSFS_KOBJ_ATTR is only necessary while creating files to decide which kernfs_ops to use. Afterwards, they behave exactly the same. This patch removes SYSFS_KOBJ_BIN_ATTR along with sysfs_is_bi

[PATCH 14/39] sysfs, kernfs: introduce kernfs_ops

We're in the process of separating out core sysfs functionality into kernfs which will deal with sysfs_dirents directly. This patch introduces kernfs_ops which hosts methods kernfs users implement and updates fs/sysfs/file.c such that sysfs_kf_*() functions populate kernfs_ops and kernfs_file_*()

[PATCH 15/39] sysfs, kernfs: add sysfs_dirent->s_attr.size

sysfs sets the size of regular files unconditionally at PAGE_SIZE and takes the size of bin files from bin_attribute. The latter is a pretty bad interface which forces bin_attribute users to create a separate copy of bin_attribute for each instance of the file - e.g. pci resource files. Add sysfs

[PATCH 01/39] sysfs: make __sysfs_add_one() fail if the parent isn't a directory

Currently the kobject based interface guarantees that a parent sysfs_dirent is always a directory; however, the planned kernfs interface will be directly based on sysfs_dirents and the caller may specify non-directory node as the parent. Add an explicit check in __sysfs_add_one() so that such atte

Re: [PATCH] mm: cache largest vma

* Davidlohr Bueso wrote: > While caching the last used vma already does a nice job avoiding > having to iterate the rbtree in find_vma, we can improve. After > studying the hit rate on a load of workloads and environments, > it was seen that it was around 45-50% - constant for a standard > deskt

Re: [PATCH] x86: Allow NR_CPUS=1024

* Josh Boyer wrote: > The current range for SMP configs is 2 - 512, or a full 4096 in the case > of MAXSMP. There are machines that have 1024 CPUs in them today and > configuring a kernel for that means you are forced to set MAXSMP. This > adds additional unnecessary overhead. While that o

[tip:x86/mce] dmi: Avoid unaligned memory access in save_mem_devices()

Commit-ID: 0841c04d65937ad2808f59c43cb54a92473c8f0e Gitweb: http://git.kernel.org/tip/0841c04d65937ad2808f59c43cb54a92473c8f0e Author: Luck, Tony AuthorDate: Fri, 1 Nov 2013 13:59:52 -0700 Committer: Ingo Molnar CommitDate: Sun, 3 Nov 2013 10:40:12 +0100 dmi: Avoid unaligned memory acc

Re: [PATCH] x86: Allow NR_CPUS=1024

* Ingo Molnar wrote: > > * Josh Boyer wrote: > > > The current range for SMP configs is 2 - 512, or a full 4096 in the case > > of MAXSMP. There are machines that have 1024 CPUs in them today and > > configuring a kernel for that means you are forced to set MAXSMP. This > > adds addition

Re: [PATCH] Critical ARC Fix for 3.12

Added CC stable, so Greg will see it. Added commit 9c41f4eeb9d51f3ece20428d35a3ea32cf3b5622, so Greg knows what to cherry-pick. On Sat, Nov 2, 2013 at 1:17 PM, Vineet Gupta wrote: > Hi Linus, > > Sorry for this extemely late patch for 3.12 but it causes a SMP build of ARC > to panic in boot. > >

[PATCH] Makefile: fix out-of-tree builds for multiple targets with 'all'

From: "Yann E. MORIN" For out-of-tree builds, this use-case fails to build: $ make clean all This is because 'all' is filtered-out in the Makefile wrapper, since the wrapper itself has a 'all' target. The 'all' target is just the usual naming for the default target in a Makefile. In fact, t

[PATCHv2 0/2] IPC DoS fix

Hi Linus, version 2 of this series uses your approach to fix the issues by changing load_msg() and friends to use a size_t for the message length. It differs slightly from your patch to cover a few more places where the message length is evaluated in sign extension problematic expressions. Also th

[PATCHv2 1/2] ipc, msg: fix message length check for negative values

On 64 bit systems the test for negative message sizes is bogus as the size, which may be positive when evaluated as a long, will get truncated to an int when passed to load_msg(). So a long might very well contain a positive value but when truncated to an int it would become negative. That in comb

[PATCHv2 2/2] ipc, msg: forbid negative values for "msg{max,mnb,mni}"

Negative message lengths make no sense -- so don't do negative queue lenghts or identifier counts. Prevent them from getting negative. Also change the underlying data types to be unsigned to avoid harry surprises with sign extensions in cases where those variables get evaluated in unsigned express

[PATCH v2] X86: MM: Add PAT Type write-through in combination with mtrr

Revision 2: added comment in code. This patch adds the Write-through memory type in combination with mtrr. If you call ioremap_cache to request cachable memory (write-back) the function tries to set the PAT to write-back only if the mtrr setting of the requested region is also marked as Wr

[PATCH] efi earlyprintk fix

there's below one line shift problem: ACPI=0xdabfe000 ACPI 2.0=0xdabfe014 SMBIOS=0xdaa9e000 [0.00] efi: In fact check efi_y and the lfb_height should be compared at the begin of the loop of early_efi_write Signed-off-by: Dave Young --- arch/x86/platform/efi/ea

[PATCH] boot_delay return value fix

Kernel report "Malformed early option boot_delay" because it returns non-zero value. Move to 'return 0' now because there's no reason it should return 1. Signed-off-by: Dave Young --- Andrew, It's based on previous patch of changing to early_param. Feel free to fold them if you want. If need I re

Re: [PATCH v3 00/15] KVM: MMU: locklessly write-protect

Marcelo can you review it please? On Wed, Oct 23, 2013 at 09:29:18PM +0800, Xiao Guangrong wrote: > Changelog v3: > - the changes from Gleb's review: > 1) drop the patch which fixed the count of spte number in rmap since it > can not be easily fixed and it has gone after applying this patch

Re: [PATCH 10/11] EFI: Runtime services virtual mapping

On 11/01/13 at 11:25am, Dave Young wrote: > On 10/31/13 at 05:25pm, Borislav Petkov wrote: > > From: Borislav Petkov > > > > We map the EFI regions needed for runtime services non-contiguously, > > with preserved alignment on virtual addresses starting from -4G down > > for a total max space of 6

Re: [PATCH 10/11] EFI: Runtime services virtual mapping

On 11/01/13 at 12:50pm, Matt Fleming wrote: > On Fri, 01 Nov, at 11:35:08AM, Dave Young wrote: > > > The conflict is caused by missing one commit in matt's efi next tree: > > > > > > commit 700870119f49084da004ab588ea2b799689efaf7 > > > Author: Josh Boyer > > > Date: Thu Apr 18 07:51:34 2013 -0

Re: [next:master 23/358] undefined reference to `i2c_add_adapter'

Fengguang Wu, le Sun 03 Nov 2013 20:08:53 +0800, a écrit : > It's a bug fix that unveils the link errors. > >drivers/built-in.o: In function `__input_unregister_device': >input.c:(.text+0xf0e55): undefined reference to `input_led_disconnect' Ok, so the "something like this" in the patch r

Re: [PATCH] CPU Jitter RNG: inclusion into kernel crypto API and /dev/random

On Sun, Nov 03, 2013 at 08:20:34AM +0100, Stephan Mueller wrote: > Another friend of mine mentioned that he assumes the rise and fall times > of transistors varies very slightly and could be the main reason for the > jitter. I do not think that this is really the case, because our gates > that f

Re: [PATCH] fs/befs/linuxvfs.c: need signed cast for variable 'block'

On 11/03/2013 12:27 AM, Al Viro wrote: > On Sat, Nov 02, 2013 at 08:44:46AM -0700, Greg KH wrote: > >>> Oh, for me, it is not suitable to move a file system sub-directory to >>> "drivers/*/" sub-directory. And I can not find any sub-directory like >>> 'staging' under "fs" sub-directory, either. >>

Re: [next:master 23/358] undefined reference to `input_led_disconnect'

Samuel Thibault, le Sun 03 Nov 2013 13:36:21 +0100, a écrit : > So in the end it would probably be simpler to just stuff leds.c along > input.c in input.ko or built-in. CONFIG_INPUT_LEDS will thus become a > bool. I'm working on that now. Here it is. This replaces both input-route-kbd-leds-throu

[PATCH 3/4] random: printk notifications for urandom pool initialization

Print a notification to the console when the nonblocking pool is initialized. Also printk a warning when a process tries reading from /dev/urandom before it is fully initialized. Signed-off-by: "Theodore Ts'o" --- drivers/char/random.c | 12 +++- 1 file changed, 11 insertions(+), 1 dele

[PATCH 0/4] random: improve entropy pool initialization at boot time

These patches improve how /dev/random initializes its entropy pool during the kernel boot sequence. With these changes, using an x86 test kernel run under KVM, the urandom pool gets initialized before the init scripts start running, and of the kernel users of get_random_bytes(), a debugging printk

[PATCH 1/4] random: use device attach events for entropy

Some investigation from FreeBSD shows that there is entropy available from measuring the device attach times: http://lists.randombit.net/pipermail/cryptography/2013-October/005689.html This will hopefully help us more quickly initialize the entropy pools while the system is booting (which is one

[PATCH 4/4] random: don't zap entropy count in rand_initialize()

The rand_initialize() function was being run fairly late in the kernel boot sequence. This was unfortunate, since it zero'ed the entropy counters, thus throwing away credit that was accumulated earlier in the boot sequence, and it also meant that initcall functions run before rand_initialize were

[PATCH 2/4] random: make add_timer_randomness() fill the nonblocking pool first

Change add_timer_randomness() so that it directs incoming entropy to the nonblocking pool first if it hasn't been fully initialized yet. This matches the strategy we use in add_interrupt_randomness(), which allows us to push the randomness where we need it the most during when the system is first b

[PATCH] Staging: ft1000: fixed a few styling issues

Fixed a few styling issues, specifically: boot.h:30: ERROR: space prohibited before open square bracket '[' boot.h:31: ERROR: space required after that ',' (ctx:VxV) boot.h:31: ERROR: space required after that ',' (ctx:VxV) boot.h:31: ERROR: space required after that ',' (ctx:VxV) boot.h:31: ERROR

[PATCH] kernel: trace: blktrace: remove redundent memcpy() in compat_blk_trace_setup()

do_blk_trace_setup() will fully initialize 'buts.name', so can remove the related memcpy(). And also use BLKTRACE_BDEV_SIZE and ARRAY_SIZE instead of hard code number '32'. Signed-off-by: Chen Gang --- include/linux/blktrace_api.h |2 +- kernel/trace/blktrace.c |3 +-- 2 files chan

Re: [virtio-net] BUG: sleeping function called from invalid context at kernel/mutex.c:616

I noticed that this fix is still not upstreamed. Any chance to push it to Linus before the 3.12 release? > >From 01e6c3f71c202aa02e4feda169e7cc9fb24193f5 Mon Sep 17 00:00:00 2001 > From: Jason Wang > Date: Mon, 21 Oct 2013 20:39:09 +0800 > Subject: [PATCH] virtio-net: fix > > --- > drivers/net/

Re: [PATCH] x86: Allow NR_CPUS=1024

On 11/03/2013 05:18 AM, Ingo Molnar wrote: > > * Josh Boyer wrote: > >> The current range for SMP configs is 2 - 512, or a full 4096 in the case >> of MAXSMP. There are machines that have 1024 CPUs in them today and >> configuring a kernel for that means you are forced to set MAXSMP. This

Re: perf events ring buffer memory barrier on powerpc

On Sat, Nov 02, 2013 at 10:32:39AM -0700, Paul E. McKenney wrote: > On Fri, Nov 01, 2013 at 03:56:34PM +0100, Peter Zijlstra wrote: > > On Wed, Oct 30, 2013 at 11:40:15PM -0700, Paul E. McKenney wrote: > > > > Now the whole crux of the question is if we need barrier A at all, since > > > > the STOR

Re: [PATCH] watchdog: at91sam9_wdt: various fixes

Hello Guenter, Are you okay with the 3 fixes/improvements provided by this patch, and the explanation I gave regarding the reason for these changes ? If so, I will submit a new series splitting the patch and including your suggestions. Best Regards, Boris On 29/10/2013 18:22, boris brezillo

Re: [PATCH] x86: Allow NR_CPUS=1024

On Sun, Nov 03, 2013 at 09:29:16AM -0500, Prarit Bhargava wrote: > On 11/03/2013 05:18 AM, Ingo Molnar wrote: > > > > * Josh Boyer wrote: > > > >> The current range for SMP configs is 2 - 512, or a full 4096 in the case > >> of MAXSMP. There are machines that have 1024 CPUs in them today and

Re: [PATCH 1/4] random: use device attach events for entropy

On Sun, Nov 03, 2013 at 08:33:12AM -0500, Theodore Ts'o wrote: > Some investigation from FreeBSD shows that there is entropy available > from measuring the device attach times: > > http://lists.randombit.net/pipermail/cryptography/2013-October/005689.html > > This will hopefully help us more quic

Re: [PATCH] KVM: x86: fix emulation of "movzbl %bpl, %eax"

On Thu, Oct 31, 2013 at 11:05:24PM +0100, Paolo Bonzini wrote: > When I was looking at RHEL5.9's failure to start with > unrestricted_guest=0/emulate_invalid_guest_state=1, I got it working with a > slightly older tree than kvm.git. I now debugged the remaining failure, > which was introduced by c

[RFC] arch: Introduce new TSO memory barrier smp_tmb()

On Sun, Nov 03, 2013 at 06:40:17AM -0800, Paul E. McKenney wrote: > If there was an smp_tmb(), I would likely use it in rcu_assign_pointer(). Well, I'm obviously all for introducing this new barrier, for it will reduce a full mfence on x86 to a compiler barrier. And ppc can use lwsync as opposed t

Re: [PATCH v5 2/7] arm64: introduce interfaces to hotpatch kernel and module code

On 10/30/2013 08:12 AM, Will Deacon wrote: > Hi Jinag Liu, > > Sorry for the delayed review, I've been travelling. > > On Fri, Oct 18, 2013 at 04:19:56PM +0100, Jiang Liu wrote: >> From: Jiang Liu > > If I try and email you at your Huawei address, I get a bounce from the mail > server. Is that

Re: [PATCH] x86: Allow NR_CPUS=1024

On Sun, Nov 03, 2013 at 11:21:32AM +0100, Ingo Molnar wrote: > > * Ingo Molnar wrote: > > > > > * Josh Boyer wrote: > > > > > The current range for SMP configs is 2 - 512, or a full 4096 in the case > > > of MAXSMP. There are machines that have 1024 CPUs in them today and > > > configuring

A Desktop Linux idea: modulized open hardware database for the linux kernel config

Hello LKML! I am a Linux Desktop user since around 2001. Doing the math, that’s more than a decade! Having watched http://www.youtube.com/watch?v=jjRAKuis7T8 (LinuxCon 2013, Dirk Hohndel and Linus Torvalds on stage) I decided to share an idea I had to make kernel building easier for computer e

Re: A Desktop Linux idea: modulized open hardware database for the linux kernel config

andreas.thalham...@linux.com wrote: > Hello LKML! > > I am a Linux Desktop user since around 2001. Doing the math, that’s more than > a decade! > > Having watched http://www.youtube.com/watch?v=jjRAKuis7T8 (LinuxCon 2013, > Dirk > Hohndel and Linus Torvalds on stage) I decided to share an id

Re: [PATCH] watchdog: at91sam9_wdt: various fixes

On 11/03/2013 06:42 AM, boris brezillon wrote: Hello Guenter, Are you okay with the 3 fixes/improvements provided by this patch, and the explanation I gave regarding the reason for these changes ? If so, I will submit a new series splitting the patch and including your suggestions. Yes, sorr

Re: A Desktop Linux idea: modulized open hardware database for the linux kernel config

Your message from Sunday, 03rd November 2013: > andreas.thalham...@linux.com wrote: > > Hello LKML! > > > > I am a Linux Desktop user since around 2001. Doing the math, that’s more > > than a decade! > > > > Having watched http://www.youtube.com/watch?v=jjRAKuis7T8 (LinuxCon 2013, > > Dirk Hohnd

Re: perf events ring buffer memory barrier on powerpc

On Sun, Nov 03, 2013 at 02:40:17PM +, Paul E. McKenney wrote: > On Sat, Nov 02, 2013 at 10:32:39AM -0700, Paul E. McKenney wrote: > > On Fri, Nov 01, 2013 at 03:56:34PM +0100, Peter Zijlstra wrote: > > > On Wed, Oct 30, 2013 at 11:40:15PM -0700, Paul E. McKenney wrote: > > > > > Now the whole c

Re: [PATCH] kernel: trace: blktrace: remove redundent memcpy() in compat_blk_trace_setup()

A quick review of this patch looks fine to me. Although, using ARRAY_SIZE() for a character string seems to me a bit over paranoid. But I'm fine with it, as it makes sure that the string is an array and not a pointer. Jens, Can you give me an Acked-by? -- Steve On Sun, 03 Nov 2013 22:23:39 +0

Re: A Desktop Linux idea: modulized open hardware database for the linux kernel config

linux.com> writes: [cut down because of gmane's web interface quotation policy] > But hey, it was just an idea. A stupid one maybe. So thanks for answering > anyway. > Uh like any great idea, you need to show the world, how serious you are about it : do the first step and collect a few, the

Re: [PATCH] x86: Allow NR_CPUS=1024

On 11/03/2013 07:57 AM, Josh Boyer wrote: > > OK, that makes sense. So in this scenario, we could probably either: > > a) do away with MAXSMP entirely and just depend on > CONFIG_CPUMASK_OFFSTACK. > > b) make MAXSMP something even higher than 4096. Like 5120 or 6144, etc. > > Which would you

Re: [PATCH v2] X86: MM: Add PAT Type write-through in combination with mtrr

On 11/03/2013 04:02 AM, Andreas Werner wrote: > > Since marking IO Memory as cachable is not valid, WT is the > best way for caching/bursting on MMIO Devices. > Uh... WT *is* cachable... -hpa -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a m

[PATCH 0/3] watchdog: at91sam9_wdt: various fixes and improvements

Hello, This patch series fix the secs_to_ticks macro in case 0 is passed as an argument. It also rework the heartbeat calculation to increase the security margin of the watchdog reset timer, and use the min_heartbeat value instead of the calculated heartbeat value for the first watchdog reset (to

[PATCH 1/3] watchdog: at91sam9_wdt: fix secs_to_ticks

Fix the secs_to_ticks macro in case 0 is passed as an argument. Signed-off-by: Boris BREZILLON --- drivers/watchdog/at91sam9_wdt.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/watchdog/at91sam9_wdt.c b/drivers/watchdog/at91sam9_wdt.c index 9bd089e..65f4691 10064

[PATCH 2/3] watchdog: at91sam9_wdt: avoid spurious watchdog reset during init

Use the min_heartbeat value instead of the calculated heartbeat value for the first watchdog reset to avoid spurious watchdog reset. Resetting the watchdog counter during init might lead to a watchdog fault reset because the watchdog counter has to be running for at least min_heartbeat. Resetting

Re: [PATCH] watchdog: at91sam9_wdt: various fixes

On 03/11/2013 17:22, Guenter Roeck wrote: On 11/03/2013 06:42 AM, boris brezillon wrote: Hello Guenter, Are you okay with the 3 fixes/improvements provided by this patch, and the explanation I gave regarding the reason for these changes ? If so, I will submit a new series splitting the patch a

[PATCH 3/3] watchdog: at91sam9_wdt: increase security margin on watchdog counter reset

Try to reset the watchdog counter 4 or 2 times more often than actually requested, to avoid spurious watchdog reset. If this is not possible because of the min_heartbeat value, reset it at the min_heartbeat period. Signed-off-by: Boris BREZILLON --- drivers/watchdog/at91sam9_wdt.c | 25 +++

Re: [PATCH 1/3] watchdog: at91sam9_wdt: fix secs_to_ticks

On 11/03/2013 09:52 AM, Boris BREZILLON wrote: Fix the secs_to_ticks macro in case 0 is passed as an argument. Signed-off-by: Boris BREZILLON Reviewed-by: Guenter Roeck -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kern

  1   2   3   >