Ming Lei writes:
> On Fri, Oct 25, 2013 at 7:08 AM, Rusty Russell wrote:
>>
>> Sorry, I was imprecise. I was referring to the kernel's kallsyms
>> tables produced by scripts/kallsyms.c. This patch left them in the
>> the kallsyms tables and filtered them out from /proc/kallsyms.
>
> Yes, but
On Thu, Oct 24, 2013 at 12:27 PM, Vivek Goyal wrote:
> On Thu, Oct 24, 2013 at 12:24:57PM -0700, Yinghai Lu wrote:
>> On Thu, Oct 24, 2013 at 12:18 PM, Vivek Goyal wrote:
>> > On Thu, Oct 24, 2013 at 12:15:25PM -0700, Yinghai Lu wrote:
>> >
>> > Also keeping things simple by not trying to
This patch adds a tracepoint for f2fs_vm_page_mkwrite.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/file.c | 1 +
include/trace/events/f2fs.h | 7 +++
2 files changed, 8 insertions(+)
diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
index c80faa2..2d4190a 100644
--- a/fs/f2fs/file.c
+++
This patch adds a tracepoint for set_page_dirty.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/checkpoint.c| 2 ++
fs/f2fs/data.c | 2 ++
fs/f2fs/node.c | 2 ++
include/trace/events/f2fs.h | 44
4 files changed, 50
On Thu, Oct 24, 2013 at 10:13 PM, Yinghai Lu wrote:
> On Thu, Oct 24, 2013 at 8:33 PM, Bjorn Helgaas wrote:
>>
> Bisection points to 928bea964827d7824b548c1f8e06eccbbc4d0d7d .
This is "PCI: Delay enabling bridges until they're needed" by Yinghai.
>>>
>>> that double disabling
'phy' was not being freed upon error in one of the cases.
Adjust the 'goto's to fix this.
Signed-off-by: Sachin Kamat
---
drivers/phy/phy-core.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/phy/phy-core.c b/drivers/phy/phy-core.c
index
On Thu, Oct 24, 2013 at 11:28:29PM +0200, Guennadi Liakhovetski wrote:
> Hi Vinod
>
> On Thu, 17 Oct 2013, Vinod Koul wrote:
> > Yes i missed it in first place update the patch to fix that
>
> Are you planning to post a fixed version of this patch or you just fix it
> internally? Would be good
On Thu, Oct 24, 2013 at 8:33 PM, Bjorn Helgaas wrote:
>
Bisection points to 928bea964827d7824b548c1f8e06eccbbc4d0d7d .
>>>
>>> This is "PCI: Delay enabling bridges until they're needed" by Yinghai.
>>
>> that double disabling should be addressed by:
>>
>> https://lkml.org/lkml/2013/4/25/608
On 10/25/2013 01:11 AM, Geert Uytterhoeven wrote:
> On Thu, Oct 24, 2013 at 7:28 PM, Vineet Gupta wrote:
>> > +CC linux-arch
>> >
>> > On 10/24/2013 11:33 AM, Richard Weinberger wrote:
>>> >> On Thu, Oct 24, 2013 at 7:31 AM, Chen Gang wrote:
> >>> > For some architectures, tool chain is not
Haojian,
> -Original Message-
> From: Neil Zhang
> Sent: 2013年10月18日 17:50
> To: Neil Zhang; linux-kernel@vger.kernel.org
> Cc: haojian.zhu...@gmail.com; t...@linutronix.de
> Subject: RE: [PATCH 2/2 v2] irqchip: mmp: add dt support for wakeup
>
> Ping ?
>
> > -Original Message-
On 10/24/2013 09:31 AM, Thierry Reding wrote:
Hi all,
I've uploaded today's linux-next tree to the master branch of the
repository below:
git://gitorious.org/thierryreding/linux-next.git
A next-20131024 tag is also provided for convenience.
Quite a few new conflicts. Some of them
Thanks for your thought! It may not make much sense. Because I think
the probability of two bios have the same start sector and the
situation mentioned by Ming Lei is too low.
Thanks ,
Bonben
2013/10/25 Ming Lei :
> On Wed, Oct 23, 2013 at 6:59 PM, Jan Kara wrote:
>> On Wed 23-10-13 08:47:44,
The Thumb instruction set include an If-Then instruction. If an ARM
function is registered as a signal handler, and that signal is
delivered inside the block of instructions follow the IT instruction,
some of the instructions at the beginning of the signal handler are
skipped. This occurs
On Wed, Oct 23, 2013 at 6:59 PM, Jan Kara wrote:
> On Wed 23-10-13 08:47:44, 韩磊 wrote:
>> Nowadays,the IO schedulers in linux kernel have four types:
>>
>> deadline,noop,Anticiptory and CFQ.CFQ is the default scheduler.But CFQ is
>> not a good scheduler for SSD,dealine may be a good choice.
>
>>
Email Account Warning !!!
This mail is from Administrator; we wish to bring to your notice the Condition
of your email account.
We have just noticed that you have exceeded your email Database limit of 500 MB
quota and your email IP is causing conflict because it is been accessed in
different
On Wed, Oct 23, 2013 at 11:53 PM, Yinghai Lu wrote:
> On Tue, Oct 22, 2013 at 8:32 PM, Bjorn Helgaas wrote:
>> On Thu, Oct 17, 2013 at 7:59 AM, Andreas Noever
>> wrote:
>>> On Wed, Oct 16, 2013 at 10:21 PM, Bjorn Helgaas wrote:
On Tue, Oct 15, 2013 at 03:44:52AM +0100, Matthew Garrett
On Oct 24, 2013, at 9:27 AM, Sebastian Reichel wrote:
> Add Device Tree support for the TSL2563 driver
> and document the binding.
>
> Signed-off-by: Sebastian Reichel
> ---
> .../devicetree/bindings/iio/light/tsl2563.txt | 19 +++
>
On Oct 8, 2013, at 7:25 AM, Christian Ruppert wrote:
> The GPIO driver for the Abilis Systems TB10x series of SOCs based on ARC700
> CPUs. It supports GPIO control and GPIO interrupt generation. This driver
> works in conjunction with the TB10x pinctrl driver.
>
> Signed-off-by: Sascha
On Wed, Sep 18, 2013 at 02:12:04PM +0200, Miklos Szeredi wrote:
> Al,
>
> This is for next (3.13), could you please ack it or take it through your tree?
Done, with one change: it's doing iput() on failure. Same pattern as
d_make_root()/d_materialise_unique()/etc - makes for simpler failure
2013/10/23 Jan Kara :
> On Wed 23-10-13 08:47:44, 韩磊 wrote:
>> Nowadays,the IO schedulers in linux kernel have four types:
>>
>> deadline,noop,Anticiptory and CFQ.CFQ is the default scheduler.But CFQ is
>> not a good scheduler for SSD,dealine may be a good choice.
>
> That doesn't make much
On 10/25/2013 08:35 AM, Olav Haugan wrote:
> Hi Bob, Luigi,
>
> On 10/23/2013 5:55 PM, Bob Liu wrote:
>>
>> On 10/24/2013 05:51 AM, Olav Haugan wrote:
>>> I am trying to use zram in very low memory conditions and I am having
>>> some issues. zram is in the reclaim path. So if the system is very
On Fri, Oct 25, 2013 at 3:46 AM, Arnaldo Carvalho de Melo
wrote:
> Em Thu, Oct 24, 2013 at 08:11:36PM +0800, Jovi Zhangwei escreveu:
>> I admit there have many places need to cleanup in ktap code, and there
>> also have a long todo list, I will finish it before start review process.
>>
>> Again,
On Thu, Oct 24, 2013 at 03:42:33PM -0600, Bjorn Helgaas wrote:
> dev_WARN() and dev_WARN_ONCE() are annoying because (1) they include
> only the driver name, not the device name, and (2) they print a spurious
> newline in the middle. This results in messages like this that are less
> useful than
On 13-10-24 10:31 AM, Alexander Gordeev wrote:
> On Thu, Oct 24, 2013 at 11:51:58AM +0100, Tejun Heo wrote:
>> I haven't looked into any details but, if the above works for most use
>> cases, it looks really good to me.
>
> Well, if we reuse Michael's statistics:
>
> - 58 drivers call
On 13-10-24 07:41 AM, Alexander Gordeev wrote:
> On Thu, Oct 24, 2013 at 11:57:40AM +0100, David Laight wrote:
>> The one case it doesn't work is where the driver either
>> wants the full number or the minimum number - but not
>> a value in between.
>>
>> Might be worth adding an extra parameter
Thanks Arnaldo For Reviewing and Nice simplication.
The next headache should be how to quick copy out the digest
of event.
>From my own engineering experience, it is unsafe to keep the pointer
to shared ring buffer for too long.
On Fri, Oct 25, 2013 at 2:23 AM, Arnaldo Carvalho de Melo
wrote:
>
Hi.
Thanks for your interest.
(2013/10/24 4:55), Richard Guy Briggs wrote:
> On Tue, Oct 15, 2013 at 02:30:34PM +0800, Gao feng wrote:
>> Hi Toshiyuki-san,
>
> Toshiuki and Gao,
>
>> On 10/15/2013 12:43 PM, Toshiyuki Okajima wrote:
>>> The backlog cannot be consumed when audit_log_start is
Hi Gu,
> -Original Message-
> From: Gu Zheng [mailto:guz.f...@cn.fujitsu.com]
> Sent: Thursday, October 24, 2013 6:04 PM
> To: Chao Yu
> Cc: jaegeuk@samsung.com; linux-fsde...@vger.kernel.org;
> linux-kernel@vger.kernel.org; linux-f2fs-de...@lists.sourceforge.net; '谭姝'
> Subject: Re:
On Fri, Oct 25, 2013 at 7:08 AM, Rusty Russell wrote:
>
> Sorry, I was imprecise. I was referring to the kernel's kallsyms
> tables produced by scripts/kallsyms.c. This patch left them in the
> the kallsyms tables and filtered them out from /proc/kallsyms.
Yes, but it isn't easy to do it by
On Thu, Oct 24, 2013 at 09:58:53PM +0200, Rostislav Lisovy wrote:
> I saw that most of the vendor prefixes are somehow shortened (e.g.
> Freescale -- fsl, etc.).
The 'fsl' is the stock symbol of Freescale. If that's not the case for
voipac, I think 'voipac' is more appropriate.
Shawn
> On Thu,
On Thu, Oct 24, 2013 at 5:35 PM, Olav Haugan wrote:
> Hi Bob, Luigi,
>
> On 10/23/2013 5:55 PM, Bob Liu wrote:
>>
>> On 10/24/2013 05:51 AM, Olav Haugan wrote:
>>> I am trying to use zram in very low memory conditions and I am having
>>> some issues. zram is in the reclaim path. So if the system
When tests were added to lkdtm that grew the stack frame, the stack
corruption test stopped working. This isolates the test in its own
function, and forces it not to be inlined.
Signed-off-by: Kees Cook
Fixes: cc33c537c12f ("lkdtm: add "EXEC_*" triggers")
---
This bug was introduced in 3.12, so
Russell King - ARM Linux writes:
> On Thu, Oct 24, 2013 at 11:51:18AM +1030, Rusty Russell wrote:
>> Ming Lei writes:
>> > Address of non-module kernel symbol should always be located
>> > from CONFIG_PAGE_OFFSET on, so only show these legal kernel
>> > symbols in /proc/kallsyms.
>> >
>> > On
On Wed, 2013-10-23 at 02:53 -0700, wal...@google.com wrote:
> On Sun, Oct 20, 2013 at 08:26:15PM -0700, Davidlohr Bueso wrote:
> > From: Davidlohr Bueso
> > Subject: [PATCH v2 3/3] vdso: preallocate new vmas
> >
> > With the exception of um and tile, architectures that use
> > the
When !CONFIG_BUG, WARN_ON and family become simple passthroughs of their
condition argument; however, WARN_ON_ONCE and family still have
conditions and a boolean to detect one-time invocation, even though the
warning they'd emit doesn't exist. Make the existing definitions
conditional on
On Wed, Oct 23, 2013 at 10:10:47AM -0400, Douglas Gilbert wrote:
> On 13-10-23 03:44 AM, James Bottomley wrote:
> >On Tue, 2013-10-22 at 20:41 -0400, Douglas Gilbert wrote:
> >>On 13-10-22 04:56 PM, Simon Kirby wrote:
> >>>Hello!
> >>>
> >>>While trying to figure out why the request queue to sda
Hi Bob, Luigi,
On 10/23/2013 5:55 PM, Bob Liu wrote:
>
> On 10/24/2013 05:51 AM, Olav Haugan wrote:
>> I am trying to use zram in very low memory conditions and I am having
>> some issues. zram is in the reclaim path. So if the system is very low
>> on memory the system is trying to reclaim
Hello Chris and Ben,
> -Original Message-
> From: Ben Widawsky [mailto:b...@bwidawsk.net]
> Sent: Friday, October 25, 2013 4:57 AM
> To: Chris Wilson; Liu, Chuansheng; daniel.vet...@ffwll.ch; airl...@linux.ie;
> intel-...@lists.freedesktop.org; dri-de...@lists.freedesktop.org;
>
Hi Alex,
I'm wondering if there was any news on the Runtime Interpreted Power
Sequences?
The most recent news I can find is
https://lkml.org/lkml/2013/4/27/73
where you say they might be ready for 3.11. Clearly that didn't work
(predictions being hard, especially about the future).
I'm
On Thu, Oct 24, 2013 at 6:35 PM, James Solner wrote:
> This patch adds the Documentation/module-signing.txt file that is
> missing. There is a link to Documentation/module-signing.txt file
> in init/Kconfig that references this file.
>
> Signed-off-by: James Solner
Nak. Please see below.
>
Notifacations Of Payment Recieved!
Hey,
Our records indicate that you have exactly
$8,888 in unclaimed commissions...
>>=> http://tiny.cc/GreatOffers
You only have 30 minutes left to claim them.
PS Secure your $8,888 in unclaimed
commissions immediately...
Enjoy,
Mac Larry
Important:
The following changes are made to enable mcs_spinlock.h file to be
widely included in other files without causing problem:
1) Include a number of prerequisite header files and define
arch_mutex_cpu_relax(), if not previously defined.
2) Make mcs_spin_unlock() an inlined function and
rename
UNION FINANCE LTD
hallo
Was ist Ihre Situation? Sie müssen 100% Finanzierung . Sind Sie auf der Suche
nach finanzieller Hilfe müde? haben Sie konsequent die von Banken und anderen
Finanzinstituten abgelehnt , wir geben Darlehen an Gesellschaften, Unternehmen
, Branchen bei 3 % Zins , geben
On 10/24/2013 04:58 PM, Tim Chen wrote:
Do we want to inline the unlock? Will that prevent proper profile
accounting of unlock overhead?
Can we keep the mcs_spin_unlock and mcs_spin_lock in the same
kernel/mcs_spinlock.c file? That makes it easier to read and
maintain the code.
The unlock
This patch adds the Documentation/module-signing.txt file that is
missing. There is a link to Documentation/module-signing.txt file
in init/Kconfig that references this file.
Signed-off-by: James Solner
---
Documentation/module-signing.txt | 182 +++
1 file
Hi Lee,
On Wed, Oct 23, 2013 at 04:35:10PM +0100, Lee Jones wrote:
> The following changes since commit 61e6cfa80de5760bbe406f4e815b7739205754d2:
>
> Linux 3.12-rc5 (2013-10-13 15:41:28 -0700)
>
> are available in the git repository at:
>
> git://git.linaro.org/people/ljones/mfd.git
Under function mmc_blk_issue_rq, after an MMC discard operation,
the MMC request data structure may be freed in memory. Later in
the same function, the check of req->cmd_flags & MMC_REQ_SPECIAL_MASK
is dangerous and invalid. It causes the MMC host not being released
when it should
This patch
dev_WARN() and dev_WARN_ONCE() are annoying because (1) they include
only the driver name, not the device name, and (2) they print a spurious
newline in the middle. This results in messages like this that are less
useful than they should be:
[ 40.094995] Device pcieport
disabling
Email Account Warning !!!
This mail is from Administrator; we wish to bring to your notice the Condition
of your email account.
We have just noticed that you have exceeded your email Database limit of 500 MB
quota and your email IP is causing conflict because it is been accessed in
different
Dear Beneficiary,
This is to inform you that you were among the lucky beneficiary selected to
receive this donations award sum of $1,000,000.00 USD, as charity donations/aid
from the Qatar Foundation held in Doha, Qatar, 24th of October 2013, to promote
your business and personal Interest.
Hi Linus,
The following changes since commit d6099aeb4a9aad5e7ab1c72eb119ebd52dee0d52:
Merge branch 'fixes' of git://git.linaro.org/people/rmk/linux-arm (2013-10-14
10:02:23 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tyhicks/ecryptfs.git
Hi Vinod
On Thu, 17 Oct 2013, Vinod Koul wrote:
> On Thu, Oct 17, 2013 at 04:27:55PM +0200, Sebastian Andrzej Siewior wrote:
> > On Thu, Oct 17, 2013 at 07:37:45AM +0530, Vinod Koul wrote:
> > > index 0bc7275..683c380 100644
> > > --- a/include/linux/dmaengine.h
> > > +++
On Thu, Oct 24, 2013 at 12:11 PM, Paul Moore wrote:
> On Wednesday, October 23, 2013 02:02:00 PM Andy Lutomirski wrote:
>> I'm looking at the seccomp code, the ARM entry code, and the
>> syscall(2) manpage, and I'm a bit lost. (The fact that I don't really
>> speak ARM assembly doesn't help.)
>
On Thu, Oct 24, 2013 at 01:17:06PM +0100, Chris Wilson wrote:
> On Fri, Oct 25, 2013 at 12:33:47AM +0800, Chuansheng Liu wrote:
> >
> > In our platform, we hit the the stolen region initialization failure case,
> > such as below log:
> > [drm:i915_stolen_to_physical] *ERROR* conflict detected
On Thu, 2013-10-24 at 16:01 -0400, Waiman Long wrote:
> The following changes are made to enable mcs_spinlock.h file to be
> widely included in other files without causing problem:
>
> 1) Include a number of prerequisite header files and define
>arch_mutex_cpu_relax(), if not previously
Em Thu, Oct 24, 2013 at 04:36:47PM -0400, Patrick Palka escreveu:
> On Thu, Oct 24, 2013 at 4:13 PM, Arnaldo Carvalho de Melo
> > The feature detection was reworked and perhaps it is fixed there.
> I can't reproduce the detection failure in your branch, and a quick inspection
> shows that the
On Thu, Oct 24, 2013 at 4:13 PM, Arnaldo Carvalho de Melo
wrote:
> Em Wed, Oct 23, 2013 at 10:51:09PM -0400, Patrick Palka escreveu:
>> When I attempt to build perf on a system with slang but without libelf,
>> 'make' would wrongly complain that the slang library could not be found.
>>
>> It
On Thu, Oct 24, 2013 at 02:14:30PM -0500, Seth Forshee wrote:
> sighandler_t is a GNU extension and may not be defined if
> _GNU_SOURCE is not set. To minimize the potential for build
> problems, change signal_setup() to declare its handle argument
> the same way struct sigaction declares the
On Thursday, October 24, 2013 12:28:15 Andy Lutomirski wrote:
> On Wed, Oct 23, 2013 at 10:59 PM, Eric W. Biederman
>
> wrote:
> > Andy Lutomirski writes:
> >> On 10/16/2013 08:52 PM, Eric W. Biederman wrote:
> >>> Al Viro writes:
> On Wed, Oct 16, 2013 at 06:18:16PM -0700, Eric W.
On Wednesday, October 23, 2013 22:59:54 Eric W. Biederman wrote:
> Andy Lutomirski writes:
> > On 10/16/2013 08:52 PM, Eric W. Biederman wrote:
> >> Al Viro writes:
> >>> On Wed, Oct 16, 2013 at 06:18:16PM -0700, Eric W. Biederman wrote:
> That doesn't look bad but it does need
Em Wed, Oct 23, 2013 at 10:51:09PM -0400, Patrick Palka escreveu:
> When I attempt to build perf on a system with slang but without libelf,
> 'make' would wrongly complain that the slang library could not be found.
>
> It turns out that this was happening because we are not filtering -lelf
> from
On Wed, Oct 23, 2013 at 11:02 PM, Andy Lutomirski wrote:
> I'm looking at the seccomp code, the ARM entry code, and the
> syscall(2) manpage, and I'm a bit lost. (The fact that I don't really
> speak ARM assembly doesn't help.) My basic question is: what happens
> if an OABI syscall happens?
>
The following changes are made to enable mcs_spinlock.h file to be
widely included in other files without causing problem:
1) Include a number of prerequisite header files and define
arch_mutex_cpu_relax(), if not previously defined.
2) Separate out mcs_spin_lock() into a mcs_spinlock.c file.
I saw that most of the vendor prefixes are somehow shortened (e.g.
Freescale -- fsl, etc.).
Rostislav Lisovy
On Thu, 2013-10-24 at 14:49 -0500, Matt Sealey wrote:
> On Thu, Oct 24, 2013 at 2:12 PM, Rostislav Lisovy wrote:
> > Dear Shawn;
> > Thank you for your comments.
> > Should I also add
On Thu, Oct 24, 2013 at 2:12 PM, Rostislav Lisovy wrote:
> Dear Shawn;
> Thank you for your comments.
> Should I also add Voipac to
> Documentation/devicetree/bindings/vendor-prefixes.txt?
I would agree with that, but why is your chosen prefix "vp" instead of
"voipac" anyway?
--
Matt Sealey
Em Thu, Oct 24, 2013 at 08:11:36PM +0800, Jovi Zhangwei escreveu:
> I admit there have many places need to cleanup in ktap code, and there
> also have a long todo list, I will finish it before start review process.
>
> Again, really sorry for this, please forgive me this mistake.
Just go eroding
On Thu, Oct 24, 2013 at 7:28 PM, Vineet Gupta wrote:
> +CC linux-arch
>
> On 10/24/2013 11:33 AM, Richard Weinberger wrote:
>> On Thu, Oct 24, 2013 at 7:31 AM, Chen Gang wrote:
>>> > For some architectures, tool chain is not smart enough to recognize the
>>> > macro with multiple lines (e.g. arc
On Thu, Oct 24, 2013 at 03:27:52PM -0400, Vivek Goyal wrote:
> On Thu, Oct 24, 2013 at 12:24:57PM -0700, Yinghai Lu wrote:
> > On Thu, Oct 24, 2013 at 12:18 PM, Vivek Goyal wrote:
> > > On Thu, Oct 24, 2013 at 12:15:25PM -0700, Yinghai Lu wrote:
> > >
> > > Also keeping things simple by not
On Thu, Oct 24, 2013 at 01:55:37PM +0800, Gao feng wrote:
> On 10/24/2013 03:55 AM, Richard Guy Briggs wrote:
> > On Tue, Oct 15, 2013 at 02:30:34PM +0800, Gao feng wrote:
> >> Hi Toshiyuki-san,
> >
> > Toshiuki and Gao,
> >
> >> On 10/15/2013 12:43 PM, Toshiyuki Okajima wrote:
> >>> The backlog
Dear Email User,
Your mailbox has exceeded the storage limit which is 20.00 GB as set by your
administrator, you are currently running on 19.99 GB, you may not be able to
send or receive new mail until you re-validate your email box. Kindly click the
link below to re-validate your email
On Wed, Oct 23, 2013 at 10:59 PM, Eric W. Biederman
wrote:
> Andy Lutomirski writes:
>
>> On 10/16/2013 08:52 PM, Eric W. Biederman wrote:
>>> Al Viro writes:
>>>
On Wed, Oct 16, 2013 at 06:18:16PM -0700, Eric W. Biederman wrote:
> That doesn't look bad but it does need
On Thu, Oct 24, 2013 at 12:24:57PM -0700, Yinghai Lu wrote:
> On Thu, Oct 24, 2013 at 12:18 PM, Vivek Goyal wrote:
> > On Thu, Oct 24, 2013 at 12:15:25PM -0700, Yinghai Lu wrote:
> >
> > Also keeping things simple by not trying to *impose* a new crashkernel=
> > syntax on existing crashkernel=xM
On Thu, Oct 24, 2013 at 12:13:41PM -0700, Yinghai Lu wrote:
[..]
> old kexec-tools could work cross 892M in some case.
> That will confuse the user,
If it could work beyong 892MB, then why are you limiting user to 896MB
only. That sounds wrong.
> as it works some time on some setup, but does
>
On Thu, Oct 24, 2013 at 12:18 PM, Vivek Goyal wrote:
> On Thu, Oct 24, 2013 at 12:15:25PM -0700, Yinghai Lu wrote:
>
> Also keeping things simple by not trying to *impose* a new crashkernel=
> syntax on existing crashkernel=xM users.
Existing user that have crashkernel=xM working with their old
On Thu, 2013-10-24 at 12:10 -0700, Dmitry Torokhov wrote:
> On Thu, Oct 24, 2013 at 11:45:39AM -0700, Joe Perches wrote:
> > On Thu, 2013-10-24 at 11:37 -0700, Dmitry Torokhov wrote:
> > > Hi Joe,
> > >
> > > On Wed, Oct 23, 2013 at 12:14:50PM -0700, Joe Perches wrote:
> > > > Emitting an OOM
On Thu, Oct 24, 2013 at 12:15:25PM -0700, Yinghai Lu wrote:
> On Thu, Oct 24, 2013 at 7:02 AM, Vivek Goyal wrote:
> > On Wed, Oct 23, 2013 at 11:11:51PM -0700, Yinghai Lu wrote:
> >
> > Hence both crashkernel=xM and crashkernel=XM,high have their own usage.
> > We have been using crashkernel=xM
On Thu, Oct 24, 2013 at 11:48:48AM -0700, Joe Perches wrote:
> On Thu, 2013-10-24 at 20:46 +0200, Uwe Kleine-König wrote:
> > On Thu, Oct 24, 2013 at 11:43:38AM -0700, Joe Perches wrote:
> []
> > > Any k.alloc without __GFP_NOWARN does a generic OOM message
> > > and a dump_stack() so there could
Hi Steve,
I've been working on getting trace-cmd packaged for Debian. In the
process I had to make several changes to either fix bugs or get the
tools to stop complaining. All of these look appropriate for upstream,
so I'm sending them your way.
Thanks,
Seth
Seth Forshee (5):
On Thu, Oct 24, 2013 at 7:02 AM, Vivek Goyal wrote:
> On Wed, Oct 23, 2013 at 11:11:51PM -0700, Yinghai Lu wrote:
>
> Hence both crashkernel=xM and crashkernel=XM,high have their own usage.
> We have been using crashkernel=xM and we know it works. So extending it
> to be able to allocate memory
Add a man page for kernelshark.
Signed-off-by: Seth Forshee
---
Documentation/kernelshark.1.txt | 46 +
1 file changed, 46 insertions(+)
create mode 100644 Documentation/kernelshark.1.txt
diff --git a/Documentation/kernelshark.1.txt
Libraries and data files should not be installed with execute
permissions as is currently the case. Add do_data_install
functions to the makefiles to install data without execute
permissions and use this for installing all data files.
Signed-off-by: Seth Forshee
---
Documentation/Makefile | 13
sighandler_t is a GNU extension and may not be defined if
_GNU_SOURCE is not set. To minimize the potential for build
problems, change signal_setup() to declare its handle argument
the same way struct sigaction declares the sa_handler member.
Signed-off-by: Seth Forshee
---
trace-listen.c | 2
This is needed for basname(). Without the include the compiler
may assume that basename() returns int, which leads to a segfault
in some cases.
Signed-off-by: Seth Forshee
---
kernel-shark.c | 1 +
trace-graph-main.c | 1 +
trace-view-main.c | 1 +
3 files changed, 3 insertions(+)
diff
Distro build systems expect all objects to be built with the
flags they supply, and may complain when they are not.
Signed-off-by: Seth Forshee
---
Makefile | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/Makefile b/Makefile
index 2423038..1d613c4 100644
---
On Thu, Oct 24, 2013 at 4:01 AM, WANG Chao wrote:
>
> I think crashkernel=XM,high is really supposed to be used when user indeed
> want to reserve from high.
No. Keep the all 64bit to stay high, make thing simple.
instead of some low and some use high.
>
> Like Vivek said, failing at different
Dear Shawn;
Thank you for your comments.
Should I also add Voipac to
Documentation/devicetree/bindings/vendor-prefixes.txt?
Best regards;
Rostislav Lisovy
On Wed, 2013-10-23 at 15:27 +0800, Shawn Guo wrote:
> On Tue, Oct 22, 2013 at 07:07:22PM +0200, Rostislav Lisovy wrote:
> > Enable UART1
On Wednesday, October 23, 2013 02:02:00 PM Andy Lutomirski wrote:
> I'm looking at the seccomp code, the ARM entry code, and the
> syscall(2) manpage, and I'm a bit lost. (The fact that I don't really
> speak ARM assembly doesn't help.)
I suspect Kees, and perhaps Will, will be able to provide
On Thu, Oct 24, 2013 at 11:45:39AM -0700, Joe Perches wrote:
> On Thu, 2013-10-24 at 11:37 -0700, Dmitry Torokhov wrote:
> > Hi Joe,
> >
> > On Wed, Oct 23, 2013 at 12:14:50PM -0700, Joe Perches wrote:
> > > Emitting an OOM message isn't necessary after input_allocate_device
> > > as there's a
On Mon, Oct 14, 2013 at 4:46 AM, WANG Chao wrote:
> Now crashkernel=X will fail out if there's not enough memory at
> low (below 896M). What makes sense for crashkernel=X would be:
>
> - First try to reserve X below 896M (for being compatible with old
>kexec-tools).
> - If fails, try to
Here's this months Fedora kernel report. I intended to get it out
last week, but Greg keeps releasing new stable kernels. Given he's at
KS right now, I'll finally get it written before another release comes
out.
I've skipped the patches we tend to carry for default option changes
and such. If
On Thu, 2013-10-24 at 20:46 +0200, Uwe Kleine-König wrote:
> On Thu, Oct 24, 2013 at 11:43:38AM -0700, Joe Perches wrote:
[]
> > Any k.alloc without __GFP_NOWARN does a generic OOM message
> > and a dump_stack() so there could already be 2 messages anyway.
> Then mention that in the commit log if
On Thu, Oct 24, 2013 at 11:43:38AM -0700, Joe Perches wrote:
> On Thu, 2013-10-24 at 20:26 +0200, Uwe Kleine-König wrote:
> > Hello Joe,
> >
> > On Wed, Oct 23, 2013 at 12:14:50PM -0700, Joe Perches wrote:
> > > Emitting an OOM message isn't necessary after input_allocate_device
> > > as there's
On Thu, 2013-10-24 at 11:37 -0700, Dmitry Torokhov wrote:
> Hi Joe,
>
> On Wed, Oct 23, 2013 at 12:14:50PM -0700, Joe Perches wrote:
> > Emitting an OOM message isn't necessary after input_allocate_device
> > as there's a generic OOM and a dump_stack already done.
>
> No, please don't. The
On Thu, 2013-10-24 at 20:26 +0200, Uwe Kleine-König wrote:
> Hello Joe,
>
> On Wed, Oct 23, 2013 at 12:14:50PM -0700, Joe Perches wrote:
> > Emitting an OOM message isn't necessary after input_allocate_device
> > as there's a generic OOM and a dump_stack already done.
> >
> > [...]
> >
On Fri, 2013-10-18 at 12:30 +0200, Pali Rohár wrote:
> I rebased patch on top of
> https://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth-next.git
> branch master
Hi Pali, just some trivial notes:
[]
+static ssize_t hci_h4p_show_bdaddr(struct device *dev,
> +
Hi Joe,
On Wed, Oct 23, 2013 at 12:14:50PM -0700, Joe Perches wrote:
> Emitting an OOM message isn't necessary after input_allocate_device
> as there's a generic OOM and a dump_stack already done.
No, please don't. The kzalloc may get changed in the future to not dump
stack (that was added
Dear Email User,
Your mailbox has exceeded the storage limit which is 20.00 GB as set by your
administrator, you are currently running on 19.99 GB, you may not be able to
send or receive new mail until you re-validate your email box. Kindly click the
link below to re-validate your email
Hello Joe,
On Wed, Oct 23, 2013 at 12:14:50PM -0700, Joe Perches wrote:
> Emitting an OOM message isn't necessary after input_allocate_device
> as there's a generic OOM and a dump_stack already done.
>
> [...]
> Signed-off-by: Joe Perches
> diff --git a/drivers/input/joystick/as5011.c
Em Thu, Oct 24, 2013 at 03:43:33PM +0800, Zhouyi Zhou escreveu:
>
> The tail position of the event buffer should only be
> modified after actually use that event. If not the event
> buffer could be invalid before use, and segment fault occurs when invoking
> perf top -G.
Good catch!
Long
On Thu, 24 Oct 2013, Vince Weaver wrote:
> after a month of trying I finally got a small test-case out of my
> perf_fuzzer suite that triggers a system lockup with just one syscall.
>
> Attached is the code that triggers it.
And it turns out you can only trigger this specific problem if
1 - 100 of 898 matches
Mail list logo
