On (10/25/12 00:32), Frederic Weisbecker wrote:
> > My understanding is (I may be wrong) that we can schedule() from ptrace
> > chain to
> > some arbitrary task, which will continue its execution from the point where
> > RCU assumes
> > CPU as not idle, while CPU in fact still in idle state --
On (10/25/12 00:32), Frederic Weisbecker wrote:
> First of all, thanks a lot for your report.
>
> 2012/10/24 Sergey Senozhatsky :
> > On (10/24/12 20:06), Oleg Nesterov wrote:
> >> On 10/24, Sergey Senozhatsky wrote:
> >> >
> >> > small question,
> >> >
> >> > ptrace_notify() and forward calls
Nobody use struct CsrEvent. Remove it.
Signed-off-by: SeongJae Park
---
drivers/staging/csr/csr_framework_ext_types.h | 14 --
1 file changed, 14 deletions(-)
diff --git a/drivers/staging/csr/csr_framework_ext_types.h
b/drivers/staging/csr/csr_framework_ext_types.h
index
Nobody use CsrEventHandle, Nobody call function using it as parameter.
So, remove it.
Signed-off-by: SeongJae Park
---
drivers/staging/csr/csr_framework_ext.h | 61 -
drivers/staging/csr/csr_framework_ext_types.h |2 -
2 files changed, 63 deletions(-)
diff
On Wed, 2012-10-24 at 13:19 -0400, Vivek Goyal wrote:
> On Tue, Oct 23, 2012 at 09:44:59AM -0700, Eric W. Biederman wrote:
> > Matthew Garrett writes:
> >
> > > On Tue, Oct 23, 2012 at 10:59:20AM -0400, Vivek Goyal wrote:
> > >
> > >> But what about creation of a new program which can call
On Wed, Oct 24, 2012 at 03:03:00PM -0700, da...@lang.hm wrote:
> Like what is being described for sqlite, loosing the tail end of the
> messages is not a big problem under normal conditions. But there is
> a need to be sure that what is there is complete up to the point
> where it's lost.
>
>
Hi Linus,
I would like to ask for pulling some minor fixes for both CMA
(Contiguous Memory Allocator) and DMA-mapping framework for v3.7-rc3.
The following changes since commit 6f0c0580b70c89094b3422ba81118c7b959c7556:
Linux
Hi, Folks
Charles has raised a problem that we don't have any tool yet
for testing the scheduler with out any disturb from other
subsystem, and I also found it's hard to test scheduler optimize
patch, since the improvement could be easily eaten by other
subsystem like IO.
So Let's check the
> this is v2 of a patchset already submitted on 2012/09/12
Thanks Davide.
For the whole series:
Acked-by: Alessandro Rubini
/alessandro
--
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
Hello,
On 10/24/2012 3:49 PM, Gregory CLEMENT wrote:
For Armada 370/XP we have the same problem that for the commit
cb01b63, so we applied the same solution: "The default 256 KiB
coherent pool may be too small for some of the Kirkwood devices, so
increase it to make sure that devices will be
On Tue, Oct 23, 2012 at 10:06:52AM -0700, Justin P. Mattock wrote:
> This is happening both with MAINLINE and NEXT.
>
> basically system is running fine, then under load system becomes
> really sluggish and unresponsive. I was able to get dmesg of the
> error..:
>
> [ 7745.007008] ath9k
On Wed, Oct 24, 2012 at 11:53 PM, Juri Lelli wrote:
> +#ifdef __SIZEOF_INT128__ /* gcc-4.6+ */
> + unsigned __int128 val;
> +#endif
So the definition of val depends on (gcc) __SIZEOF_INT128__...
> +/*
> + * Make usage of __int128 dependent on arch code so they can
> + * judge if gcc is
On Wed, Oct 24, 2012 at 8:04 PM, wrote:
> On Wed, 24 Oct 2012, Nico Williams wrote:
>> COW is "copy on write", which is actually a bit of a misnomer -- all
>> COW means is that blocks aren't over-written, instead new blocks are
>> written. In particular this means that inodes, indirect blocks,
On Tue, Oct 23, 2012 at 03:53:11PM -0400, Vladislav Bolkhovitin wrote:
> Yes, SCSI has full support for ordered/simple commands designed
> exactly for that task: to have steady flow of commands even in case
> when some of them are ordered.
SCSI does, yes --- *if* the device actually
On 10/25/2012 12:36 PM, Hugh Dickins wrote:
On Wed, 24 Oct 2012, Dave Jones wrote:
Machine under significant load (4gb memory used, swap usage fluctuating)
triggered this...
WARNING: at mm/shmem.c:1151 shmem_getpage_gfp+0xa5c/0xa70()
Pid: 29795, comm: trinity-child4 Not tainted 3.7.0-rc2+ #49
On 10/24/2012 01:24 PM, Dave Jones wrote:
> I've been able to trigger this for the last week or so.
> Unclear whether this is a new bug, or my fuzzer got smarter, but I see the
> pi-futex code hasn't changed since the last time it found something..
>
> > BUG: unable to handle kernel NULL
On 25 October 2012 10:06, Darren Hart wrote:
> Absolutely, that was great. Siddhesh, any objection to this test being
> incorporated into futextest?
>
> http://git.kernel.org/?p=linux/kernel/git/dvhart/futextest.git;a=summary
>
I have no objection to the test being incorporated into futextest.
On 10/24/2012 11:08 AM, Thomas Gleixner wrote:
> On Wed, 24 Oct 2012, Siddhesh Poyarekar wrote:
>
>>> Now there is a different solution to that problem. Do not look at the
>>> user space value at all and enforce a lookup of possibly available
>>> pi_state. If pi_state can be found, then the new
On Wed, 24 Oct 2012, Dave Jones wrote:
> Machine under significant load (4gb memory used, swap usage fluctuating)
> triggered this...
>
> WARNING: at mm/shmem.c:1151 shmem_getpage_gfp+0xa5c/0xa70()
> Pid: 29795, comm: trinity-child4 Not tainted 3.7.0-rc2+ #49
> Call Trace:
> []
On 10/23/2012 01:29 PM, Thomas Gleixner wrote:
> Darren, Siddhesh,
>
> On Tue, 23 Oct 2012, Darren Hart wrote:
>
>> Hi Siddesh,
>>
>> Thanks for the patch and your work to isolate it in the glibc bug 14076.
>>
>> On 10/21/2012 08:20 PM, Siddhesh Poyarekar wrote:
>>> In futex_lock_pi_atomic, we
Hi Dmitry,
Thanks for review.
> -Original Message-
> From: Dmitry Torokhov [mailto:dmitry.torok...@gmail.com]
> Sent: Thursday, October 25, 2012 2:13 AM
> To: Scott Liu
> Cc: linux-in...@vger.kernel.org; linux-...@vger.kernel.org;
linux-kernel@vger.kernel.org;
> Benjamin
Hi Chen,
> But how can bdi related ra_pages reflect different files' readahead
> window? Maybe these different files are sequential read, random read
> and so on.
It's simple: sequential reads will get ra_pages readahead size while
random reads will not get readahead at all.
Talking about the
On 25 October 2012 09:39, Shiraz Hashim wrote:
> Add support for PWM chips present on SPEAr platforms. These PWM
> chips support 4 channel output with programmable duty cycle and
> frequency.
>
> More details on these PWM chips can be obtained from relevant
> chapter of reference manual, present
On Wed, Oct 24, 2012 at 5:43 AM, Lai Jiangshan wrote:
> Currently memory_hotplug only manages the node_states[N_HIGH_MEMORY],
> it forgets to manage node_states[N_NORMAL_MEMORY]. it may cause
> node_states[N_NORMAL_MEMORY] becomes incorrect.
>
> Example, if a node is empty before online, and we
Add support for PWM chips present on SPEAr platforms. These PWM
chips support 4 channel output with programmable duty cycle and
frequency.
More details on these PWM chips can be obtained from relevant
chapter of reference manual, present at following[1] location.
1.
On Wed, Oct 24, 2012 at 07:51:37AM +0200, Thierry Reding wrote:
> On Mon, Oct 22, 2012 at 04:36:41PM +0530, Shiraz Hashim wrote:
> [...]
> > +struct spear_pwm_chip {
> > + void __iomem *mmio_base;
> > + struct clk *clk;
> > + struct pwm_chip chip;
>
> My editor shows a tab between pwm_chip
On Wed, Oct 24, 2012 at 04:20:32PM -0700, Kees Cook wrote:
> If a series of scripts are executed, each triggering module loading via
> unprintable bytes in the script header, kernel stack contents can leak
> into the command line.
>
> Normally execution of binfmt_script and binfmt_misc happens
>
Hi all,
Changes since 201201024:
New tree: akpm-current
The modules tree lost its conflict.
The pm tree lost its build failure.
The usb tree gained a conflict against the usb.current tree.
The staging tree gained a conflict against the staging.current tree.
The akpm tree lost its 2 build
From: Wen Congyang
The guest should run after reseting it, but it does not run if its
old state is RUN_STATE_INTERNAL_ERROR or RUN_STATE_PAUSED.
We don't set runstate to RUN_STATE_PAUSED when reseting the guest,
so the runstate will be changed from RUN_STATE_INTERNAL_ERROR or
RUN_STATE_PAUSED
[...]
>> /*
>> + * Thermal Sensor
>> + */
>> +
>> +static struct resource db8500_thsens_resources[] = {
>> + {
>> + .name = "IRQ_HOTMON_LOW",
>> + .start = IRQ_PRCMU_HOTMON_LOW,
>> + .end= IRQ_PRCMU_HOTMON_LOW,
>> + .flags =
Make this generic variable more specific to the printk
subsystem to allow this variable to be used without
a specific extern.
Also update fs/proc/kmsg.c as it uses log_wait.
Signed-off-by: Joe Perches
---
fs/proc/kmsg.c |4 ++--
kernel/printk/printk.c | 12 ++--
2 files
This event will be emited when the guest is panicked.
Signed-off-by: Wen Congyang
---
monitor.c |1 +
monitor.h |1 +
2 files changed, 2 insertions(+)
diff --git a/monitor.c b/monitor.c
index d17ae2d..d2e4bbf 100644
--- a/monitor.c
+++ b/monitor.c
@@ -457,6 +457,7 @@ static const char
在 2012-10-24三的 02:43 -0700，tip-bot for Paul Turner写道：
> Commit-ID: 9d85f21c94f7f7a84d0ba686c58aa6d9da58fdbb
> Gitweb: http://git.kernel.org/tip/9d85f21c94f7f7a84d0ba686c58aa6d9da58fdbb
> Author: Paul Turner
> AuthorDate: Thu, 4 Oct 2012 13:18:29 +0200
> Committer: Ingo Molnar
>
Generic restructuring.
Create kmsg_dump.c, add to Makefile and remove from printk.c
Signed-off-by: Joe Perches
---
kernel/printk/Makefile|1 +
kernel/printk/kmsg_dump.c | 328 +
kernel/printk/printk.c| 318
Move syslog functions to a separate file.
Add compilation unit to Makefile.
Add missing #include
Reported-by: Yuanhan Liu
Signed-off-by: Joe Perches
---
kernel/printk/Makefile|1 +
kernel/printk/printk.c| 351 +
Move these functions to printk_log.
Move the static function print_prefix too.
Add "#include " to printk_log.c.
Signed-off-by: Joe Perches
---
kernel/printk/printk.c | 112 ---
kernel/printk/printk_log.c | 114
Make these static functions global and prefix them with printk_.
Create declarations for these functions in printk_log.h
Signed-off-by: Joe Perches
---
kernel/printk/printk.c | 43 ---
kernel/printk/printk_log.h |4
2 files changed, 28
Move the devkmsg_ functions and kmsg_fops declaration
to devkmsg.c.
Add devkmsg.o to Makefile.
Signed-off-by: Joe Perches
---
kernel/printk/Makefile |1 +
kernel/printk/devkmsg.c | 309 +++
kernel/printk/printk.c | 296
Rename the LOG_LINE_MAX and PREFIX_MAX #defines with PRINTK_ prefixes.
Move the defines to printk_log.h
Remove duplicate define too.
Fixed redefined PRINTK_LOG_LINE_MAX and PRINTK_PREFIX_MAX.
Reported-by: Yuanhan Liu
Signed-off-by: Joe Perches
---
kernel/printk/printk.c | 22
Move the variable to the .h file too.
Signed-off-by: Joe Perches
---
kernel/printk/printk_log.h |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/kernel/printk/printk_log.h b/kernel/printk/printk_log.h
index 0327f8d..e846f1d 100644
--- a/kernel/printk/printk_log.h
+++
Move print_log variables and functions into a separate file.
Signed-off-by: Joe Perches
---
kernel/printk/Makefile |1 +
kernel/printk/printk.c | 128 -
kernel/printk/printk_log.c | 149
3 files
Create a header file for printk_log functions and variables.
Signed-off-by: Joe Perches
---
kernel/printk/printk.c | 91 +--
kernel/printk/printk_log.h | 115
2 files changed, 116 insertions(+), 90 deletions(-)
On 24 October 2012 22:32, Joe Perches wrote:
> On Wed, 2012-10-24 at 19:58 +0800, hongbo.zhang wrote:
>> This patch adds device tree properties for ST-Ericsson DB8500 thermal driver,
>> also adds the platform data to support the old fashion.
>
> Just a trivial note:
>
>> diff --git
Make the #define more specific to the printk subsystem.
Signed-off-by: Joe Perches
---
kernel/printk/printk.c |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
index 0134b2e..bc0b4ed 100644
---
Allow a separation of functions and variables into
multiple files.
Signed-off-by: Joe Perches
---
kernel/printk/printk.c | 46 +++---
1 files changed, 23 insertions(+), 23 deletions(-)
diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
index
Make these variables more specific to the printk log subsystem
adding prefix printk_log_. This allows them to become non-static.
Signed-off-by: Joe Perches
---
kernel/printk/printk.c | 34 +-
1 files changed, 17 insertions(+), 17 deletions(-)
diff --git
Make this generic name more specific to the printk
subsystem and allow it to become non-static.
Signed-off-by: Joe Perches
---
kernel/printk/printk.c | 102
1 files changed, 51 insertions(+), 51 deletions(-)
diff --git a/kernel/printk/printk.c
Make this generic enum more specific to the printk subsystem.
Signed-off-by: Joe Perches
---
kernel/printk/printk.c | 32 +---
1 files changed, 17 insertions(+), 15 deletions(-)
diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
index 992c064..341f2d9
Make these generic names more specific to the printk
subsystem and allow these variables and functions to
become non-static.
Rename log_text to printk_log_text.
Rename log_dict to printk_log_dict.
Rename log_from_idx to printk_log_from_idx.
Rename log_next to printk_log_next.
Rename log_store to
Make these generic names more specific to the printk
subsystem and allow these variables to become non-static.
Rename log_first_idx to printk_log_first_idx.
Rename log_first_seq to printk_log_first_seq.
Rename log_next_idx to printk_log_next_idx.
Rename log_next_seq to printk_log_next_seq.
Make these generic names more specific to the printk
subsystem and allow these variables to become non-static.
Rename log_buf to printk_log_buf.
Rename __LOG_BUF_LEN define to __PRINTK_LOG_BUF_LEN.
Signed-off-by: Joe Perches
---
kernel/printk/printk.c | 76
Rename the struct to enable moving portions of
printk.c to separate files.
The rename changes output of /proc/vmcoreinfo.
Signed-off-by: Joe Perches
---
kernel/printk/printk.c | 80
1 files changed, 40 insertions(+), 40 deletions(-)
diff
Make the code a bit more compact by always using a pointer
for the active console_cmdline.
Move overly indented code to correct indent level.
Signed-off-by: Joe Perches
---
kernel/printk/printk.c | 49 +--
1 files changed, 26 insertions(+), 23
Create files with prototypes and static inlines for braille
support. Make braille_console functions return 1 on success.
Corrected CONFIG_A11Y_BRAILLE_CONSOLE=n _braille_console_setup
return value to NULL.
link:
http://lkml.kernel.org/r/1350999678-17441-1-git-send-email-ming@canonical.com
Add an include file for the console_cmdline struct
so that the braille console driver can be separated.
Signed-off-by: Joe Perches
---
kernel/printk/console_cmdline.h | 14 ++
kernel/printk/printk.c | 13 -
2 files changed, 18 insertions(+), 9 deletions(-)
Make it easier to break up printk into bite-sized chunks.
Remove printk path/filename from comment.
Signed-off-by: Joe Perches
---
kernel/Makefile |3 ++-
kernel/printk/Makefile |1 +
kernel/{ => printk}/printk.c |2 --
3 files changed, 3 insertions(+), 3
Make printk a bit more readable.
Created directory:
kernel/printk
Created source files:
printk.cGeneric printk and console routines
printk_log.[ch] Log buffer routines
printk_syslog.[ch] syslog(2) routines
braille.c
If the target is x86/x86_64, the guest's kernel will write 0x01 to the
port KVM_PV_EVENT_PORT when it is panciked. This patch introduces a new
qom device kvm_pv_ioport to listen this I/O port, and deal with panicked
event according to panicked_action's value. The possible actions are:
1. emit
From: Wen Congyang
Signed-off-by: Wen Congyang
---
hw/pc_piix.c|6 +-
qemu-config.c |4
qemu-options.hx |3 ++-
3 files changed, 11 insertions(+), 2 deletions(-)
diff --git a/hw/pc_piix.c b/hw/pc_piix.c
index fb67dc1..864d356 100644
--- a/hw/pc_piix.c
+++
Hi Andrew,
On Wed, 24 Oct 2012 17:16:27 -0700 a...@linux-foundation.org wrote:
>
> The mm-of-the-moment snapshot 2012-10-24-17-15 has been uploaded to
>
>http://www.ozlabs.org/~akpm/mmotm/
I have split this series so that all the next tagged patches before
linux-next.patch are in the
From: Wen Congyang
The guest will be in this state when it is panicked.
Signed-off-by: Wen Congyang
---
qapi-schema.json |6 +-
qmp.c|3 ++-
vl.c |7 ++-
3 files changed, 13 insertions(+), 3 deletions(-)
diff --git a/qapi-schema.json
We can know the guest is panicked when the guest runs on xen.
But we do not have such feature on kvm.
Another purpose of this feature is: management app(for example:
libvirt) can do auto dump when the guest is panicked. If management
app does not do auto dump, the guest's user can do dump by hand
update kernel headers to add pv event macros.
Signed-off-by: Wen Congyang
Signed-off-by: Hu Tao
---
linux-headers/asm-x86/kvm_para.h |1 +
linux-headers/linux/kvm_para.h |6 ++
2 files changed, 7 insertions(+)
diff --git a/linux-headers/asm-x86/kvm_para.h
Hi Andrew,
After merging the akpm tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
mm/rmap.c: In function 'try_to_unmap_cluster':
mm/rmap.c:1364:9: warning: unused variable 'pud' [-Wunused-variable]
mm/rmap.c:1363:9: warning: unused variable 'pgd' [-Wunused-variable]
On 10/24/2012 05:38 PM, Peter Zijlstra wrote:
> On Wed, 2012-10-24 at 17:25 +0800, Huacai Chen wrote:
>> We found poweroff sometimes fails on our computers, so we have the
>> lock debug options configured. Then, when we do poweroff or take a
>> cpu down via cpu-hotplug, kernel complain as below.
Hi Andrew,
On Thu, 25 Oct 2012 14:28:54 +1100 Stephen Rothwell
wrote:
>
> After merging the akpm tree, today's linux-next build (powerpc
> ppc64_defconfig) produced these warnings:
>
> drivers/infiniband/hw/cxgb3/cxio_resource.c: In function
> '__cxio_init_resource_fifo':
>
Hi Andrew,
After merging the akpm tree, today's linux-next build (powerpc
ppc64_defconfig) produced these warnings:
drivers/infiniband/hw/cxgb3/cxio_resource.c: In function
'__cxio_init_resource_fifo':
drivers/infiniband/hw/cxgb3/cxio_resource.c:62:3: warning: comparison of
distinct pointer
> Subject: Re: [PATCH] extcon : callback function to read cable property
>
> On 10/19/2012 12:13 PM, Tc, Jenny wrote:
> >
> >
> >> Subject: Re: [PATCH] extcon : callback function to read cable
> >> property
> >>
> >> I think the reason why we have extcon is in first place is to
On Thu, Oct 25, 2012 at 10:58 AM, Fengguang Wu wrote:
> Hi Chen,
>
>> But how can bdi related ra_pages reflect different files' readahead
>> window? Maybe these different files are sequential read, random read
>> and so on.
>
> It's simple: sequential reads will get ra_pages readahead size while
On Thu, Oct 25, 2012 at 10:38 AM, Fengguang Wu wrote:
> Hi YingHang,
>
>> Actually I've talked about it with Fengguang, he advised we should unify the
>> ra_pages in struct bdi and file_ra_state and leave the issue that
>> spreading data
>> across disks as it is.
>> Fengguang, what's you opinion
On Mon, 22 Oct 2012, Mel Gorman wrote:
> The compact_pages_moved and compact_pagemigrate_failed events are
> convenient for determining if compaction is active and to what
> degree migration is succeeding but it's at the wrong level. Other
> users of migration may also want to know if migration
This patch introudce new madvise behavior MADV_VOLATILE and
MADV_NOVOLATILE for anonymous pages. It's different with
John Stultz's version which considers only tmpfs. This patch
cannot cover John's one so if below idea is proved as reasonable
maybe, we can unify both concepts and I hope interface
Hi Rusty,
Thank you for your review of my patch and improvement for it.
>So I prefer the following fix:
I also prefer your way of fix from readability point of view.
I tested your patch and confirmed that it works fine.
Best Regards,
Masaki
--
To unsubscribe from this list: send the line
Hi Randy,
On Wed, 24 Oct 2012 18:17:59 -0700 Randy Dunlap wrote:
>
> uml on x86_64 defconfig:
>
> arch/um/drivers/chan_kern.c: In function 'tty_receive_char':
> arch/um/drivers/chan_kern.c:89:42: error: 'struct tty_struct' has no member
> named 'raw'
Caused by commit 53c5ee2cfb4d ("TTY: move
On Thu, Oct 25, 2012 at 11:43 AM, Greg Kroah-Hartman
wrote:
> On Thu, Oct 25, 2012 at 11:23:13AM +0900, YAMANE Toshiaki wrote:
>> fixed below checkpatch warning.
>> - WARNING: Prefer netdev_warn(netdev, ... then dev_warn(dev, ... then
>> pr_warn(... to printk(KERN_WARNING ...
>>
>> some of them
On Thu, Oct 25, 2012 at 11:23:13AM +0900, YAMANE Toshiaki wrote:
> fixed below checkpatch warning.
> - WARNING: Prefer netdev_warn(netdev, ... then dev_warn(dev, ... then
> pr_warn(... to printk(KERN_WARNING ...
>
> some of them have been replaced by dev_dbg or pr_debug,
> and added pr_fmt.
>
Hi YingHang,
> Actually I've talked about it with Fengguang, he advised we should unify the
> ra_pages in struct bdi and file_ra_state and leave the issue that
> spreading data
> across disks as it is.
> Fengguang, what's you opinion about this?
Yeah the two ra_pages may run out of sync for
Machine under significant load (4gb memory used, swap usage fluctuating)
triggered this...
WARNING: at mm/shmem.c:1151 shmem_getpage_gfp+0xa5c/0xa70()
Pid: 29795, comm: trinity-child4 Not tainted 3.7.0-rc2+ #49
Call Trace:
[] warn_slowpath_common+0x7f/0xc0
[] warn_slowpath_null+0x1a/0x20
[]
On Thu, Oct 25, 2012 at 10:12 AM, Ni zhan Chen wrote:
> On 10/25/2012 10:04 AM, YingHang Zhu wrote:
>>
>> On Thu, Oct 25, 2012 at 9:50 AM, Dave Chinner wrote:
>>>
>>> On Thu, Oct 25, 2012 at 08:17:05AM +0800, YingHang Zhu wrote:
On Thu, Oct 25, 2012 at 4:19 AM, Dave Chinner
Hello Pekka,
Thanks for taking a look into this!
On Wed, Oct 24, 2012 at 12:03:10PM +0300, Pekka Enberg wrote:
> On Mon, 22 Oct 2012, Anton Vorontsov wrote:
> > This patch introduces VMEVENT_ATTR_PRESSURE, the attribute reports Linux
> > virtual memory management pressure. There are three
fixed below checkpatch warning.
- WARNING: Prefer netdev_warn(netdev, ... then dev_warn(dev, ... then
pr_warn(... to printk(KERN_WARNING ...
some of them have been replaced by dev_dbg or pr_debug,
and added pr_fmt.
Signed-off-by: YAMANE Toshiaki
---
drivers/staging/comedi/drivers/gsc_hpdi.c
Hi Greg,
Today's linux-next merge of the staging tree got a conflict in
drivers/staging/comedi/drivers/amplc_dio200.c between commit dfb2540e91e1
("staging: comedi: amplc_dio200: fix possible NULL deref during detach")
from the staging.current tree and commit 71b3e9e8dc21 ("staging: comedi:
On Thu, Oct 25, 2012 at 01:05:45PM +1100, Stephen Rothwell wrote:
> Hi Greg,
>
> Today's linux-next merge of the usb tree got a conflict in
> drivers/usb/misc/ezusb.c between commit 197ef5ef37d9 ("USB: Add missing
> license tag to ezusb driver") from the usb.current tree and commitc
> 30186e51e53
On 10/25/2012 10:04 AM, YingHang Zhu wrote:
On Thu, Oct 25, 2012 at 9:50 AM, Dave Chinner wrote:
On Thu, Oct 25, 2012 at 08:17:05AM +0800, YingHang Zhu wrote:
On Thu, Oct 25, 2012 at 4:19 AM, Dave Chinner wrote:
On Wed, Oct 24, 2012 at 07:53:59AM +0800, YingHang Zhu wrote:
Hi Dave,
On Wed,
On Thu, Oct 25, 2012 at 6:50 AM, Arnaldo Carvalho de Melo
wrote:
> From: Borislav Petkov
>
> There's a portion in the "perf list" output refering to the exact
> specification of raw hardware events.
>
> Since this description is in the perf-list manpage, try to build and
> install the man pages,
Hi Greg,
Today's linux-next merge of the usb tree got a conflict in
drivers/usb/misc/ezusb.c between commit 197ef5ef37d9 ("USB: Add missing
license tag to ezusb driver") from the usb.current tree and commitc
30186e51e53 ("USB: ezusb: unexport some functions that aren't being
used") from the usb
On Thu, Oct 25, 2012 at 9:50 AM, Dave Chinner wrote:
> On Thu, Oct 25, 2012 at 08:17:05AM +0800, YingHang Zhu wrote:
>> On Thu, Oct 25, 2012 at 4:19 AM, Dave Chinner wrote:
>> > On Wed, Oct 24, 2012 at 07:53:59AM +0800, YingHang Zhu wrote:
>> >> Hi Dave,
>> >> On Wed, Oct 24, 2012 at 6:47 AM,
Resending a patch by changing a subject from "PATCH 2/5" to "PATCH v2 2/5".
[Issue]
Currently, efi_pstore driver simply overwrites existing panic messages in NVRAM.
So, in the following scenario, we will lose 1st panic messages.
1. kernel panics.
2. efi_pstore is kicked and writes panic
[Issue]
Currently, a variable name, which identifies each entry, consists of type, id
and ctime.
But if multiple events happens in a short time, a second/third event may fail
to log because
efi_pstore can't distinguish each event with current variable name.
[Solution]
A reasonable way to
[Issue]
Currently, a variable name, which is used to identify each log entry, consists
of type,
id and ctime. But an erase callback does not use ctime.
If efi_pstore supported just one log, type and id were enough.
However, in case of supporting multiple logs, it doesn't work because
it can't
[Issue]
Currently, efi_pstore driver simply overwrites existing panic messages in NVRAM.
So, in the following scenario, we will lose 1st panic messages.
1. kernel panics.
2. efi_pstore is kicked and writes panic messages to NVRAM.
3. system reboots.
4. kernel panics again before a user checks
[Issue]
Currently, efi_pstore driver simply overwrites existing panic messages in NVRAM.
So, in the following scenario, we will lose 1st panic messages.
1. kernel panics.
2. efi_pstore is kicked and writes panic messages to NVRAM.
3. system reboots.
4. kernel panics again before a user
[Issue]
As discussed in a thread below, Running out of space in EFI isn't a well-tested
scenario.
And we wouldn't expect all firmware to handle it gracefully.
http://marc.info/?l=linux-kernel=134305325801789=2
On the other hand, current efi_pstore doesn't check a remaining space of
storage at
On Thu, Oct 25, 2012 at 08:17:05AM +0800, YingHang Zhu wrote:
> On Thu, Oct 25, 2012 at 4:19 AM, Dave Chinner wrote:
> > On Wed, Oct 24, 2012 at 07:53:59AM +0800, YingHang Zhu wrote:
> >> Hi Dave,
> >> On Wed, Oct 24, 2012 at 6:47 AM, Dave Chinner wrote:
> >> > On Tue, Oct 23, 2012 at 08:46:51PM
Changelog
v1 -> v2
- Separate into 5 patches in accordance with Mike's comment
- Erase an extra line of comment in patch 1/5
[Issue]
Currently, efi_pstore driver simply overwrites existing panic messages in
NVRAM.
So, in the following scenario, we will lose 1st panic messages.
On 10/25/2012 08:17 AM, YingHang Zhu wrote:
On Thu, Oct 25, 2012 at 4:19 AM, Dave Chinner wrote:
On Wed, Oct 24, 2012 at 07:53:59AM +0800, YingHang Zhu wrote:
Hi Dave,
On Wed, Oct 24, 2012 at 6:47 AM, Dave Chinner wrote:
On Tue, Oct 23, 2012 at 08:46:51PM +0800, Ying Zhu wrote:
Hi,
On 2012-10-25 9:31, Tang Chen wrote:
> Hi Toshi,
>
> On 10/25/2012 01:14 AM, Toshi Kani wrote:
>> On Wed, 2012-10-24 at 14:05 +0800, Tang Chen wrote:
>>> +static int container_device_remove(struct acpi_device *device)
>>> +{
>>> +int ret;
>>> +struct acpi_eject_event *ej_event;
>>> +
>>>
On 25 Oct 2012, Theodore Ts'o stated:
> On Thu, Oct 25, 2012 at 12:27:02AM +0100, Nix wrote:
>>
>> - /sbin/reboot -f of running system
>>-> Journal replay, no problems other than the expected free block
>> count problems. This is not such a severe problem after all!
>>
>> - Normal
In
https://bugzilla.kernel.org/show_bug.cgi?id=48981
Peter reported that /proc/bus/pci/??/??.? does not works for 3.6.
This is This is because the device configuration space registers will
be not accessible if the corresponding parent bridge is suspended or
the device is put into D3cold state.
Hi Toshi,
On 10/25/2012 01:14 AM, Toshi Kani wrote:
On Wed, 2012-10-24 at 14:05 +0800, Tang Chen wrote:
+static int container_device_remove(struct acpi_device *device)
+{
+ int ret;
+ struct acpi_eject_event *ej_event;
+
+ /* stop container device at first */
+ ret =
1 - 100 of 1718 matches
Mail list logo
