Hi Gu,
> Hi Yuan,
> On 10/08/2013 07:30 PM, Yuan Zhong wrote:
>
>> Hi Gu,
>>
>>> Hi Yuan,
>>> On 10/08/2013 04:30 PM, Yuan Zhong wrote:
>>
Previously, do_checkpoint() will call congestion_wait() for waiting the
pages (previous submitted node/meta/data pages) to be written back.
Hi Andrew,
On 10/09/2013 01:44 AM, Andrew Morton wrote:
> On Tue, 8 Oct 2013 13:16:26 +0530 Vineet Gupta
> wrote:
>
>> When debugging a ARC SMP 3.11 build failure due to a ST insn dealing with
>> task_struct.thread going out of range, I spotted @fpu_counter in task_struct
>> which only SH/x86
Because dev_*() are used along with pr_debug() function in this code,
the debug message is not tidy. This patch converts from pr_debug() to
dev_dbg() since dev_*() are encouraged to use in device driver code.
Signed-off-by: Sangjung Woo
---
drivers/rtc/rtc-puv3.c | 20 ++--
1
On Tue, Oct 08, 2013 at 10:32:27PM -0700, Joe Perches wrote:
> Currently, devm_ managed memory only supports kzalloc.
>
> Convert the devm_kzalloc implementation to devm_kmalloc
> and remove the complete memset to 0 but still set the
> initial struct devres header and whatever padding before
>
On Sun, 6 Oct 2013, Sebastian Reichel wrote:
> This patch adds Synchronous Serial Interface (SSI) hwmod support for
> OMAP34xx SoCs.
>
> Signed-off-by: Sebastian Reichel
Thanks, queued this one for v3.13. You can drop it from any future
reposts of this series.
- Paul
--
To unsubscribe from
add multiple burst size support for 910-squ.
Signed-off-by: Qiao Zhou
---
drivers/dma/mmp_tdma.c | 25 -
1 files changed, 24 insertions(+), 1 deletions(-)
diff --git a/drivers/dma/mmp_tdma.c b/drivers/dma/mmp_tdma.c
index 38cb517..d84354b 100644
---
v1: add multiple burst size support. remove previous fixed 32-byte setting.
Qiao Zhou (1):
dma: mmp_tdma: add multiple burst size support for 910-squ
drivers/dma/mmp_tdma.c | 25 -
1 files changed, 24 insertions(+), 1 deletions(-)
--
To unsubscribe from this list:
From: Vineet Gupta
Only a couple of arches (sh/x86) use fpu_counter in task_struct so it
can be moved out into ARCH specific thread_struct, reducing the size of
task_struct for other arches.
Compile tested i386_defconfig + gcc 4.7.3
Signed-off-by: Vineet Gupta
Acked-by: Ingo Molnar
Cc:
On 10/09/2013 01:59 PM, Joe Perches wrote:
The commit message doesn't match the patch subject
(shows kzalloc)
I was a bit surprised to find there isn't a devm_kmalloc.
This seems fine otherwise.
I just sent the second patch file after modifying the commit message.
Thank you for your opinion.
Currently, devm_ managed memory only supports kzalloc.
Convert the devm_kzalloc implementation to devm_kmalloc
and remove the complete memset to 0 but still set the
initial struct devres header and whatever padding before
data to 0.
Add the other normal alloc variants as static inlines with
In order to be free automatically and make the cleanup paths more
simple, use devm_kzalloc() instead of kmalloc().
Signed-off-by: Sangjung Woo
---
drivers/rtc/rtc-pl030.c |7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/drivers/rtc/rtc-pl030.c
On Tuesday, October 08, 2013 3:23 PM, Kishon Vijay Abraham I wrote:
> On Friday 06 September 2013 12:24 PM, Jingoo Han wrote:
> > This patch adds support for Message Signaled Interrupt in the
> > Exynos PCIe diver using Synopsys designware PCIe core IP.
> >
> > Signed-off-by: Siva Reddy Kallam
>
On Tue, Oct 8, 2013 at 7:55 PM, Linus Walleij wrote:
> On Mon, Oct 7, 2013 at 7:35 PM, Tony Lindgren wrote:
>
>> Hi Linus W,
>>
>> Any comments on the pinctrl patches 3 - 5 in this series?
>
> I have no problems with this patch #3, as it is just changing syntax,
> not semantics.
>
> The problems
Hi Simon,
On Wed, Oct 9, 2013 at 12:40 PM, Simon Horman wrote:
> On Tue, Oct 08, 2013 at 02:34:03PM +0900, takas...@ops.dti.ne.jp wrote:
>> Use common clock framework version of clock
>> drivers/clk/shmobile/clk-emev2.c
>> instead of sh-clkfwk version
>> arch/arm/mach-shmobile/clock-emev2.c
>>
On Wed, 2013-10-09 at 13:36 +0900, sangjung.woo wrote:
> On 10/09/2013 01:07 PM, Joe Perches wrote:
> > On Wed, 2013-10-09 at 13:00 +0900, Sangjung Woo wrote:
> >> In order to be free automatically and make the cleanup paths more
> >> simple, use devm_kzalloc() instead of kzalloc().
> > []
> >>
> -Original Message-
> From: Wood Scott-B07421
> Sent: Wednesday, October 09, 2013 4:27 AM
> To: Bhushan Bharat-R65777
> Cc: alex.william...@redhat.com; j...@8bytes.org; b...@kernel.crashing.org;
> ga...@kernel.crashing.org; linux-kernel@vger.kernel.org; linuxppc-
>
>
> Then please test everything again. I.e.
> o speaker-test -D hdmi:CARD=Generic,DEV=0 -c8 -r192000 -F S32_LE
>
this work fine
> o Is there any difference seen
> with these, in the beginning/end (i.e. fade-out/in):
> speaker-test -D hdmi:CARD=Generic,DEV=0,AES0=0x04 -c2 -r48000
>
On 10/09/2013 01:07 PM, Joe Perches wrote:
On Wed, 2013-10-09 at 13:00 +0900, Sangjung Woo wrote:
In order to be free automatically and make the cleanup paths more
simple, use devm_kzalloc() instead of kzalloc().
[]
diff --git a/drivers/rtc/rtc-pl030.c b/drivers/rtc/rtc-pl030.c
[]
@@ -106,7
On Tue, 2013-10-08 at 20:55 -0700, H. Peter Anvin wrote:
> Why not add a minimum number to pci_enable_msix(), i.e.:
>
> pci_enable_msix(pdev, msix_entries, nvec, minvec)
>
> ... which means "nvec" is the number of interrupts *requested*, and
> "minvec" is the minimum acceptable number (otherwise
On Thu, 2013-09-26 at 04:33 -0700, Jacob Pan wrote:
> This will enable intel_powerclamp driver on newer Intel CPUs
> including some Ivy Bridge and Haswell processors.
>
> Signed-off-by: Jacob Pan
applied to thermal -next.
thanks,
rui
> ---
> drivers/thermal/intel_powerclamp.c |5 +
>
Hi Yuan,
On 10/08/2013 07:30 PM, Yuan Zhong wrote:
> Hi Gu,
>
>> Hi Yuan,
>> On 10/08/2013 04:30 PM, Yuan Zhong wrote:
>
>>> Previously, do_checkpoint() will call congestion_wait() for waiting the
>>> pages (previous submitted node/meta/data pages) to be written back.
>>> Because
On Wed, 2013-10-09 at 13:00 +0900, Sangjung Woo wrote:
> In order to be free automatically and make the cleanup paths more
> simple, use devm_kzalloc() instead of kzalloc().
[]
> diff --git a/drivers/rtc/rtc-pl030.c b/drivers/rtc/rtc-pl030.c
[]
> @@ -106,7 +106,7 @@ static int pl030_probe(struct
In order to be free automatically and make the cleanup paths more
simple, use devm_kzalloc() instead of kzalloc().
Signed-off-by: Sangjung Woo
---
drivers/rtc/rtc-pl030.c |7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/drivers/rtc/rtc-pl030.c
On 10/02/2013 03:29 AM, Alexander Gordeev wrote:
>
> As result, device drivers will cease to use the overcomplicated
> repeated fallbacks technique and resort to a straightforward
> pattern - determine the number of MSI/MSI-X interrupts required
> before calling pci_enable_msi_block() and
On Tue, Oct 08, 2013 at 02:34:03PM +0900, takas...@ops.dti.ne.jp wrote:
> Use common clock framework version of clock
> drivers/clk/shmobile/clk-emev2.c
> instead of sh-clkfwk version
> arch/arm/mach-shmobile/clock-emev2.c
> when it is configured as a part of multi-platform.
>
> Signed-off-by:
On Tue, Oct 08, 2013 at 02:54:26PM +0900, Magnus Damm wrote:
> On Tue, Oct 8, 2013 at 2:33 PM, wrote:
> > Add minimum clock tree description to .dts file.
> > This provides same set of clocks as current sh-clkfwk version .c
> > code does.
> >
> > Signed-off-by: Takashi Yoshii
Thanks.
I plan
Some more comments.
> - your patches might break apps/ABI
Can you please explain that a bit more. We have a lot of CONFIG options
that disable syscalls, /sys, lots of stuff. Whoever uses them needs
to know what they are doing. I thought it was pretty
much consensus that Linux is supposed to be
On Tue, Oct 08, 2013 at 02:58:08PM +0900, Magnus Damm wrote:
> On Tue, Oct 8, 2013 at 2:32 PM, wrote:
> > Device tree clock binding document for EMMA Mobile EV2 SMU,
> > And Common clock framework based implementation of it.
> > Following nodes are defined to describe clock tree.
> > -
On Thu, 2013-10-03 at 14:15 +0200, Ingo Molnar wrote:
> * Davidlohr Bueso wrote:
[...]
> > --- a/kernel/lockdep_proc.c
> > +++ b/kernel/lockdep_proc.c
> > @@ -421,6 +421,7 @@ static void seq_lock_time(struct seq_file *m, struct
> > lock_time *lt)
> > seq_time(m, lt->min);
> > seq_time(m,
On Tue, Oct 08, 2013 at 08:28:43PM -0700, Paul E. McKenney wrote:
> On Tue, Oct 08, 2013 at 01:40:56PM -0700, Paul E. McKenney wrote:
> > On Tue, Oct 08, 2013 at 09:47:18PM +0200, Ingo Molnar wrote:
[ . . . ]
> > > > Should I be thinking about making a kernel/rcu?
> > >
> > > I wanted to raise
On Tue, Oct 08, 2013 at 01:40:56PM -0700, Paul E. McKenney wrote:
> On Tue, Oct 08, 2013 at 09:47:18PM +0200, Ingo Molnar wrote:
> >
> > * Paul E. McKenney wrote:
> >
> > > On Tue, Oct 08, 2013 at 12:23:31PM +0200, Ingo Molnar wrote:
> > > >
> > > > * Peter Zijlstra wrote:
> > > >
> > > > >
Similar to other findnew based methods if the requested
object is not found, add it to the list.
v2: followed format of other findnew methods per acme's request
Signed-off-by: David Ahern
Cc: Ingo Molnar
Cc: Frederic Weisbecker
Cc: Peter Zijlstra
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Stephane
When recording raw_syscalls for the entire system, e.g.,
perf record -e raw_syscalls:*,sched:sched_switch -a -- sleep 1
you end up with a negative feedback loop as perf itself calls
write() fairly often. This patch handles the problem by mmap'ing the
file in chunks of 64M at a time and copies
When enabled dumps a summary of all syscalls by task with the usual
statistics -- min, max, average and relative stddev. For example,
make - 26341 : 3344 [ 17.4% ] 0.000 ms
read : 520.000 4.802 0.644 30.08
write : 200.004
Hi Arnaldo:
Revision to intlist per your comment with the summary option
updated per your perf/core branch.
The mmap output file has survived local testing without problems
so please consider it for inclusion as well. It lowers the overhead
of perf-record.
David Ahern (3):
perf util: Add
> So I test-built a config close to your config with both tracing and perf
> on and off (note, I had OPROFILE and KVM in a module), and got the
> following kernel sizes:
Yes I mistakenly included KVM (I think that was the difference)
Without KVM it's ~272k text, 96k BSS data delta.
Still big,
Dear Sebastian,
On Tue, 8 Oct 2013 05:24:33 -0700
Sebastian Hesselbarth wrote:
> This adds initial support for the Marvell Berlin (88DE3xxx) SoC family
> and basic machine setup for Armada 1500 (88DE3100) SoCs.
First of all, thanks for these patches. I worked and is still working on Marvell
> You'd think that, but for whatever reason, ftrace/perf oopses still happen.
Hiding bugs seems like a poor use of the CONFIG option. It would
be better to figure out a way to catch them earlier. Perhaps
trinity needs to run more often? any chance of a fengguang style nightly
service for
Mikulas,
> Waking up every 100ms in flush_proc is not good because it wastes CPU time
> and energy if the driver is idle.
Yes, 100ms is too short. I will change it to 1sec then.
We can wait for 1 sec in termination.
> The problem is that if you fill up the whole cache device in less time
>
On Wed, 2013-10-09 at 13:22 +1100, Ryan Mallon wrote:
> Anyway, updated patch below:
nit:
> diff --git a/lib/vsprintf.c b/lib/vsprintf.c
[]
> @@ -1312,11 +1313,36 @@ char *pointer(const char *fmt, char *buf, char *end,
> void *ptr,
> spec.field_width =
On Tue, Oct 8, 2013 at 7:06 PM, Al Viro wrote:
> On Tue, Oct 08, 2013 at 06:38:47PM -0700, Linus Torvalds wrote:
>> On Tue, Oct 8, 2013 at 6:18 PM, Al Viro wrote:
>> >
>> > Point, but I would argue that we should yell very loud if we get 0 from
>> > vfs_write() for non-zero size. I'm not sure
On 09/10/13 13:00, Joe Perches wrote:
> On Wed, 2013-10-09 at 12:55 +1100, Ryan Mallon wrote:
>> On 09/10/13 12:30, Joe Perches wrote:
>>> On Tue, 2013-10-08 at 17:49 -0700, Joe Perches wrote:
On Wed, 2013-10-09 at 11:15 +1100, Ryan Mallon wrote:
> Some setuid binaries will allow reading
://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc (2013-09-19 18:49:08
-0500)
are available in the git repository at:
git://git.infradead.org/linux-mtd.git tags/for-linus-20131008
for you to fetch changes up to 2b468ef0e7959b703626b64c4d264ef822c9267a:
mtd: m25p80: Fix 4 byte
Hi!
I'll try an up-to-date kernel tomorrow, but with 3.10.x running, I
thought the usual fixes for black screens should be included.
The board features a VGA as well as a DVI connector, VGA is
connected. No LVDS, no DisplayPort. With DRM debugging enabled, I get
this:
[0.00] Linux
On Tue, Oct 08, 2013 at 06:38:47PM -0700, Linus Torvalds wrote:
> On Tue, Oct 8, 2013 at 6:18 PM, Al Viro wrote:
> >
> > Point, but I would argue that we should yell very loud if we get 0 from
> > vfs_write() for non-zero size. I'm not sure if POSIX allows write(2)
> > to return that, but a lot
On Wed, 2013-10-09 at 12:55 +1100, Ryan Mallon wrote:
> On 09/10/13 12:30, Joe Perches wrote:
> > On Tue, 2013-10-08 at 17:49 -0700, Joe Perches wrote:
> >> On Wed, 2013-10-09 at 11:15 +1100, Ryan Mallon wrote:
> >>> Some setuid binaries will allow reading of files which have read
> >>> permission
On Tue, Oct 08, 2013 at 11:58:10AM +0200, Paolo Bonzini wrote:
> Il 08/10/2013 03:05, Marcelo Tosatti ha scritto:
> > +void pvclock_touch_watchdogs(void)
> > +{
> > + touch_softlockup_watchdog_sync();
> > + clocksource_touch_watchdog();
> > + rcu_cpu_stall_reset();
> > +
On Tue, Oct 08, 2013 at 12:02:32PM +0800, Xiao Guangrong wrote:
>
> Hi Marcelo,
>
> On Oct 8, 2013, at 9:23 AM, Marcelo Tosatti wrote:
>
> >>
> >> + if (kvm->arch.rcu_free_shadow_page) {
> >> + kvm_mmu_isolate_pages(invalid_list);
> >> + sp = list_first_entry(invalid_list,
On 13-10-02 06:29 AM, Alexander Gordeev wrote:
..
> This update converts pci_enable_msix() and pci_enable_msi_block()
> interfaces to canonical kernel functions and makes them return a
> error code in case of failure or 0 in case of success.
Rather than silently break dozens of drivers in
On 09/10/13 12:30, Joe Perches wrote:
> On Tue, 2013-10-08 at 17:49 -0700, Joe Perches wrote:
>> On Wed, 2013-10-09 at 11:15 +1100, Ryan Mallon wrote:
>>> Some setuid binaries will allow reading of files which have read
>>> permission by the real user id. This is problematic with files which
>>>
On Tue, Oct 08, 2013 at 06:47:41PM -0500, delicious quinoa wrote:
> On Tue, Oct 8, 2013 at 4:44 PM, Greg Kroah-Hartman
> wrote:
> > On Tue, Oct 08, 2013 at 12:00:14PM -0500, Alan Tull wrote:
> >> On Fri, 2013-10-04 at 16:33 -0700, Greg Kroah-Hartman wrote:
> >> > On Fri, Oct 04, 2013 at
On Tue, 2013-10-08 at 21:05 +0200, Jakub Jelinek wrote:
> On Tue, Oct 08, 2013 at 08:51:54PM +0200, Oleg Nesterov wrote:
> > On 10/08, Linus Torvalds wrote:
> > >
> > > (not yet merged), see:
> > >
> > >
> > >
On Tue, Oct 08, 2013 at 10:47:28AM -0300, Fabio Estevam wrote:
> clk_prepare_enable() may fail, so let's check its return value and propagate
> it
> in the case of error.
>
> Also, fix the sequence for disabling the clock in the probe error path and
> also in the remove function.
>
>
On Tue, Oct 8, 2013 at 6:18 PM, Al Viro wrote:
>
> Point, but I would argue that we should yell very loud if we get 0 from
> vfs_write() for non-zero size. I'm not sure if POSIX allows write(2)
> to return that, but a lot of userland code won't be expecting that and
> won't be able to cope...
On Tue, Oct 08, 2013 at 09:33:02AM +0200, Alexander Gordeev wrote:
> On Tue, Oct 08, 2013 at 03:33:30PM +1100, Michael Ellerman wrote:
> > On Wed, Oct 02, 2013 at 12:29:04PM +0200, Alexander Gordeev wrote:
> > > This technique proved to be confusing and error-prone. Vast share
> > > of device
On Tue, Oct 8, 2013 at 6:09 PM, Fengguang Wu wrote:
> [ 27.189229] BUG: unable to handle kernel NULL pointer dereference at
> 0108
> [ 27.190165] IP: [] rw_verify_area+0xa0/0x1b0
This looks like file->f_inode is NULL, and it's trying to access inode->i_flock.
There's a number of other
From: xiao jin
Date: Wed, 9 Oct 2013 09:38:45 +0800
Subject: [PATCH] xhci-hub.c: handle command_trb that may be link TRB
When xhci stop device, it's possible cmd_ring enqueue point to
link TRB after queue the last but one stop endpoint. We must
handle the command_trb point to the next segment
On Tue, 2013-10-08 at 17:49 -0700, Joe Perches wrote:
> On Wed, 2013-10-09 at 11:15 +1100, Ryan Mallon wrote:
> > Some setuid binaries will allow reading of files which have read
> > permission by the real user id. This is problematic with files which
> > use %pK because the file access permission
On Mon, Oct 7, 2013 at 12:40 AM, Guennadi Liakhovetski
wrote:
> Hi Russell
>
> On Sun, 6 Oct 2013, Russell King - ARM Linux wrote:
>
>> On Sat, Oct 05, 2013 at 11:00:45PM +0200, Guennadi Liakhovetski wrote:
>> > On Sat, 5 Oct 2013, Russell King - ARM Linux wrote:
>> >
>> > > On Sat, Oct 05, 2013
On Wed, Oct 09, 2013 at 12:03:19PM +1100, Michael Ellerman wrote:
> On Tue, 2013-10-08 at 12:31 -0700, Sukadev Bhattiprolu wrote:
> > Michael Ellerman [mich...@ellerman.id.au] wrote:
> > | bool is_load_store(int ext_opcode)
> > | {
> > | upper = ext_opcode >> 5;
> > | lower =
Useful for locating buggy drivers on kernel oops.
It may add dozens of new lines to boot dmesg. DEBUG_KOBJECT_RELEASE is
hopefully only enabled in debug kernels (like maybe the Fedora rawhide
one, or at developers), so being a bit more verbose is likely ok.
CC: Russell King - ARM Linux
CC: Greg
On Tue, Oct 08, 2013 at 03:44:12PM +0200, Thierry Reding wrote:
> Today's linux-next merge of the imx-mxs tree got conflicts in
>
> arch/arm/mach-imx/mach-imx6q.c
>
> caused by commits 4d9d18a (ARM: imx: remove custom .init_time hook),
> e709f38 (ARM: imx6: report soc info via soc device)
On Wed, Oct 09, 2013 at 02:18:33AM +0100, Al Viro wrote:
> Point, but I would argue that we should yell very loud if we get 0 from
> vfs_write() for non-zero size. I'm not sure if POSIX allows write(2)
> to return that, but a lot of userland code won't be expecting that and
> won't be able to
Kindly ping :)
Any comments?
Br, David Cohen
On 10/01/2013 01:18 PM, David Cohen wrote:
Implement initial SDHCI Intel Merrifield support.
This patch is based on previous one from Yunpeng Gao
Signed-off-by: David Cohen
---
drivers/mmc/host/sdhci-pci.c | 30 ++
On Tue, Oct 08, 2013 at 05:45:37PM -0700, Linus Torvalds wrote:
> normally that whole DEBUG_KOBJECT_RELEASE
> thing is hopefully only enabled in debug kernels (like maybe the
> Fedora rawhide one
Nope. After spending a couple of days fruitlessly trying to get my machine to
boot
with it
On Tue, Oct 08, 2013 at 05:52:42PM -0700, Linus Torvalds wrote:
> On Tue, Oct 8, 2013 at 5:15 PM, Al Viro wrote:
> >
> > ... and deal with short writes properly
>
> .. except you don't.
>
> > + while (nr) {
> > + if (dump_interrupted())
> > + return 0;
From: xiao jin
Date: Wed, 9 Oct 2013 09:09:46 +0800
Subject: [PATCH] xhci: correct the usage of USB_CTRL_SET_TIMEOUT
The usage of USB_CTRL_SET_TIMEOUT is incorrect. The
definition of USB_CTRL_SET_TIMEOUT is 5000ms. The
input timeout to wait_for_completion_interruptible_timeout
is jiffies. That
Mike,
I am happy to see that
guys from filesystem to the block subsystem
have been discussing how to handle barriers in each layer
almost independently.
>> Merging the barriers and replacing it with a single FLUSH
>> by accepting a lot of writes
>> is the reason for deferring barriers in
On 10/09/2013 01:56 AM, Oleg Nesterov wrote:
> On 10/08, Chen Gang wrote:
>>
>> On 10/07/2013 08:43 PM, Oleg Nesterov wrote:
>>>
but still recommend to check it
in __change_pid() to let itself consistency.
>>>
>>> Why?
>>>
>>> Contrary, I think we should not hide the problem. If
On Tue, 2013-10-08 at 12:31 -0700, Sukadev Bhattiprolu wrote:
> Michael Ellerman [mich...@ellerman.id.au] wrote:
> | bool is_load_store(int ext_opcode)
> | {
> | upper = ext_opcode >> 5;
> | lower = ext_opcode & 0x1f;
> |
> | /* Short circuit as many misses as we can */
>
On Tue, Oct 8, 2013 at 5:15 PM, Al Viro wrote:
>
> ... and deal with short writes properly
.. except you don't.
> + while (nr) {
> + if (dump_interrupted())
> + return 0;
> + n = vfs_write(file, addr, nr, );
> + if (n < 0)
>
On Wed, 2013-10-09 at 11:15 +1100, Ryan Mallon wrote:
> Some setuid binaries will allow reading of files which have read
> permission by the real user id. This is problematic with files which
> use %pK because the file access permission is checked at open() time,
> but the kptr_restrict setting is
Ulf,
While this patch might be correct, it's not solving the problem I
claimed and my explanation was wrong. See comments in this code
review:
https://chromium-review.googlesource.com/#/c/170880/1//COMMIT_MSG
While I no longer see the same crash with this change in our "ToT
tree", I'm able to
On Tue, Oct 8, 2013 at 3:48 PM, Greg Kroah-Hartman
wrote:
>
> It's going to make things really noisy at boot time, but then it should
> settle down and not be bad at all. Let's try it and see if it helps or
> not.
Yeah. And quite frankly, normally that whole DEBUG_KOBJECT_RELEASE
thing is
On Tue, Oct 08, 2013 at 03:48:40PM -0700, Greg KH wrote:
> On Tue, Oct 08, 2013 at 11:14:17PM +0100, Russell King - ARM Linux wrote:
> > On Tue, Oct 08, 2013 at 08:17:42PM +0800, Fengguang Wu wrote:
> > > I find the above debug messages very helpful in locating the buggy
> > > driver. How about
Signed-off-by: Al Viro
---
fs/binfmt_elf.c |3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff --git a/fs/binfmt_elf.c b/fs/binfmt_elf.c
index bb59220..42ef312 100644
--- a/fs/binfmt_elf.c
+++ b/fs/binfmt_elf.c
@@ -2034,7 +2034,6 @@ static int elf_core_dump(struct coredump_params
just getting rid of bitrot
Signed-off-by: Al Viro
---
arch/x86/ia32/ia32_aout.c | 70 +++--
1 files changed, 36 insertions(+), 34 deletions(-)
diff --git a/arch/x86/ia32/ia32_aout.c b/arch/x86/ia32/ia32_aout.c
index bae3aba..80361c0 100644
---
Signed-off-by: Al Viro
---
arch/x86/ia32/ia32_aout.c |2 +-
fs/binfmt_aout.c |2 +-
fs/binfmt_elf.c |4 ++--
fs/binfmt_elf_fdpic.c | 11 +++
fs/coredump.c | 43 ++-
include/linux/coredump.h |
Signed-off-by: Al Viro
---
arch/powerpc/platforms/cell/spufs/coredump.c | 69 +++--
1 files changed, 20 insertions(+), 49 deletions(-)
diff --git a/arch/powerpc/platforms/cell/spufs/coredump.c
b/arch/powerpc/platforms/cell/spufs/coredump.c
index 5d9b0a2..158 100644
Signed-off-by: Al Viro
---
arch/powerpc/include/asm/spu.h |3 +-
arch/powerpc/platforms/cell/spu_syscalls.c |5 ++-
arch/powerpc/platforms/cell/spufs/coredump.c | 44 ++
arch/powerpc/platforms/cell/spufs/spufs.h|3 +-
fs/binfmt_elf.c
Signed-off-by: Al Viro
---
fs/binfmt_elf_fdpic.c | 109 ++---
1 files changed, 31 insertions(+), 78 deletions(-)
diff --git a/fs/binfmt_elf_fdpic.c b/fs/binfmt_elf_fdpic.c
index 77bf7e3..1806e25 100644
--- a/fs/binfmt_elf_fdpic.c
+++
Some setuid binaries will allow reading of files which have read
permission by the real user id. This is problematic with files which
use %pK because the file access permission is checked at open() time,
but the kptr_restrict setting is checked at read() time. If a setuid
binary opens a %pK file
Signed-off-by: Al Viro
---
arch/ia64/kernel/elfcore.c |6 ++
arch/x86/um/elfcore.c |8 ++--
fs/binfmt_elf.c|4 +++-
fs/binfmt_elf_fdpic.c |4 +++-
include/linux/elfcore.h|2 +-
5 files changed, 11 insertions(+), 13 deletions(-)
diff --git
dump_skip to given alignment...
Signed-off-by: Al Viro
---
arch/powerpc/platforms/cell/spufs/coredump.c |2 +-
fs/binfmt_elf.c | 10 ++
fs/binfmt_elf_fdpic.c| 10 ++
fs/coredump.c|6
Signed-off-by: Al Viro
---
arch/x86/ia32/ia32_aout.c | 20
fs/binfmt_aout.c |7 +++
2 files changed, 11 insertions(+), 16 deletions(-)
diff --git a/arch/x86/ia32/ia32_aout.c b/arch/x86/ia32/ia32_aout.c
index 80361c0..9e26e9e 100644
---
... and deal with short writes properly - the output might be to pipe, after
all; as it is, e.g. no-MMU case of elf_fdpic coredump can write a whole lot
more than a page worth of data at one call.
Signed-off-by: Al Viro
---
fs/coredump.c | 17 -
1 files changed, 12
dump_write() analog, takes core_dump_params instead of file,
keeps track of the amount written in cprm->written and checks for
cprm->limit. Start using it in binfmt_elf.c...
Signed-off-by: Al Viro
---
fs/binfmt_elf.c | 62 +
fs/coredump.c
Signed-off-by: Al Viro
---
fs/binfmt_elf.c | 14 +++---
1 files changed, 3 insertions(+), 11 deletions(-)
diff --git a/fs/binfmt_elf.c b/fs/binfmt_elf.c
index 666a5a5..bc01aaf 100644
--- a/fs/binfmt_elf.c
+++ b/fs/binfmt_elf.c
@@ -2093,7 +2093,6 @@ static int elf_core_dump(struct
This series tries to regularize the coredump writes/seeks/rlimit
handling
etc. Quite a bit of boilerplate code removed, another open-coded caller of
->write() converted to use of normal codepath (which was the original reason
I've got into that mess). RLIMIT_CORE handling got a lot more
Signed-off-by: Al Viro
---
arch/ia64/kernel/elfcore.c |6 ++
arch/x86/um/elfcore.c |7 ++-
fs/binfmt_elf.c|4 ++--
fs/binfmt_elf_fdpic.c |4 +++-
include/linux/elfcore.h|5 +++--
kernel/elfcore.c | 10 +++---
6 files changed,
--
Vážení Web - Mail Majitel účtu:
To přišlo na naše upozornění , že vaše e-mailová neprošel ověření /
aktualizace proces, který jsme v současné době pracuje na . V současné
době modernizace naší databázi a e - mailový účet centrum , čímž Smazání
všech starých webový e-mail e-mailový účet
On Tue, Oct 8, 2013 at 4:44 PM, Greg Kroah-Hartman
wrote:
> On Tue, Oct 08, 2013 at 12:00:14PM -0500, Alan Tull wrote:
>> On Fri, 2013-10-04 at 16:33 -0700, Greg Kroah-Hartman wrote:
>> > On Fri, Oct 04, 2013 at 11:12:13AM -0700, H. Peter Anvin wrote:
>> > > On 10/04/2013 10:44 AM, Michal Simek
From: Rafael J. Wysocki
The e-mail address r...@sisk.pl that I have been using for quite some
time is going to expire at one point, so replace it with a new one,
r...@rjwysocki.net, everywhere in MAINTAINERS and Documentation/ABI.
Signed-off-by: Rafael J. Wysocki
---
On Tue, 8 Oct 2013, Joseph S. Myers wrote:
> I'll send as a followup the testcase I used for verifying that the
> instructions (other than the theoretical conversions to 64-bit
> integers) produce the correct results. In addition, this has been
> tested with the glibc testsuite (with the e500
Hi All,
The following two patches update my e-mail address (the one I use for kernel
development) and ACPI-related information in MAINTAINERS.
Kind regards,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
From: Rafael J. Wysocki
Update the ACPI subsystem's git tree and Web links in the
MAINTAINERS file.
Signed-off-by: Rafael J. Wysocki
---
MAINTAINERS |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Index: linux-pm/MAINTAINERS
From: Joseph Myers
The e500 SPE floating-point emulation code has several problems in how
it handles conversions to integer and fixed-point fractional types.
There are the following 20 relevant instructions. These can convert
to signed or unsigned 32-bit integers, either rounding towards zero
On Tue, 2013-10-08 at 17:25 -0600, Bjorn Helgaas wrote:
> >> - u32 msiir_offset; /* Offset of MSIIR, relative to start of CCSR */
> >> + dma_addr_t msiir; /* MSIIR Address in CCSR */
> >
> > Are you sure dma_addr_t is right here, versus phys_addr_t? It implies
> > that it's the output of
These aren't necessary after switch and while statements.
Signed-off-by: Joe Perches
---
drivers/media/common/b2c2/flexcop-sram.c | 6 +++---
drivers/media/dvb-frontends/cx24110.c| 2 +-
drivers/media/dvb-frontends/cx24123.c| 2 +-
>> - u32 msiir_offset; /* Offset of MSIIR, relative to start of CCSR */
>> + dma_addr_t msiir; /* MSIIR Address in CCSR */
>
> Are you sure dma_addr_t is right here, versus phys_addr_t? It implies
> that it's the output of the DMA API, but I don't think the DMA API is
> used in the MSI
1 - 100 of 1602 matches
Mail list logo
