On Thu, Jul 17, 2014 at 1:18 PM, Joakim Tjernlund
wrote:
> Trying to real /proc//exe I noticed I could not read links not
> belonging to my user such as:
> jocke > ls -l /proc/1/exe
> ls: cannot read symbolic link /proc/1/exe: Permission denied
>
> Is this expected?
Why do you
Hi,
On 15/07/14 09:45, Ley Foon Tan wrote:
> This patch adds support for system calls from userspaces. It uses the
> asm-generic/unistd.h definitions with architecture spcific syscall. The
> sys_call_table
> is just an array defined in a C file and it contains pointers to the syscall
>
o handle kernel NULL pointer dereference at
> (null)
> [0.00] IP: wake_up_process (kernel/sched/core.c:1768)
> [0.00] PGD 0
> [0.00] Oops: [#1] PREEMPT SMP DEBUG_PAGEALLOC
> [0.000000] Modules linked in:
> [0.00] CPU: 0 PID:
On 07/18/2014 06:00 PM, Antoine Ténart wrote:
The Berlin SoC has a two SATA ports. Add a PHY driver to handle them.
The mode selection can let us think this PHY can be configured to fit
other purposes. But there are reasons to think the SATA mode will be
the only one usable: the PHY registers
On our hardware, the MACB connected to a heavilly used AXI bus, fails to
correctly write RX descriptors.
This leds to RX ring errors that can be managed.
These patchs add RX error management according to the Cadence MACB User Guide.
The first patch separates the RX and TX rings init in order to
On Thu, Jul 17, 2014 at 09:26:04AM -0400, Johannes Weiner wrote:
>
>
> Andrew, could you please replace this patch with the following?
>
> ---
> From bbe8c1645c77297a96ecd5d64d659ddcd6984d03 Mon Sep 17 00:00:00 2001
> From: Johannes Weiner
> Date: Mon, 14 Jul 2014 08:51:54 -0400
> Subject:
In certain circumstances, the MACB fails to write correct RX ring
descriptor, and lead to actually managed by BUG_ON() error cases.
Handle these two cases by returning error values, while resetting
the RX ring and RX HW path in the poll methos.
In the same time, check and handle BNA and OVR into
On Mon, Jul 14, 2014 at 09:20:48AM -0400, Johannes Weiner wrote:
> As per Mel, use bool for reclaimability throughout and simplify the
> reclaimability tracking in shrink_zones().
>
> Signed-off-by: Johannes Weiner
Acked-by: Mel Gorman
--
Mel Gorman
SUSE Labs
--
To unsubscribe from this
On Mon, Jul 14, 2014 at 09:20:47AM -0400, Johannes Weiner wrote:
> As per Mel, replace out label with breaks from the loop.
>
> Signed-off-by: Johannes Weiner
Acked-by: Mel Gorman
--
Mel Gorman
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
A single method is called to initialize the TX and RX rings.
Separate the methods into distinct ones for MACB and GEM contexts.
Also remove the multiple assignments from the original code.
Signed-off-by: Neil Armstrong
---
drivers/net/ethernet/cadence/macb.c | 36
On Fri, Jul 18, 2014 at 01:31:40PM +0100, Jason Cooper wrote:
> On Fri, Jul 18, 2014 at 10:02:05AM +0100, Mark Rutland wrote:
> > On Thu, Jul 17, 2014 at 03:12:35PM +0100, Jason Cooper wrote:
> > > On Thu, Jul 17, 2014 at 02:55:34PM +0100, Mark Rutland wrote:
> > > > Hi Jason,
> > > >
> > > > On
On Fri, Jul 11, 2014 at 03:37:38PM +0800, Jiang Liu wrote:
> When CONFIG_HAVE_MEMORYLESS_NODES is enabled, cpu_to_node()/numa_node_id()
> may return a node without memory, and later cause system failure/panic
> when calling kmalloc_node() and friends with returned node id.
> So use
> Currently, one would have to put a loop on the address transfer waiting an ack
> is received in user space.
This is what most i2c master drivers would need to do anyhow. I have
never heard of hardware support for that. Do you know an IP core which
does that? And how are timeouts
On 07/14/2014 04:15 PM, Jiri Olsa wrote:
>> for more data while reading the "events" traces. The latter will be
>> probably replaced by https://lkml.org/lkml/2014/4/3/217.
>> Babeltrace needs only
>> "ctf-writer: Add support for the cpu_id field"
>>
The ahci_platform driver is a generic driver using the libahci_platform
functions. Add a generic compatible to avoid having an endless list of
compatibles with no differences for the same driver.
Signed-off-by: Antoine Ténart
---
drivers/ata/ahci_platform.c | 2 ++
1 file changed, 2
Hi all,
Sheetal reported a weird issue on arm where events which have been
closed seem to stay around and compete for HW counters if an application
has forked between the events being opened and them being closed.
I've reproduced this in mainline and linux-next and this seems to be a
generic
On Fri, Jul 18, 2014 at 10:02:05AM +0100, Mark Rutland wrote:
> On Thu, Jul 17, 2014 at 03:12:35PM +0100, Jason Cooper wrote:
> > On Thu, Jul 17, 2014 at 02:55:34PM +0100, Mark Rutland wrote:
> > > Hi Jason,
> > >
> > > On Thu, Jul 17, 2014 at 02:18:54PM +0100, Jason Cooper wrote:
> > > > On Wed,
Tejun, Kishon, Sebastian,
I looked into the AHCI framework to see how to map PHYs and ports
information. I see two ways of doing this:
- We can attach the ahci_port_priv to the ahci_host_priv structure,
but that would require quite a lot of changes since the
ahci_port_priv is
The current implementation of the libahci does not allow to use multiple
PHYs. This patch adds the support of multiple PHYs by the libahci while
keeping the old bindings valid for device tree compatibility.
This introduce a new way of defining SATA ports in the device tree, with
one port per
This patch moves force_port_map and mask_port_map into the
ahci_host_priv structure. This allows to modify them into the AHCI
framework. This is needed by the new dt bindings representing ports as
the port_map mask is computed automatically.
Signed-off-by: Antoine Ténart
---
drivers/ata/ahci.h
The libahci now allows to use multiple PHYs and to represent each port
as a sub-node. Add these bindings to the documentation.
Signed-off-by: Antoine Ténart
---
.../devicetree/bindings/ata/ahci-platform.txt | 37 ++
1 file changed, 37 insertions(+)
diff --git
The BG2Q has an AHCI SATA controller. Add the corresponding nodes
(AHCI, PHY) into its device tree.
Signed-off-by: Antoine Ténart
---
arch/arm/boot/dts/berlin2q.dtsi | 39 +++
1 file changed, 39 insertions(+)
diff --git a/arch/arm/boot/dts/berlin2q.dtsi
The Berlin SoC has a two SATA ports. Add a PHY driver to handle them.
The mode selection can let us think this PHY can be configured to fit
other purposes. But there are reasons to think the SATA mode will be
the only one usable: the PHY registers are only accessible indirectly
through two
The BG2Q has an AHCI SATA controller with an eSATA interface. Enable it.
Only enable the first port, the BG2Q DMP does not support the second one.
Signed-off-by: Antoine Ténart
---
arch/arm/boot/dts/berlin2q-marvell-dmp.dts | 8
1 file changed, 8 insertions(+)
diff --git
The Berlin SATA PHY drives the PHY related to the SATA interface. Add
the corresponding documentation.
Signed-off-by: Antoine Ténart
---
.../devicetree/bindings/phy/berlin-sata-phy.txt| 34 ++
1 file changed, 34 insertions(+)
create mode 100644
On 07/18/2014 02:12 PM, Jiri Slaby wrote:
> This is the start of the stable review cycle for the 3.12.25 release.
> There are 170 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should
On Fri, Jul 18, 2014 at 11:28:14 +0200,
Dietmar Eggemann wrote:
Didn't see what I was looking for in your dmesg output. Did you use
'earlyprintk=keep sched_debug'
I was missing a space. I'll get it on the next run.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
Previously we would do a regulator get against the main Arizona device
to obtain the MICVDD regulator. Arizona is an MFD device and normally
MICVDD will be supplied by one of its children (the arizona-micsupp
regulator). As devres destruction for the MFD device will run after all
its children have
From: Joerg Roedel
When a memory bitmap is fully populated on a large memory
machine (several TB of RAM) it can take more than a minute
to walk through all bits. This causes the soft lockup
detector on these machine to report warnings.
Avoid this by touching the soft lockup watchdog in the
Hi,
here is a patch set to improve the scalability of the memory
bitmap implementation used for hibernation. The current
implementation does not scale well to machines with several
TB of memory. A resume on those machines may cause soft
lockups to be reported.
These patches improve the data
From: Joerg Roedel
This patch adds the code to allocate and build the radix
tree to store the memory bitmap. The old data structure is
left in place until the radix tree implementation is
finished.
Signed-off-by: Joerg Roedel
---
kernel/power/snapshot.c | 224
From: Joerg Roedel
The radix tree implementatio is proved to work the same as
the old implementation now. So the old implementation can be
removed to finish the switch to the radix tree for the
memory bitmaps.
Signed-off-by: Joerg Roedel
---
kernel/power/snapshot.c | 260
From: Joerg Roedel
Add a function to find a bit in the radix tree for a given
pfn. Also add code to the memory bitmap wrapper functions to
use the radix tree together with the existing memory bitmap
implementation.
On read accesses compare the results of both bitmaps to make
sure the radix tree
From: Joerg Roedel
The existing implementation of swsusp_free iterates over all
pfns in the system and checks every bit in the two memory
bitmaps.
This doesn't scale very well with large numbers of pfns,
especially when the bitmaps are not populated very densly.
Change the algorithm to iterate
From: Joerg Roedel
Add code to remember the last position that was requested in
the radix tree. Use it as a cache for faster linear walking
of the bitmap in the memory_bm_rtree_next_pfn() function
which is also added with this patch.
Signed-off-by: Joerg Roedel
---
kernel/power/snapshot.c |
‘rx_buf’ is not used in this function.
Signed-off-by: Sachin Kamat
---
drivers/mfd/tps65912-spi.c |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/mfd/tps65912-spi.c b/drivers/mfd/tps65912-spi.c
index 69a5178bf152..de60ad98bd9f 100644
---
Removed code unused in this function.
Signed-off-by: Sachin Kamat
Cc: Cory Maccarrone
---
Compile tested.
---
drivers/mfd/htc-i2cpld.c |5 -
1 file changed, 5 deletions(-)
diff --git a/drivers/mfd/htc-i2cpld.c b/drivers/mfd/htc-i2cpld.c
index d7b2a75aca3e..b44f0203983b 100644
---
On Fri, 18 Jul 2014 12:44:18 +0800
Wang Nan wrote:
> Hi Steve,
>
> What's your opinion on my v2 patch ( https://lkml.org/lkml/2014/7/14/839 )?
>
> I have swapped if consitions following your suggestion.
>
Bah I didn't see it.
Damn Claws mail, I need to figure out why the f*ck it randomly
On 07/18/2014 04:02 AM, Petr Mládek wrote:
> On Thu 2014-07-17 12:59:10, Alex Elder wrote:
>> If log_store() gets flags containing LOG_PREFIX, it indicates the
>> record getting stored should implicitly complete the previous log
>> record and start a new one.
>>
>> We can also ensure the previous
On Thu, Jul 17, 2014 at 11:24:45PM -0400, Nick Krause wrote:
> >
> Yes I am human. Now thinking about it we need it to test for staging.
Why do you say that?
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
Hi Catalin,
On 18 July 2014 16:37, Catalin Marinas wrote:
> On Tue, Jun 24, 2014 at 03:38:34PM +0100, Mark Salter wrote:
>> On Tue, 2014-06-24 at 15:14 +0100, Catalin Marinas wrote:
>> > On Mon, Jun 23, 2014 at 02:17:03PM +0100, Mark Salter wrote:
>> > > On Mon, 2014-06-23 at 12:09 +0100,
On 7/17/2014 8:25 PM, Alan Stern wrote:
I can't say this is actually wrong, but have you ever encountered a
situation where this would be needed? How often does anyone need to do
a multi-packet transfer over an interrupt endpoint?
Honestly, I haven't found any such real device yet. I did this
On Fri, Jul 18, 2014 at 12:25:17PM +0200, Richard Weinberger wrote:
> > if (ret != buflen)
>
> A small nit-pick, missing "{".
Thanks, good catch. Fixed.
- Ted
--
To unsubscribe from this list: send the line "unsubscribe
This patch adds virtual endpoint address mapping to functionfs.
So far endpoint addresses given by user through endpoint descriptors
were ignored, and replaced by physical endpoint addresses. Endpoint
address in wIndex field of setup requesti, addressed to endpoint, was
the physical endpoint
On Thu 2014-07-17 09:09:11, Alex Elder wrote:
> This patch corrects a few more typographical errors in "printk.c".
>
> Signed-off-by: Alex Elder
Reviewed-by: Petr Mladek
Best Regards,
Petr
> ---
> kernel/printk/printk.c | 10 +-
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
>
On Thu 2014-07-17 09:09:10, Alex Elder wrote:
> If a log record has LOG_PREFIX set, its predecessor record should be
> terminated if it was marked LOG_CONT. In devkmsg_read(), this
> condition was being ignored, which would lead to such records
> showing up combined when reading /dev/kmsg. Fix
From: Kamil Debski
This patch moves the part of code that initializes the PHY bus width.
This results in simpler code and removes the need to check whether
the Generic PHY Framework is used.
Signed-off-by: Kamil Debski
Signed-off-by: Marek Szyprowski
Signed-off-by: Robert Baldyga
---
From: Marek Szyprowski
Some DWC2/s3c-hsotg debug messages are really useless for typical user,
so hide them behind dev_dbg().
Signed-off-by: Marek Szyprowski
Signed-off-by: Robert Baldyga
---
drivers/usb/dwc2/gadget.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
From: Andrzej Pietrasiewicz
Adjust the debug text to the name of the printed variable.
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Robert Baldyga
---
drivers/usb/dwc2/gadget.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/dwc2/gadget.c
From: Marek Szyprowski
This patch fixes possible freeze caused by infinite loop in interrupt
context.
Signed-off-by: Marek Szyprowski
Signed-off-by: Robert Baldyga
---
drivers/usb/dwc2/gadget.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/dwc2/gadget.c
Because we have not enough memory to have each TX FIFO of size at least
3072 bytes (the maximum single packet size with 3 transactions per
microframe), we create four FIFOs of lenght 1024, and four of length
3072 bytes, and assing them to endpoints dynamically according to
maxpacket size value of
From: Marek Szyprowski
This leads to potential spinlock recursion in composite framework, other
udc drivers also don't call it directly from pullup method.
Signed-off-by: Marek Szyprowski
Signed-off-by: Robert Baldyga
---
drivers/usb/dwc2/gadget.c | 1 -
1 file changed, 1 deletion(-)
diff
Endpoint 0 should not be disabled, so we start loop counter from number 1.
Signed-off-by: Robert Baldyga
---
drivers/usb/dwc2/gadget.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/dwc2/gadget.c b/drivers/usb/dwc2/gadget.c
index 11f038e..cc31088 100644
---
When device is stopped or suspended clock is not needed so we
can disable it for this time.
Signed-off-by: Robert Baldyga
---
drivers/usb/dwc2/gadget.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/drivers/usb/dwc2/gadget.c b/drivers/usb/dwc2/gadget.c
index e74094a..11f038e
Hi Linus,
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
pm+acpi-3.16-rc6
to receive ACPI and power management fixes for v3.16-rc6
with top-most commit 3962808023d54f0e1adbde403eb8e572984ccb2a
Merge branches 'pm-sleep' and 'pm-cpufreq'
on top of commit
From: Marek Szyprowski
This patch fixes kernel panic/interrupt storm/etc issues if bootloader
left s3c-hsotg module in enabled state. Now interrupt handler is enabled
only after proper configuration of hardware registers.
Signed-off-by: Marek Szyprowski
Signed-off-by: Robert Baldyga
---
From: Kamil Debski
When the driver is removed s3c_hsotg_phy_disable is called three times
instead of once. This results in decreasing of the phy reference counter
below zero and thus consecutive inserts of the module fails.
This patch removes calls to s3c_hsotg_phy_disable from s3c_hsotg_remove
Hello,
This patchset contains fixes for dwc2 gadget driver. It touches PHY,
FIFO configuration, initialization sequence and adds many other small fixes.
Best regards
Robert Baldyga
Samsung R Institute Poland
Changelog:
v3:
- use endpoint index instead of FIFO index for EPFIFO
- extend patch
From: Marek Szyprowski
Print warning if FIFOs are configured in such a way that they don't fit
into the SPRAM available on the s3c hsotg module.
Signed-off-by: Marek Szyprowski
Signed-off-by: Robert Baldyga
---
drivers/usb/dwc2/core.h | 1 +
drivers/usb/dwc2/gadget.c | 15 ++-
From: Kamil Debski
In the Generic PHY Framework a NULL phy is considered to be a valid phy
thus the "if (hsotg->phy)" check does not give us the information whether
the Generic PHY Framework is used.
In addition to the above this patch also removes phy_init from probe and
phy_exit from remove.
On 18/07/14 13:28, Hans de Goede wrote:
Hi,
On 07/18/2014 09:16 AM, Mikko Perttunen wrote:
So here's v5: this time, as suggested, I handle the sata clock myself and let
ahci_platform handle it too, leading it to be prepared+enabled twice. This
works fine, and allows us to remove the DT
Aua. This really hurts. I wonder how this could ever be admitted to
the Linux kernel...
Further comments suppressed because the would most likely violate the
CDA.
If someone should not grasp what this patch does, they should consider
what happens upon unloading/reloading the kernel module.
Hi Hemant,
(2014/07/17 14:53), Hemant Kumar wrote:
> This patchset helps in listing dtrace style markers(SDT) present in user space
> applications through perf.
> Notes/markers are placed at important places by the
> developers. They have a negligible overhead when not enabled.
> We can enable
The following changes since commit 3c8fb50445833b93f69b6b703a29aae3523cad0c:
Merge tag 'pm+acpi-3.16-rc2' of
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm (2014-06-19
18:58:57 -1000)
are available in the git repository at:
On Fri, Jul 18, 2014 at 05:05:20PM +0800, Tang Chen wrote:
> Hi Gleb,
>
> On 07/17/2014 09:57 PM, Gleb Natapov wrote:
> >On Thu, Jul 17, 2014 at 09:34:20PM +0800, Tang Chen wrote:
> >>Hi Gleb,
> >>
> >>On 07/15/2014 08:40 PM, Gleb Natapov wrote:
> >>..
>
> And yes, we have the
Hi Linus,
please, pull a couple of UBI fixes.
The following changes since commit a497c3ba1d97fc69c1e78e7b96435ba8c2cb42ee:
Linux 3.16-rc2 (2014-06-21 19:02:54 -1000)
are available in the git repository at:
git://git.infradead.org/linux-ubifs.git tags/upstream-3.16-rc6
for you to fetch
On Thu, Jul 17, 2014 at 04:09:23PM -0700, Nishanth Aravamudan wrote:
> [Apologies for the large Cc list, but I believe we have the following
> interested parties:
>
> x86 (recently posted memoryless node support)
> ia64 (existing memoryless node support)
> ppc (existing memoryless node support)
>
0
[0.00] Oops: [#1] PREEMPT SMP DEBUG_PAGEALLOC
[0.00] Modules linked in:
[0.00] CPU: 0 PID: 0 Comm: swapper/0 Tainted: GW
3.16.0-rc5-next-20140718-sasha-00046-g054cefc #898
[0.00] task: 9fa2d580 ti: 9fa29580 task.ti:
9fa2
Currently, tracing_thresh works only if we specify it before selecting
function_graph tracer. If we do the opposite, tracing_thresh will change
it's value, but it will not be applied.
To fix it, we add update_thresh callback which is called whenever
tracing_thresh is updated and for function_graph
On Friday 18 July 2014 15:41:27 Naveen Krishna Ch wrote:
> >
> > {
> > .name = "s3c24xx-adc",
> > .driver_data= TYPE_ADCV1,
> > }, {
> > .name = "s3c2443-adc",
> > .driver_data= TYPE_ADCV11,
On Friday 18 July 2014 19:00:48 Chanwoo Choi wrote:
> On 07/18/2014 06:47 PM, Arnd Bergmann wrote:
> >
> > Further, why is it called "sclk_adc" rather than just "sclk"?
>
> The sclk means 'special clock' in Exynos TRM. Exynos SoC has varisou sclk
> clocks.
> 'sclk_adc' is only used for ADC IP.
On 07/16/2014 09:58 PM, Paul Zimmerman wrote:
>> From: Robert Baldyga [mailto:r.bald...@samsung.com]
>> Sent: Wednesday, July 16, 2014 3:22 AM
>>
>> Because we have not enough memory to have each TX FIFO of size at least 3072
>> bytes (the maximum single packet size), we create four FIFOs of
On Tue, Jun 24, 2014 at 03:38:34PM +0100, Mark Salter wrote:
> On Tue, 2014-06-24 at 15:14 +0100, Catalin Marinas wrote:
> > On Mon, Jun 23, 2014 at 02:17:03PM +0100, Mark Salter wrote:
> > > On Mon, 2014-06-23 at 12:09 +0100, Catalin Marinas wrote:
> > > > My proposal (in the absence of any kind
I guess someone working over the summertime. :)
[ cut here ]
WARNING: CPU: 1 PID: 495 at mm/slab_common.c:69 kmem_cache_create+0x1a9/0x330()
Modules linked in: virtio_net virtio_scsi(+) drm virtio_pci i2c_core
virtio_ring ata_generic pata_acpi virtio sunrpc dm_crypt
On Thu, Jul 17, 2014 at 08:52:00AM -0700, Joe Perches wrote:
> c90 section "6.7.2 Type Specifiers" says:
> "type specifiers may occur in any order"
>
> That means that:
> short int is the same as int short
> unsigned short int is the same as int unsigned short
> etc...
>
>
Konrad Rzeszutek Wilk writes:
> On Tue, Jul 15, 2014 at 05:43:17PM +0200, Vitaly Kuznetsov wrote:
>> Konrad Rzeszutek Wilk writes:
>>
>> > On Tue, Jul 15, 2014 at 03:40:37PM +0200, Vitaly Kuznetsov wrote:
>> >> From: Olaf Hering
>> >>
>> >> This is a respin of
Hi Thierry,
于 2014年07月18日 18:03, Thierry Reding 写道:
On Fri, Jul 18, 2014 at 01:05:56PM +0800, caesar wrote:
于 2014年07月18日 03:24, Beniamino Galvani 写道:
On Thu, Jul 17, 2014 at 02:08:14PM +0800, caesar wrote:
[...]
@@ -119,9 +185,12 @@ static int rockchip_pwm_probe(struct platform_device
On Thu 2014-07-17 09:09:09, Alex Elder wrote:
> This patch fixes a problem similar to what was addressed in the
> previous patch.
>
> All paths that read and format log records (for consoles, and for
> reading via syslog and /dev/kmsg) go through msg_print_text(). That
> function starts with
Hi Linus:
This push fixes a boot hang in virt guests when the virtio RNG
is enabled.
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git
or
master.kernel.org:/pub/scm/linux/kernel/git/herbert/crypto-2.6.git
Amit Shah (2):
hwrng: fetch randomness only
On Thu 2014-07-17 09:09:07, Alex Elder wrote:
> Two log record flags--LOG_CONT and LOG_NEWLINE--are mutually
> exclusive. That is, one or the other is always set, but they are
> never both set at the same time in a log record flags field. What
> follows is a great deal of explanation that aims
Am 18.07.2014 12:44, schrieb Chen Gang:
> On 07/18/2014 03:35 PM, Richard Weinberger wrote:
>> Am 18.07.2014 02:36, schrieb Chen Gang:
>>>
>>> On 07/18/2014 02:09 AM, Richard Weinberger wrote:
Am 17.07.2014 12:48, schrieb Arnd Bergmann:
> AFAICT, NO_IOMEM only has a real purpose on UML
Thanks!
- Mikko
On 18/07/14 13:26, Hans de Goede wrote:
Hi,
On 07/18/2014 09:12 AM, Mikko Perttunen wrote:
This adds support for the integrated AHCI-compliant Serial ATA
controller present on the NVIDIA Tegra124 system-on-chip.
Signed-off-by: Mikko Perttunen
---
v5: let ahci_platform
Hi Daniel,
Am Freitag, 18. Juli 2014, 11:46:51 schrieb Daniel Lezcano:
> On 07/07/2014 05:13 PM, Matthias Brugger wrote:
> > This adds a generic devicetree board file and a dtsi for boards
> > based on MT6589 SoCs from Mediatek.
> >
> > Apart from the generic parts (gic, clocks) the only
On 07/17/2014 12:12 PM, Sasha Levin wrote:
> On 07/17/2014 12:10 PM, Vlastimil Babka wrote:
>> > On 07/15/2014 12:28 PM, Hugh Dickins wrote:
>>> >> In the end I decided that we had better look at it as two problems,
>>> >> the trinity faulting starvation, and the indefinite punching loop,
>>> >>
On 07/18/2014 03:35 PM, Richard Weinberger wrote:
> Am 18.07.2014 02:36, schrieb Chen Gang:
>>
>> On 07/18/2014 02:09 AM, Richard Weinberger wrote:
>>> Am 17.07.2014 12:48, schrieb Arnd Bergmann:
AFAICT, NO_IOMEM only has a real purpose on UML these days. Could we take
a shortcut here
On Thu 2014-07-17 09:09:06, Alex Elder wrote:
> Two global variables, "syslog_prev" and "console_prev", maintain a
> copy of the flags value used in the log record most recently
> formatted for syslog or the console, respectively.
>
> Initially there is no previous formatted log record, and these
Hi,
Here are the current set of small fixes relating to GFS2.
This patch set contains two minor docs/spelling fixes, some fixes for
flock, a change to use GFP_NOFS to avoid recursion on a rarely used code
path and a fix for a race relating to the glock lru,
Steve.
--
To unsubscribe from this
From: Bob Peterson
Function gfs2_glock_dq_wait is supposed to dequeue a glock and then
wait for the lock to be demoted. The problem is, if this is a shared
lock, its demote will depend on the other holders, which means you
might end up waiting forever because the other process is blocked.
This
From: Fabian Frederick
kcalloc manages count*sizeof overflow.
Cc: cluster-de...@redhat.com
Signed-off-by: Fabian Frederick
Signed-off-by: Steven Whitehouse
diff --git a/fs/gfs2/lock_dlm.c b/fs/gfs2/lock_dlm.c
index 91f274d..4fafea1 100644
--- a/fs/gfs2/lock_dlm.c
+++ b/fs/gfs2/lock_dlm.c
@@
Normally GFP_KERNEL is ok here, but there is now a rarely used code path
relating to deallocation of unlinked inodes (in certain corner cases)
which if hit at times of memory shortage can cause recursion while
trying to free memory.
One solution would be to try and move the gfs2_glock_get() call
From: Bob Peterson
This patch removes the GLF_NOCACHE flag from the glocks associated with
flocks. There should be no good reason not to cache glocks for flocks:
they only force the glock to be demoted before they can be reacquired,
which can slow down performance and even cause glock hangs,
From: Bob Peterson
This patch allows flock glocks to use a non-blocking dequeue rather
than dq_wait. It also reverts the previous patch I had posted regarding
dq_wait. The reverted patch isn't necessarily a bad idea, but I decided
this might avoid unforeseen side effects, and was therefore
From: Geert Uytterhoeven
Signed-off-by: Geert Uytterhoeven
Cc: cluster-de...@redhat.com
Signed-off-by: Steven Whitehouse
diff --git a/fs/gfs2/glops.c b/fs/gfs2/glops.c
index fc11007..2ffc67d 100644
--- a/fs/gfs2/glops.c
+++ b/fs/gfs2/glops.c
@@ -234,8 +234,8 @@ static void
From: Fabian Frederick
Cc: cluster-de...@redhat.com
Signed-off-by: Fabian Frederick
Signed-off-by: Steven Whitehouse
diff --git a/fs/gfs2/rgrp.c b/fs/gfs2/rgrp.c
index db629d1..f4cb9c0 100644
--- a/fs/gfs2/rgrp.c
+++ b/fs/gfs2/rgrp.c
@@ -337,7 +337,7 @@ static bool
On Fri, 18 Jul 2014 17:50:55 +0900, Namjae Jeon wrote:
> > On Tue, 8 Jul 2014 16:02:28 +0200 (CEST), Lukáš Czerner
> > wrote:
> > Non-text part: MULTIPART/MIXED
> > > On Tue, 8 Jul 2014, Namjae Jeon wrote:
> > >
> > > > Date: Tue, 08 Jul 2014 21:00:02 +0900
> > > > From: Namjae Jeon
> > > >
We must not leave items on the LRU list with GLF_LOCK set, since
they can be removed if the glock is brought back into use, which
may then potentially result in a hang, waiting for GLF_LOCK to
clear.
It doesn't happen very often, since it requires a glock that has
not been used for a long time to
Mark,
Please disregard this single patch.
On Thu, Jul 17, 2014 at 09:21:37PM +0800, Nicolin Chen wrote:
> SAI will not clear their FIFOs after disabling TE/RE. Therfore, the driver
> should take care the task so as not to let useless data remain in the FIFO.
>
> Signed-off-by: Nicolin
tested-by: Prakash Burla
This driver tested on IFC6410 with USB Driver.
On Fri, Jul 18, 2014 at 1:46 AM, Srinivas Kandagatla
wrote:
> This patch makes the phy reset clk and reset line optional as this clk
> is not available on boards like IFC6410 with APQ8064.
>
> phy-reset clk is only used as
Hi,
On 07/18/2014 09:16 AM, Mikko Perttunen wrote:
> So here's v5: this time, as suggested, I handle the sata clock myself and let
> ahci_platform handle it too, leading it to be prepared+enabled twice. This
> works fine, and allows us to remove the DT ordering requirement.
>
> I also have in
Hi,
On 07/18/2014 09:11 AM, Mikko Perttunen wrote:
> This patch adds device tree binding documentation for the SATA
> controller found on NVIDIA Tegra SoCs.
>
> Signed-off-by: Mikko Perttunen
> ---
> v5: remove ordering requirement again
Acked-by: Hans de Goede
Regards,
Hans
>
>
701 - 800 of 2038 matches
Mail list logo
