The functions irq_irq_err and ipu_irq_fn are identical plus/minus the
comments. Remove one.
Signed-off-by: Thomas Gleixner
Cc: Vinod Koul
Cc: Dan Williams
Cc: dmaeng...@vger.kernel.org
---
drivers/dma/ipu/ipu_irq.c | 46 --
1 file changed, 4 insert
The first patch prepares the interrupt handlers for removal of the irq
argument.
While doing that I noticed that the handler functions are
identical. Consolidate them.
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to maj
The irq argument of most interrupt flow handlers is unused or merily
used instead of a local variable. The handlers which need the irq
argument can retrieve the irq number from the irq descriptor.
Search and update was done with coccinelle and the invaluable help of
Julia Lawall.
Signed-o
On Fri, Jul 31, 2015 at 12:40:00PM -0700, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.14.49 release.
> There are 125 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me kno
> 在 2015年7月31日，22:14，Thomas Gleixner 写道：
>
>
> On Fri, 31 Jul 2015, Thomas Gleixner wrote:
>
>> On Fri, 31 Jul 2015, yalin wang wrote:
>>> it is optimised to 2 instructions ,
>>>
>>> this is my patch, hope can be merged :
>>
>> We are not exposing the internals of kthread management. Period.
On Sat, Aug 01, 2015 at 12:39:25PM +0530, Sudip Mukherjee wrote:
> On Fri, Jul 31, 2015 at 12:40:00PM -0700, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 3.14.49 release.
> > There are 125 patches in this series, all will be posted as a response
> > to this one
On Sat, 1 Aug 2015, yalin wang wrote:
> size built-in.o*
> text data bss dec hex filename
> 743937 50786 56008 850731 cfb2b built-in.o// with the
> patch
> 744069 50786 56008 850863 cfbaf built-in.o_old // with out the
> patch
Not al
On Fri, Jul 31, 2015 at 03:52:38PM -0700, Linus Torvalds wrote:
> Is that correct? Maybe, I haven't checked. And maybe it's a big bad
> bug. Regardless, it sure as hell isn't just changing the order of the
> access to those fields. That "DCACHE_ENTRY_TYPE | DCACHE_FALLTHRU"
> clearing came from __
W dniu 01.08.2015 o 03:49, Bartlomiej Zolnierkiewicz pisze:
> The new CPU clock type allows the use of generic CPUfreq driver.
> Switch Exynos4x12 to using generic cpufreq driver.
>
> Also make CPUFREQ_DT config option select Exynos thermal driver
> if Exynos platform support is enabled.
Why? I t
* Brian Gerst wrote:
> On Fri, Jul 31, 2015 at 10:04 AM, tip-bot for Brian Gerst
> wrote:
> > Commit-ID: ba3e127ec105e790eeec4034d9769e018e4a1b54
> > Gitweb:
> > http://git.kernel.org/tip/ba3e127ec105e790eeec4034d9769e018e4a1b54
> > Author: Brian Gerst
> > AuthorDate: Wed, 29 Jul 201
On Fri, Jul 31, 2015 at 12:40:42PM -0700, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.10.85 release.
> There are 89 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know
Linus,
Please pull the latest x86-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-for-linus
# HEAD: 37868fe113ff2ba814b3b4eb12df214df555f8dc x86/ldt: Make modify_ldt
synchronous
Fallout from the recent NMI fixes: make x86 LDT handling
When and What time can i Call you? Respond ASAP
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Linus,
please pull the latest irq-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
irq-urgent-for-linus
Just two updates to the maintainers file.
Thanks,
tglx
-->
Thomas Gleixner (2):
MAINTAINERS: Appoint Marc Zyngier
> 在 2015年7月31日，18:14，Will Deacon 写道：
>
> On Fri, Jul 31, 2015 at 10:33:55AM +0100, Peter Zijlstra wrote:
>> On Fri, Jul 31, 2015 at 05:25:02PM +0800, yalin wang wrote:
On Jul 31, 2015, at 15:52, Peter Zijlstra wrote:
On Fri, Jul 31, 2015 at 03:41:37PM +0800, yalin wang wrote:
> Th
Commit-ID: d74892c5b291c0010295d26d6b1e11cd70451722
Gitweb: http://git.kernel.org/tip/d74892c5b291c0010295d26d6b1e11cd70451722
Author: Luiz Capitulino
AuthorDate: Wed, 29 Jul 2015 15:14:17 -0400
Committer: Thomas Gleixner
CommitDate: Sat, 1 Aug 2015 12:00:13 +0200
clockevents: Drop red
On Fri, 31 Jul 2015, Shaohua Li wrote:
> @@ -336,6 +336,22 @@ static void __setup_APIC_LVTT(unsigned int clocks, int
> oneshot, int irqen)
> apic_write(APIC_LVTT, lvtt_value);
>
> if (lvtt_value & APIC_LVT_TIMER_TSCDEADLINE) {
> + u64 msr;
> +
> + /*
> +
On Fri, 31 Jul 2015 22:18:17 +0200
Michael Hornung wrote:
> * Fix sparse warning "Using plain integer as NULL pointer"
>
> Signed-off-by: Michael Hornung
Acked-by: Christian Gromm
> ---
> drivers/staging/most/aim-network/networking.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
On Saturday 25 July 2015 15:17:13 Lars-Peter Clausen wrote:
> On 07/25/2015 12:28 PM, Pali Rohár wrote:
> > Hello,
> >
> > sometimes after rebooting Nokia N900 initializing alsa audio fails.
> > Here output from dmesg log when it happen:
> >
> > [6.925140] tpa6130a2 2-0060: Write failed
> > [
Al Viro wrote on Sat, Aug 01, 2015:
> And that has turned the check done to an inode that *was* ours at some
> point (i.e. fetching it had been followed by checking that ->d_seq had
> been still valid) into something completely unprotected. Suppose we
> are in lazy mode and somebody had evicted nd
>> From: Markus Elfring
>> Date: Sat, 4 Jul 2015 15:30:18 +0200
>>
>> Skip checks for a few variables in three error handling cases within
>> the ocfs2_rename() function by adjustment of a few jump targets
>> according to the Linux coding style convention.
>>
>> Signed-off-by: Markus Elfring
>
>
On 31-07-15, 20:49, Bartlomiej Zolnierkiewicz wrote:
> For Exynos4x12 platforms, add CPU operating points (using
> opp-v2 bindings) and CPU regulator supply properties for
> migrating from Exynos specific cpufreq driver to using
> generic cpufreq driver.
>
> Based on the earlier work by Thomas Abr
Cc'ing Rafael, please keep him in loop for such patches and better use
get_maintainers to get the cc list automatically.
On 31-07-15, 20:49, Bartlomiej Zolnierkiewicz wrote:
> Exynos4x12 based platforms have switched over to use generic
> cpufreq driver for cpufreq functionality. So the Exynos
>
Dominique Martinet wrote on Sat, Aug 01, 2015:
> I had to adapt a bit because using an old kernel (4bf46a272), will try
> again with a recent master to doublecheck
There have been more changes than what I thought, can't seem to
reproduce in a while on linus' HEAD with that fix (it fell in that
che
Hi Peter,
Thanks for looking. I'll try to reply on Monday, just one note...
On 07/30, Peter Zijlstra wrote:
>
> On Tue, Jul 21, 2015 at 09:22:47PM +0200, Oleg Nesterov wrote:
>
> > +static int cpu_stop_queue_two_works(int cpu1, struct cpu_stop_work *work1,
> > + int
On Sat, Aug 01, 2015 at 04:42:27AM +0900, Masahiro Yamada wrote:
> Kbuild descends into drivers/base/regmap/ only when CONFIG_REGMAP
> is enabled. (see drivers/base/Makefile)
>
> $(CONFIG_REGMAP) in drivers/base/regmap/Makefile always evaluates
> to 'y'.
> -obj-$(CONFIG_REGMAP) += regmap.o regcac
On 31-07-15, 20:49, Bartlomiej Zolnierkiewicz wrote:
> Remove no longer needed CPU_FREQ_BOOST_SW config option.
>
> As a result scaling_boost_freqs sysfs attribute is available
> when cpufreq-dt driver is used and boost support is enabled.
>
> Cc: Viresh Kumar
> Cc: Thomas Abraham
> Cc: Javier
On 31-07-15, 20:49, Bartlomiej Zolnierkiewicz wrote:
> diff --git a/drivers/cpufreq/Kconfig b/drivers/cpufreq/Kconfig
> index 659879a..bf6d596 100644
> --- a/drivers/cpufreq/Kconfig
> +++ b/drivers/cpufreq/Kconfig
> @@ -191,6 +191,7 @@ config CPUFREQ_DT
> # if CPU_THERMAL is on and THERMAL=m,
On 31-07-15, 11:00, Joe Perches wrote:
> On Fri, 2015-07-31 at 16:36 +0530, Viresh Kumar wrote:
> > On 31-07-15, 03:28, Joe Perches wrote:
> > > If it's all fixed, then it's unlikely to be needed in checkpatch.
> >
> > I thought checkpatch is more about not committing new mistakes, rather than
> >
The patch
regulator: fan53555: Export I2C module alias information
has been applied to the regulator tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
On Fri, 31 Jul 2015 18:06:45 -0300
Danilo Cesar Lemes de Paula wrote:
> Describing arguments at top of a struct definition works fine
> for small/medium size structs, but it definitely doesn't work well
> for struct with a huge list of elements.
>
> Keeping the arguments list inside the struct b
On 31-07-15, 09:58, Dmitry Torokhov wrote:
> On Fri, Jul 31, 2015 at 02:08:25PM +0530, Viresh Kumar wrote:
> > IS_ERR(_OR_NULL) already contain an 'unlikely' compiler flag and there
> > is no need to do that again from its callers. Drop it.
>
> I'd rather keep it as it documents the expected behav
On 31-07-15, 08:30, Radivoje Jovanovic wrote:
> I just looked over the notifier in the current upstream (my patch was
> made on our production kernel which is 3.14 and has old notifier
> implementation with notifier_device in place) and I see your point.
That's disappointing. You were expected to
On 31-07-15, 09:37, Stephen Boyd wrote:
> Do we need vendor specific properties for that though?
Sorry Lee :), but this is exactly why I wanted this thread to exist. We must and
should do this in a generic enough way.
--
viresh
--
To unsubscribe from this list: send the line "unsubscribe linux-k
On 31-07-15, 10:04, Stephen Boyd wrote:
> We're removing struct clk from the clk provider API, so switch
> this code to using the clk_hw based provider APIs.
>
> Cc: Viresh Kumar
> Signed-off-by: Stephen Boyd
> ---
> drivers/clk/spear/clk-vco-pll.c | 2 +-
> 1 file changed, 1 insertion(+), 1 de
On Saturday 01 August 2015 13:22:51 Viresh Kumar wrote:
> On 31-07-15, 09:58, Dmitry Torokhov wrote:
> > On Fri, Jul 31, 2015 at 02:08:25PM +0530, Viresh Kumar wrote:
> > > IS_ERR(_OR_NULL) already contain an 'unlikely' compiler flag and
> > > there is no need to do that again from its callers. Dro
On Wed, 29 Jul 2015, Dmitry Torokhov wrote:
> > Another and less intrusive fix would be:
> >
> > char *name = dev->battery->desc->name;
> > struct power_supply_desc *psy_desc = dev->battery->desc;
> > power_supply_unregister(dev->battery);
> > kfree(name);
> > kfree(psy_desc);
On Mon, Jul 27, 2015 at 12:33 AM, Sedat Dilek wrote:
> Hi,
>
> this my first build of a 4.2-rcN Linux-kernel and I see this...
>
Just FYI:
I am *not* seeing this with drm-intel-nightly from below url.
Also, I plan to test Linux v4.2-rc5.
- Sedat -
[1]
http://kernel.ubuntu.com/~kernel-ppa/mai
Allow a trace events header file to disable compilation of its
trace events by defining the preprocessor macro NOTRACE.
This could be done, for example, according to a Kconfig option.
Signed-off-by: Tal Shorer
---
include/linux/tracepoint.h | 17 ++---
include/trace/define_trace.h
Add a new options to trace Kconfig, CONFIG_TRACING_EVENTS_GPIO, that is
used for enabling/disabling compilation of gpio function trace events.
Signed-off-by: Tal Shorer
Acked-by: Linus Walleij
---
include/trace/events/gpio.h | 4
kernel/trace/Kconfig| 7 +++
2 files changed, 11
Currently, enabling CONFIG_TRACING on a system comes as all-or-nothing:
either tracepoints for all subsystems are compiled (with CONFIG_TRACING)
or none of them are (without it).
This caused me an unacceptable performance penalty (obviously SOME penalty
was expected, but not one so severe) which m
Hi Mark,
2015-08-01 19:59 GMT+09:00 Mark Brown :
> On Sat, Aug 01, 2015 at 04:42:27AM +0900, Masahiro Yamada wrote:
>> Kbuild descends into drivers/base/regmap/ only when CONFIG_REGMAP
>> is enabled. (see drivers/base/Makefile)
>>
>> $(CONFIG_REGMAP) in drivers/base/regmap/Makefile always evaluat
When and What time can i Call you? Respond ASAP
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Hi Jon,
On Saturday 01 August 2015 13:22:10 Jonathan Corbet wrote:
> On Fri, 31 Jul 2015 18:06:45 -0300 Danilo Cesar Lemes de Paula wrote:
> > Describing arguments at top of a struct definition works fine
> > for small/medium size structs, but it definitely doesn't work well
> > for struct with a
On Fri, Jul 31, 2015 at 01:43:06PM -0700, Dmitry Torokhov wrote:
> On Fri, Jul 31, 2015 at 01:36:18PM -0700, Greg KH wrote:
> > On Fri, Jul 31, 2015 at 11:04:26PM +0530, Sudip Mukherjee wrote:
> > > On Fri, Jul 31, 2015 at 09:54:27AM -0700, Dmitry Torokhov wrote:
> > > > On Fri, Jul 31, 2015 at 03:
Originally watchdog_nmi_enable(cpu) and watchdog_nmi_disable(cpu) were
only called in watchdog thread context. However, the following commits
utilize these functions outside of watchdog thread context too.
commit 9809b18fcf6b8d8ec4d3643677345907e6b50eca
Author: Michal Hocko
Date: Tue Sep
This interface can be utilized to deactivate the hard and soft lockup
detector temporarily. Callers are expected to minimize the duration of
deactivation. Multiple deactivations are allowed to occur in parallel
but should be rare in practice.
Signed-off-by: Ulrich Obergfell
---
include/linux/nmi
Remove update_watchdog() and restart_watchdog_hrtimer() since these
functions are no longer needed. Changes of parameters such as the
sample period are honored at the time when the watchdog threads are
being unparked.
Signed-off-by: Ulrich Obergfell
---
kernel/watchdog.c | 40 ++-
Remove watchdog_nmi_disable_all() and watchdog_nmi_enable_all()
since these functions are no longer needed. If a subsystem has a
need to deactivate the watchdog temporarily, it should utilize the
watchdog_suspend() and watchdog_resume() functions.
Signed-off-by: Ulrich Obergfell
---
arch/x86/ker
These functions are intended to be used only from inside kernel/watchdog.c
to park/unpark all watchdog threads that are specified in watchdog_cpumask.
Signed-off-by: Ulrich Obergfell
---
kernel/watchdog.c | 36
1 file changed, 36 insertions(+)
diff --git a/k
Don,
> Uli privately has been working on a patchset that cleans up a bunch of these
> race conditions. We believe it should cover this case. It uses the
> proc_mutex to synchronize everything.
>
> I think he is reaching out to you. If you could try his patchset to see if
> it fixes things, it
Sometimes a scatter-gather has to be split into several chunks, or sub scatter
lists. This happens for example if a scatter list will be handled by multiple
DMA channels, each one filling a part of it.
A concrete example comes with the media V4L2 API, where the scatter list is
allocated from users
On Sat, Aug 01, 2015 at 03:12:42PM +0800, yalin wang wrote:
>
> > 在 2015年7月31日，22:14，Thomas Gleixner 写道：
> >
> >
> > On Fri, 31 Jul 2015, Thomas Gleixner wrote:
> >
> >> On Fri, 31 Jul 2015, yalin wang wrote:
> >>> it is optimised to 2 instructions ,
> >>>
> >>> this is my patch, hope can be
acpi_debugfs_init function is declared with return type int in
drivers/acpi/internal.h when CONFIG_DEBUG_FS is enabled, but its
definition in drivers/acpi/debugfs.c has return type void. This is due
to commit aecad432fd68 ("ACPI: Cleanup custom_method debug stuff"),
which changed the return type fr
gfx_v7_0_print_status contains a for loop on variable queue which does
not update this variable between each iteration. This is bug is
reported by clang while building allmodconfig LLVMLinux on x86_64:
drivers/gpu/drm/amd/amdgpu/gfx_v7_0.c:5126:19: error: variable
'queue' used in loop con
Directly including access_ok.h can result in the following compile errors
if an architecture such as ia64 does not support direct unaligned accesses.
include/linux/unaligned/access_ok.h:7:19: error:
redefinition of 'get_unaligned_le16'
include/linux/unaligned/le_struct.h:6:19: note:
Including access_ok.h causes the ia64:allmodconfig build (and maybe others)
to fail with
include/linux/unaligned/le_struct.h:6:19: error:
redefinition of 'get_unaligned_le16'
include/linux/unaligned/access_ok.h:7:19: note:
previous definition of 'get_unaligned_le16' was here
includ
On Sat, Aug 01, 2015 at 02:49:23PM +0200, Ulrich Obergfell wrote:
> This interface can be utilized to deactivate the hard and soft lockup
> detector temporarily. Callers are expected to minimize the duration of
> deactivation. Multiple deactivations are allowed to occur in parallel
> but should be
On Fri, Jul 31, 2015 at 05:27:13PM +0200, Borislav Petkov wrote:
> On Fri, Jul 31, 2015 at 05:08:06PM +0200, Peter Zijlstra wrote:
> > But its things like set_memory_XX(), and afaict that's all buggy against
> > MTRR modifications.
>
> I think the idea is to not do any MTRR modifications at some p
> - Original Message -
> From: "Guenter Roeck"
> ...
> Subject: Re: [PATCH 2/4] watchdog: introduce watchdog_suspend() and
> watchdog_resume()
>
> On Sat, Aug 01, 2015 at 02:49:23PM +0200, Ulrich Obergfell wrote:
>> This interface can be utilized to deactivate the hard and soft lockup
>>
On Sat, Aug 01, 2015 at 10:39:22AM -0400, Ulrich Obergfell wrote:
> > - Original Message -
> > From: "Guenter Roeck"
> > ...
> > Subject: Re: [PATCH 2/4] watchdog: introduce watchdog_suspend() and
> > watchdog_resume()
> >
> > On Sat, Aug 01, 2015 at 02:49:23PM +0200, Ulrich Obergfell wro
On Sat, Jul 25, 2015 at 02:02:46AM +0200, Niklas Cassel wrote:
> In order to use the mctrl_gpio helpers, we change the DT bindings:
> ri-gpios renamed to rng-gpios. cd-gpios renamed to dcd-gpios.
> However, no in-tree dts/dtsi specifies these, so no worries.
>
> Signed-off-by: Niklas Cassel
Acke
On Sat, Jul 25, 2015 at 02:00:40AM +0200, Niklas Cassel wrote:
> Implementing enable_ms is optional by serial_core.
> check_modem_status is just an empty local function.
>
> Signed-off-by: Niklas Cassel
Reviewed-by: Guenter Roeck
Tested-by: Guenter Roeck
--
To unsubscribe from this list: send
Hi Mike,
On Fri, 31 Jul 2015, Michael Turquette wrote:
> Quoting Paul Osmialowski (2015-07-30 14:40:48)
> > Hi Mike,
> >
> > I encountered some trouble while I tried to implement code fitting to DTS
> > that you proposed. SIM_CLKDIVx are SIM device registers, not MCG.
> > Therefore, in MCG de
On Sat, Aug 01, 2015 at 10:25:26AM +0530, Sudip Mukherjee wrote:
> On Fri, Jul 31, 2015 at 01:52:13PM -0700, Greg Kroah-Hartman wrote:
> > On Fri, Jul 31, 2015 at 11:08:47AM +0530, Shraddha Barke wrote:
> > > This patch fixes the following checkpatch.pl warning:
> > >
> > > WARNING: do not add new
On Sat, Aug 1, 2015 at 12:26 AM, Al Viro wrote:
>
> Actually, the shit had hit the fan earlier. Look: in
> commit b18825a7c8e37a7cf6abb97a12a6ad71af160de7
> Author: David Howells
> Date: Thu Sep 12 19:22:53 2013 +0100
>
> VFS: Put a small type field into struct dentry::d_flags
>
> we have
Hi Linus,
Here is the first fixes request for 4.2
We had a regression due to reuse of descriptor so we have reverted that.
Rest are driver fixes:
at_hdmac and at_xdmac for residue, trannfer width, and channel config
pl330 final fix for dma fails and overflow issue
xgene resouce
On Sat, Aug 01, 2015 at 09:05:52AM -0400, Ulrich Obergfell wrote:
>
> Don,
>
> > Uli privately has been working on a patchset that cleans up a bunch of these
> > race conditions. We believe it should cover this case. It uses the
> > proc_mutex to synchronize everything.
> >
> > I think he is re
On Sat, Aug 01, 2015 at 04:28:20PM +0200, Luis R. Rodriguez wrote:
> I need to update this documentation to remove set_memory_wc() there as we've
> learned with the MTRR --> PAT conversion that set_memory_wc() cannot be used
> on
> IO memory, it can only be used for RAM. I am not sure if I would c
On Sat, Aug 01 2015 at 2:58am -0400,
Ming Lin wrote:
> On Fri, 2015-07-31 at 17:38 -0400, Mike Snitzer wrote:
> >
> > OK, once setup, to run the 2 tests in question directly you'd do
> > something like:
> >
> > dmtest run --suite thin-provisioning -n discard_a_fragmented_device
> >
> > dmtest
On Sat, Aug 1, 2015 at 9:33 AM, Borislav Petkov wrote:
>
> Well, it doesn't really make sense to write-combine IO memory, does it?
Quite the reverse.
It makes no sense to write-combine normal memory (RAM), because caches
work and sane memory is always cache-coherent. So marking regular
memory wr
Replace ACCESS_ONCE() macro in smp_store_release() and smp_load_acquire()
from arch/x86/include/asm/barrier.h with WRITE_ONCE() and READ_ONCE() since
ACCESS_ONCE does not work reliably on non-scalar types.
WRITE_ONCE() and READ_ONCE() were introduced in the commits 230fa253df63
("kernel: Provide R
On Sat, Aug 01, 2015 at 09:39:07AM -0700, Linus Torvalds wrote:
> Quite the reverse.
>
> It makes no sense to write-combine normal memory (RAM), because caches
> work and sane memory is always cache-coherent. So marking regular
> memory write-combining is a sign of crap hardware (which admittedly
On Sat, Aug 01, 2015 at 06:45:34PM +0200, Andrey Konovalov wrote:
> Replace ACCESS_ONCE() macro in smp_store_release() and smp_load_acquire()
> from arch/x86/include/asm/barrier.h with WRITE_ONCE() and READ_ONCE() since
> ACCESS_ONCE does not work reliably on non-scalar types.
>
> WRITE_ONCE() and
On Fri, Jul 31, 2015 at 10:56 PM, Casey Schaufler
wrote:
> On 7/31/2015 1:11 AM, Amir Goldstein wrote:
>> On Thu, Jul 30, 2015 at 6:33 PM, Casey Schaufler
>> wrote:
>>> On 7/30/2015 7:47 AM, Amir Goldstein wrote:
On Thu, Jul 30, 2015 at 4:55 PM, Seth Forshee
wrote:
> On Thu, Jul 3
On Sat, Aug 1, 2015 at 9:49 AM, Borislav Petkov wrote:
>
> My simplistic mental picture while thinking of this is the IO range
> where you send the commands to the device and you don't really want to
> delay those but they should reach the device as they get issued.
Well, even for command streams
On Sat, Aug 01, 2015 at 09:09:24AM -0700, Linus Torvalds wrote:
> On Sat, Aug 1, 2015 at 12:26 AM, Al Viro wrote:
> >
> > Actually, the shit had hit the fan earlier. Look: in
> > commit b18825a7c8e37a7cf6abb97a12a6ad71af160de7
> > Author: David Howells
> > Date: Thu Sep 12 19:22:53 2013 +0100
This allows the module to be autoloaded.
Together with 07949bf9c63c ("cpufreq: dt: allow driver to boot
automatically") this is sufficient to allow a modular kernel (such
as Debian's) to enable cpufreq on a Cubietruck.
Signed-off-by: Ian Campbell
Cc: Liam Girdwood
Cc: Mark Brown
Cc: Chen-Yu Ts
On Sat, Aug 01, 2015 at 06:45:34PM +0200, Andrey Konovalov wrote:
> Replace ACCESS_ONCE() macro in smp_store_release() and smp_load_acquire()
> from arch/x86/include/asm/barrier.h with WRITE_ONCE() and READ_ONCE() since
> ACCESS_ONCE does not work reliably on non-scalar types.
>
> WRITE_ONCE() and
As UFS driver registers IRQ handler as a shared IRQ, when
CONFIG_DEBUG_SHIRQ=y, an extra call will be made while unregistering
the IRQ handler. Unfortunately, the extra call will accesses already
freed hostdata. This is because devm_request_irq() is used to register
IRQ handler so that it will be
On Fri, 2015-07-31 at 22:21 -0400, Waiman Long wrote:
> The smp_store_release() is not a full barrier. In order to avoid missed
> wakeup, we may need to add memory barrier around locked and cpu state
> variables adding to complexity. As the chance of spurious wakeup is very
> low, it is easier and
Greg, over the last two months we have sent numerous Hyper-V patches and
these are yet to be comitted (all review comments have been addressed
for these patches). Please let me know if I should resend these patches.
Regards,
K. Y
--
To unsubscribe from this list: send the line "unsubscribe lin
On Sat, Aug 01, 2015 at 12:46:10PM -0700, K. Y. Srinivasan wrote:
>
> Greg, over the last two months we have sent numerous Hyper-V patches and
> these are yet to be comitted (all review comments have been addressed
> for these patches). Please let me know if I should resend these patches.
They a
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Saturday, August 1, 2015 11:36 AM
> To: KY Srinivasan
> Cc: linux-kernel@vger.kernel.org; de...@linuxdriverproject.org;
> o...@aepfle.de; a...@canonical.com; vkuzn...@redhat.com;
> jasow...@redhat.com
> Subj
Eyal Moscovici writes:
...
>
> We can start to implement polling, but I am unsure if the cgroups
> integration
> will be sufficient. The polling vhost thread should be scheduled all
> the time and just moving it from one cgroup to the other wont be
> sufficient.
> I think it needs a deeper int
On Tue, 2015-06-16 at 17:33 +0100, Luis Henriques wrote:
> On Tue, May 05, 2015 at 02:16:39AM +0100, Ben Hutchings wrote:
[...]
> > [bwh: Backported to 3.2:
> > - Plumb in debugfs_super_operations, which we didn't previously
> > define
>
> It looks like this is introducing a regression[1]. Basi
On 07/31/15 at 10:51am, Joe Stringer wrote:
> On 31 July 2015 at 07:34, Hannes Frederic Sowa wrote:
> > In general, this shouldn't be necessary as the packet should already be
> > scrubbed before they arrive here.
> >
> > Could you maybe add a WARN_ON and check how those skbs with conntrack
> > da
The audit watch count was imbalanced, adding an unnecessary layer of watch
references. Only add the second reference when it is added to a parent.
Signed-off-by: Richard Guy Briggs
---
kernel/audit_watch.c |5 ++---
kernel/auditfilter.c | 16 +++-
2 files changed, 5 insertions
The audit watch parent count was imbalanced, adding an unnecessary layer of
watch parent references. Decrement the additional parent reference when a
watch is reused, already having a reference to the parent.
audit_find_parent() gets a reference to the parent, if the parent is
already known. Thi
While working on the audit by executable path feature, it was discovered that
watches and parent references were slightly imbalanced and deeper than
necessary.
Only bump up references when they are actually used and decrease when removed.
v4: Eliminate unnecessary gotos and call return directly.
Signed-off-by: Richard Guy Briggs
---
include/uapi/linux/audit.h |2 ++
kernel/audit.c |2 +-
kernel/audit_watch.c |8
kernel/auditsc.c |6 +++---
4 files changed, 10 insertions(+), 8 deletions(-)
diff --git a/include/uapi/linux/audit.h b/incl
This is a patch to clean up a number of places were casted magic numbers are
used to represent unset inode and device numbers inpreparation for the audit by
executable path patch set.
Richard Guy Briggs (1):
audit: use macros for unset inode and device values
include/uapi/linux/audit.h |2
This patch was split out from the audit by executable path patch set due to the
potential to use it elsewhere.
In particular, some questions came up while assessing the potential for code
reuse:
Why does audit_remove_parent_watches() not call audit_del_rule() for
each entry found?
Move the access to the entry for audit_match_signal() to the beginning of the
function in case the entry found is the same one passed in. This will enable
it to be used by audit_remove_mark_rule().
Signed-off-by: Richard Guy Briggs
---
kernel/auditfilter.c |3 ++-
1 files changed, 2 inserti
This is to be used to audit by executable path rules, but audit watches should
be able to share this code eventually.
At the moment the audit watch code is a lot more complex. That code only
creates one fsnotify watch per parent directory. That 'audit_parent' in
turn has a list of 'audit_watches
This adds the ability to audit the actions of children of a not-yet-running
process.
This is a split-out of a heavily modified version of a patch originally
submitted by Eric Paris with some ideas from Peter Moody.
Cc: Peter Moody
Cc: Eric Paris
Signed-off-by: Richard Guy Briggs
---
include/u
Please see the accompanying userspace patchset:
https://www.redhat.com/archives/linux-audit/2015-July/thread.html
[[PATCH V2] 0/2] Log on the future execution of a path
The userspace interface is not expected to change appreciably unless something
important has been overlooked. Set
This adds the ability audit the actions of a not-yet-running process.
This patch implements the ability to filter on the executable path. Instead of
just hard coding the ino and dev of the executable we care about at the moment
the rule is inserted into the kernel, use the new audit_fsnotify
infr
> > I wonder what devices do if you do a word read beyond their end address?
> > Perhaps in odd cases we should always fall back to byte reads?
>
> In my tests I can read beyond the end address, but I cannot be sure if this
> is OK for all
> devices. This was actually a suggestion from Wolfram f
> + if (at24->use_smbus) {
> + status =
> + i2c_smbus_read_i2c_block_data_or_emulated(client,
> + offset,
> + c
1 - 100 of 330 matches
Mail list logo
