Florian Westphal wrote:
> Indeed. Setting net.netfilter.nf_conntrack_default_on=0 cuts time
> cleanup time by 2/3 ...
>
> nf unregister is way too happy to issue synchronize_net(), I'll work on
> a fix.
I'll test this patch as a start. Maybe we can also leverage exit_batch
more on netfilter si
On Thu, 20 Apr 2017, Mehmet Kayaalp wrote:
> > On Apr 20, 2017, at 7:13 PM, Henrique de Moraes Holschuh
> > wrote:
> > On Thu, 20 Apr 2017, Mehmet Kayaalp wrote:
> >> Include a random filled binary in vmlinux at the space reserved with
> >> CONFIG_SYSTEM_EXTRA_CERTIFICATE. This results in an unco
On 21/04/17 22:36, David Miller wrote:
> From: Nikolay Aleksandrov
> Date: Fri, 21 Apr 2017 21:30:42 +0300
>
>> On 21/04/17 20:42, Nikolay Aleksandrov wrote:
>>> Andrey Konovalov reported a BUG caused by the ip6mr code which is caused
>>> because we call unregister_netdevice_many for a device tha
Dne 21.4.2017 v 21:36 Masahiro Yamada napsal(a):
> Since Kbuild runs in the objtree, __FILE__ can be a very long path
> depending of $(srctree).
>
> Commit 9da0763bdd82 ("kbuild: Use relative path when building in a
> subdir of the source tree") made the situation better for cases
> where objtree
Hi Masahiro,
El Fri, Apr 21, 2017 at 02:02:46PM +0900 Masahiro Yamada ha dit:
> 2017-04-05 2:27 GMT+09:00 Matthias Kaehlcke :
> > From: VinÃcius Tinti
> >
> > Add rules to kbuild in order to generate LLVM bitcode files with the .ll
> > extension when using clang.
>
>
> First, I'd like to be su
Hi Elena,
On Fri, Apr 21, 2017 at 10:55:29AM +, Reshetova, Elena wrote:
> >
> > At the very least, what is there now could probably be made about twice as
> > fast
> > by removing the checks that don't actually help mitigate refcount overflow
> > bugs,
> > specifically all the checks in ref
On Fri, 2017-04-21 at 21:21 +0200, SF Markus Elfring wrote:
> > I don't think this patch series falls in either category
>
> I find that my update suggestion touches some aspects for the desired
> source code quality, doesn't it?
No.
Bart.
1) Don't race in IPSEC dumps, from Yuejie Shi.
2) Verify lengths properly in IPSEC reqeusts, from Herbert Xu.
3) Fix out of bounds access in ipv6 segment routing code, from David
Lebrun.
4) Don't write into the header of cloned SKBs in smsc95xx driver, from
James Hughes.
5) Several other
On 21/04/17 22:50, Nikolay Aleksandrov wrote:
> On 21/04/17 22:36, David Miller wrote:
>> From: Nikolay Aleksandrov
>> Date: Fri, 21 Apr 2017 21:30:42 +0300
>>
>>> On 21/04/17 20:42, Nikolay Aleksandrov wrote:
Andrey Konovalov reported a BUG caused by the ip6mr code which is caused
becau
From: Nikolay Aleksandrov
Date: Fri, 21 Apr 2017 22:50:35 +0300
> On 21/04/17 22:36, David Miller wrote:
>> From: Nikolay Aleksandrov
>> Date: Fri, 21 Apr 2017 21:30:42 +0300
>>
>>> On 21/04/17 20:42, Nikolay Aleksandrov wrote:
Andrey Konovalov reported a BUG caused by the ip6mr code which
From: Nikolay Aleksandrov
Date: Fri, 21 Apr 2017 22:56:26 +0300
> On 21/04/17 22:50, Nikolay Aleksandrov wrote:
>> On 21/04/17 22:36, David Miller wrote:
>>> From: Nikolay Aleksandrov
>>> Date: Fri, 21 Apr 2017 21:30:42 +0300
>>>
On 21/04/17 20:42, Nikolay Aleksandrov wrote:
> Andrey Ko
On Thu, Apr 20, 2017 at 9:09 AM, Alan Tull wrote:
> @@ -382,7 +377,13 @@ static int fpga_region_notify_pre_apply(struct
> fpga_region *region,
> if (of_property_read_bool(nd->overlay, "encrypted-fpga-config"))
> info->flags |= FPGA_MGR_ENCRYPTED_BITSTREAM;
>
> - of_
On Sat, Apr 22, 2017 at 10:17:11AM -0700, priyalee.kushw...@intel.com wrote:
> From: Priyalee Kushwaha
>
> Most OS distribution have awk in /usr/bin not in /bin
> Without this patch, kernel-devsrc fails to build as
> runtime dependency for srcu-cbmc script /bin/awk is
> not found.
Adding Lance o
On Fri, Apr 21, 2017 at 12:55 PM, Eric Biggers wrote:
> Hi Elena,
>
> On Fri, Apr 21, 2017 at 10:55:29AM +, Reshetova, Elena wrote:
>> >
>> > At the very least, what is there now could probably be made about twice as
>> > fast
>> > by removing the checks that don't actually help mitigate refc
On Fri, Apr 21, 2017 at 10:52:29AM -0700, Linus Torvalds wrote:
> On Thu, Apr 20, 2017 at 7:30 AM, Mel Gorman
> wrote:
> >> The end result was a revert, and this is waiting in AKPMs quilt queue:
> >>
> >> http://ozlabs.org/~akpm/mmots/broken-out/revert-mm-page_alloc-only-use-per-cpu-allocator-f
Please pull
git://linux-nfs.org/~bfields/linux.git tags/nfsd-4.11-2
Fix a 4.11 regression that triggers a BUG() on an attempt to use an
unsupported NFSv4 compound op.
(Apologies for what's probably a last-minute fix. I was hoping to have
a few more ready to roll up with it, but they'll probab
On Thu, Apr 20, 2017 at 9:52 PM, Kees Cook wrote:
> On Thu, Apr 20, 2017 at 3:15 AM, Arnd Bergmann wrote:
>> On Sun, Apr 16, 2017 at 9:52 PM, Kees Cook wrote:
> The original gcc-4.3 release was in early 2008. If we decide to still
> support that, we probably want the first 10 quirks in t
On Sat, 2017-04-22 at 04:03 +0900, Masahiro Yamada wrote:
> Kbuild works in objtree, not in srctree. So, __FILE__ is prefixed
> with $(srctree)/ for out-of-tree build.
>
> It would be nice to see the same log regardless
> in-tree, or out-of-tree build.
>
> 1/2 adds a new macro KBUILD_FILE. This
I ran into this warning during randconfig testing:
drivers/staging/rtl8723bs/os_dep/rtw_proc.c: In function
'rtw_adapter_proc_deinit':
drivers/staging/rtl8723bs/os_dep/rtw_proc.c:738:25: error: unused variable
'drv_proc' [-Werror=unused-variable]
drivers/staging/rtl8723bs/os_dep/rtw_proc.c: In f
When I2C is disabled, we get a link error:
drivers/platform/built-in.o: In function `cht_int33fe_remove':
intel_cht_int33fe.c:(.text+0x8ba): undefined reference to
`i2c_unregister_device'
drivers/platform/built-in.o: In function `cht_int33fe_probe':
intel_cht_int33fe.c:(.text+0x9ec): undefined re
On 4/21/17 2:31 AM, Arnd Bergmann wrote:
On Fri, Apr 21, 2017 at 8:39 AM, santosh.shilim...@oracle.com
wrote:
On 4/20/17 10:53 PM, Arnd Bergmann wrote:
On Fri, Apr 21, 2017 at 2:54 AM, Stephen Rothwell
wrote:
Hi all,
Today's linux-next merge of the pm tree got a conflict in:
include/
On Fri, Apr 21, 2017 at 1:55 PM, Arnd Bergmann wrote:
> On Thu, Apr 20, 2017 at 9:52 PM, Kees Cook wrote:
>> On Thu, Apr 20, 2017 at 3:15 AM, Arnd Bergmann wrote:
>>> On Sun, Apr 16, 2017 at 9:52 PM, Kees Cook wrote:
>> The original gcc-4.3 release was in early 2008. If we decide to still
>
On 4/20/2017 12:29 PM, matthew.gerl...@linux.intel.com wrote:
On Thu, 20 Apr 2017, Anatolij Gustschin wrote:
Add FPGA manager driver for loading Arria/Cyclone/Stratix
FPGAs via CvP.
Signed-off-by: Anatolij Gustschin
---
Hi Anatolij,
Since you say the driver works with Arria-10, I though
While this may appear as a humdrum one line change, it's actually quite
important. An sk_buff stores data in three places:
1. A linear chunk of allocated memory in skb->data. This is the easiest
one to work with, but it precludes using scatterdata since the memory
must be linear.
2. The arra
On Fri, 2017-04-21 at 13:22 -0700, Kees Cook wrote:
> On Fri, Apr 21, 2017 at 12:55 PM, Eric Biggers
> wrote:
> > > > Of course, having extra checks behind a debug option is fine.
> > > > But they should not be part of the base feature; the base
> > > > feature should just be mitigation of ref
On Friday, April 21, 2017 05:46:45 PM Andy Shevchenko wrote:
> Recently introduced helpers take pointers to uuid_{be|le} instead of
> reference.
>
> Using them makes code less ugly.
>
> Cc: "Rafael J. Wysocki"
> Signed-off-by: Andy Shevchenko
> ---
> drivers/acpi/acpi_extlog.c | 2 +-
> driver
On Fri, Apr 21, 2017 at 2:27 PM, James Bottomley
wrote:
> On Fri, 2017-04-21 at 13:22 -0700, Kees Cook wrote:
>> On Fri, Apr 21, 2017 at 12:55 PM, Eric Biggers
>> wrote:
>> > > > Of course, having extra checks behind a debug option is fine.
>> > > > But they should not be part of the base featur
The biggest change is the rewrite of the function probe trigger code.
I need to make a few enhancements on that code and it was basically
created with a hack on top of an hack, and I didn't want to add more
hacks. Instead, I gutted it and rewrote it in a way that the patch series
is still bisectabl
From: "Steven Rostedt (VMware)"
The trace_event benchmark thread runs in kernel space in an infinite loop
while also calling cond_resched() in case anything else wants to schedule
in. Unfortunately, on a PREEMPT kernel, that makes it a nop, in which case,
this will never voluntarily schedule. Tha
From: Namhyung Kim
The function-fork option is same as event-fork that it tracks task
fork/exit and set the pid filter properly. This can be useful if user
wants to trace selected tasks including their children only.
Link: http://lkml.kernel.org/r/20170417024430.21194-3-namhy...@kernel.org
Sig
From: "Steven Rostedt (VMware)"
Modify the snapshot probe trigger to work with instances. This way the
snapshot function trigger will only affect the instance that it is added to
in the set_ftrace_filter file.
Signed-off-by: Steven Rostedt (VMware)
---
kernel/trace/trace.c | 44 +++
From: "Steven Rostedt (VMware)"
Nothing calls unregister_ftrace_function_probe(). Remove it as well as the
flag PROBE_TEST_DATA, as this function was the only one to set it.
Signed-off-by: Steven Rostedt (VMware)
---
kernel/trace/ftrace.c | 18 +++---
kernel/trace/trace.h | 3 ---
From: "Steven Rostedt (VMware)"
In order to eventually have each trace_array instance have its own unique
set of function probes (triggers), the trace array needs to hold the ops and
the filters for the probes.
This is the first step to accomplish this. Instead of having the private
data of the
From: "Steven Rostedt (VMware)"
Nothing uses "flags" in the ftrace_func_probe descriptor. Remove it.
Signed-off-by: Steven Rostedt (VMware)
---
kernel/trace/ftrace.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c
index b5ce7ea67e02..b6dc29583c8
From: "Steven Rostedt (VMware)"
As nothing outside the tracing directory uses the function probes mechanism,
I'm moving the prototypes out of the include/linux/ftrace.h and into the
local kernel/trace/trace.h header. I plan on making them hook to the
trace_array structure which is local to kernel
From: "Steven Rostedt (VMware)"
As the data pointer for individual ips will soon be removed and no longer
passed to the callback function probe handlers, convert the rest of the function
trigger counters over to the new ftrace_func_mapper helper functions.
Signed-off-by: Steven Rostedt (VMware)
Hi,
> > My personal opinion is that formats in drm_fourcc.h should be
> > independent of the CPU byte order and the function
> > drm_mode_legacy_fb_format() and drivers depending on that incorrect
> > assumption be fixed instead.
>
> The problem is this isn't a kernel-internal thing any more
From: "Steven Rostedt (VMware)"
The processes of updating a ops filter_hash is a bit complex, and requires
setting up an old hash to perform the update. This is done exactly the same
in two locations for the same reasons. Create a helper function that does it
in one place.
Signed-off-by: Steven
From: "Steven Rostedt (VMware)"
No users of the function probes uses the data field anymore. Remove it, and
change the init function to take a void *data parameter instead of a
void **data, because the init will just get the data that the registering
function was received, and there's no state af
From: "Steven Rostedt (VMware)"
None of the probe users uses the data field anymore of the entry. They all
have their own print() function. Remove showing the data field in the
generic function as the data field will be going away.
Signed-off-by: Steven Rostedt (VMware)
---
kernel/trace/ftrace
From: "Steven Rostedt (VMware)"
With the redesign of the registration and execution of the function probes
(triggers), data can now be passed from the setup of the probe to the probe
callers that are specific to the trace_array it is on. Although, all probes
still only affect the toplevel trace a
From: "Steven Rostedt (VMware)"
Have the traceon/off function probe triggers affect only the instance they
are set in. This required making the trace_on/off accessible for other files
in the tracing directory.
Signed-off-by: Steven Rostedt (VMware)
---
kernel/trace/trace.c | 4 ++--
From: "Steven Rostedt (VMware)"
As the data pointer for individual ips will soon be removed and no longer
passed to the callback function probe handlers, convert the snapshot
trigger counter over to the new ftrace_func_mapper helper functions.
Signed-off-by: Steven Rostedt (VMware)
---
kernel/
From: "Steven Rostedt (VMware)"
Add a link list to the trace_array to hold func probes that are registered.
Currently, all function probes are the same for all instances as it was
before, that is, only the top level trace_array holds the function probes.
But this lays the ground work to have func
From: "Steven Rostedt (VMware)"
In order to move the ops to the function probes directly, they need a way to
map function ips to their own data without depending on the infrastructure
of the function probes, as the data field will be going away.
New helper functions are added that are based on t
From: "Steven Rostedt (VMware)"
Have the stacktrace function trigger probe trigger stack traces within the
instance that they were added to in the set_ftrace_filter.
># cd /sys/kernel/debug/tracing
># mkdir instances/foo
># cd instances/foo
># echo schedule:stacktrace:1 > set_ftrace_filter
From: "Steven Rostedt (VMware)"
Now that the function probes have their own ftrace_ops, there's no reason to
continue using the ftrace_func_hash to find which probe to call in the
function callback. The ops that is passed in to the function callback is
part of the probe_ops to call.
Signed-off-b
On Friday, April 21, 2017 02:02:35 PM santosh.shilim...@oracle.com wrote:
>
> On 4/21/17 2:31 AM, Arnd Bergmann wrote:
> > On Fri, Apr 21, 2017 at 8:39 AM, santosh.shilim...@oracle.com
> > wrote:
> >> On 4/20/17 10:53 PM, Arnd Bergmann wrote:
> >>>
> >>> On Fri, Apr 21, 2017 at 2:54 AM, Stephen R
From: "Steven Rostedt (VMware)"
Pass the trace_array associated to a ftrace_probe_ops into the probe_ops
func(), init() and free() functions. The trace_array is the descriptor that
describes a tracing instance. This will help create the infrastructure that
will allow having function probes unique
From: "Steven Rostedt (VMware)"
There are no users of unregister_ftrace_function_probe_all(). The only probe
function that is used is unregister_ftrace_function_probe_func(). Rename the
internal static function __unregister_ftrace_function_probe() to
unregister_ftrace_function_probe_func() and ma
From: "Steven Rostedt (VMware)"
Have the function probes have their own ftrace_ops, and remove the
trace_probe_ops. This simplifies some of the ftrace infrastructure code.
Individual entries for each function is still allocated for the use of the
output for set_ftrace_filter, but they will be re
From: "Steven Rostedt (VMware)"
Currently unregister_ftrace_function_probe_func() is a void function. It
does not give any feedback if an error occurred or no item was found to
remove and nothing was done.
Change it to return status and success if it removed something. Also update
the callers to
From: "Steven Rostedt (VMware)"
Just writing into the set_ftrace_filter file does not reset triggers, even
though it can reset the function list. Triggers require writing the trigger
name with a "!" prepended. It's worse that it requires the number if the
trigger has a count associated to it.
Ad
From: "Steven Rostedt (VMware)"
If the ftrace_hash_move_and_update_ops() fails, and an ops->free() function
exists, then it needs to be called on all the ops that were added by this
registration.
Signed-off-by: Steven Rostedt (VMware)
---
kernel/trace/ftrace.c | 16 +++-
1 file cha
On Thu, 2017-04-13 at 13:31 +0200, Borislav Petkov wrote:
> On Thu, Apr 13, 2017 at 12:29:25AM +0200, Borislav Petkov wrote:
> > On Wed, Apr 12, 2017 at 03:26:19PM -0700, Luck, Tony wrote:
> > > We can futz with that and have them specify which chain (or both)
> > > that they want to be added to.
>
From: "Steven Rostedt (VMware)"
Pass around the local trace_array that is the descriptor for tracing
instances, when enabling and disabling probes. This by default sets the
enable/disable of event probe triggers to work with instances.
The other probes will need some more work to get them workin
From: "Steven Rostedt (VMware)"
This adds a test to test the function tiggers traceon and traceoff to make
sure that it starts and stops tracing when a function is hit.
The test performs the following:
o Enables all events
o Writes schedule:traceoff into set_ftrace_filter
o Makes sure the
From: "Steven Rostedt (VMware)"
The set_ftrace_file lists both functions that are filtered, as well as
function probes (triggers) that are attached to a function, like traceon or
stacktrace, etc. The reading of this file is not as trivial as most pseudo
files are, and there's been various bugs th
From: "Steven Rostedt (VMware)"
In preparation to cleaning up the probe function registration code, the
"data" parameter will eventually be removed from the probe->func() call.
Instead it will receive its own "ops" function, in which it can set up its
own data that it needs to map.
Signed-off-by
On 4/21/2017 9:55 AM, Borislav Petkov wrote:
On Tue, Apr 18, 2017 at 04:17:35PM -0500, Tom Lendacky wrote:
Add support to the early boot code to use Secure Memory Encryption (SME).
Since the kernel has been loaded into memory in a decrypted state, support
is added to encrypt the kernel in place
Disable two clang warnings that generate a lot of noise.
Matthias Kaehlcke (2):
kbuild: clang: Disable 'address-of-packed-member' warning
kbuild: clang: Disable the 'duplicate-decl-specifier' warning
Makefile | 2 ++
1 file changed, 2 insertions(+)
--
2.12.2.816.g281164-goog
clang generates plenty of these warnings in different parts of the code.
They are mostly caused by container_of() and other macros which declare
a "const *" variable for their internal use which triggers a
"duplicate 'const' specifier" warning if the is already const
qualified.
Wording-mostly-fr
clang generates plenty of these warnings in different parts of the code,
to an extent that the warnings are little more than noise. Disable the
'address-of-packed-member' warning.
Signed-off-by: Matthias Kaehlcke
---
Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git a/Makefile b/Makefil
On Fri, Apr 21, 2017 at 09:19:10AM +0200, Hans de Goede wrote:
> Hi,
>
> On 20-04-17 14:51, Tobias Regnery wrote:
> > With CONFIG_I2C=m and CONFIG_INTEL_CHT_INT33FE=y we see the following link
> > errors:
> >
> > drivers/built-in.o: In function 'cht_int33fe_remove':
> > intel_cht_int33fe.c:(.text
From: "Steven Rostedt (VMware)"
When two function probes are added to set_ftrace_filter, and then one of
them is removed, the update to the function locations is not performed, and
the record keeping of the function states are corrupted, and causes an
ftrace_bug() to occur.
This is easily reprod
There is a new forward declaration for two global cftype arrays, but
that fails to build when CONFIG_CGROUPS is disabled:
In file included from /git/arm-soc/block/bfq-iosched.c:105:0:
block/bfq-iosched.h:820:22: error: array type has incomplete element type
'struct cftype'
extern struct cftype b
From: "Steven Rostedt (VMware)"
As nothing outside the tracing directory uses the function command mechanism,
I'm moving the prototypes out of the include/linux/ftrace.h and into the
local kernel/trace/trace.h header. I plan on making them hook to the
trace_array structure which is local to kerne
From: "Steven Rostedt (VMware)"
t_hash_start() does not increment *pos, where as t_next() must. But when
t_next() does increment *pos, it must still pass in the original *pos to
t_hash_start() otherwise it will skip the first instance:
# cd /sys/kernel/debug/tracing
# echo schedule:traceoff >
On Fri, Apr 21, 2017 at 11:03:13PM +0200, Arnd Bergmann wrote:
> When I2C is disabled, we get a link error:
>
> drivers/platform/built-in.o: In function `cht_int33fe_remove':
> intel_cht_int33fe.c:(.text+0x8ba): undefined reference to
> `i2c_unregister_device'
> drivers/platform/built-in.o: In fu
From: Namhyung Kim
In my virtual machine setup, running ftracetest failed on creating
LOG_DIR on a read-only filesystem. It'd be convenient to provide an
option to specify a different directory as log directory.
Link: http://lkml.kernel.org/r/20170417024430.21194-4-namhy...@kernel.org
Cc: Ingo
Serge,
Is there any change of a Signed-off-by on this patch? Otherwise I don't
think we can merge it.
Eric
"Serge E. Hallyn" writes:
> Root in a non-initial user ns cannot be trusted to write a traditional
> security.capability xattr. If it were allowed to do so, then any
> unprivileged use
From: "Steven Rostedt (VMware)"
This adds a test to enable and disable trace events via the function
triggers. It tests enabling and disabling the sched:sched_switch event via
the the event_enable and event_disable function triggers attached to the
schedule() kernel function.
The test does the f
The #ifdef is slightly wrong as it doesn't cover the xhci_priv_resume_quirk()
function, causing a harmless warning:
drivers/usb/host/xhci-plat.c:58:12: error: 'xhci_priv_resume_quirk' defined but
not used [-Werror=unused-function]
static int xhci_priv_resume_quirk(struct usb_hcd *hcd)
A simpler
On Fri, Apr 21, 2017 at 11:02 PM, santosh.shilim...@oracle.com
wrote:
> On 4/21/17 2:31 AM, Arnd Bergmann wrote:
>>
>> On Fri, Apr 21, 2017 at 8:39 AM, santosh.shilim...@oracle.com
>> wrote:
>>>
>>> On 4/20/17 10:53 PM, Arnd Bergmann wrote:
On Fri, Apr 21, 2017 at 2:54 AM, Stephen
On 4/21/2017 2:31 PM, Rafael J. Wysocki wrote:
On Friday, April 21, 2017 02:02:35 PM santosh.shilim...@oracle.com wrote:
On 4/21/17 2:31 AM, Arnd Bergmann wrote:
On Fri, Apr 21, 2017 at 8:39 AM, santosh.shilim...@oracle.com
[...]
I still see two conflicting trees in linux-next as of toda
Quoting Eric W. Biederman (ebied...@xmission.com):
>
> Serge,
>
> Is there any change of a Signed-off-by on this patch? Otherwise I don't
> think we can merge it.
For pete's sake! I'm sorry, i seem to remember with just about every
other project other than this. particular. patch.
Does this
On 04/18/2017 02:17 PM, Tom Lendacky wrote:
> @@ -55,7 +57,7 @@ static inline void copy_user_page(void *to, void *from,
> unsigned long vaddr,
> __phys_addr_symbol(__phys_reloc_hide((unsigned long)(x)))
>
> #ifndef __va
> -#define __va(x) ((void *)((unsigned
> long)(
Tested 9 distros centos, Debian, Fedora, Gentoo, Opensuse, slackware, Ubuntu,
poky showed awk at /usr/bin/awk.
Here is another similar patch which has been approved
https://patchwork.kernel.org/patch/9650581/
centos-7:
lrwxrwxrwx 1 root root 4 Mar 15 19:58 /bin/awk -> gawk lrwxrwxrwx 1 root ro
+Dave,
On 4/21/2017 2:44 PM, Arnd Bergmann wrote:
On Fri, Apr 21, 2017 at 11:02 PM, santosh.shilim...@oracle.com
wrote:
On 4/21/17 2:31 AM, Arnd Bergmann wrote:
[...]
arm-soc/next/drivers:
ae3874cc931b ARM: keystone: Drop PM domain support for k2g
52835d59fc6c soc: ti: Add ti_sci_pm_domain
On 04/18/2017 02:22 PM, Tom Lendacky wrote:
> Add sysfs support for SME so that user-space utilities (kdump, etc.) can
> determine if SME is active.
>
> A new directory will be created:
> /sys/kernel/mm/sme/
>
> And two entries within the new directory:
> /sys/kernel/mm/sme/active
> /sys/ke
When CONFIG_PM is disabled, we get a build error:
arch/arm/mach-omap2/omap-smp.c: In function 'omap4_smp_maybe_reset_cpu1':
arch/arm/mach-omap2/omap-smp.c:309:20: error: implicit declaration of function
'omap4_get_cpu1_ns_pa_addr'; did you mean 'omap4_get_scu_base'?
[-Werror=implicit-function-de
On 04/21/2017 03:41 PM, Arnd Bergmann wrote:
> There is a new forward declaration for two global cftype arrays, but
> that fails to build when CONFIG_CGROUPS is disabled:
>
> In file included from /git/arm-soc/block/bfq-iosched.c:105:0:
> block/bfq-iosched.h:820:22: error: array type has incomplet
"Serge E. Hallyn" writes:
> Quoting Eric W. Biederman (ebied...@xmission.com):
>>
>> Serge,
>>
>> Is there any change of a Signed-off-by on this patch? Otherwise I don't
>> think we can merge it.
>
> For pete's sake! I'm sorry, i seem to remember with just about every
> other project other th
On Fri, Apr 21, 2017 at 11:15 AM, Andy Lutomirski wrote:
> I was trying to figure out what how flush_tlb_current_task() would
> possibly work correctly if current->mm != current->active_mm, but I
> realized I could spare myself the effort: it has no callers except
> the unused flush_tlb() macro.
On Thu, Apr 20, 2017 at 9:24 PM, Al Viro wrote:
> On Thu, Apr 20, 2017 at 07:54:45PM +0200, Arnd Bergmann wrote:
>> kernelci.org reports a new compile warning for old code in the pmcraid
>> driver:
>>
>> arch/mips/include/asm/uaccess.h:138:21: warning: passing argument 1 of
>> '__access_ok' makes
On Fri, Apr 14, 2017 at 04:26:00PM -0700,
sathyanarayanan.kuppusw...@linux.intel.com wrote:
> From: Kuppuswamy Sathyanarayanan
>
> Currently in WCOVE PMIC mfd driver, all second level irq chips
By currently I believe you mean after the earlier patch in this series is
applied, correct? This one
On Fri, 2017-04-21 at 14:30 -0700, Kees Cook wrote:
> On Fri, Apr 21, 2017 at 2:27 PM, James Bottomley
> wrote:
> > On Fri, 2017-04-21 at 13:22 -0700, Kees Cook wrote:
> > > On Fri, Apr 21, 2017 at 12:55 PM, Eric Biggers <
> > > ebigge...@gmail.com>
> > > wrote:
> > > > > > Of course, having extra
On Fri, Apr 21, 2017 at 11:42:54PM +0200, Arnd Bergmann wrote:
> The #ifdef is slightly wrong as it doesn't cover the xhci_priv_resume_quirk()
> function, causing a harmless warning:
>
> drivers/usb/host/xhci-plat.c:58:12: error: 'xhci_priv_resume_quirk' defined
> but not used [-Werror=unused-fun
On Wednesday, April 19, 2017 12:49 PM, Lorenzo Pieralisi wrote:
>
> PCI configuration space should be mapped with a memory region type that
> generates on the CPU host bus non-posted write transations. Update the
> driver to use the devm_pci_remap_cfg* interface to make sure the correct
> memory m
As pointed out by Al Viro for my previous series, the driver has no need
to call access_ok() and __copy_from_user()/__copy_to_user(). Changing
it to regular copy_from_user()/copy_to_user() simplifies the code without
any real downsides, making it less error-prone at best.
This patch by itself also
On Fri, Apr 21, 2017 at 09:52:10PM +, Kushwaha, Priyalee wrote:
> Tested 9 distros centos, Debian, Fedora, Gentoo, Opensuse, slackware, Ubuntu,
> poky showed awk at /usr/bin/awk.
>
> Here is another similar patch which has been approved
> https://patchwork.kernel.org/patch/9650581/
>
> cen
This patch ports the x86-specific atomic overflow handling from PaX's
PAX_REFCOUNT to the upstream refcount_t API. This is an updated version
from PaX that eliminates the saturation race condition by resetting the
atomic counter back to the INT_MAX saturation value on both overflow and
underflow. T
On Wed, Apr 19, 2017 at 4:10 PM, Vladimir Murzin
wrote:
> On 19/04/17 11:02, Arnd Bergmann wrote:
>> Can you either modify the description to explain why we now need this on
>> all ARMv7M, or add a '|| CPU_V7M' for the 'bool' line to make it optional?
>>
>> Would it be better to leave the default
I don't think the patch is correct, so I haven't bothered signing off on
it. Probably the & is not correct in the IS_ERR call?
julia
-- Forwarded message --
Date: Sat, 22 Apr 2017 06:09:26 +0800
From: kbuild test robot
To: kbu...@01.org
Cc: Julia Lawall
Subject: [PATCH] ASoC: f
From: Guenter Roeck
The port controller interface driver interconnects the Type-C Port
Manager with a Type-C Port Controller Interface (TCPCI) compliant
port controller.
Signed-off-by: Guenter Roeck
Signed-off-by: Guenter Roeck
---
v5:
- API changes
[set_pd_header -> set_roles]
v4:
- Fix RP
From: Guenter Roeck
This driver implements the USB Type-C Power Delivery state machine
for both source and sink ports. Alternate mode support is not
fully implemented.
The driver attaches to the USB Type-C class code implemented in
the following patches.
usb: typec: add driver for Intel
* Arnd Bergmann [170421 14:59]:
> When CONFIG_PM is disabled, we get a build error:
>
> arch/arm/mach-omap2/omap-smp.c: In function 'omap4_smp_maybe_reset_cpu1':
> arch/arm/mach-omap2/omap-smp.c:309:20: error: implicit declaration of
> function 'omap4_get_cpu1_ns_pa_addr'; did you mean 'omap4_ge
On Fri, 21 Apr 2017 09:53:34 -0400
Steven Rostedt wrote:
> On Fri, 21 Apr 2017 19:00:25 +0900
> Masami Hiramatsu wrote:
>
> > On Fri, 21 Apr 2017 18:36:17 +0900
> > Masami Hiramatsu wrote:
> >
> > > On Thu, 20 Apr 2017 13:30:34 -0400
> > > Steven Rostedt wrote:
> > > >
> > > > An tracing
GED driver is currently set up as a platform driver. On modern operating
systems, most of the drivers are compiled as kernel modules. It is possible
that a GED interrupt event is received and the driver such as GHES/GPIO/I2C
to service it is not available yet. To accommodate this use case, delay
GE
On Thu, Apr 20, 2017 at 11:27 PM, Jessica Yu wrote:
> +++ Kees Cook [12/04/17 16:16 -0700]:
>
>> Accessing the mod structure (e.g. for mod->name) prior to having completed
>> check_modstruct_version() can result in writing garbage to the error logs
>> if the layout of the mod structure loaded from
601 - 700 of 845 matches
Mail list logo
