On 12/03/2012 06:06 PM, Andrew Morton wrote:
On Mon, 19 Nov 2012 18:56:49 -0800
Josh Hunt wrote:
We found with newer kernels we started seeing the cdrom device showing
up in /proc/partitions, but it was not there before. Looking into this I found
that commit d27769ec... block: add GENHD_FL_NO_
On Mon, Dec 3, 2012 at 3:01 PM, Andrew Morton wrote:
> On Fri, 30 Nov 2012 22:56:27 -0800
> Michel Lespinasse wrote:
>
>> 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
On Mon, Dec 3, 2012 at 3:21 PM, Belisko Marek wrote:
> On Mon, Dec 3, 2012 at 8:29 PM, Bryan Wu wrote:
>> On Fri, Nov 30, 2012 at 2:00 PM, Marek Belisko
>> wrote:
>>> Signed-off-by: Marek Belisko
>>> ---
>>> Documentation/devicetree/bindings/leds/tca6507.txt | 33
>>>
>>
On Mon, 2012-12-03 at 13:25 +0200, Michael S. Tsirkin wrote:
> On Mon, Dec 03, 2012 at 02:09:28PM +0800, Jason Wang wrote:
> > On Sunday, December 02, 2012 06:09:06 PM Michael S. Tsirkin wrote:
> > > On Tue, Nov 27, 2012 at 06:16:00PM +0800, Jason Wang wrote:
> > > > This patch implement the {set|g
On Mon, 2012-12-03 at 12:25 +0800, Hanjun Guo wrote:
> On 2012/11/30 6:27, Toshi Kani wrote:
> > On Thu, 2012-11-29 at 12:48 +0800, Hanjun Guo wrote:
> >> On 2012/11/29 2:41, Toshi Kani wrote:
> >>> On Wed, 2012-11-28 at 19:05 +0800, Hanjun Guo wrote:
> On 2012/11/24 1:50, Vasilis Liaskovitis
> From: yhlu.ker...@gmail.com [mailto:yhlu.ker...@gmail.com] On Behalf Of
> Yinghai Lu
> 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
> > Au
On Sat, Dec 1, 2012 at 5:26 AM, Mark Brown
wrote:
> On Thu, Nov 29, 2012 at 10:14:58PM -0800, Olof Johansson wrote:
>> On Thu, Nov 29, 2012 at 6:13 PM, Simon Glass wrote:
>
>> > It was originally done separately but I think it was felt that this
>> > was overly complex. Olof can you please commen
On Mon, 19 Nov 2012 18:56:49 -0800
Josh Hunt wrote:
> We found with newer kernels we started seeing the cdrom device showing
> up in /proc/partitions, but it was not there before. Looking into this I found
> that commit d27769ec... block: add GENHD_FL_NO_PART_SCAN introduces this
> change
> in b
On Wed, Nov 28, 2012 at 08:18:01PM -0800, John Stultz wrote:
> On 11/21/2012 04:36 PM, John Stultz wrote:
> >2) Being able to use this with tmpfs files. I'm currently trying
> >to better understand the rmap code, looking to see if there's a
> >way to have try_to_unmap_file() work similarly to
> >tr
On 3 Dec 2012 16:19:11 -0500
"George Spelvin" wrote:
> (Not sure who owns this; Cc: to the last few people to touch
> drivers/tty/vt/keyboard.c.)
linux-input is probably the best place to discuss this
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a mes
On Thursday 01 November 2012, Lars-Peter Clausen wrote:
> Nothing is using the vmlist field in mm_context_t anymore. It has been removed
> from the non-generic versions over 3 years ago 8feae1311 ("NOMMU: Make VMAs
> per
> MM as for MMU-mode linux").
>
> Signed-off-by: Lars-Peter Clausen
Whole
Hi John,
Sorry for the long delay.
At last, I get a chance to look at this, again.
On Wed, Nov 21, 2012 at 04:36:42PM -0800, John Stultz wrote:
> On 10/29/2012 06:29 PM, Minchan Kim wrote:
> >This patch introudces new madvise behavior MADV_VOLATILE and
> >MADV_NOVOLATILE for anonymous pages. It's
> -Original Message-
> From: Josh Boyer [mailto:jwbo...@gmail.com]
> Sent: Monday, December 03, 2012 6:26 PM
> To: Deucher, Alexander
> Cc: Ben Hutchings; Greg KH; linux-kernel@vger.kernel.org;
> sta...@vger.kernel.org; a...@linux-foundation.org;
> a...@lxorguk.ukuu.org.uk
> Subject: Re: [
On Mon, Dec 3, 2012 at 3:07 PM, Linus Torvalds
wrote:
>
> I guess I need to try harder. I'm guessing that there's a 4kB
> filesystem there, and the block device size isn't 4kB-aligned or
> something.
Yup, I can reproduce it with that.
I'll shut the printk up some way. In the meantime, you can ig
Start with zero and grow up to KVM_MEM_SLOTS_NUM. A modest guest
without device assignment likely uses around 1/4 of the total
entries. We don't attempt to shrink the array when slots are
released. Both x86 and powerpc still have some statically sized
elements elsewhere, but this covers the bulk
struct kvm_memory_slot is currently 52 bytes (LP64), not counting the
arch data. On x86 this means the memslot array to support a tiny 32+3
entries (user+private) is over 2k. We'd like to support more slots
so that we can support more assigned devices, but it doesn't make
sense to penalize everyo
In order to make the memslots array grow on demand, move the private
slots to the lower indexes of the array. The private slots are
assumed likely to be in use, so if we didn't do this we'd end up
allocating the full memslots array all the time.
Signed-off-by: Alex Williamson
---
arch/ia64/kvm/
This allows us to resize this structure and therefore the number of
memslots as part of the RCU update.
Signed-off-by: Alex Williamson
---
include/linux/kvm_host.h |5 ++---
virt/kvm/kvm_main.c |4 ++--
2 files changed, 4 insertions(+), 5 deletions(-)
diff --git a/include/linux/kvm
Seems like everyone copied x86 and defined 4 private memory slots
that never actually get used. Even x86 only uses 3 of the 4. These
aren't exposed so there's no need to add padding.
Signed-off-by: Alex Williamson
---
arch/ia64/include/asm/kvm_host.h|2 --
arch/powerpc/include/asm/kvm_
It's easy to confuse KVM_MEMORY_SLOTS and KVM_MEM_SLOTS_NUM. One is
the user accessible slots and the other is user + private. Make this
more obvious.
Signed-off-by: Alex Williamson
---
arch/ia64/include/asm/kvm_host.h|2 +-
arch/ia64/kvm/kvm-ia64.c|2 +-
arch/powerpc/i
Memory slots are currently a fixed resource with a relatively small
limit. When using PCI device assignment in a qemu guest it's fairly
easy to exhaust the number of available slots. I posted patches
exploring growing the number of memory slots a while ago, but it was
prior to caching memory slot
On Mon, Dec 3, 2012 at 8:29 PM, Bryan Wu wrote:
> On Fri, Nov 30, 2012 at 2:00 PM, Marek Belisko
> wrote:
>> Signed-off-by: Marek Belisko
>> ---
>> Documentation/devicetree/bindings/leds/tca6507.txt | 33
>>
>> 1 file changed, 33 insertions(+)
>> create mode 100644 Docu
On Mon, Dec 3, 2012 at 10:35 AM, Deucher, Alexander
wrote:
>> -Original Message-
>> From: Josh Boyer [mailto:jwbo...@gmail.com]
>> Sent: Monday, December 03, 2012 10:25 AM
>> To: Ben Hutchings; Greg KH
>> Cc: linux-kernel@vger.kernel.org; sta...@vger.kernel.org; akpm@linux-
>> foundation.o
There are two cases we need to adjust page size in set_spte:
1): the one is other vcpu creates new sp in the window between mapping_level()
and acquiring mmu-lock.
2): the another case is the new sp is created by itself (page-fault path) when
guest uses the target gfn as its page table.
In
On Sun, 02 Dec 2012 19:55:09 +
Chris Clayton wrote:
>
>
> On 11/29/12 10:52, Chris Clayton wrote:
> > On 11/28/12 23:52, Andrew Morton wrote:
> >> On Wed, 21 Nov 2012 23:09:46 +0800
> >> Jiang Liu wrote:
> >>
> >>> Subject: Re: [RFT PATCH v2 4/5] mm: provide more accurate estimation
> >>>
On Mon, Dec 3, 2012 at 3:07 PM, Linus Torvalds
wrote:
>
> I guess I need to try harder. I'm guessing that there's a 4kB
> filesystem there, and the block device size isn't 4kB-aligned or
> something.
Anyway, to clarify: the printk's are harmless, since the IO past the
end of the device is just er
On 11/05/2012 02:55 PM, Heinz Wiesinger wrote:
On Monday 05 November 2012 11:13:31 Greg KH wrote:
On Mon, Nov 05, 2012 at 01:11:18AM -0800, Jonathan Nieder wrote:
Hi,
In March, Greg KH wrote:
3.2-stable review patch. If anyone has any objections, please let me
know.
Sorry, I'm a little late
The PCI IDs for IvyBridge IOAT DMA needs to go into a header file since
dma_v3.c looks them up for certain hardware workarounds. Need to add to the
alignment workaround for IOAT 3.2 since it wasn't fixed in IVB.
Signed-off-by: Dave Jiang
---
drivers/dma/ioat/dma_v3.c | 22
On Mon, Dec 3, 2012 at 2:44 PM, Tony Luck wrote:
>> Just for info, can you add a "WARN_ON_ONCE()" to handle_bad_sector()
>> just so that I see which particular path your kvm load triggers.
>
> On native ia64 (with SLES11 userspace) I see:
Interesting. I knew about the possibility of this, and had
On Fri, 30 Nov 2012 22:56:27 -0800
Michel Lespinasse wrote:
> 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 m
Thank you Kyungmin Park for the review.
On 3 December 2012 22:28, Kyungmin Park wrote:
>
> Hi,
>
> On Mon, Dec 3, 2012 at 9:16 PM, Giridhar Maruthy
> wrote:
> > This patch adds slave support to i2c. The dt entry i2c-mode
> > decides at probe time if the controller needs to work in
> > slave mode
On 12/02/2012 01:43 PM, Ingo Molnar wrote:
This is not entirely correct as this task might have scheduled or
migrate ther - but statistically there will be correlation to the
there?
tasks that we share memory with, and correlation is all we need.
We map out the relation itself
On Mon, 3 Dec 2012 12:36:26 -0800 Linus Torvalds
wrote:
>
> The only things I want to see are fixes that people care deeply about.
> If it's not critical, or you don't have an actual problem report from
> an actual user, just put it in the queue under the christmas tree, and
> let it got for 3.8
> Just for info, can you add a "WARN_ON_ONCE()" to handle_bad_sector()
> just so that I see which particular path your kvm load triggers.
On native ia64 (with SLES11 userspace) I see:
WARNING: at block/blk-core.c:1557 generic_make_request_checks+0x680/0xa40()
Hardware name: I8QBH
Modules linked i
On Mon, Dec 3, 2012 at 2:20 PM, Romain Francoise wrote:
>
> Could these changes be the reason for the following suddenly appearing in
> one of my VMs with rc8 (no such messages with rc7)? Pretty standard virtio
> setup in KVM.
>
> [ 11.832295] attempt to access beyond end of device
> [ 11.8322
On Mon, Dec 3, 2012 at 2:29 PM, Tony Luck wrote:
>
>
>
> On Mon, Dec 3, 2012 at 2:20 PM, Romain Francoise
> wrote:
>>
>> Hi Linus,
>>
>> Linus Torvalds writes:
>>
>> > Linus Torvalds (5):
>> > fs/buffer.c: make block-size be per-page and protected by the
>> > page lock
>> > blockdev:
On Sat, Dec 1, 2012 at 6:40 PM, Cyril Roelandt wrote:
> This call is followed by a call to memcpy() on the same memory area, so it can
> be safely removed.
>
> Signed-off-by: Cyril Roelandt
> ---
> drivers/scsi/megaraid/megaraid_sas_fusion.c |2 --
> 1 file changed, 2 deletions(-)
>
> diff -
Hi Linus,
Linus Torvalds writes:
> Linus Torvalds (5):
> fs/buffer.c: make block-size be per-page and protected by the page lock
> blockdev: remove bd_block_size_semaphore again
> direct-io: don't read inode->i_blkbits multiple times
> blkdev_max_block: make private to fs
On 12/01/2012 06:40 PM, Cyril Roelandt wrote:
These calls are followed by calls to memcpy() on the same memory area, so they
can be safely removed.
Signed-off-by: Cyril Roelandt
---
drivers/scsi/bnx2fc/bnx2fc_hwi.c |4
1 file changed, 4 deletions(-)
diff --git a/drivers/scsi/bnx2fc
Adding Andi
On 11/23/2012 02:19 AM, Christoph Hellwig wrote:
> On Wed, Nov 21, 2012 at 04:40:49PM -0600, Dave Kleikamp wrote:
>> From: Zach Brown
>>
>> __blockdev_direct_IO() had two instances of the same code to determine
>> if a given offset wasn't aligned first to the inode's blkbits and then
diff --git a/Documentation/dvb/get_dvb_firmware
b/Documentation/dvb/get_dvb_firmware
index 3348d31..511dd4d 100644
--- a/Documentation/dvb/get_dvb_firmware
+++ b/Documentation/dvb/get_dvb_firmware
@@ -114,7 +114,7 @@ sub tda10045 {
sub tda10046 {
my $sourcefile = "TT_PCI_2.19h_28_11_20
I'm announcing the release of the 3.0.54 kernel.
All users of the 3.0 kernel series must upgrade.
The updated 3.0.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.0.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Documentation/dvb/get_dvb_firmware
b/Documentation/dvb/get_dvb_firmware
index d1d4a17..b361e08 100755
--- a/Documentation/dvb/get_dvb_firmware
+++ b/Documentation/dvb/get_dvb_firmware
@@ -115,7 +115,7 @@ sub tda10045 {
sub tda10046 {
my $sourcefile = "TT_PCI_2.19h_28_11_200
I'm announcing the release of the 3.4.21 kernel.
All users of the 3.4 kernel series must upgrade.
The updated 3.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.4.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Documentation/dvb/get_dvb_firmware
b/Documentation/dvb/get_dvb_firmware
index 12d3952e..32bc56b 100755
--- a/Documentation/dvb/get_dvb_firmware
+++ b/Documentation/dvb/get_dvb_firmware
@@ -116,7 +116,7 @@ sub tda10045 {
sub tda10046 {
my $sourcefile = "TT_PCI_2.19h_28_11_20
I'm announcing the release of the 3.6.9 kernel.
All users of the 3.6 kernel series must upgrade.
The updated 3.6.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.6.y
and can be browsed at the normal kernel.org git web browser:
Hello, Aristeu.
On Mon, Dec 03, 2012 at 02:14:12PM -0500, Aristeu Rozanski wrote:
> > Maybe I'm misunderstanding something but the behavior seems a bit
> > inconsistent. So, you can't add an exception which isn't allowed by
> > your parent, right? But, if your parent disallows an existing
> > ex
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
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 slot loca
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 * dev_name - The name of the slot where the device resides
([domain:]bus:device.function).
u32 status - Either the correct
(Not sure who owns this; Cc: to the last few people to touch
drivers/tty/vt/keyboard.c.)
I happen to have both a PS/2 and USB keyboard plugged, in, but was
noticing that the caps lock key seemed inverted. When the LED was off,
I got all caps (unless I used shift), while when it was on I got norma
On Mon, Dec 03, 2012 at 09:13:49PM +, Ortiz, Lance E wrote:
> This a fine idea. I'm thinking we might want to implement that in a
> later patch since it is a bigger change and we still need to see about
> adding additional strings.
Yes, definitely in a later patch or more depending on how much
>
> Maybe we should ask Yanmin who added those strings in
> 6c2b374d74857e892080ee726184ec1d15e7d4e4; CCed.
>
> Also, it would make a lot of sense to have those string definitions
> at one place and then reuse them instead of define them again in the
> tracepoint header and they get out of sync a
A release candidate preview, Git v1.8.1-rc0, is now available for
testing at the usual places.
This cycle has been a bit slow (perhaps because it had a major US
holiday to slow people down) but we seem to have managed to apply
reasonably large number of usability improvement changes, with a
handfu
From: Zach Brown
use_mm() is used in more places than just aio. There's no need to
mention callers when describing the function.
Signed-off-by: Zach Brown
Signed-off-by: Kent Overstreet
---
mm/mmu_context.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/mm/mmu_context.c b/mm/mmu_conte
From: Zach Brown
This removes the retry-based AIO infrastructure now that nothing in tree
is using it.
We want to remove retry-based AIO because it is fundemantally unsafe.
It retries IO submission from a kernel thread that has only assumed the
mm of the submitting task. All other task_struct r
From: Zach Brown
These are handy for measuring the cost of the aio infrastructure with
operations that do very little and complete immediately.
Signed-off-by: Zach Brown
Signed-off-by: Kent Overstreet
---
drivers/char/mem.c | 35 +++
1 file changed, 35 insertio
Nothing used the return value, and it probably wasn't possible to use it
safely for the locked versions (aio_complete(), aio_put_req()). Just
kill it.
Acked-by: Zach Brown
Signed-off-by: Kent Overstreet
---
fs/aio.c| 19 +++
include/linux/aio.h | 8
2 files
Minor refactoring, to get rid of some duplicated code
v2: Fix return value for NULL kiocb, so it matches old code; change
synchronization to use xchg() instead of a bit in ki_flags, so we can
get rid of ki_flags.
Signed-off-by: Kent Overstreet
---
fs/aio.c | 72 +
Signed-off-by: Kent Overstreet
---
fs/aio.c | 57 -
1 file changed, 24 insertions(+), 33 deletions(-)
diff --git a/fs/aio.c b/fs/aio.c
index 35a2153e..4cceba1 100644
--- a/fs/aio.c
+++ b/fs/aio.c
@@ -8,6 +8,8 @@
*
* See ../COPYING f
aio_get_req() will fail if we have the maximum number of requests
outstanding, which depending on the application may not be uncommon. So
avoid doing an unnecessary fget().
Signed-off-by: Kent Overstreet
---
fs/aio.c | 22 +-
1 file changed, 9 insertions(+), 13 deletions(-)
On Mon, 2012-12-03 at 09:47 -0800, Joe Perches wrote:
> On Sat, 2012-10-20 at 09:22 -0700, Joe Perches wrote:
> > Use the normal kernel test instead of a module specific one.
>
> ping?
Your timely is perfect, I just cleared out all the ixgbe patches in my
queue that were before yours, and your pa
From: Zach Brown
Signed-off-by: Zach Brown
Signed-off-by: Kent Overstreet
---
include/linux/aio.h | 24
1 file changed, 24 deletions(-)
diff --git a/include/linux/aio.h b/include/linux/aio.h
index 31ff6db..b46a09f 100644
--- a/include/linux/aio.h
+++ b/include/linux/a
The usage of ctx->dead was fubar - it makes no sense to explicitly
check it all over the place, especially when we're already using RCU.
Now, ctx->dead only indicates whether we've dropped the initial
refcount. The new teardown sequence is:
set ctx->dead
hlist_del_rcu();
synchronize_rcu();
Now we
Converting read_events() to prepare_to_wait_exclusive() and
hrtimers simplifies it quite a bit.
v2: Move finish_wait() call so we're not calling copy_to_user in
TASK_INTERRUPTIBLE state
Signed-off-by: Kent Overstreet
---
fs/aio.c | 77 ++--
On Mon, Dec 03, 2012 at 12:20:30PM -0700, Stephen Warren wrote:
> On 11/30/2012 03:38 AM, Thierry Reding wrote:
> > On Fri, Nov 30, 2012 at 10:56:39AM +0200, Terje Bergström wrote:
> >> On 29.11.2012 13:47, Thierry Reding wrote:
> >>> On Thu, Nov 29, 2012 at 12:21:04PM +0200, Terje Bergström
> >>>
Previously, aio_read_event() pulled a single completion off the
ringbuffer at a time, locking and unlocking each time.
Changed it to pull off as many events as it can at a time, and copy them
directly to userspace.
This also fixes a bug where if copying the event to userspace failed,
we'd lose th
Signed-off-by: Kent Overstreet
---
fs/aio.c | 45 +
1 file changed, 17 insertions(+), 28 deletions(-)
diff --git a/fs/aio.c b/fs/aio.c
index 5eca2a4..e3ca2c0 100644
--- a/fs/aio.c
+++ b/fs/aio.c
@@ -208,33 +208,15 @@ static int aio_setup_ring(struct ki
The aio code tries really hard to avoid having to deal with the
completion ringbuffer overflowing. To do that, it has to keep track of
the number of outstanding kiocbs, and the number of completions
currently in the ringbuffer - and it's got to check that every time we
allocate a kiocb. Ouch.
But
Previously, allocating a kiocb required touching quite a few global
(well, per kioctx) cachelines... so batching up allocation to amortize
those was worthwhile. But we've gotten rid of some of those, and in
another couple of patches kiocb allocation won't require writing to any
shared cachelines, s
See the previous patch for why we want to do this - this basically
implements a per cpu allocator for reqs_available that doesn't actually
allocate anything.
Note that we need to increase the size of the ringbuffer we allocate,
since a single thread won't necessarily be able to use all the
reqs_av
Freeing a kiocb needed to touch the kioctx for three things:
* Pull it off the reqs_active list
* Decrementing reqs_active
* Issuing a wakeup, if the kioctx was in the process of being freed.
This patch moves these to aio_complete(), for a couple reasons:
* aio_complete() already has to issu
This implements a refcount with similar semantics to
atomic_get()/atomic_dec_and_test(), that starts out as just an atomic_t
but dynamically switches to per cpu refcounting when the rate of
gets/puts becomes too high.
It also implements two stage shutdown, as we need it to tear down the
percpu cou
This just converts the ioctx refcount to the new generic dynamic percpu
refcount code.
Signed-off-by: Kent Overstreet
---
fs/aio.c | 27 ---
1 file changed, 12 insertions(+), 15 deletions(-)
diff --git a/fs/aio.c b/fs/aio.c
index bde360d..931606b 100644
--- a/fs/aio.c
++
So, for sticking kiocb completions on the kioctx ringbuffer, we need a
lock - it unfortunately can't be lockless.
When the kioctx is shared between threads on different cpus and the rate
of completions is high, this lock sees quite a bit of contention - in
terms of cacheline contention it's the ho
struct aio_ring_info was kind of odd, the only place it's used is where
it's embedded in struct kioctx - there's no real need for it.
The next patch rearranges struct kioctx and puts various things on their
own cachelines - getting rid of struct aio_ring_info now makes that
reordering a bit cleare
The number of outstanding kiocbs is one of the few shared things left
that has to be touched for every kiocb - it'd be nice to make it percpu.
We can make it per cpu by treating it like an allocation problem: we
have a maximum number of kiocbs that can be outstanding (i.e. slots) -
then we just al
Signed-off-by: Kent Overstreet
---
fs/aio.c | 26 --
1 file changed, 16 insertions(+), 10 deletions(-)
diff --git a/fs/aio.c b/fs/aio.c
index cebd8f2..70a34f6 100644
--- a/fs/aio.c
+++ b/fs/aio.c
@@ -67,13 +67,6 @@ struct kioctx {
unsigned long user_id;
On Mon, Dec 3, 2012 at 1:00 PM, Alex Williamson
wrote:
> On Mon, 2012-12-03 at 12:48 -0700, Alex Williamson wrote:
>> On Mon, 2012-12-03 at 10:40 -0700, Shuah Khan wrote:
>> > On Mon, Dec 3, 2012 at 9:37 AM, Betty Dall wrote:
>> > > The function aer_recover_queue() makes a call to
>> > > pci_get
Yay faster kernel compiles
Signed-off-by: Kent Overstreet
---
arch/s390/hypfs/inode.c | 1 +
block/scsi_ioctl.c | 1 +
drivers/char/mem.c | 1 +
drivers/infiniband/hw/ipath/ipath_file_ops.c | 1 +
drivers/infiniband/hw/qib/
Cancelling kiocbs requires adding them to a per kioctx linked list,
which is one of the few things we need to take the kioctx lock for in
the fast path. But most kiocbs can't be cancelled - so if we just do
this lazily, we can avoid quite a bit of locking overhead.
Signed-off-by: Kent Overstreet
Signed-off-by: Kent Overstreet
---
drivers/usb/gadget/inode.c | 1 +
fs/aio.c | 61 ++
include/linux/aio.h| 61 --
3 files changed, 62 insertions(+), 61 deletions(-)
diff --git a/dr
From: Zach Brown
This removes the only in-tree user of aio retry. This will let us
remove the retry code from the aio core.
Removing retry is relatively easy as the USB gadget wasn't using it to
retry IOs at all. It always fully submitted the IO in the context of
the initial io_submit() call.
Last posting: http://thread.gmane.org/gmane.linux.kernel.aio.general/3169
Changes since the last posting should all be noted in the individual
patch descriptions.
* Zach pointed out the aio_read_evt() patch was calling functions that
could sleep in TASK_INTERRUPTIBLE state, that patch is rewr
On Mon, Dec 03, 2012 at 10:46:59AM +0100, David Henningsson wrote:
> On 11/30/2012 07:45 PM, Greg Kroah-Hartman wrote:
> >3.0-stable review patch. If anyone has any objections, please let me know.
> >
> >--
> >
> >From: David Henningsson
> >
> >commit 34c3d1926bdaf45d3a891dd577482
On Mon, 3 Dec 2012 12:36:26 -0800 Linus Torvalds
wrote:
>
> (Ok, while writing this I got another pull request that made me go "We
> don't really need this". I'll pull that, because technically it came
> in before I'd given people this warning, but ...)
You really are an old softie, aren't you ;
From: David Daney
Problem:
1) Huge page mapping of anonymous memory is initially invalid. Will be
faulted in by copy-on-write mechanism.
2) Userspace attempts store at the end of the huge mapping.
3) TLB Refill exception handler fill TLB with a normal (4K sized)
invalid page at the end
I really didn't want it to come to this, but I was uncomfortable doing
the 3.7 release yesterday due to last-minute issues, and decided to
sleep on it.
And today, I ended up even *less* comfortable about it due to the
resurrection of a kswapd issue, so I decided that I'm going to do
another -rc af
Two small fixes for Sparc, nobody uses sparc, so these are
low risk :-)
1) Piggyback is too picky about the symbol types that _start
and _end have in the final kernel image, and it thus breaks
with newer binutils. Future proof by getting rid of the
symbol type checks.
2) exit_group() s
Without this patch, a SPI device may keep its drvdata whereas it was unbound
from its driver. This may result in accessing an invalid pointer.
As for i2c-core, let the SPI core handle the removal of the device's drvdata,
after a remove(), or a probe() failure.
This is a resent of the previous pat
On Mon, Dec 03, 2012 at 08:01:46PM +, Ortiz, Lance E wrote:
> > > +#define correctable_error_string \
> > > + {BIT(0),"Receiver Error"}, \
> > > + {BIT(6),"Bad TLP"}, \
> > > + {BIT(7),"Bad DLLP"},\
> >
> -Original Message-
> From: Arnd Bergmann [mailto:a...@arndb.de]
> Sent: Saturday, December 01, 2012 12:49 PM
> To: Philip Balister
> Cc: Greg KH; Eli Billauer; linux-kernel@vger.kernel.org; Pavel Machek; John
> Linn; Michal Simek; Ira W.
> Snyder; Josh Cartwright
> Subject: Re: [PATCH 2/
On Mon, 2012-12-03 at 20:20 +, Ortiz, Lance E wrote:
> > > +#define correctable_error_string \
> > > + {BIT(0),"Receiver Error"}, \
> > > + {BIT(6),"Bad TLP"}, \
> > > + {BIT(7),"Bad DLLP"},\
> > > + {B
On Mon, 2012-12-03 at 12:48 -0700, Alex Williamson wrote:
> On Mon, 2012-12-03 at 10:40 -0700, Shuah Khan wrote:
> > On Mon, Dec 3, 2012 at 9:37 AM, Betty Dall wrote:
> > > The function aer_recover_queue() makes a call to
> > > pci_get_domain_bus_and_slot().
> > > That function is documented to r
> > +#define correctable_error_string \
> > + {BIT(0),"Receiver Error"}, \
> > + {BIT(6),"Bad TLP"}, \
> > + {BIT(7),"Bad DLLP"},\
> > + {BIT(8),"RELAY_NUM Rollover"}, \
> > + {
Le 02/12/2012 16:32, Axel Lin a écrit :
> This fixes below build error:
>
> CC arch/arm/mach-sunxi/sunxi.o
> arch/arm/mach-sunxi/sunxi.c: In function 'sunxi_restart':
> arch/arm/mach-sunxi/sunxi.c:55:3: error: implicit declaration of function
> 'mdelay' [-Werror=implicit-function-declarati
Le 02/12/2012 16:08, Axel Lin a écrit :
> The of_device_id table is supposed to be zero-terminated.
Applied, thanks
--
Maxime Ripard, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
--
To unsubscribe from this
Le 02/12/2012 15:40, Axel Lin a écrit :
> The of_device_id table is supposed to be zero-terminated.
Applied, thanks.
--
Maxime Ripard, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
--
To unsubscribe from this
On Mon, Dec 03, 2012 at 01:22:41PM +, David Woodhouse wrote:
> On Wed, 2012-11-28 at 23:33 +0100, Krzysztof Mazur wrote:
> >
> > Many ATM drivers store vcc in ATM_SKB(skb)->vcc and use it for
> > freeing skbs. Now they can just use atm_pop_skb() to free such
> > buffers.
> >
> > Signed-off-by
From: "Michael S. Tsirkin"
Date: Mon, 3 Dec 2012 22:07:14 +0200
> Historically tun supported two modes of operation:
> - in default mode, a small number of packets would get queued
> at the device, the rest would be queued in qdisc
> - in one queue mode, all packets would get queued at the devi
101 - 200 of 577 matches
Mail list logo
