2013-11-29 21:56, Borislav Petkov:
> On Fri, Nov 29, 2013 at 09:28:48PM +0100, Levente Kurusa wrote:
>> This patch adds a call to put_device() when the device_register()
>> call has failed. This is required so that the last reference to the
>> device is given up.
>
> I'd assume this is not
Thanks for you replies.
Yeah, I understand that we need to utilize the resources as much as we
can. At the same time user should not
feel that system is slow and user should never wait for the copying
operation should complete to launch another
application meanwhile.
If the user is a system
This patch integrates redundant bio operations on read and write IOs.
1. Move bio-related codes to the top of data.c.
2. Replace f2fs_submit_bio with f2fs_submit_merged_bio, which handles read
bios additionally.
3. Introduce __submit_merged_bio to submit the merged bio.
4. Change f2fs_readpage
On Fri, Nov 29, 2013 at 03:09:05PM -0500, Theodore Ts'o wrote:
> Applied, although I slightly edited the commit description the the
> debug message mentioned in the description was removed since the first
> version of your patch series, and it wasn't updated as part of the
> rebase.
Ah, good
On 11/29/2013 12:05 PM, Oleg Nesterov wrote:
> On 11/29, Andi Kleen wrote:
>>
>>> Andi, et al. I am going to discuss the things I do not really
>>> understand, probably this can't make any sense, but...
>>
>> I think it's enough to set the dirty bit in the underlying
>> struct page, no need to
Hi,
[snip]
> > > So how about add all pages of page list to node_inode's address space by
> > > add_to_page_cache_lru() with arg sum_entry->nid?
> >
> > I don't think it's proper way to use add_to_page_cache_lru() directly.
>
> This is the way used in VM readahead(i.e.
Hi
On Sat, Nov 30, 2013 at 5:48 AM, Michael Trimarchi
wrote:
> Hi Roger
>
> On Fri, Nov 29, 2013 at 2:01 PM, Roger Quadros wrote:
>> With u-boot 2013.10, USB devices are sometimes not detected
>> on OMAP4 Panda. To make us independent of what bootloader does
>> with the USB Host module, we must
Locking is performed by regmap API so no additional locking is needed.
Nevertheless, keep locking in the ADC conversion routine. This need
for keep proper read ADC sequence when calling from adc & touchscreen
drivers.
Signed-off-by: Alexander Shiyan
---
drivers/input/misc/mc13783-pwrbutton.c
If this driver being loaded from devicetree, the pdata is NULL.
This cause kernel Oops when "fsl,mc13xxx-uses-codec" and/or
"fsl,mc13xxx-uses-touch" properties is specified.
mc13xxx spi0.0: mc13783: rev: 3.3, fin: 0, fab: 0, icid: 2/0
Unable to handle kernel NULL pointer dereference at virtual
Hi Roger
On Fri, Nov 29, 2013 at 2:01 PM, Roger Quadros wrote:
> With u-boot 2013.10, USB devices are sometimes not detected
> on OMAP4 Panda. To make us independent of what bootloader does
> with the USB Host module, we must RESET it to get it to a known
> good state. This patch Soft RESETs the
Change the device name of the regulator function to the one chosen for
MODULE_ALIAS. This fixes kernel auto-module loading for the regulator function.
Signed-off-by: Axel Lin
---
Hi,
I don't have the hardware to test, but I think this needs fix.
We have a similar fix in
commit ec8da805c43a "mfd:
Good day,
I have a project(humanitarian) I will propose you help me execute.contact me
via email to discuss in details.
Cheers,
Patrick Seddigh.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info
usb: chipidea: hw_phymode_configure moved before ci_usb_phy_init
hw_phymode_configure configures the PORTSC registers and allow the
following phy_inits to operate on the right parameters. This fix a problem
where the UPLI (ISP1504) could not detected, because the Viewport was not
available and
usb: chipidea: Reallocate regmap only if lpm is detected
The regmap only needs to reallocate if the hw_read on the CAP register shows
lpm is used. Therefore the if() statement check the change.
Signed-off-by: Chris Ruehl
Acked-by: Peter Chen
---
drivers/usb/chipidea/core.c |3 ++-
1 file
usb: chipidea: Fix Internal error: : 808 [#1] ARM related to STS flag
* init the sts flag to 0 (missed)
* Set PORTCS_STS only if VUSB_HS_PHY_TYPE > 1
otherwise the register is ReadOnly
* Set/Reset correct BIT(28)/BIT(29) for STS
Signed-off-by: Chris Ruehl
---
drivers/usb/chipidea/core.c |
Good day,
I have an interesting transaction proposal for you that will be of immense
benefit for both of us. Although this may be hard for you to believe, we stand
to gain 7.2 Millon USD in a matter of days. Please grant me the benefit of
doubt and hear me out.I need you to signify your interest
On Thu, Nov 28, 2013 at 10:12:55AM +0100, Michal Hocko wrote:
> On Wed 27-11-13 18:33:53, Johannes Weiner wrote:
> [...]
> > diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> > index 13b9d0f..5f9e467 100644
> > --- a/mm/memcontrol.c
> > +++ b/mm/memcontrol.c
> > @@ -2675,7 +2675,7 @@ static int
On Fri, Nov 29, 2013 at 04:00:09PM -0800, David Rientjes wrote:
> On Wed, 27 Nov 2013, Johannes Weiner wrote:
>
> > > None that I am currently aware of, I'll continue to try them out. I'd
> > > suggest just dropping the sta...@kernel.org from the whole series though
> > > unless there is
On Saturday, November 30, 2013 02:28 AM, Michael Grzeschik wrote:
On Fri, Nov 29, 2013 at 03:19:45PM +0800, Chris Ruehl wrote:
usb: chipidea: Fix Internal error: : 808 [#1] ARM related to STS flag
* init the sts flag to 0 (missed)
* set the sts flag only if not 0
Signed-off-by: Chris Ruehl
On Fri, Nov 29, 2013 at 05:21:12PM -0500, Tejun Heo wrote:
> On Thu, Nov 28, 2013 at 02:54:13PM -0500, Tejun Heo wrote:
> > Hello, Greg.
> >
> > For some reason, quilt can rebase the patches automatically here. I'm
> > reposting the rest of the series (patches 07-41) here just in case.
> > git
This fixes another regression in the IMA code.
Please pull.
The following changes since commit dc1ccc48159d63eca5089e507c82c7d22ef60839:
Linux 3.13-rc2 (2013-11-29 12:57:14 -0800)
are available in the git repository at:
On 11/28/13 18:45, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20131128:
>
on x86_64:
CONFIG_ACPI is not enabled.
CC drivers/gpu/drm/i915/intel_opregion.o
In file included from drivers/gpu/drm/i915/intel_opregion.c:31:0:
include/linux/acpi_io.h:7:45: error: unknown type name
Previously f2fs allocates its own bi_private data structure all the time even
though we don't use it. But, can we remove this bi_private allocation?
This patch removes such the additional bi_private allocation.
1. Retrieve f2fs_sb_info from its page->mapping->host->i_sb.
- This removes the
On 2013/11/29 22:18, Serge Hallyn wrote:
> Quoting Libo Chen (clbchenlibo.c...@huawei.com):
>> On 2013/11/29 13:05, Serge Hallyn wrote:
>>> Quoting Libo Chen (clbchenlibo.c...@huawei.com):
Hello LXC experts,
I meet a problem. When using vlan as network device in suse11 system
On 11/28/13 18:45, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20131128:
>
on x86_64:
when CONFIG_ACPI is not enabled:
CC drivers/sfi/sfi_acpi.o
drivers/sfi/sfi_acpi.c: In function 'sfi_acpi_parse_xsdt':
drivers/sfi/sfi_acpi.c:105:12: error: dereferencing pointer to incomplete
On Saturday, November 30, 2013 02:28 AM, Michael Grzeschik wrote:
On Fri, Nov 29, 2013 at 03:19:45PM +0800, Chris Ruehl wrote:
usb: chipidea: Fix Internal error: : 808 [#1] ARM related to STS flag
* init the sts flag to 0 (missed)
* set the sts flag only if not 0
Signed-off-by: Chris Ruehl
On Saturday, November 30, 2013 02:28 AM, Michael Grzeschik wrote:
On Fri, Nov 29, 2013 at 03:19:45PM +0800, Chris Ruehl wrote:
usb: chipidea: Fix Internal error: : 808 [#1] ARM related to STS flag
* init the sts flag to 0 (missed)
* set the sts flag only if not 0
Signed-off-by: Chris Ruehl
On Wed, Nov 13, 2013 at 03:08:28AM -0500, Greg Price wrote:
> The only mutable data accessed here is ->entropy_count, but since
> 902c098a3 ("random: use lockless techniques in the interrupt path")
> that member isn't protected by the lock anyway. Since 10b3a32d2
> ("random: fix accounting race
On Wed, Nov 13, 2013 at 03:08:21AM -0500, Greg Price wrote:
> This logic is exactly equivalent to the old logic, but it should
> be easier to see what it's doing.
>
> The equivalence depends on one fact from outside this function:
> when 'r->limit' is false, 'reserved' is zero. (Well, two facts;
On Fri, Nov 29, 2013 at 04:00:09PM -0800, David Rientjes wrote:
> On Wed, 27 Nov 2013, Johannes Weiner wrote:
>
> > > None that I am currently aware of, I'll continue to try them out. I'd
> > > suggest just dropping the sta...@kernel.org from the whole series though
> > > unless there is
On Fri, Nov 29, 2013 at 3:24 PM, Jiri Kosina wrote:
>
> Do you think this'd be faster than the int3-based aproach?
Unlikely to be faster, but perhaps more robust and more portable. Maybe.
And the reason we use the int3-based approach is that doing TLB
shootdowns of kernel mappings is completely
On 11/27/2013 04:34 AM, srinivas_g_go...@dell.com wrote:
>
> *Dell - Internal Use - Confidential *
>
> I hit a bug during one of our stress tests, Here is the issue that I
> am looking at.
>
> We have IPMI_READ_EVENT_MSG_BUFFER_CMD getting invoked from
> smi_event_handler.
>
> In case we hit error
On Saturday, November 30, 2013 12:45:55 AM Rafael J. Wysocki wrote:
> On Saturday, November 30, 2013 12:38:26 AM Rafael J. Wysocki wrote:
> > On Tuesday, November 26, 2013 06:26:54 PM Yinghai Lu wrote:
> > > On Tue, Nov 26, 2013 at 5:24 PM, Rafael J. Wysocki
> > > wrote:
> > > >
> > > > So
On Thu, 28 Nov 2013, Michal Hocko wrote:
> > None that I am currently aware of,
>
> Are you saing that scenarios described in 3812c8c8f395 (mm: memcg: do not
> trap chargers with full callstack on OOM) are not real or that _you_
> haven't seen an issue like that?
>
> The later doesn't seem to
On Wed, 27 Nov 2013, Johannes Weiner wrote:
> > None that I am currently aware of, I'll continue to try them out. I'd
> > suggest just dropping the sta...@kernel.org from the whole series though
> > unless there is another report of such a problem that people are running
> > into.
>
> The
On Wednesday 27 November 2013 20:44:51 Pali Rohár wrote:
> On Wednesday 27 November 2013 20:13:20 Pavel Machek wrote:
> > Hi!
> >
> > > Hi, I already have this patch prepared for 3.13.
> >
> > Cool :-). Do you plan to publish / is there 3.13 based tree
> > I could pull somewhere?
> >
> >
On Thu, 28 Nov 2013, Michal Hocko wrote:
> > Ok, so let's forget about GFP_KERNEL | __GFP_NOFAIL since anything doing
> > __GFP_FS should not be holding such locks, we have some of those in the
> > drivers code and that makes sense that they are doing GFP_KERNEL.
> >
> > Focusing on the
Hi Joe,
On Friday 29 November 2013 14:10:40 Joe Perches wrote:
> On Fri, 2013-11-29 at 14:56 +0200, Andy Shevchenko wrote:
> > On Thu, 2013-11-28 at 10:32 -0800, Joe Perches wrote:
> > > On Thu, 2013-11-28 at 13:28 +0200, user.email wrote:
> > > > From: Andy Shevchenko
> > > >
> > > > Add the
On 11/29/2013 04:56 PM, Andreas Mohr wrote:
> Hi,
>
>> My laptop has 4GB of ram, before I issue the command around 1.5GB of
>> memory
>> is used, when I issue the cp command around 3.7GB of memory is used.
>> And the cp command takes a lot of time to copy.
>>
>> I am not able to launch other
On Saturday, November 30, 2013 12:38:26 AM Rafael J. Wysocki wrote:
> On Tuesday, November 26, 2013 06:26:54 PM Yinghai Lu wrote:
> > On Tue, Nov 26, 2013 at 5:24 PM, Rafael J. Wysocki
> > wrote:
> > >
> > > So assume pci_destroy_dev() is called twice in parallel for the same dev
> > > by two
Vince,
Ok, I have added PP1 now and it works fine on my HSW desktop.
What I want to know now is what is this map to on servers?
And on clients, it is always mapped to the GFX. If so, then
we can use a more specific name: power/energy-gfx/
I will send a patch soon.
Thanks.
On Fri, Nov 29, 2013
On Tuesday, November 26, 2013 06:26:54 PM Yinghai Lu wrote:
> On Tue, Nov 26, 2013 at 5:24 PM, Rafael J. Wysocki wrote:
> >
> > So assume pci_destroy_dev() is called twice in parallel for the same dev
> > by two different threads. Thread 1 does the atomic_inc_and_test() and
> > finds that it is
On Fri, 29 Nov 2013, Oleg Nesterov wrote:
> > > Andi, et al. I am going to discuss the things I do not really
> > > understand, probably this can't make any sense, but...
> >
> > I think it's enough to set the dirty bit in the underlying
> > struct page, no need to play games with the PTE.
>
>
On Fri, Nov 29, 2013 at 9:37 AM, Peter Zijlstra wrote:
> Use the 'latch' data structure for cyc2ns.
>
> This is a data structure first proposed by me and later named by
> Mathieu. If anybody's got a better name; do holler.
That structure must exist in the literature, but I have no idea what
it's
If noone is feeling responsible, please, forward this to someone
capable!
Please ask me later for additional information, as I won't post
my full system info to lkml at first.
The module in question may be: serio_raw
Best regards, Manuel Krause
On 2013-11-26 23:19, Manuel Krause wrote:
The tty core provides an interface for flushing the driver's
write buffer: tty_driver_flush_buffer(); prefer the provided
interface over open-coded. Open-coding can lead to errors
such as the duplicated call in the st_kim driver.
Signed-off-by: Peter Hurley
---
drivers/misc/ti-st/st_core.c | 2
On Fri, 2013-11-29 at 23:50 +0100, Lars-Peter Clausen wrote:
> On 11/29/2013 11:10 PM, Joe Perches wrote:
[]
> > $ cat dma_addr_t.cocci
> > @@
> > dma_addr_t foo;
> > @@
> >
> > * (unsigned long long)foo;
>
> Remove the semicolon, otherwise it will only match statements which are
> nothing
>
On 11/29/2013 11:10 PM, Joe Perches wrote:
On Fri, 2013-11-29 at 14:56 +0200, Andy Shevchenko wrote:
On Thu, 2013-11-28 at 10:32 -0800, Joe Perches wrote:
On Thu, 2013-11-28 at 13:28 +0200, user.email wrote:
From: Andy Shevchenko
Add the %paD format specifier for printing a dma_addr_t type,
We're back on the normal weekly schedule, although I'm planning on
eventually slipping back to a Sunday release schedule. In the
meantime, it's like Xmas every Friday! Or, perhaps more appropriately
for the date, Hanukkah.
Anyway, everything looks normal for an -rc2. Nothing hugely alarming,
lots
On Mon, Nov 25, 2013 at 07:00:14PM +, Michele Baldessari wrote:
> We've received multiple reports in Fedora via (BZ 907193)
> that the Seagate Momentus SpinPoint M8 errors out when enabling AA:
> [2.555905] ata2.00: failed to enable AA (error_mask=0x1)
> [2.568482] ata2.00: failed to
On Tue, Nov 26, 2013 at 12:43:37PM +0800, Ming Lei wrote:
> sg_copy_buffer() can't meet demand for some drrivers(such usb
> mass storage), so we have to use the sg_miter_* APIs to access
> sg buffer, then need export sg_miter_skip() for these drivers.
>
> The API is needed for converting to
On Tue, Nov 26, 2013 at 05:21:52PM +0800, Yuanhan Liu wrote:
> Greetings,
>
> I got the below dmesg and the first bad commit is
>
> commit 98de48a0e011f2ef497a0f0c40b79169198cf797
> Author: Tejun Heo
> AuthorDate: Sat Nov 23 18:01:54 2013 -0500
> Commit: Tejun Heo
> CommitDate: Sat Nov
On Thu, Nov 28, 2013 at 02:54:13PM -0500, Tejun Heo wrote:
> Hello, Greg.
>
> For some reason, quilt can rebase the patches automatically here. I'm
> reposting the rest of the series (patches 07-41) here just in case.
> git branches for both pending patchsets are updated accordingly.
>
>
Oops, this was v3 posting.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
fs/sysfs/symlink.c::sysfs_delete_link() tests @sd->s_flags for
SYSFS_FLAG_NS. Let's add kernfs_ns_enabled() so that sysfs doesn't
have to test sysfs_dirent flag directly. This makes things tidier for
kernfs proper too.
This is purely cosmetic.
v2: To avoid possible NULL deref, use noop dummy
sysfs_dirent includes some information which should be available to
kernfs users - the type, flags, name and parent pointer. This patch
moves sysfs_dirent definition from kernfs/kernfs-internal.h to
include/linux/kernfs.h so that kernfs users can access them.
The type part of flags is exported
On Fri, 2013-11-29 at 14:56 +0200, Andy Shevchenko wrote:
> On Thu, 2013-11-28 at 10:32 -0800, Joe Perches wrote:
> > On Thu, 2013-11-28 at 13:28 +0200, user.email wrote:
> > > From: Andy Shevchenko
> > >
> > > Add the %paD format specifier for printing a dma_addr_t type, since the
> > > DMA
This patch adds PE/COFF header fields to the start of the Image
so that it appears as an EFI application to EFI firmware. An EFI
stub is included to allow direct booting of the kernel Image. Due
to EFI firmware limitations, only little endian kernels with 4K
page sizes are supported at this time.
Signed-off-by: Mark Salter
CC: Catalin Marinas
CC: Will Deacon
CC: linux-arm-ker...@lists.infradead.org
CC: matt.flem...@intel.com
CC: linux-...@vger.kernel.org
CC: linux-...@vger.kernel.org
CC: Rob Landley
CC: Leif Lindholm
CC: roy.fr...@linaro.org
---
Documentation/arm64/booting.txt | 4
This patch series adds EFI support to the arm64 kernel. This support has
two main parts: an EFI stub and runtime support. The EFI stub support
has the kernel masquerade as a PE/COFF application which can be directly
booted by EFI firmware (or by secondary loaders with EFI support). The
runtime
This patch adds EFI runtime support for arm64. The runtime support allows the
kernel to access various EFI runtime services provided by EFI firmware. Things
like reboot, real time clock, EFI boot variables, and others.
Signed-off-by: Mark Salter
CC: Catalin Marinas
CC: Will Deacon
CC:
Hi,
> My laptop has 4GB of ram, before I issue the command around 1.5GB of
> memory
> is used, when I issue the cp command around 3.7GB of memory is used.
> And the cp command takes a lot of time to copy.
>
> I am not able to launch other applications(take a lot of time) and
> even compiz
Is this version good, or should I make some more improvements?
On Thu, 2013-11-14 at 16:06 -0500, David Turner wrote:
> Not sure what the official subject line format is for revising only
> one of N patches, so I'm trying this one. Let me now if it is wrong.
>
> On Thu, 2013-11-14 at 02:15
There are several failure paths in cxusb_i2c_xfer(), where
d->i2c_mutex is left held. The patch fixes them.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
drivers/media/usb/dvb-usb/cxusb.c | 19 ---
1 file changed, 12
On Friday 29 November 2013, Linus Walleij wrote:
> On Thu, Nov 28, 2013 at 5:37 PM, Arnd Bergmann wrote:
> > On Thursday 28 November 2013, Jonas Jensen wrote:
> >> +static void __iomem *moxart_gpio_base;
> >
> > Just one comment: the usual way to do such a driver is to have
> > a derived data
From: Ondrej Puzman
Date: Thu, 28 Nov 2013 10:44:38 +0100
> Hi,
> I'm sending the pch_gbe patch set again per David Miller's request.
> Now the patches should be correctly numbered.
>
> The patches fixes problems I found on our industrial computer with
> Intel Atom E680T CPU and EG20T chipset.
On Fri, Nov 29, 2013 at 06:12:44PM +0100, Michal Nazarewicz wrote:
> From: Michal Nazarewicz
>
> u8 type, which is unsigned, is promoted to int, which is singned, when
> doing a binary shift. Then, on 64-bit machines, it is further promoted
> to unsigned long which may lead to more significant
From: Ondrej Puzman
Date: Thu, 28 Nov 2013 10:44:39 +0100
> According to Documentation/networking/driver.txt the ndo_start_xmit method
> should not return NETDEV_TX_BUSY under normal circumstances.
> Stop the transmit queue when tx_ring is full.
Please format your commit message text to 80
From: Hannes Frederic Sowa
Date: Thu, 28 Nov 2013 20:04:11 +0100
> Since patch "IPv6: Fixed support for blackhole and prohibit routes" we
> need ip6_pkt_prohibit(_out) available without CONFIG_IPV6_MULTIPLE_TABLES
> defined.
>
> Cc: Kamala R
> Signed-off-by: Hannes Frederic Sowa
Please
From: Hannes Frederic Sowa
Date: Thu, 28 Nov 2013 19:09:14 +0100
> On Thu, Nov 28, 2013 at 09:51:22AM -0800, Eric Dumazet wrote:
>> From: Eric Dumazet
>>
>> In commit c9e9042994d3 ("ipv4: fix possible seqlock deadlock") I left
>> another places where IP_INC_STATS_BH() were improperly used.
>>
From: Shawn Landden
Date: Sun, 24 Nov 2013 22:36:28 -0800
> Commit 35f9c09fe (tcp: tcp_sendpages() should call tcp_push() once)
> added an internal flag MSG_SENDPAGE_NOTLAST, similar to
> MSG_MORE.
>
> algif_hash, algif_skcipher, and udp used MSG_MORE from tcp_sendpages()
> and need to see the
On 11/29/2013 12:35 PM, Oleg Nesterov wrote:
> On 11/29, H. Peter Anvin wrote:
>>
>> On 11/29/2013 12:05 PM, Oleg Nesterov wrote:
>>>
>>> Can't we invalidate pte (so that any user will stuck in page fault),
>>> update the page(s), restore the pte and drop the locks?
>>
>> That would require a
jffs2_do_read_inode_internal() does unlock of f->sem mutex
on several failure paths, while its users expect
f->sem is still held. As a result double unlock of the mutex
can happen.
The patch makes jffs2_do_read_inode_internal() consistent
regarding f->sem handling.
Found by Linux Driver
On Fri, Nov 29, 2013 at 06:00:18PM +0100, Michal Nazarewicz wrote:
> From: Michal Nazarewicz
>
> “wait” wait queue is defined but never used in the function, thus
> it can be removed.
>
> Signed-off-by: Michal Nazarewicz
> drivers/char/tpm/tpm_i2c_nuvoton.c | 1 -
> 1 file changed, 1
On Friday, November 29, 2013 10:30:57 AM Alan Stern wrote:
> On Fri, 29 Nov 2013, Rafael J. Wysocki wrote:
>
> > That should have been
> >
> > driver->runtime_suspend(dev)
> > do_X(dev)
> >
> > because do_Y(dev) is for runtime suspend. Sorry.
> >
> > And of course, the subsystem-level
On Fri, Nov 29, 2013 at 09:28:48PM +0100, Levente Kurusa wrote:
> This patch adds a call to put_device() when the device_register()
> call has failed. This is required so that the last reference to the
> device is given up.
I'd assume this is not something you're actually hitting but have caught
On Wed, Nov 13, 2013 at 03:08:14AM -0500, Greg Price wrote:
> This comment didn't quite keep up as extract_entropy() was split into
> four functions. Put each bit by the function it describes.
>
> Cc: "Theodore Ts'o"
> Signed-off-by: Greg Price
Thanks, applied.
On 11/29, H. Peter Anvin wrote:
>
> On 11/29/2013 12:05 PM, Oleg Nesterov wrote:
> >
> > Can't we invalidate pte (so that any user will stuck in page fault),
> > update the page(s), restore the pte and drop the locks?
> >
>
> That would require a global TLB shootdown
Well, it is not really
On Fri, Nov 29, 2013 at 09:09:46PM +0100, Stephane Eranian wrote:
> > So in theory it would be harmless to export the values even if not
> > supported. What is the worst failure mode? That somehow a recent CPU
> > doesn't support the MSR and we get a GPF when trying to access it?
> >
> Yes. I
On Fri, Nov 29, 2013 at 12:11 PM, Jonas Jensen wrote:
> Add GPIO driver for MOXA ART SoCs.
>
> Signed-off-by: Jonas Jensen
OK this v6 version is looking *really good* so I have
applied it, couldn't hesitate.
> +static struct gpio_chip moxart_template_chip = {
> + .label
This patch adds a call to put_device() when the device_register()
call has failed. This is required so that the last reference to the
device is given up.
Signed-off-by: Levente Kurusa
---
arch/x86/kernel/cpu/mcheck/mce.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
Or would it make sense to drop header_size and use off + something as
function parameters?
Zoli
On 29/11/13 18:56, Zoltan Kiss wrote:
Before checksum setup we need to make sure we have enough data in linear
buffer, so we do a pull if not. The calculation of the required data counts
with
Currently both setup_new_exec() and flush_old_exec() issue
a call to arch_pick_mmap_layout().
As setup_new_exec() and flush_old_exec() are always called
pairwise arch_pick_mmap_layout() is called twice.
This patch removes one call from setup_new_exec() to have
it only called once.
Signed-off-by:
On Thu, Nov 28, 2013 at 5:37 PM, Arnd Bergmann wrote:
> On Thursday 28 November 2013, Jonas Jensen wrote:
>> +static void __iomem *moxart_gpio_base;
>
> Just one comment: the usual way to do such a driver is to have
> a derived data structure like
>
> struct moxart_gpio_chip {
> struct
On 11/29/2013 12:05 PM, Oleg Nesterov wrote:
>
> Can't we invalidate pte (so that any user will stuck in page fault),
> update the page(s), restore the pte and drop the locks?
>
That would require a global TLB shootdown (and wouldn't help
shared-memory code segments, if we care about that at
On Fri, Nov 29, 2013 at 8:16 PM, Vince Weaver wrote:
> On Thu, 28 Nov 2013, Stephane Eranian wrote:
>
>> On Thu, Nov 28, 2013 at 1:26 PM, Ingo Molnar wrote:
>> >
>> > * Vince Weaver wrote:
>> >
>> >> On Wed, 27 Nov 2013, Stephane Eranian wrote:
>> >>
>> >> > On Wed, Nov 27, 2013 at 7:35 PM,
On Fri, Nov 29, 2013 at 9:05 PM, Lars-Peter Clausen wrote:
> On 11/29/2013 08:52 PM, Linus Walleij wrote:
>> I guess you may be referring to the problem of instatiating
>> a dynamic IRQ chip in *board code* and then passing the
>> obtained dynamic IRQ numbers as resources to the
>> devices also
On Wed, Nov 13, 2013 at 03:07:40AM -0500, Greg Price wrote:
> The loop condition never changes until just before a break, so we
> might as well write it as a constant. Also since v2.6.33-rc7~40^2~2
> ("random: drop weird m_time/a_time manipulation") we don't do
> anything after the loop finishes,
On 11/29, Andi Kleen wrote:
>
> > Andi, et al. I am going to discuss the things I do not really
> > understand, probably this can't make any sense, but...
>
> I think it's enough to set the dirty bit in the underlying
> struct page, no need to play games with the PTE.
Ah, sorry for confusion, I
On Wed, Nov 13, 2013 at 03:07:32AM -0500, Greg Price wrote:
> After this remark was written, commit d2e7c96af added a use of
> arch_get_random_long() inside the get_random_bytes codepath.
> The main point stands, but it needs to be reworded.
>
> Cc: "Theodore Ts'o"
> Signed-off-by: Greg Price
> This also needs to change .free callback in the dma_map_ops for amd_gart
> and sta2x11, because these dma_ops are also using
> dma_generic_alloc_coherent().
Looks good to me from a quick read.
-Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Fri, Nov 29, 2013 at 5:01 PM, Michal Nazarewicz wrote:
> From: Michal Nazarewicz
>
> [commit 8185554d: fix incorrect inode acl reset] introduced a dead
> code by adding a condition which can never be true to an else
> branch. The condition can never be true because it is already
> checked by
On Fri, Nov 29, 2013 at 11:51:44PM +0900, Akinobu Mita wrote:
> This patch set extends support for the DMA Contiguous Memory Allocator
> on x86. Currently it is only supported on pci-nommu. So this aims at
> enabling it on swiotlb and intel-iommu, too.
>
> Regardless of which dma mapping
On Wed, Nov 13, 2013 at 03:07:26AM -0500, Greg Price wrote:
> There's only one function here now, as uuid_strategy is long gone.
> Also make the bit about "If accesses via ..." clearer.
>
> Cc: "Theodore Ts'o"
> Signed-off-by: Greg Price
Thanks, applied.
On Wed, Nov 13, 2013 at 03:07:14AM -0500, Greg Price wrote:
> Cc: "Theodore Ts'o"
> Signed-off-by: Greg Price
Applied, thanks.
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Hi Oleg,
Thanks for finding all these problems.
> We are going to change this user page, it seems that we need
> set_page_dirty() ?
That's true. Will add it next rev.
>
> Andi, et al. I am going to discuss the things I do not really
> understand, probably this can't make any sense, but...
I
Hi Srinivas,
On Tue, Nov 12, 2013 at 01:53:03PM +, srinivas.kandaga...@st.com wrote:
> From: Srinivas Kandagatla
>
> STi series SOCs have a glue layer on top of the synopsis gmac IP, this
> glue layer needs to be configured before the gmac driver starts using
> the IP.
>
> This patch adds
I'm announcing the release of the 3.12.2 kernel.
All users of the 3.12 kernel series must upgrade.
The updated 3.12.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.12.y
and can be browsed at the normal kernel.org git web browser:
Em Fri, Nov 29, 2013 at 03:42:35PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Thu, Nov 28, 2013 at 12:33:05PM +0100, Jiri Olsa escreveu:
> > This plugin adds field resolving functions for following tracepoint events:
> > jbd2:jbd2_checkpoint_stats
> > jbd2:jbd2_run_stats
> > The diff of
I'm announcing the release of the 3.10.21 kernel.
All users of the 3.10 kernel series must upgrade.
The updated 3.10.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.10.y
and can be browsed at the normal kernel.org git web
1 - 100 of 798 matches
Mail list logo
