expand_stack() runs with a shared mmap_sem lock. Because of this, there
could be multiple concurrent stack expansions in the same mm, which may
cause problems in the vma gap update code.
I propose to solve this by taking the mm->page_table_lock around such vma
expansions, in order to avoid the con
On Fri, Nov 30, 2012 at 8:01 PM, Rob Herring wrote:
[...]
>> This is based on next-20121126.
>
> I'll apply the series but I need a stable base. Looks like xtensa has
> the dependency. Or I can just drop xtensa.
Please drop it, I will follow up with a conversion.
--
Thanks.
-- Max
--
To unsub
On Fri, 30 Nov 2012, Tejun Heo wrote:
> Hey, again.
>
> Can you please test whether the following patch makes any difference?
>
> Thanks!
>
> diff --git a/kernel/workqueue.c b/kernel/workqueue.c
> index 042d221..26368ef 100644
> --- a/kernel/workqueue.c
> +++ b/kernel/workqueue.c
> @@ -1477,7 +1
On Fri, 30 Nov 2012 14:30:23 -0800
Dmitry Torokhov wrote:
> Hi Chris,
>
> On Friday, November 30, 2012 01:54:06 PM Chris Moeller wrote:
> > I've submitted versions of this with prior patch sets, and this part
> > was never accepted, possibly because it depended on other patches to
> > work, or p
On Sat, Dec 01, 2012 at 02:22:44AM +0100, Cong Ding wrote:
> On Fri, Nov 30, 2012 at 10:33 PM, Hans J. Koch wrote:
> > On Fri, Nov 30, 2012 at 12:12:46PM +0100, Tux9 wrote:
> >> I like Vitalii's solution more. Hans's solution assign the value
> >> -ENOMEM to ret in every round of the loop, which i
On 11/30/2012 09:36 AM, Greg KH wrote:
On Fri, Nov 30, 2012 at 05:28:47PM +, Arnd Bergmann wrote:
On Wednesday 28 November 2012, Eli Billauer wrote:
Xillybus is a general-purpose framework for communication between programmable
logic (FPGA) and a host. It provides a simple connection betwe
Witaj,
Żadna firma nie może być istnieć bez zadowolonych Klientów.
Nasza firma zajmuje się badaniami, planowaniem strategii, wdrożeniami
wewnętrznych działów obsługi Klienta i contact center, szkoleniami z zakresu
obsługi Klienta, wdrożeń contact center oraz sprzedaży konsultacyjnej.
Zamów tera
On Fri, Nov 30, 2012 at 02:00:48AM +, Al Viro wrote:
> OK, that settles it. WARN_ON() and printks in the area can be dropped;
> the right fix is below. However, there's a similar place in cifs that
> also needs to be dealt with and I really, really wonder why the hell do
> we do d_drop() in
From: Namjae Jeon
In function f2fs_mkdir, err is being initialized without even checking
if there was any error in new inode creation. So, instead check the
inode error and make use of error/return condition.
Signed-off-by: Namjae Jeon
Signed-off-by: Amit Sahrawat
---
fs/f2fs/namei.c |3 +
From: Namjae Jeon
No need to initialize "struct f2fs_gc_kthread *gc_th = NULL",
as gc_th = NULL, will be taken care by the return values of kmalloc().
And fix codes in other places.
Signed-off-by: Namjae Jeon
Signed-off-by: Amit Sahrawat
---
fs/f2fs/gc.c |2 +-
fs/f2fs/segment.c |
From: Namjae Jeon
If the filesystem is mounted as read-only then return from that point itself
instead of first doing a writeout/wait and then checking for read-only
condition.
Signed-off-by: Namjae Jeon
Signed-off-by: Amit Sahrawat
---
fs/f2fs/file.c |5 +++--
1 file changed, 3 insertion
From: Namjae Jeon
Since, __GFP_ZERO is used while f2fs inode allocation, so we do not
need memset for f2fs_inode_info, as this is already zeroed out.
Signed-off-by: Namjae Jeon
Signed-off-by: Amit Sahrawat
---
fs/f2fs/super.c |1 -
1 file changed, 1 deletion(-)
diff --git a/fs/f2fs/super
From: Namjae Jeon
print the invalid argument/value from parse_options in case of
mount failure.
Signed-off-by: Namjae Jeon
Signed-off-by: Amit Sahrawat
---
fs/f2fs/super.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
index 4360600..c72e517 100644
From: Namjae Jeon
When CONFIG_CC_OPTIMIZE_FOR_SIZE is enabled in the kernel, -Os optimisation
flag is passed to gcc for compilation, and somehow while trying to optimize
the code, compiler is might not able to see the initialisation of variable
ne struct variable inside the get_node_info() functi
On Fri, Nov 30, 2012 at 06:00:02PM +0800, Wang YanQing wrote:
> I found the mainline's r8169 works the same as realtek's driver,
> the first time don't work, but it works after reboot, the reason
> is the pci driver's shutdown don't call rtl_rar_set in 3.0 stable
> tree but the mainline does.
Sorry
On Fri, Nov 30, 2012 at 10:33 PM, Hans J. Koch wrote:
> On Fri, Nov 30, 2012 at 12:12:46PM +0100, Tux9 wrote:
>> I like Vitalii's solution more. Hans's solution assign the value
>> -ENOMEM to ret in every round of the loop, which is a kind of wasting
>> CPU cycles.
>
> The difference between
> 1 f
> What I actually meant was: can "this" CPU avoid stopping other CPUs so early?
> If we stop the other CPUs when this CPU is ready to
> stop itself then there will never be such deadlocks.
Let me explain my opinion.
When we focus on the deadlock only, the code will be simple by moving
smp_sen
Greg KH writes:
> Is this really needed? For the large majority of the stable
> patches, specifically enumerating this isn't a big deal, it's a tiny
> patch, and if you think I'll remember to tell you which specific
> clause you didn't follow, then you think I have more spare time than
> I reall
Greg --
Thanks for the very quick response.
Greg KH writes:
> This is an obvious one, it needs to be upstream first.
>
> Or if not, a whole lot of explaination saying that you know it
> isn't, and why it isn't, and why it isn't applicable there,
I thought that I did provide exactly this inform
On Fri, Nov 30, 2012 at 4:25 PM, tip-bot for Fenghua Yu
wrote:
> Commit-ID: 474355fe313391de2429ae225e0fb02f67ec6c31
> Gitweb: http://git.kernel.org/tip/474355fe313391de2429ae225e0fb02f67ec6c31
> Author: Fenghua Yu
> AuthorDate: Thu, 29 Nov 2012 17:47:43 -0800
> Committer: H. Peter Anvi
On Fri, Nov 30, 2012 at 05:44:13PM -0700, Anthony Foiani wrote:
>
> From: Anthony Foiani
>
> Having recently received a formletter rejection on a stable patch, I
> found it difficult to determine exactly which guideline I had missed.
>
> Numbering the guidelines will allow the stable maintainer
On Fri, Nov 30, 2012 at 09:48:05AM +, Grant Likely wrote:
> > If you attempt to stick a 'reg' in a block nested below a
> > 'device_type="pci"' the kernel throws lots of error messsages and
> > generates bad address mappings.
>
> Have you added the appropriate #address-cells and #size-cells t
Hi Thorsten,
On Fri, Nov 30, 2012 at 01:39:03PM +0100, Thorsten Leemhuis wrote:
> /me wonders how to elegantly get out of his man-in-the-middle position
You control the mighty koji :-)
But seriously, this is very helpful, thank you! John now also Cc'd
directly.
> John was able to reproduce the
From: Anthony Foiani
Having recently received a formletter rejection on a stable patch, I
found it difficult to determine exactly which guideline I had missed.
Numbering the guidelines will allow the stable maintainer to quickly
and easily indicate which guidelines have not been followed.
The
Commit-ID: 11af32b69ef7ee64c7d8848cad71a6f3749d9e37
Gitweb: http://git.kernel.org/tip/11af32b69ef7ee64c7d8848cad71a6f3749d9e37
Author: H. Peter Anvin
AuthorDate: Thu, 29 Nov 2012 13:28:39 -0800
Committer: H. Peter Anvin
CommitDate: Thu, 29 Nov 2012 13:28:39 -0800
x86, 386 removal: Docu
Commit-ID: 45c39fb0cc20d24da08d5bb159f57d191098104d
Gitweb: http://git.kernel.org/tip/45c39fb0cc20d24da08d5bb159f57d191098104d
Author: H. Peter Anvin
AuthorDate: Wed, 28 Nov 2012 11:50:30 -0800
Committer: H. Peter Anvin
CommitDate: Thu, 29 Nov 2012 13:25:39 -0800
x86, cleanups: Simplif
Commit-ID: a5c2a893dbd4956a72fb261e8790d19f67b52c99
Gitweb: http://git.kernel.org/tip/a5c2a893dbd4956a72fb261e8790d19f67b52c99
Author: H. Peter Anvin
AuthorDate: Wed, 28 Nov 2012 11:50:28 -0800
Committer: H. Peter Anvin
CommitDate: Thu, 29 Nov 2012 13:23:03 -0800
x86, 386 removal: Remo
Commit-ID: 094ab1db7cb7833cd4c820acd868fc26acf3f08e
Gitweb: http://git.kernel.org/tip/094ab1db7cb7833cd4c820acd868fc26acf3f08e
Author: H. Peter Anvin
AuthorDate: Wed, 28 Nov 2012 11:50:27 -0800
Committer: H. Peter Anvin
CommitDate: Thu, 29 Nov 2012 13:23:02 -0800
x86, 386 removal: Remo
Commit-ID: 7ac468b1300f35143a9b5b100e3970ca7ae1d9b8
Gitweb: http://git.kernel.org/tip/7ac468b1300f35143a9b5b100e3970ca7ae1d9b8
Author: H. Peter Anvin
AuthorDate: Wed, 28 Nov 2012 11:50:25 -0800
Committer: H. Peter Anvin
CommitDate: Thu, 29 Nov 2012 13:23:02 -0800
x86, 386 removal: Remo
Commit-ID: d55c5a93db2d5fa95f233ab153f594365d95b777
Gitweb: http://git.kernel.org/tip/d55c5a93db2d5fa95f233ab153f594365d95b777
Author: H. Peter Anvin
AuthorDate: Wed, 28 Nov 2012 11:50:24 -0800
Committer: H. Peter Anvin
CommitDate: Thu, 29 Nov 2012 13:23:01 -0800
x86, 386 removal: Remo
Commit-ID: eb068e781020cf491333c773fb41820b57bfada4
Gitweb: http://git.kernel.org/tip/eb068e781020cf491333c773fb41820b57bfada4
Author: H. Peter Anvin
AuthorDate: Wed, 28 Nov 2012 11:50:23 -0800
Committer: H. Peter Anvin
CommitDate: Thu, 29 Nov 2012 13:23:01 -0800
x86, 386 removal: Remo
On Fri, Nov 30, 2012 at 05:19:28PM -0700, Anthony Foiani wrote:
> Greg KH writes:
> > This is not the correct way to submit patches for inclusion in the
> > stable kernel tree. Please read Documentation/stable_kernel_rules.txt
> > for how to do this properly.
>
> My checklist against stable_kern
Greg KH writes:
> This is not the correct way to submit patches for inclusion in the
> stable kernel tree. Please read Documentation/stable_kernel_rules.txt
> for how to do this properly.
My checklist against stable_kernel_rules.txt is below.
I could only find two reasons why you are saying thi
On Fri, Nov 30, 2012 at 02:10:47PM -0800, Olof Johansson wrote:
> Hi,
>
> On Thu, Oct 4, 2012 at 1:58 AM, Simon Horman wrote:
> > On Thu, Oct 04, 2012 at 08:34:54AM +, Arnd Bergmann wrote:
> >> On Wednesday 03 October 2012, Simon Horman wrote:
> >> > I looked through my fines and found a conf
Commit-ID: 474355fe313391de2429ae225e0fb02f67ec6c31
Gitweb: http://git.kernel.org/tip/474355fe313391de2429ae225e0fb02f67ec6c31
Author: Fenghua Yu
AuthorDate: Thu, 29 Nov 2012 17:47:43 -0800
Committer: H. Peter Anvin
CommitDate: Fri, 30 Nov 2012 15:18:16 -0800
x86/microcode_intel_early.
Commit-ID: da7d824a00ec0f4d19e2b51653410bde0de40226
Gitweb: http://git.kernel.org/tip/da7d824a00ec0f4d19e2b51653410bde0de40226
Author: Fenghua Yu
AuthorDate: Thu, 29 Nov 2012 17:47:42 -0800
Committer: H. Peter Anvin
CommitDate: Fri, 30 Nov 2012 15:18:15 -0800
x86/microcode_intel_lib.c:
Commit-ID: d42bdf2139115faa4d5bdb0dc591d435a644fde4
Gitweb: http://git.kernel.org/tip/d42bdf2139115faa4d5bdb0dc591d435a644fde4
Author: Fenghua Yu
AuthorDate: Thu, 29 Nov 2012 17:47:41 -0800
Committer: H. Peter Anvin
CommitDate: Fri, 30 Nov 2012 15:18:15 -0800
x86/microcode_core_early.c
Commit-ID: 17f1087f1a80d2dfada790c31720eb6a57da2d1f
Gitweb: http://git.kernel.org/tip/17f1087f1a80d2dfada790c31720eb6a57da2d1f
Author: Fenghua Yu
AuthorDate: Thu, 29 Nov 2012 17:47:40 -0800
Committer: H. Peter Anvin
CommitDate: Fri, 30 Nov 2012 15:18:14 -0800
x86/microcode_intel.h: Def
Commit-ID: 31ae1d90c127310c67618b8bd79f01c394116187
Gitweb: http://git.kernel.org/tip/31ae1d90c127310c67618b8bd79f01c394116187
Author: Fenghua Yu
AuthorDate: Fri, 30 Nov 2012 07:45:51 -0800
Committer: H. Peter Anvin
CommitDate: Fri, 30 Nov 2012 15:18:14 -0800
x86, doc: Early microcode
On 01/12/12 03:48, Alex Williamson wrote:
On Fri, 2012-11-30 at 17:14 +1100, Alexey Kardashevskiy wrote:
This patch initializes IOMMU groups based on the IOMMU
configuration discovered during the PCI scan on POWERNV
(POWER non virtualized) platform. The IOMMU groups are
to be used later by VFIO
-- Forwarded message --
From: Steve French
Date: Fri, Nov 30, 2012 at 5:59 PM
Subject: [GIT] 2 CIFS Fixes for Regressions
To: Linus Torvalds
Cc: linux-c...@vger.kernel.org
Resending the merge request from earlier in the week. These are two
low risk, small fixes, that fix cifs r
t; expose the call chain. It won't help at all in case A though :\
>
> Regards,
> Peter Hurley
>
> -- >% --
> Subject: [PATCH -next] tty: debug: Narrow possible causes of access-after-free
>
>
> Signed-off-by: Peter Hurley
> ---
> drivers/tty/pty.c |
On Fri, Nov 30, 2012 at 10:39:06PM +0100, Hans J. Koch wrote:
> On Fri, Nov 30, 2012 at 01:16:19PM +0200, Vitalii Demianets wrote:
> > On Friday 30 November 2012 01:58:22 Hans J. Koch wrote:
> > > On Thu, Nov 29, 2012 at 06:36:59PM +0200, Vitalii Demianets wrote:
> > > > > On Thursday 29 November 2
Hi
After Frank posted a patch i managed the 3.6.7-rt18 kernel to boot:
There are some local platform modifications for arm mach-pcm043 but nothing
which should
cause this. The kernel got renamed so that the hw debugger works. HR_TIMERS are
disabled in my config.
The kernel continues to work af
On Fri, 30 Nov 2012 22:59:13 +
Seiji Aguchi wrote:
> >
> > Let's step back a bit. Please identify with great specificity the code
> > sites which are stopping other CPUs before taking locks which
> > those other CPUs might have been holding.
> >
> > Then let's see what we can do to fix up
I get a board with 8168e-vl(10ec:8168 with RTL_GIGA_MAC_VER_34),
everything looks well first, I can use ifconfig to set ip, netmask,
etc. And the rx/tx statistics show by ifconfig looks good when I
ping another host or ping it from another host. But it don't work,
I can't get ICMP REPLAY from both
Hi,
On Tue, Nov 13, 2012 at 12:32 PM, Belisko Marek wrote:
> On Tue, Nov 13, 2012 at 11:11 AM, Ondrej Zary
> wrote:
>> On Monday 12 November 2012, Belisko Marek wrote:
>>> Hi Ondrej,
>>>
>>> On Fri, Nov 9, 2012 at 10:42 PM, Ondrej Zary
>> wrote:
>>> > Unify struct ft1000_info between ft1000-usb
Hi Linus,
The following changes since commit 9489e9dcae718d5fde988e4a684a0f55b5f94d17:
Linux 3.7-rc7 (2012-11-25 17:59:19 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/urgent
H. Peter Anvin (2):
x86, kvm: Remove incorrect
On 30.11.2012 23:52, Tejun Heo wrote:
Hello, Zlatko.
Sorry about the delay. Your message was in my spam folder. The
attachment seems to have confused the filter.
On Sat, Nov 17, 2012 at 02:01:29PM +0100, Zlatko Calusic wrote:
This week I spent some hours tracking a regression in 3.7 kernel
t
The following changes since commit 9489e9dcae718d5fde988e4a684a0f55b5f94d17:
Linux 3.7-rc7 (2012-11-25 17:59:19 -0800)
are available in the git repository at:
git://linux-c6x.org/git/projects/linux-c6x-upstreaming.git tags/for-linus
for you to fetch changes up to 93bbd0c087eb299e0fe11c59d34
On Sat, Dec 01, 2012 at 09:40:41AM +1100, Dave Chinner wrote:
> So it was based on this interface?
Based on that. I had dropped the inode operation as it's not really
a generic operation but a callback for either the buffered I/O code
or direct I/O and should be treated as such. I've also split
Thank you for giving me the comment.
> - Makes the logic in this area even more twisty and complex, when
> what we need to do is to simplify it
>
> - Reinitialises in-use locks
>
> - Gives the boolean variable "yes" three states, but didn't rename
> that variable to something appropriate.
On 11/15/2012 11:20 AM, Grant Likely wrote:
On Mon, 12 Nov 2012 16:28:22 -0500, Murali Karicheri
wrote:
This adds OF support to DaVinci SPI controller to configure platform
data through device bindings.
Signed-off-by: Murali Karicheri
Hi Murali,
Comments below...
---
.../devicetree/bin
Hey, again.
Can you please test whether the following patch makes any difference?
Thanks!
diff --git a/kernel/workqueue.c b/kernel/workqueue.c
index 042d221..26368ef 100644
--- a/kernel/workqueue.c
+++ b/kernel/workqueue.c
@@ -1477,7 +1477,10 @@ bool mod_delayed_work_on(int cpu, struct
workqueu
Hello, again.
Can you please try this patch? Thanks!
diff --git a/kernel/workqueue.c b/kernel/workqueue.c
index 042d221..26368ef 100644
--- a/kernel/workqueue.c
+++ b/kernel/workqueue.c
@@ -1477,7 +1477,10 @@ bool mod_delayed_work_on(int cpu, struct
workqueue_struct *wq,
} while (unlike
Hello, Zlatko.
Sorry about the delay. Your message was in my spam folder. The
attachment seems to have confused the filter.
On Sat, Nov 17, 2012 at 02:01:29PM +0100, Zlatko Calusic wrote:
> This week I spent some hours tracking a regression in 3.7 kernel
> that was producing high context switch
On Fri, Nov 30, 2012 at 11:36:01AM -0500, Christoph Hellwig wrote:
> On Fri, Nov 30, 2012 at 01:49:10PM +1100, Dave Chinner wrote:
> > > Ugh. That's a big violation of how buffer-heads are supposed to work:
> > > the block number is very much defined to be in multiples of b_size
> > > (see for exam
On Fri, Nov 30, 2012 at 02:42:14PM -0700, Bjorn Helgaas wrote:
> On Fri, Nov 30, 2012 at 11:41 AM, Bjorn Helgaas wrote:
> > On Fri, Oct 19, 2012 at 6:59 AM, Konrad Rzeszutek Wilk
> > wrote:
> >> On Thu, Oct 18, 2012 at 11:03:36AM +0100, David Vrabel wrote:
> >>> From: David Vrabel
> >>>
> >>> Ba
On Thu, 2012-11-29 at 10:25 +0800, Jiang Liu wrote:
> On 2012-11-29 9:42, Jaegeuk Hanse wrote:
> > On Wed, Nov 28, 2012 at 04:47:42PM +0800, Jiang Liu wrote:
> >> Hi all,
> >>Seems it's a great chance to discuss about the memory hotplug feature
> >> within this thread. So I will try to give som
Dear hackers,
I built scribe, a record/replay engine implemented in the kernel.
If you want to explore the code,
here it is: git://github.com/nviennot/linux-2.6-scribe.git
most of it is in the ./scribe directory.
Warning: contains time-space continuum bending material
Additionally, here is a blo
Hi Chris,
On Friday, November 30, 2012 01:54:06 PM Chris Moeller wrote:
> I've submitted versions of this with prior patch sets, and this part
> was never accepted, possibly because it depended on other patches to
> work, or possibly because it wasn't so cleanly organized. This time,
> I've split
On Fri, 30 Nov 2012 17:11:07 +
Seiji Aguchi wrote:
> If one cpu ,which is taking a logbuf_lock or console_sem,
> receive IPI/NMI from a panicked cpu via smp_send_stop(),
> the panicked cpu hangs up in subsequent kmsg_dump()/printk()
> because logbuf_lock and console_sem are taken in the func
On 11/30/2012 2:01 PM, Eric Paris wrote:
> Do other LSMs need this too Casey? I remember we mentioned how select
> was dangerous :-(
I don't see any missing dependencies, but then, I missed INET.
Yes, you mentioned that it was dangerous.
>
> On Fri, Nov 30, 2012 at 12:28 PM, Casey Schaufler
>
Hi,
On Thu, Oct 4, 2012 at 1:58 AM, Simon Horman wrote:
> On Thu, Oct 04, 2012 at 08:34:54AM +, Arnd Bergmann wrote:
>> On Wednesday 03 October 2012, Simon Horman wrote:
>> > I looked through my fines and found a config that I believe
>> > worked with a derivative of 2.6.35.7.
>> >
>> > It ha
> + ret = cpulist_parse(buf, newmask);
> + if (!ret) {
> + spin_lock(&bdi->wb_lock);
> + task = wb->task;
> + get_task_struct(task);
> + spin_unlock(&bdi->wb_lock);
> + if (task)
> + ret = set_cpus_allowed_ptr(t
Commit-ID: 644c154186386bb1fa6446bc5e037b9ed098db46
Gitweb: http://git.kernel.org/tip/644c154186386bb1fa6446bc5e037b9ed098db46
Author: Vincent Palatin
AuthorDate: Fri, 30 Nov 2012 12:15:32 -0800
Committer: H. Peter Anvin
CommitDate: Fri, 30 Nov 2012 13:48:05 -0800
x86, fpu: Avoid FPU l
Hey Jens
Please git pull the following branch
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
stable/for-jens-3.8
which has one cleanup and one tiny fix.
Please pull!
Roger Pau Monne (2):
xen-blkback: move free persistent grants code
xen-blkfront: free allocated page
Do other LSMs need this too Casey? I remember we mentioned how select
was dangerous :-(
On Fri, Nov 30, 2012 at 12:28 PM, Casey Schaufler
wrote:
> Because NETLABEL depends on INET SECURITY_SMACK
> has to explicitly call out the dependency.
>
> Signed-off-by: Casey Schaufler
> ---
> security/s
Signed-off-by: Marek Belisko
---
Documentation/devicetree/bindings/leds/tca6507.txt | 33
1 file changed, 33 insertions(+)
create mode 100644 Documentation/devicetree/bindings/leds/tca6507.txt
diff --git a/Documentation/devicetree/bindings/leds/tca6507.txt
b/Documentatio
Support added only for leds (not for gpio's).
Signed-off-by: Marek Belisko
---
Changes from v3:
- fix code according Bryan suggestions
- use common leds binding description instead copy'n'paste
- use "-" instead "_" in bindings example for leds names
Changes from v2:
- change compatible property
Signed-off-by: Chris Moeller
---
diff -urpN a/drivers/input/joystick/xpad.c b/drivers/input/joystick/xpad.c
--- a/drivers/input/joystick/xpad.c 2012-11-30 12:33:10.604607590 -0800
+++ b/drivers/input/joystick/xpad.c 2012-11-30 12:41:19.374756212 -0800
@@ -260,13 +260,12 @@ struct usb_xpad
I've submitted versions of this with prior patch sets, and this part
was never accepted, possibly because it depended on other patches to
work, or possibly because it wasn't so cleanly organized. This time,
I've split the LED setting command off into its own static function,
then call that on contr
On Fri, Nov 30, 2012 at 11:55 AM, H. Peter Anvin wrote:
>
> On 11/30/2012 11:54 AM, Vincent Palatin wrote:
> >>
> > I have done a patch v2 according to your suggestions.
> > I will run the testing on it now.
> > I probably need at least 2 to 3 hours to validate it.
> >
>
> That would be super. Le
On Fri, 30 Nov 2012 11:42:40 +0100
Lukas Czerner wrote:
> New wait_event{_interruptible}_lock_irq{_cmd} macros added. This commit
> moves the private wait_event_lock_irq() macro from MD to regular wait
> includes, introduces new macro wait_event_lock_irq_cmd() instead of using
> the old method wi
On Fri, Nov 30, 2012 at 11:41 AM, Bjorn Helgaas wrote:
> On Fri, Oct 19, 2012 at 6:59 AM, Konrad Rzeszutek Wilk
> wrote:
>> On Thu, Oct 18, 2012 at 11:03:36AM +0100, David Vrabel wrote:
>>> From: David Vrabel
>>>
>>> Backend drivers shouldn't transistion to CLOSED unless the frontend is
>>> CLOS
On Fri, Nov 30, 2012 at 01:16:19PM +0200, Vitalii Demianets wrote:
> On Friday 30 November 2012 01:58:22 Hans J. Koch wrote:
> > On Thu, Nov 29, 2012 at 06:36:59PM +0200, Vitalii Demianets wrote:
> > > > On Thursday 29 November 2012 18:05:27 Tux9 wrote:
> > > > > Hans, I think there are something w
These changes make cper_print_aer more consistent with aer_print_error
which is called in the AER interrupt case. The string in the variable
'prefix' is printed at the beginning of each print statement in
cper_print_aer(). The prefix is a string containing the driver name
and the device's path. Lo
This patch will provide a more reliable and easy way for user-space
applications to have access to AER logs rather than reading them from the
message buffer. It also provides a way to notify user-space when an AER
event occurs.
The aer driver is updated to generate a trace event of function 'aer_e
This header file will define a new trace event that will be triggered when
a AER event occurs. The following data will be provided to the trace
event.
char * name - String containing the device path
u32 status -Either the correctable or uncorrectable register
indicating wha
On Fri, Nov 30, 2012 at 12:12:46PM +0100, Tux9 wrote:
> I like Vitalii's solution more. Hans's solution assign the value
> -ENOMEM to ret in every round of the loop, which is a kind of wasting
> CPU cycles.
The difference between
1 files changed, 12 insertions(+), 4 deletions(-) and
1 files change
On 11/30/2012 09:25 PM, Luis R. Rodriguez wrote:
> On Fri, Nov 30, 2012 at 11:18 AM, Luis R. Rodriguez
> wrote:
>> On Fri, Nov 30, 2012 at 12:38 AM, Arend van Spriel
>> wrote:
>>> So what is the rationale here. During mainlining our drivers we had to
>>> remove all uses of 'typedef struct foo fo
On Fri, Nov 30, 2012 at 12:58:25PM -0800, Dmitry Torokhov wrote:
> On Friday, November 30, 2012 12:44:06 PM Greg KH wrote:
> > On Fri, Nov 30, 2012 at 12:09:40PM -0800, Dmitry Torokhov wrote:
> > > On Friday, November 30, 2012 10:57:55 AM Greg KH wrote:
> > > > On Fri, Nov 30, 2012 at 10:45:44AM -0
Hello, Anders.
Sorry about the delay.
On Wed, Nov 28, 2012 at 10:17:28AM -0500, Anders Kaseorg wrote:
> On Wed, 28 Nov 2012, Anders Kaseorg wrote:
> > My Intel 6250 wireless card (iwldvm) can no longer associate with a
> > WPA-Enterprise network (PEAP-MSCHAPv2). To my surprise, I bisected this
On Fri, Nov 30, 2012 at 9:49 PM, Meelis Roos wrote:
>> I tried 3.7-rc5 on an ironlale PC and got the warning in subject. The
>> computer last ran 3.6.0 without any warnings. Second reboot showed the
>> same warning plus a couple of EDID warnings (also below).
>
> Still there with 3.7.0-rc7-00113-g
> I tried 3.7-rc5 on an ironlale PC and got the warning in subject. The
> computer last ran 3.6.0 without any warnings. Second reboot showed the
> same warning plus a couple of EDID warnings (also below).
Still there with 3.7.0-rc7-00113-gcc19528 and 100% reproducible:
[0.646574] WARNING: a
On Fri, 2012-11-30 at 13:39 -0700, Lance Ortiz wrote:
> This patch will provide a more reliable and easy way for user-space
> applications to have access to AER logs rather than reading them from the
> message buffer. It also provides a way to notify user-space when an AER
> event occurs.
Please r
On Friday, November 30, 2012 12:44:06 PM Greg KH wrote:
> On Fri, Nov 30, 2012 at 12:09:40PM -0800, Dmitry Torokhov wrote:
> > On Friday, November 30, 2012 10:57:55 AM Greg KH wrote:
> > > On Fri, Nov 30, 2012 at 10:45:44AM -0800, Dmitry Torokhov wrote:
> > > > However you snipped the rest of my re
On 11/30/2012 12:42 PM, Tejun Heo wrote:
> On Wed, Nov 28, 2012 at 04:03:58PM -0800, Dave Hansen wrote:
>> My system is just qemu booted with:
>>
>> -smp 8 -m 8192 -numa node,nodeid=0,cpus=0-3 -numa node,nodeid=1,cpus=4-7
>>
>> Watch the "PERCPU:" line early in boot, and you can see the "Embedded"
Hi Artem,
Thanks for the taking the time to answer.
On Fri, Nov 30, 2012 at 8:08 AM, Artem Bityutskiy wrote:
>
>> I don't know how many ubi volumes a user typically creates, but I
>> expect not to be too many.
>
> I think I saw something like 8-10 in some peoples' reports.
>
Mmm, that's more th
On Fri, Nov 30, 2012 at 12:39:43PM -0800, H. Peter Anvin wrote:
> On 11/29/2012 10:43 AM, Greg Kroah-Hartman wrote:
> >
> >-/* Used for HOTPLUG */
> >-#define __devinit__section(.devinit.text) __cold notrace
> >-#define __devinitdata__section(.devinit.data)
> >-#define __devinitconst
>> On Fri, Nov 30 2012, Vitaly Andrianov wrote:
>> > This patch fixes a couple of bugs that otherwise impair CMA
>> > functionality on PAE machines:
>> >
>> > - alignment must be a 64-bit type when running on systems with 64-
>> bit
>> > physical addresses. If this is not the case, the limi
On Fri, Nov 30, 2012 at 12:39:01PM -0800, H. Peter Anvin wrote:
> On 11/29/2012 10:43 AM, Greg Kroah-Hartman wrote:
> >From: Greg Kroah-Hartman
> >
> >With the recent work to remove CONFIG_HOTPLUG, we are starting to get a
> >bunch of __devinit section warnings, despite CONFIG_HOTPLUG always being
These changes make cper_print_aer more consistent with aer_print_error
which is called in the AER interrupt case. The string in the variable
'prefix' is printed at the beginning of each print statement in
cper_print_aer(). The prefix is a string containing the driver name
and the device's path. Lo
This patch will provide a more reliable and easy way for user-space
applications to have access to AER logs rather than reading them from the
message buffer. It also provides a way to notify user-space when an AER
event occurs.
The aer driver is updated to generate a trace event of function 'aer_e
This header file will define a new trace event that will be triggered when
a AER event occurs. The following data will be provided to the trace
event.
char * name - String containing the device path
u32 status -Either the correctable or uncorrectable register
indicating wha
On Fri, Nov 30, 2012 at 12:09:40PM -0800, Dmitry Torokhov wrote:
> On Friday, November 30, 2012 10:57:55 AM Greg KH wrote:
> > On Fri, Nov 30, 2012 at 10:45:44AM -0800, Dmitry Torokhov wrote:
> > > However you snipped the rest of my reply: do we really need to renumber
> > > ioctls? There is no ben
>The only strange thing I noticed is that some groups have 0 limit. Is
>this intentional?
>grep memory.limit_in_bytes cgroups | grep -v uid | sed 's@.*/@@' | sort | uniq
>-c
> 3 memory.limit_in_bytes:0
These are users who are not allowed to run anything.
azur
--
To unsubscribe from this l
H. Peter Anvin writes:
>
> On 11/29/2012 10:43 AM, Greg Kroah-Hartman wrote:
> > From: Greg Kroah-Hartman
> >
> > With the recent work to remove CONFIG_HOTPLUG, we are starting to get a
> > bunch of __devinit section warnings, despite CONFIG_HOTPLUG always being
> > enabled. So, stop marking the
On Fri, Nov 30, 2012 at 10:36:43AM +0900, Yoshihiro YUNOMAE wrote:
> Hi Marcelo,
>
> >>>Can you please write a succint but complete description of the method
> >>>so it can be verified?
> >>
> >>Sure.
> >>
> >>- Prerequisite
> >>1. the host TSC is synchronized and stable.
> >>2. kvm_write_tsc_offs
Hello, Dave.
On Wed, Nov 28, 2012 at 04:03:58PM -0800, Dave Hansen wrote:
> My system is just qemu booted with:
>
> -smp 8 -m 8192 -numa node,nodeid=0,cpus=0-3 -numa node,nodeid=1,cpus=4-7
>
> Watch the "PERCPU:" line early in boot, and you can see the "Embedded"
> come and go with or without yo
1 - 100 of 671 matches
Mail list logo
