On Sat, Feb 16, 2013 at 12:13:41PM +0800, Chen Gang wrote:
>
> arg2 will never < 0, for its type is 'unsigned long'
>
> so need beautify the relative source code (better to use macros).
>
> Reported-by: Cyrill Gorcunov
> Signed-off-by: Chen Gang
Looks good to me, thanks Chen!
--
To
On Fri, Feb 15, 2013 at 8:13 PM, Chen Gang wrote:
>
> arg2 will never < 0, for its type is 'unsigned long'
>
> so need beautify the relative source code (better to use macros).
>
> Reported-by: Cyrill Gorcunov
> Signed-off-by: Chen Gang
Acked-by: Kees Cook
-Kees
--
Kees Cook
Chrome OS
On Fri, Feb 15, 2013 at 11:20:18PM -0800, Raymond Jennings wrote:
> An even bigger question might be why an execve is allowed to get into
> an unrecoverable state to begin with. Assuming that one builds the
> new mm_struct and whatnot BEFORE discarding old state, why would
> execve be in a
Add the needed sections to enable audio support on
Devkit8000 when booted with DT blob.
Signed-off-by: Anil Kumar
---
This patch is based on top of kernel 3.8-rc5 and
the following patches.
Peter Ujfalusi:-
ASoC: twl4030: Correct the support for Voice port
ASoC: twl4030: Convert MICBIAS to
since already call irq_alloc_descs before,
we need call irq_free_descs when quiting, or resource leak.
Signed-off-by: Chen Gang
---
drivers/gpio/gpio-twl4030.c |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/drivers/gpio/gpio-twl4030.c
On Fri, Feb 15, 2013 at 6:20 PM, Al Viro wrote:
> Arrgh... OK, I'm a blind idiot. These places in binfmt_elf.c currently use
> force_sig(), not send_sig_info(). Currently == since 2006 when somebody
> noticed the problem. Their counterparts in binfmt_elf_fdpic.c were *not*
> noticed. Anyway,
DevKit8000 is a beagle board clone from Timll, sold by
armkits.com. The DevKit8000 has RS232 serial port, LCD, DVI-D,
S-Video, Ethernet, SD/MMC, keyboard, camera, SPI, I2C, USB and
JTAG interface.
This patch adds the basic DT support for devkit8000. At this time, Information
of twl4030 (PMIC),
On Fri, Feb 15, 2013 at 11:44:44PM +0100, Richard Weinberger wrote:
> > The ability to deprecate this code has been called into question[1],
> > but if that remains to be finalized, then making this change in the
> > interim seems to make sense.
>
> Do we really want to remove this system call in
Michael Grosshaeuser wrote:
> Zhang Rui intel.com> writes:
>
>>
>> Hi, Roberto,
>>
>> please attach the acpidump output.
>>
>> On Tue, 2012-12-04 at 13:57 +0100, Roberto Oppedisano wrote:
>> > Hello,
>> > with recent kernels after a suspend/resume cycle on my laptop (HP
>> > 6730b) the
On Sat, Feb 16, 2013 at 05:18:10AM +, Ben Hutchings wrote:
> Don't worry about it - I think the log messages are a pretty good clue.
>
> Does this patch fix the log messages and/or the other issues?
>
Yes! In fact after a quick reboot, the log lines look to me like they exist
properly, acpi
On 02/14/2013 02:38 AM, Seth Jennings wrote:
This patch adds support for evicting swap pages that are currently
compressed in zswap to the swap device. This functionality is very
important and make zswap a true cache in that, once the cache is full
or can't grow due to memory pressure, the
Signed-off-by: Axel Lin
---
drivers/regulator/max8649.c | 39 ++-
1 file changed, 6 insertions(+), 33 deletions(-)
diff --git a/drivers/regulator/max8649.c b/drivers/regulator/max8649.c
index 3ca1438..fdb67ff 100644
--- a/drivers/regulator/max8649.c
+++
Signed-off-by: Axel Lin
---
drivers/regulator/88pm8607.c | 36
1 file changed, 4 insertions(+), 32 deletions(-)
diff --git a/drivers/regulator/88pm8607.c b/drivers/regulator/88pm8607.c
index c79ab84..493948a 100644
--- a/drivers/regulator/88pm8607.c
+++
Add enable_is_inverted flag to indicate set enable_mask bits to disable
when using regulator_enable_regmap and friends APIs.
Signed-off-by: Axel Lin
---
drivers/regulator/core.c | 24
include/linux/regulator/driver.h |3 +++
2 files changed, 23
[Purpose of this patch]
As Vaibhav explained in the thread below, tracepoints for irq vectors
are useful.
http://www.spinics.net/lists/mm-commits/msg85707.html
The current interrupt traces from irq_handler_entry and irq_handler_exit
provide when an interrupt is handled. They provide good data
[Issue]
Currently, irq vector handlers for tracing are just
copied non-trace handlers by simply inserting tracepoints.
It is difficult to manage the codes.
[Solution]
This patch shares common codes between non-trace and trace handlers
as follows to make them manageable and readable.
Non-trace
From: Steven Rostedt
Each TRACE_EVENT() adds several helper functions. If two or more trace events
share the same structure and print format, they can also share most of these
helper functions and save a lot of space from duplicate code. This is why the
DECLARE_EVENT_CLASS() and DEFINE_EVENT()
On 02/04/2013 08:23 AM, Minchan Kim wrote:
Zsmalloc has two methods 1) copy-based and 2) pte based to access
allocations that span two pages.
You can see history why we supported two approach from [1].
But it was bad choice that adding hard coding to select architecture
which want to use pte
Change log
v9 -> v10
- Add an explanation the reason why tracepoints has to place inside irq
enter/exit handling. (patch 3/3)
v8 -> v9
- Rebase to 3.8-rc6
- Add Steven's email address at the top of the message and
move my signed-off-by below Steven's one because it is
originally
On 02/14/2013 02:38 AM, Seth Jennings wrote:
This patch adds a documentation file for zsmalloc at
Documentation/vm/zsmalloc.txt
Signed-off-by: Seth Jennings
---
Documentation/vm/zsmalloc.txt | 68 +
1 file changed, 68 insertions(+)
create mode
In ehea.h the minimal entries is 2^7 - 1:
#define EHEA_MIN_ENTRIES_QP 127
Thus change the module param description accordinglly
Signed-off-by: Dave Young
---
drivers/net/ethernet/ibm/ehea/ehea_main.c |8
1 file changed, 4 insertions(+), 4 deletions(-)
---
On Sat, Feb 16, 2013 at 11:26:30AM +0900, Simon Horman wrote:
> On Fri, Feb 15, 2013 at 11:07:16AM +0100, Guennadi Liakhovetski wrote:
> > Add device-tree bindings to the AS3711 regulator and backlight drivers.
>
> Hi,
>
> at this stage I do not expect this code to go through the renesas tree.
>
On Sat, Feb 16, 2013 at 1:35 PM, Axel Lin wrote:
>
>> I think that enable_pulldown is a little hard to understand. How about
>> change
>> the name, like set_to_disable or something else?
>
>
> How about "enable_invert"?
> ( We have ena_gpio_invert setting for GPIO controlled enable lines )
>
>
On Fri, Feb 15, 2013 at 11:07:16AM +0100, Guennadi Liakhovetski wrote:
> Add device-tree bindings to the AS3711 regulator and backlight drivers.
>
> Signed-off-by: Guennadi Liakhovetski
> ---
>
> As usual - comments to the new bindings are very welcome!
>
>
Fair enough. Sounds good.
Seiji Aguchi wrote:
>> > How important is it that the tracepoint is *inside* the enter/exit
>> > handling? If not, it would be simpler to just do:
>> >
>> > smp_trace_irq_handler()
>> > {
>> >trace_irq_entry();
>> >smp_irq_handler();
>> >trace_irq_exit();
> -Original Message-
> From: tip tree robot [mailto:tip...@zytor.com] On Behalf Of tip-bot for Ingo
> Molnar
> Sent: Monday, February 11, 2013 8:20 PM
> To: linux-tip-comm...@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org; h...@zytor.com; mi...@kernel.org;
> a.p.zijls...@chello.nl;
> > How important is it that the tracepoint is *inside* the enter/exit
> > handling? If not, it would be simpler to just do:
> >
> > smp_trace_irq_handler()
> > {
> > trace_irq_entry();
> > smp_irq_handler();
> > trace_irq_exit();
> > }
> >
> > ... which seems a bit cleaner. If this
On Fri, 2013-02-15 at 22:23 -0500, tmhik...@gmail.com wrote:
> On Thu, Feb 14, 2013 at 05:04:07AM +, Ben Hutchings wrote:
> > On Tue, 2013-02-12 at 00:01 -0500, tmhik...@gmail.com wrote:
> > > Okay, I finally have located the patch causing this bizzare problem
> > > for me. Before I discuss
On 02/15/2013 08:38 PM, Peter Zijlstra wrote:
> On Wed, 2013-02-13 at 21:22 +0800, Alex Shi wrote:
>> No, the flags set on MC/CPU domain, but is checked in their parents
>> balancing, like in NUMA domain.
>> Without the flag, will cause NUMA domain imbalance. like on my 2
>> sockets
>> NHM EP: 3
On Fri, 15 Feb 2013, Russell King - ARM Linux wrote:
> On Thu, Feb 14, 2013 at 11:47:50PM +0100, Arnd Bergmann wrote:
> > Patch c08e20d24 "arm: Add v7_invalidate_l1 to cache-v7.S"
> > moves the v7_invalidate_l1 symbol out of imx/headsmp.S,
> > which seems to cause a link error because it is now
>
Currently the functions smp_call_function_many()/single() will
give a WARN()ing only in the case of irqs_disabled(), but that
check is not enough to guarantee execution of the SMP
cross-calls.
In many other cases such as softirq handling/interrupt handling,
the two APIs still can not be called,
Currently the functions smp_call_function_many()/single() will
give a WARN()ing only in the case of irqs_disabled(), but that
check is not enough to guarantee execution of the SMP
cross-calls.
In many other cases such as softirq handling/interrupt handling,
the two APIs still can not be called,
This file is included verbatim from the ChromeOS EC respository.
Ideally we would prefer to avoid changing it, to make it easier
to track this rapidly-changing file.
Signed-off-by: Simon Glass
Signed-off-by: Che-Liang Chiou
Signed-off-by: Vincent Palatin
---
Changes in v4: None
Changes in v3:
This uses an I2C bus to talk to the ChromeOS EC. The protocol
is defined by the EC and is fairly simple, with a length byte,
checksum, command byte and version byte (to permit easy creation
of new commands).
Signed-off-by: Simon Glass
Signed-off-by: Che-Liang Chiou
---
Changes in v4: None
We now have a binding which adds two parameters to the matrix keypad DT
node. This is separate from the GPIO-driven matrix keypad binding, and
unfortunately incompatible, since that uses row-gpios/col-gpios for the
row and column counts.
So the easiest option here is to provide a function for
Use the key-matrix layer to interpret key scan information from the EC
and inject input based on the FDT-supplied key map. This driver registers
itself with the ChromeOS EC driver to perform communications.
The matrix-keypad FDT binding is used with a small addition to control
ghosting.
This is the base EC implementation, which provides a high level
interface to the EC for use by the rest of the kernel. The actual
communcations is dealt with by a separate protocol driver which
registers itself with this interface.
Interrupts are passed on through a notifier.
A simple message
This uses a SPI bus to talk to the ChromeOS EC. The protocol
is defined by the EC and is fairly simple, with a length byte,
checksum, command byte and version byte (to permit easy creation
of new commands).
Signed-off-by: Simon Glass
---
Changes in v4: None
Changes in v3: None
Changes in v2:
-
The ChromeOS Embedded Controller (EC) is an Open Source EC implementation
used on ARM and Intel Chromebooks. Current implementations use a Cortex-M3
connected on a bus (such as I2C, SPI, LPC) to the AP. A separate interrupt
line is used to indicate when the EC needs service.
Functions performed
arg2 will never < 0, for its type is 'unsigned long'
so need beautify the relative source code (better to use macros).
Reported-by: Cyrill Gorcunov
Signed-off-by: Chen Gang
---
kernel/sys.c |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/kernel/sys.c
On 02/14/2013 02:38 AM, Seth Jennings wrote:
zswap is a thin compression backend for frontswap. It receives
pages from frontswap and attempts to store them in a compressed
memory pool, resulting in an effective partial memory reclaim and
dramatically reduced swap device I/O.
Additionally, in
Hi Joe,
On Tue, Feb 12, 2013 at 7:35 PM, Joe Perches wrote:
> On Tue, 2013-02-12 at 18:42 -0800, Simon Glass wrote:
>> This is the base EC implementation, which provides a high level
>> interface to the EC for use by the rest of the kernel. The actual
>> communcations is dealt with by a separate
Hi Dmitry,
On Thu, Feb 14, 2013 at 9:31 AM, Dmitry Torokhov
wrote:
> On Wed, Feb 13, 2013 at 10:45:07PM -0800, Simon Glass wrote:
>> >>
>> >> +config KEYBOARD_CROS_EC
>> >> + tristate "ChromeOS EC keyboard"
>> >> + select INPUT_MATRIXKMAP
>> >> + select MFD_CROS_EC
>> >
>> > Is this
On Tue, Feb 12, 2013 at 11:47 PM, Artem Bityutskiy wrote:
> On Mon, 2013-01-28 at 12:57 +0800, Huang Shijie wrote:
>> + {"SmartMedia 256MiB 3,3V", {0, 0x71}, 512, 256, 0x4000 },
>> + {"SmartMedia 256MiB 3,3V ROM", {0, 0x5b}, 512, 256, 0x4000,
>> NAND_ROM},
>
> Sorry for a
Sjur Brændeland writes:
> How about supporting struct vringh_kiov and struct kvec as well?
> I currently get the following complaints with my V2 patch-set:
>
> drivers/net/caif/caif_virtio.c:486:2: warning: passing argument 1 of
> ‘vringh_iov_init’ from incompatible pointer type [enabled by
On 2013/2/13 17:15, Ingo Molnar wrote:
>
> * Namhyung Kim wrote:
>
>> Hi,
>>
>> On Mon, 11 Feb 2013 10:54:58 +0100, Ingo Molnar wrote:
>>> * Clark Williams wrote:
>>>
I figured that was coming. :)
>>>
>>> ;-)
>>>
I'll look at it again and see about pulling the
autogroup/cgroup
On 02/14/2013 02:38 AM, Seth Jennings wrote:
=
DO NOT MERGE, FOR REVIEW ONLY
This patch introduces zsmalloc as new code, however, it already
exists in drivers/staging. In order to build successfully, you
must select EITHER to driver/staging version OR this version.
Once zsmalloc is
On 15 February 2013 23:51, Arnd Bergmann wrote:
> As Andy pointed out today, we don't have a good solution for the
> dw_dmac DT binding in linux-next yet. I have posted my series
> once before and then got distracted after getting feedback from
> Viresh, Andy and Russell. I have now updated my
On 15 February 2013 23:51, Arnd Bergmann wrote:
> diff --git a/Documentation/devicetree/bindings/dma/snps-dma.txt
> b/Documentation/devicetree/bindings/dma/snps-dma.txt
> +- #dma-cells: must be <3>
> +DMA clients connected to the Designware DMA controller must use the format
> +described in the
On 02/14/2013 02:38 AM, Seth Jennings wrote:
Lots of changes this time around. Hopefully I collected and acted on
all the feedback. I apologize ahead of time if I missed something.
Please let me know if I did.
Changelog:
v5:
* zsmalloc patch converted from promotion to "new code" (for review
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
or
master.kernel.org:/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive updates for the input subsystem. You will get 2 small driver
fixups and a documentation update
On Fri, Feb 15, 2013 at 08:36:21PM +0100, Henrik Rydberg wrote:
> To properly setup event parameters for emulated events, pass
> the appropriate flag to the slot initialization function. Also,
> all MT-related events should be setup before initialization.
>
> Incidentally, this solves the issue
TWL6030_FIXED_RESOURCE is not used now, remove it.
TWL6030_FIXED_RESOURCE is not used since commit e76ab829cc
"regulator: twl: Remove references to the twl4030 regulator"
twl6030_fixed_resource is removed by commit 029dd3cef
"regulator: twl: Remove another unused variable warning".
On Fri, Feb 15, 2013 at 8:36 PM, Axel Lin wrote:
> The info parameter is not used at all, remove it.
>
> Signed-off-by: Axel Lin
> ---
> drivers/regulator/max8925-regulator.c |5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/regulator/max8925-regulator.c
On Fri, Feb 15, 2013 at 5:19 PM, Axel Lin wrote:
> Add enable_pulldown flag to indicate pulldown on EN input when using
> regulator_enable_regmap and friends APIs.
>
> Signed-off-by: Axel Lin
> ---
> drivers/regulator/core.c | 24
>
On Fri, 2013-02-15 at 11:46 -0800, Sukadev Bhattiprolu wrote:
>
> POWER could use an additional field:
>
> mem_deratmiss:1
If you want to make that field more "generic" make it "lvl1_tlb_miss",
ie, a miss in the internal "level 1" TLB which is the smallest/fastest
TLB
Many i2c users consider short transfers to be an error and would prefer
getting -EIO instead of a positive return value and having to convert
it to error code by themselves. So let's add the following new helpers:
i2c_master_send_exact()
i2c_master_recv_exact()
Many i2c users consider short transfers to be an error and would prefer
getting -EIO instead of a positive return value and having to convert
it to error code by themselves. So let's add the following new helpers:
i2c_master_send_exact()
i2c_master_recv_exact()
On Fri, 2013-02-15 at 18:11 -0800, H. Peter Anvin wrote:
> Not-yet-signed-off-by: Steven Rostedt
Also note that the "Not-yet-signed-off-by" was to let people know that,
even though I ran it through various tests, I did not run it through my
main test suite.
I probably wont change it much, if
Signed-off-by: Axel Lin
---
drivers/regulator/twl-regulator.c | 12 +++-
1 file changed, 3 insertions(+), 9 deletions(-)
diff --git a/drivers/regulator/twl-regulator.c
b/drivers/regulator/twl-regulator.c
index d62604c0..2b3dc5b 100644
--- a/drivers/regulator/twl-regulator.c
+++
On Fri, Feb 15, 2013 at 11:07:16AM +0100, Guennadi Liakhovetski wrote:
> Add device-tree bindings to the AS3711 regulator and backlight drivers.
Hi,
at this stage I do not expect this code to go through the renesas tree.
However, in order to provide a basis for work on renesas SoCs I have added
On Fri, 2013-02-15 at 18:11 -0800, H. Peter Anvin wrote:
> >
> > This switch should always be outside the funny NMI and debug zone.
> > I think you missed a patch that I sent you to deal with exactly this:
> >
> > https://lkml.org/lkml/2013/2/1/532
> >
> > I sent it directly to you, maybe it got
On Sat, Feb 16, 2013 at 01:50:24AM +, Al Viro wrote:
> On Fri, Feb 15, 2013 at 04:46:43PM -0800, Shentino wrote:
> > On Fri, Feb 15, 2013 at 4:38 PM, Shentino wrote:
> > > On Fri, Feb 15, 2013 at 4:04 PM, Al Viro wrote:
> > >> How would you manage to have it masked at that point?
This switch should always be outside the funny NMI and debug zone.
I think you missed a patch that I sent you to deal with exactly this:
https://lkml.org/lkml/2013/2/1/532
I sent it directly to you, maybe it got buried in your INBOX.
I saw it. It had a:
Not-yet-signed-off-by: Steven
This fixes an inconsistent behavior between list_voltage() and get_voltage()
because current implementation of get_voltage() does not check the case
IS_UNSUP() is true.
Signed-off-by: Axel Lin
---
drivers/regulator/twl-regulator.c |9 -
1 file changed, 4 insertions(+), 5
On Fri, 2013-02-15 at 16:09 -0800, H. Peter Anvin wrote:
> On 02/04/2013 02:49 PM, Seiji Aguchi wrote:
> > +
> > +static void switch_to_trace_idt(void *arg)
> > +{
> > + store_idt(this_cpu_ptr(_idt_descr));
> > + load_idt(_idt_descr);
> > +
> > + return;
> > +}
> > +
> > +static void
On 2013/2/13 18:07, Matt Fleming wrote:
>> In efi_init() memory aligns in IA64_GRANULE_SIZE(16M). If set
>> "crashkernel=1024M-:600M"
>> and use sparse memory model, when crash kernel booting it changes
>> [128M-728M] to [128M-720M].
>> But initrd memory is in [709M-727M], and virt_addr_valid()
Hi Linus,
If you're doing another RC, please grab these two. Otherwise I'll send
them off to -stable.
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus
This fixes a long standing problem where the btrfs scan ioctl was racing
with mkfs.btrfs and dropping dirty pages
On Fri, Feb 15, 2013 at 04:46:43PM -0800, Shentino wrote:
> On Fri, Feb 15, 2013 at 4:38 PM, Shentino wrote:
> > On Fri, Feb 15, 2013 at 4:04 PM, Al Viro wrote:
> >> How would you manage to have it masked at that point? setup_new_exec()
> >> is inevitable after success of flush_old_exec() and
On Fri, Feb 15, 2013 at 5:22 PM, Al Viro wrote:
>
> Fine by me - the variant I'd posted simply moved these calls in one
> place; I've no problem with replacing them with force_sig() (or
> force_sigsegv(SIGSEGV, current), for paranoia sake). OTOH, I'd probably
> prefer to make it a separate
On Fri, Feb 15, 2013 at 5:26 PM, Yinghai Lu wrote:
> On Fri, Feb 15, 2013 at 4:39 PM, Bjorn Helgaas wrote:
>> On Thu, Feb 14, 2013 at 5:50 PM, Yinghai Lu wrote:
>>> On Tue, Feb 12, 2013 at 12:22 PM, Rafael J. Wysocki wrote:
On Tuesday, February 12, 2013 11:11:23 AM Yinghai Lu wrote:
>
On Fri, Feb 15, 2013 at 4:39 PM, Bjorn Helgaas wrote:
> On Thu, Feb 14, 2013 at 5:50 PM, Yinghai Lu wrote:
>> On Tue, Feb 12, 2013 at 12:22 PM, Rafael J. Wysocki wrote:
>>> On Tuesday, February 12, 2013 11:11:23 AM Yinghai Lu wrote:
Peter Hurley found "irq 18 nobody cared" with pci-next,
On Fri, 2013-02-15 at 16:13 -0800, H. Peter Anvin wrote:
> How important is it that the tracepoint is *inside* the enter/exit
> handling? If not, it would be simpler to just do:
>
> smp_trace_irq_handler()
> {
> trace_irq_entry();
> smp_irq_handler();
> trace_irq_exit();
> }
>
On Fri, Feb 15, 2013 at 04:40:18PM -0800, Linus Torvalds wrote:
> On Fri, Feb 15, 2013 at 4:04 PM, Al Viro wrote:
> > On Fri, Feb 15, 2013 at 03:12:30PM -0800, Shentino wrote:
> >> > + send_sig(SIGSEGV, current, 0);
> >>
> >> This might be a stupid miscue on my part,
Hello,
On Fri, 15 Feb 2013 08:52:12 -0800, Eric Dumazet wrote:
> Driver is buggy, as TX completion can happen both from ndo_start_xmit()
> and a timer, and there is no spinlock or appropriate synchro.
Yes, it is a known issue. I did post a patch fixing the problem on
netdev@ a while ago [1],
On Fri, Feb 15, 2013 at 7:01 AM, Oleg Nesterov wrote:
> On 02/14, Mandeep Singh Baines wrote:
>>
>> This patch makes wait_for_dump_helpers() not to abort piping the core
>> dump data when the crashing process has received any but a fatal signal
>> (SIGKILL). The rationale is that a crashing
On Wed, Feb 13, 2013 at 5:59 AM, Rafael J. Wysocki wrote:
> On Tuesday, February 12, 2013 05:54:08 PM Yinghai Lu wrote:
>> On Tue, Feb 12, 2013 at 4:16 PM, Rafael J. Wysocki wrote:
>> > From: Rafael J. Wysocki
>> >
>> > After commit 1aeae82 (ACPI / PCI: avoid building pci_slot as module)
>> >
From: Ben Chan
Make wait_for_dump_helpers() not abort piping the core dump data when the
crashing process has received a non-fatal signal. The abort still occurs
in the case of SIGKILL.
Testing:
localhost ~ # echo "|/usr/bin/sleep 1d" > /proc/sys/kernel/core_pattern
localhost ~ # sleep 1d &
On Fri, Feb 15, 2013 at 4:38 PM, Shentino wrote:
> On Fri, Feb 15, 2013 at 4:04 PM, Al Viro wrote:
>> How would you manage to have it masked at that point? setup_new_exec()
>> is inevitable after success of flush_old_exec() and it will do
>> flush_signal_handlers() for us.
>
> I wouldn't know
On Sat, 16 Feb 2013, Al Viro wrote:
> > > + send_sig(SIGSEGV, current, 0);
> >
> > This might be a stupid miscue on my part, but shouldn't it be
> > force_sig instead of send_sig?
> >
> > I've got this crazy hunch that having SEGV masked might muck something up.
>
On Fri, Feb 15, 2013 at 4:04 PM, Al Viro wrote:
> On Fri, Feb 15, 2013 at 03:12:30PM -0800, Shentino wrote:
>> > + send_sig(SIGSEGV, current, 0);
>>
>> This might be a stupid miscue on my part, but shouldn't it be
>> force_sig instead of send_sig?
>>
>> I've got this
On Thu, Feb 14, 2013 at 5:50 PM, Yinghai Lu wrote:
> On Tue, Feb 12, 2013 at 12:22 PM, Rafael J. Wysocki wrote:
>> On Tuesday, February 12, 2013 11:11:23 AM Yinghai Lu wrote:
>>> Peter Hurley found "irq 18 nobody cared" with pci-next, and dmesg has
>>>
>>> [8.983246] pci :00:1e.0: can't
On Fri, Feb 15, 2013 at 4:04 PM, Al Viro wrote:
> How would you manage to have it masked at that point? setup_new_exec()
> is inevitable after success of flush_old_exec() and it will do
> flush_signal_handlers() for us.
I wouldn't know for sure but I read somewhere that even if execve
resets
Remove the printing of warning in case of failed mappings. Sometimes
they are expected as in case of Qemu mapping pages during HVM guest
creation.
Signed-off-by: Mukesh Rathor
---
arch/x86/xen/mmu.c |3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff --git a/arch/x86/xen/mmu.c
On 02/04/2013 02:50 PM, Seiji Aguchi wrote:
> [Issue]
>
> Currently, irq vector handlers for tracing are just
> copied non-trace handlers by simply inserting tracepoints.
>
> It is difficult to manage the codes.
>
> [Solution]
>
> This patch shares common codes between non-trace and trace
On 02/04/2013 02:49 PM, Seiji Aguchi wrote:
> +
> +static void switch_to_trace_idt(void *arg)
> +{
> + store_idt(this_cpu_ptr(_idt_descr));
> + load_idt(_idt_descr);
> +
> + return;
> +}
> +
> +static void restore_original_idt(void *arg)
> +{
> + if
From: Ben Chan
Make wait_for_dump_helpers() not abort piping the core dump data when the
crashing process has received a non-fatal signal. The abort still occurs
in the case of SIGKILL.
Addresses http://crosbug.com/21559
Changes since v1:
* Mandeep Singh Baines
* To prevent blocking
On Fri, Feb 15, 2013 at 03:12:30PM -0800, Shentino wrote:
> > + send_sig(SIGSEGV, current, 0);
>
> This might be a stupid miscue on my part, but shouldn't it be
> force_sig instead of send_sig?
>
> I've got this crazy hunch that having SEGV masked might muck
On Fri, 15 Feb 2013 17:39:38 -0600
Nathan Zimmer wrote:
> > So are all these games with local variable `llseek' still needed?
> > afaict the increment of pde_users will stabilize ->fops?
> We still are setting de->proc_fops to NULL to prevent new callers.
> Also we still have to save fops->
On Fri, 15 Feb 2013 18:13:04 -0500
Johannes Weiner wrote:
> On Fri, Feb 15, 2013 at 01:27:38PM -0800, Andrew Morton wrote:
> > On Fri, 15 Feb 2013 01:34:50 -0500
> > Johannes Weiner wrote:
> >
> > > + * The status is returned in a vector of bytes. The least significant
> > > + * bit of each
On 02/15/2013 04:12 PM, Andrew Morton wrote:
On Fri, 15 Feb 2013 14:47:54 -0600
Nathan Zimmer wrote:
I am currently tracking a hotlock reported by a customer on a large system,
512 cores. I am currently running 3.8-rc7 but the issue looks like it has been
this way for a very long time.
The
This series is an attempt to define a common way for devicetree
initialized power_supplies to define their list of supplicants
in a common manner.
Instead of relying on custom properties which contain is list of
strings, use the much more direct method of phandles to reference
the supplicants and
With the addition of the device_nodes to use similar to how
supplied_to works, add a helper function which will parse out the
phandles for the supplied-nodes directly from the node. This
implmentation requires the property name to be "supplied-nodes".
Signed-off-by: Rhyland Klein
---
With the growing support for dt, it make sense to try to make sure of
dt features as to make the general code cleaner. This patch is an
attempt to commonize how chargers receive their "supplied_to" list
of supplicants. This was previously done via passing an array of
strings.
Currently, charger
This property is meant to be used in device nodes which represent
power_supply devices that wish to provide a list of supplies to
which they provide power. A common case is a AC Charger with
the batteries it powers.
Signed-off-by: Rhyland Klein
---
.../bindings/power_supply/power_supply.txt
Zhang Rui intel.com> writes:
>
> Hi, Roberto,
>
> please attach the acpidump output.
>
> On Tue, 2012-12-04 at 13:57 +0100, Roberto Oppedisano wrote:
> > Hello,
> > with recent kernels after a suspend/resume cycle on my laptop (HP
> > 6730b) the fans stays at full speed.
> does the fan
On Thu, 14 Feb 2013 15:38:14 -0800
Mandeep Singh Baines wrote:
> Replace the for loop with a simple if.
Well OK, but why? Presumably the loop was added for a reason and
presumably you believe that reason to be (no longer?) correct. Please
describe all these things.
> --- a/kernel/exit.c
>
On Thu, 14 Feb 2013 15:38:16 -0800
Mandeep Singh Baines wrote:
> From: Ben Chan
>
> This patch makes wait_for_dump_helpers() not to abort piping the core
> dump data when the crashing process has received any but a fatal signal
> (SIGKILL). The rationale is that a crashing process may still
Wolfram,
On Fri, Feb 15, 2013 at 11:53 AM, Wolfram Sang wrote:
>
>> I'll re-send with I2C subsystem wide. I probably won't attempt the
>> whole kernel wide at this point, but would be very happy if someone
>> else wanted to! :)
>
> Thanks. Please double check that setting NULL is really
On Fri, 15 Feb 2013 16:45:38 +0900
Jingoo Han wrote:
> Fixed build warning as below:
>
> drivers/rtc/rtc-max77686.c: In function 'max77686_rtc_update':
> drivers/rtc/rtc-max77686.c:147:6: warning: 'data' may be used uninitialized
> in this function [-Wuninitialized]
>
> Signed-off-by: Jingoo
1 - 100 of 1276 matches
Mail list logo
