On Saturday 26 July 2014 11:03 AM, Grant Likely wrote:
> On Fri, 25 Jul 2014 09:15:22 -0500, Rob Herring wrote:
>> On Fri, Jul 25, 2014 at 6:02 AM, Vineet Gupta
>> wrote:
>>> Hi Grant,
>>>
>>> linux-next has a series for arc_uart (via tty tree) which converts it to
>>> generic
>>> earlycon and s
Hi Rob,
On Friday 25 July 2014 07:45 PM, Rob Herring wrote:
> On Fri, Jul 25, 2014 at 6:02 AM, Vineet Gupta
> wrote:
>> > Hi Grant,
>> >
>> > linux-next has a series for arc_uart (via tty tree) which converts it to
>> > generic
>> > earlycon and specifies console via /chosen/stdout-path vs. an
On Fri, Jul 25, 2014 at 09:32:36PM +0300, Andrey Utkin wrote:
> Please ignore. I didn't notice that Hans has already posted a patch
> fixing that and more.
>
Heh. I was just about to send my fix for this bug as well.
I don't follow linux-media so I didn't realize this driver was getting
promote
On Fri, Jul 25, 2014 at 03:37:41PM +0530, Arjun AK wrote:
> >From 8e7748dd81cf63c62dbef8f102e97da1d4d5d90a Mon Sep 17 00:00:00 2001
> From: Arjun AK
> Date: Fri, 25 Jul 2014 15:09:11 +0530
> Subject: [PATCH] Staging: unisys: Fix code style
Why is all of this here in this message?
>
> Fixes code
On Fri, 25 Jul 2014 09:15:22 -0500, Rob Herring wrote:
> On Fri, Jul 25, 2014 at 6:02 AM, Vineet Gupta
> wrote:
> > Hi Grant,
> >
> > linux-next has a series for arc_uart (via tty tree) which converts it to
> > generic
> > earlycon and specifies console via /chosen/stdout-path vs. an explicit
Is there a time when this doesn't get called to prefetch entries in
readdir() order? It isn't clear to me what benefit there is of returning
the entries to userspace instead of just doing the statahead implicitly
in the kernel?
The Lustre client has had what we call "statahead" for a while,
and s
On Fri, Jul 25, 2014 at 9:42 PM, Steven Noonan wrote:
> On Thu, Jul 24, 2014 at 12:06 AM, Alexander Holler
> wrote:
>> Am 23.07.2014 19:50, schrieb Steven Noonan:
>>
>>> (Oops, LKML doesn't like rich text, resending. Was trying to avoid
>>> GMail's bad line wrapping. Going to use Mutt instead.)
On Thu, Jul 24, 2014 at 12:06 AM, Alexander Holler wrote:
> Am 23.07.2014 19:50, schrieb Steven Noonan:
>
>> (Oops, LKML doesn't like rich text, resending. Was trying to avoid
>> GMail's bad line wrapping. Going to use Mutt instead.)
>>
>> I'm starting to wonder if it's bad RAM or something. Just
In commit 4a0e637738f0 ("clocksource: Get rid of cycle_last"),
currently in the -tip tree, there was a small typo where cycles_t
was used intstead of cycle_t. This broke ppc64 builds.
Fix this by using the proper cycle_t type for this usage, in
both the definition and the ia64 implementation.
Now
If the worker task is not idle, it may sleep on some conditions by the request
of the work. Our unfriendly wakeup in the insert_kthread_work() may confuse
the worker.
Signed-off-by: Lai Jiangshan
---
kernel/kthread.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/kern
When an object or a subsystem quits, we need to destroy the kthread_work
which is used by the object or the subsystem. We used to use
flush_kthread_work(). But flush_kthread_work() has not any guarantee
about the suspension of the work, this duty is pushed to the users.
So we introduce the cance
The wait_queue_head_t done was totally unused since the flush_kthread_work()
had been re-implemented. So we removed it including the initialization
code. Some LOCKDEP code also depends on this wait_queue_head, so the
LOCKDEP code is also cleanup.
Signed-off-by: Lai Jiangshan
---
include/linux/
On Fri, Jul 25, 2014 at 11:25:17PM -0400, Benjamin Tissoires wrote:
> On Jul 25 2014 or thereabouts, Dmitry Torokhov wrote:
> > Hi Benjamin,
> >
> > On Thu, Jul 24, 2014 at 02:14:01PM -0400, Benjamin Tissoires wrote:
> > > Now that wacom is a hid driver, there is no point in having a separate
> >
On Fri, Jul 25, 2014 at 11:21:27PM -0400, Benjamin Tissoires wrote:
> On Jul 25 2014 or thereabouts, Dmitry Torokhov wrote:
> > Hi Benjamin,
> >
> > On Thu, Jul 24, 2014 at 02:13:55PM -0400, Benjamin Tissoires wrote:
> > > Hi Dmitry,
> > >
> > > this is the second series I told you about for waco
On Jul 25 2014 or thereabouts, Dmitry Torokhov wrote:
> Hi Benjamin,
>
> On Thu, Jul 24, 2014 at 02:14:01PM -0400, Benjamin Tissoires wrote:
> > Now that wacom is a hid driver, there is no point in having a separate
> > driver for bluetooth devices.
> > This patch prepares the common paths of Blue
On Jul 25 2014 or thereabouts, Dmitry Torokhov wrote:
> Hi Benjamin,
>
> On Thu, Jul 24, 2014 at 02:13:55PM -0400, Benjamin Tissoires wrote:
> > Hi Dmitry,
> >
> > this is the second series I told you about for wacom.ko. This series also
> > have
> > a good number of removed lines of code. \o/
>
W
3.16.0-rc6-next-20140725-sasha-00048-ga713fc0-dirty #937
[ 31.330473] task: 8805f9c4 ti: 88030bcd4000 task.ti:
88030bcd4000
[ 31.330473] RIP: assoc_array_insert (lib/assoc_array.c:480
lib/assoc_array.c:1021)
[ 31.330473] RSP: :88030bcd7bc8 EFLAGS: 000
The name of may_start_working() became misleading due to the semantics of
"!pool->nr_idle" is changed and any worker can start working in spite of
the value of pool->nr_idle.
So we remove the may_start_working() and use "!pool->nr_idle" directly,
need_to_create_worker() is also removed along with
There is an undocumented requirement for create_worker() that it can
only be called from existing worker (aka. manager) except the first call.
The reason is that the current create_worker() queues the new worker to
idle_list at first and then wake up it. But the new worker is not
guaranteed to be
There are some problems with the managers:
1) The last idle worker prefer managing to processing.
It is better that the processing of work items should be the first
priority to make the whole system make progress earlier.
2) managers among different pools can be parallel, but actually
Current kworker prefer creating worker (if required) to processing work items,
we hope the processing should be the first priority.
The jobs in managers are serialized, it is just wasting if we have multiple
managers, only one worker-creater is enough.
It causes much complication and tricky when
Hi all,
The series is a draft of generic MSI driver that supports PCI
and Non-PCI device which have MSI capability. If you're not interested
it, sorry for the noise.
The series is based on Linux-3.16-rc1.
MSI was introduced in PCI Spec 2.2. Currently, kernel MSI
driver codes are bonding
Save MSI irq in PCI MSI layer, this is preparation
for generic MSI.
Signed-off-by: Yijing Wang
---
drivers/pci/msi.c |5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/pci/msi.c b/drivers/pci/msi.c
index 21b16e0..f96dd38 100644
--- a/drivers/pci/msi.c
+++ b/driv
Add new MSI type marco(MSI_TYPE and MSIX_TYPE) to support
the future generic MSI driver. The coming generic MSI driver
will be used by PCI and Non-PCI devices that have MSI capability.
Signed-off-by: Yijing Wang
---
arch/mips/pci/msi-octeon.c |4 ++--
arch/powerpc/kernel/msi.c
Because some Non-PCI devices don't need to create sysfs object,
so move populate_msi_sysfs() out of generic MSI function
msi/x_capability_init().
Signed-off-by: Yijing Wang
---
drivers/pci/msi.c | 31 ++-
1 files changed, 18 insertions(+), 13 deletions(-)
diff --gi
Move MSIX table address mapping work to PCI MSIX layer.
Some Non-PCI MSI device will do their address mapping work before
enable MSIX capability or their MSIX table address is within
device address block. So Move address mapping stuff out of the
generic MSIX core. This is prepartion for generic MSI
Pci_dev_msi_enabled() is used to check whether device
MSI/MSIX enabled. Refactor this function to suuport
checking only device MSI or MSIX enabled.
Signed-off-by: Yijing Wang
---
arch/cris/arch-v32/drivers/pci/bios.c |2 +-
arch/frv/mb93090-mb00/pci-vdk.c |2 +-
arch/ia64/
Signed-off-by: Yijing Wang
---
arch/x86/include/asm/io_apic.h |2 +-
arch/x86/include/asm/irq_remapping.h |4 +-
arch/x86/include/asm/pci.h |6 ++--
arch/x86/include/asm/x86_init.h | 10 +++---
arch/x86/kernel/apic/io_apic.c | 23 +++
arch/x8
Currently, MSI driver is bonding with PCI everywhere.
Now introduce a new struct msi_irqs to manage all MSI
related informations in a MSI support device. In addition,
we introduce struct msi_ops to hook all device specific
MSI operations. Then MSI driver can be decoupled with
PCI.
Signed-off-by: Y
MSI interrupt will not only used in PCI device, more
and more Non-PCI device also want to use MSI. ARM
GIC v3 spec says in ARM platform with GIC v3 controller,
Non-PCI device can also be design to support MSI to
simplify interrupt wires, for the existing Non-PCI
device, consolidator is designed and
Use struct msi_ops to hook PCI MSI operations,
and use struct msi_irqs to refactor PCI MSI drvier.
Signed-off-by: Yijing Wang
---
drivers/pci/msi.c | 351 ++-
include/linux/msi.h | 14 +-
include/linux/pci.h | 11 +-
3 files changed, 222 ins
Save the MSI-X entry initial mask status in
msix_setup_entries(), also mask the entry.
This is preparation for generic MSI.
Signed-off-by: Yijing Wang
---
drivers/pci/msi.c | 21 +++--
1 files changed, 11 insertions(+), 10 deletions(-)
diff --git a/drivers/pci/msi.c b/drivers/
PCI devices save the msi and msix capability offset in pci_dev->msi_cap
and pci_dev->msix_cap. When we access PCI device MSI and MSIX
registers, we can use msi_cap and msix_cap in pci_dev directly.
Remove the pos member in msi_attrib.
Signed-off-by: Yijing Wang
---
arch/mips/pci/msi-octeon.c
CPU: 17 PID: 9306 Comm: trinity-main Not tainted
3.16.0-rc6-next-20140725-sasha-00048-ga713fc0-dirty #937
[ 488.098736] 00fb ea0017d0c380
8805f444b740
[ 488.099933] b6dc96f3 8805f444b810 8805f444b800
b242d17c
[ 488.100020] 880be21
On Fri, Jul 25, 2014 at 08:10:57PM -0400, Pranith Kumar wrote:
> On 07/25/2014 07:36 PM, Paul E. McKenney wrote:
> > [ Note: This applies on top of commit 187497fa5e9e (rcu: Allow for NULL
> > tick_nohz_full_mask when nohz_full= missing) in -tip
> > or -rcu. To make this work on top of rcu
. I'm seeing
the following:
[ 490.446927] BUG: using __this_cpu_read() in preemptible [] code:
kworker/16:1/7368
[ 490.447909] caller is __this_cpu_preempt_check+0x13/0x20
[ 490.448596] CPU: 8 PID: 7368 Comm: kworker/16:1 Not tainted
3.16.0-rc6-next-20140725-sasha-00047-g9eb9a52 #933
[
On 07/17/2014 08:25 AM, Ivan T. Ivanov wrote:
> From: "Ivan T. Ivanov"
>
> This is the pinctrl, pinmux, pinconf and gpiolib driver for the
> Qualcomm GPIO and MPP sub-function blocks found in the PMIC chips.
> QPNP_REG_STATUS1_GPIO_EN_REV0_MASK
> Signed-off-by: Ivan T. Ivanov
(...)
> +static in
Hi Benjamin,
On Thu, Jul 24, 2014 at 02:13:55PM -0400, Benjamin Tissoires wrote:
> Hi Dmitry,
>
> this is the second series I told you about for wacom.ko. This series also have
> a good number of removed lines of code. \o/
>
> The first patch is Jason's one that I finally decided to take with me
Hey Guys,
After building my first rc kernel. I am sad to state it doesn't
boot.It states that it can't find my root uuid for my ssd boot drive.
I am using GSP with UEFI, on a Sandy Bridge i5 2500k build I have had
for a few years. The kernel boots and after a few seconds
drops to a busybox ash she
The first userspace attempt to read or write the PER_CPU segment
will write the accessed bit to the GDT. This is visible to
userspace using the LAR instruction.
Set the segment's accessed bit at boot to keep all userspace GDT
access idempotent.
Signed-off-by: Andy Lutomirski
---
arch/x86/kerne
This makes it easier to see what's going on. It produces exactly
the same segment descriptor as the old code.
Signed-off-by: Andy Lutomirski
---
arch/x86/kernel/vsyscall_64.c | 18 +++---
1 file changed, 11 insertions(+), 7 deletions(-)
diff --git a/arch/x86/kernel/vsyscall_64.c b/
IMO users ought not to be able to use 16-bit segments without using
modify_ldt. Fortunately, it's impossible to break espfix64 by
loading the PER_CPU segment into SS because it's a read-only
segment, but marking it 32-bit seems less fragile.
Signed-off-by: Andy Lutomirski
---
arch/x86/kernel/vs
x86 sets up a per-cpu GDT entry so that vgetcpu can use LSL on it
to determine the CPU number and node.
This series, in little baby steps, cleans up that code and sets
the accessed and 32-bit flags on the segment.
The accessed bit prevents user code from setting the accessed bit
on its own, and m
Hi Linus,
please pull blackfin fixes for v3.16, smc nor flash PM fix, pinctrl group fix,
update defconfig, and build fixes.
The following changes since commit 9a3c4145af32125c5ee39c0272662b47307a8323:
Linux 3.16-rc6 (2014-07-20 21:04:16 -0700)
are available in the git repository at:
http:
On Fri, Jul 25, 2014 at 08:10:57PM -0400, Pranith Kumar wrote:
> On 07/25/2014 07:36 PM, Paul E. McKenney wrote:
> > [ Note: This applies on top of commit 187497fa5e9e (rcu: Allow for NULL
> > tick_nohz_full_mask when nohz_full= missing) in -tip
> > or -rcu. To make this work on top of rcu
Hi Benjamin,
On Thu, Jul 24, 2014 at 02:14:01PM -0400, Benjamin Tissoires wrote:
> Now that wacom is a hid driver, there is no point in having a separate
> driver for bluetooth devices.
> This patch prepares the common paths of Bluetooth devices in the
> common wacom driver.
> It also adds the sys
On Fri, Jul 25, 2014 at 10:52:57AM -0700, Zach Brown wrote:
> On Fri, Jul 25, 2014 at 01:37:19PM -0400, Abhijith Das wrote:
> > Hi all,
> >
> > The topic of a readdirplus-like syscall had come up for discussion at last
> > year's
> > LSF/MM collab summit. I wrote a couple of syscalls with their G
On Sat, 2014-07-26 at 01:24 +0200, Hannes Frederic Sowa wrote:
> On Fri, Jul 25, 2014, at 18:38, Jun Zhao wrote:
> > ndm_type means L3 address type, in neighbour proxy and vxlan, it's
> > RTN_UNICAST.
> > NDA_DST is for netlink TLV type, hence it's not right value in this
> > context.
>
> The valu
Semi-MT devices are pointers too, so let's tell that to
input_mt_init_slots(), as well as let it set up the devices as semi-MT,
instead of us doing it manually.
Reviewed-by: Daniel Kurtz
Reviewed-by: Benson Leung
Signed-off-by: Dmitry Torokhov
---
drivers/input/mouse/synaptics.c | 6 +++---
1
-next (2014-07-22 21:55:45 +0100)
>
> are available in the git repository at:
>
>
> git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
> tags/keys-next-20140725
>
> for you to fetch changes up to 8f3438ccea149647ad1849651d1e14c7b8b85e63:
>
> PKCS
On 07/25/2014 07:36 PM, Paul E. McKenney wrote:
> [ Note: This applies on top of commit 187497fa5e9e (rcu: Allow for NULL
> tick_nohz_full_mask when nohz_full= missing) in -tip
> or -rcu. To make this work on top of rcu/next, move the
> call to rcu_organize_nocb_kthreads(rsp) to the en
From: Randy Dunlap
Fixes: d90c3eb31535 "Kconfig cleanup (PARPORT_PC dependencies)"
Do not split the PARPORT-related symbols with the new kconfig
symbol ARCH_MIGHT_HAVE_PC_PARPORT. The split was causing incorrect
display of these symbols -- they were not being displayed together
as they should be
On Fri, 25 Jul 2014 18:57:33 -0400, Nick Krause said:
> Hey guys after compiling and running the kernel in the subject line I
> get no sound
> and a message of no sound codec could be found. I am new so this may be
> a missed needed config for sound or it's a bug. I am attaching my config
> to he
On Fri, Jul 25, 2014 at 4:43 PM, H. Peter Anvin wrote:
> On 07/25/2014 11:30 AM, Andy Lutomirski wrote:
>> - 32-bit GDT code segments [huge attack surface]
>> - 64-bit GDT code segments [probably pointless]
>
> I presume you mean s/GDT/LDT/.
>
> We already don't allow 64-bit LDT code segme
On 07/25/2014 11:30 AM, Andy Lutomirski wrote:
> - 32-bit GDT code segments [huge attack surface]
> - 64-bit GDT code segments [probably pointless]
I presume you mean s/GDT/LDT/.
We already don't allow 64-bit LDT code segments. Also, it is unclear to
me how 32-bit LDT segments have a hug
Commit-ID: 53b884ac3745353de220d92ef792515c3ae692f0
Gitweb: http://git.kernel.org/tip/53b884ac3745353de220d92ef792515c3ae692f0
Author: Andy Lutomirski
AuthorDate: Fri, 25 Jul 2014 16:30:27 -0700
Committer: H. Peter Anvin
CommitDate: Fri, 25 Jul 2014 16:34:15 -0700
x86_64/vsyscall: Fix
Commit-ID: ac379835e820de27429b5c4eadf4c1b40320cff4
Gitweb: http://git.kernel.org/tip/ac379835e820de27429b5c4eadf4c1b40320cff4
Author: Andy Lutomirski
AuthorDate: Fri, 25 Jul 2014 16:27:01 -0700
Committer: H. Peter Anvin
CommitDate: Fri, 25 Jul 2014 16:32:53 -0700
x86/vdso: Set VM_MAYR
[ Note: This applies on top of commit 187497fa5e9e (rcu: Allow for NULL
tick_nohz_full_mask when nohz_full= missing) in -tip
or -rcu. To make this work on top of rcu/next, move the
call to rcu_organize_nocb_kthreads(rsp) to the end of the
for_each_rcu_flavor(rsp) lo
This commit in Linux 3.6:
commit c767a54ba0657e52e6edaa97cbe0b0a8bf1c1655
Author: Joe Perches
Date: Mon May 21 19:50:07 2012 -0700
x86/debug: Add KERN_ to bare printks, convert printks to
pr_
caused warn_bad_vsyscall to output garbage in the middle of the
line. Revert th
+pr_info("Total:%lu, unnecessary:%lu, case1:%lu, case2:%lu,
case3:%lu\n",
+total_wakeups, unnecessary_wakeups, case1, case2, case3);
+
+}
wake_up(&rsp->gp_wq); /* Memory barrier implied by wake_up() path. */
}
--
2.0.1
[0.000000] Initializing
On Fri, Jul 25, 2014 at 4:27 PM, Andy Lutomirski wrote:
> AFAIK this has no effect whatsoever unless x86 suddenly turns into a
> nommu architecture. Nonetheless, not setting it is suspicious.
Sorry, forgot to mention: this is based on tip/x86/vdso.
--Andy
>
> Reported-by: Nathan Lynch
> Signe
AFAIK this has no effect whatsoever unless x86 suddenly turns into a
nommu architecture. Nonetheless, not setting it is suspicious.
Reported-by: Nathan Lynch
Signed-off-by: Andy Lutomirski
---
arch/x86/vdso/vma.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/vdso
On Fri, Jul 25, 2014, at 18:38, Jun Zhao wrote:
> ndm_type means L3 address type, in neighbour proxy and vxlan, it's
> RTN_UNICAST.
> NDA_DST is for netlink TLV type, hence it's not right value in this
> context.
The value of NDA_DST == RTN_UNICAST, otherwise we couldn't do this
change as it would
On 07/25/2014 07:19 PM, Paul E. McKenney wrote:
> On Thu, Jul 24, 2014 at 07:28:35PM -0400, Sasha Levin wrote:
>> > On 07/24/2014 06:54 PM, Paul E. McKenney wrote:
>>> > > On Thu, Jul 24, 2014 at 06:19:11PM -0400, Sasha Levin wrote:
> >> Hi all,
> >>
> >> While fuzzing with trinity i
On Fri, Jul 25, 2014 at 7:19 PM, wrote:
> On Fri, 25 Jul 2014 18:57:33 -0400, Nick Krause said:
>
>> Hey guys after compiling and running the kernel in the subject line I
>> get no sound
>> and a message of no sound codec could be found. I am new so this may be
>> a missed needed config for soun
On Fri, Jul 25, 2014 at 9:38 AM, Jun Zhao wrote:
> ndm_type means L3 address type, in neighbour proxy and vxlan, it's
> RTN_UNICAST.
> NDA_DST is for netlink TLV type, hence it's not right value in this context.
>
Looks correct to me, at least libnl uses RTN_* for ndm_type.
--
To unsubscribe fro
Bluetooth Intuos 4 use 1-bit definition while the USB ones use a 4-bits
definition. This changes the size of the raw image we receive, and thus
the kernel will only accept 1-bit images for Bluetooth and 4-bits for
USB.
Signed-off-by: Benjamin Tissoires
---
drivers/hid/wacom_sys.c | 15 +-
Hi Guillaume
On 25/07/14 13:47, Guillaume Clement wrote:
Sparse reported that the data from tagSCmdRequest is given by
userspace, so it should be tagged as such.
extra is not in user space
All Wireless Extensions ioctl extra calls originate from
ioctl_standard_iw_point in wext-core.
Either
On Fri, Jul 25, 2014 at 06:23:41PM -0400, Pranith Kumar wrote:
> On Fri, Jul 25, 2014 at 11:02 AM, Paul E. McKenney
> wrote:
> > On Fri, Jul 25, 2014 at 02:24:34AM -0400, Pranith Kumar wrote:
> >> On Fri, Jul 25, 2014 at 1:06 AM, Pranith Kumar
> >> wrote:
> >>
> >> >
> >> > In rcu_report_qs_rsp(
On Thu, May 29, 2014 at 4:14 AM, Rafael J. Wysocki wrote:
> On Thursday, May 29, 2014 10:41:43 AM Zdenek Kabelac wrote:
>> Hi
>>
>>
>> I've noticed this message in my dmesg:
>> (Possibly related to this commit?:
>> a8d22396302b7e4e5f0a594c1c1594388c29edaf)
>
> Well, does reverting that commit make
Hi Przemo,
On Jul 25 2014 or thereabouts, Przemo Firszt wrote:
> Dnia 2014-07-24, czw o godzinie 14:13 -0400, Benjamin Tissoires pisze:
> [..]
> Hi Benjamin,
> I'm testing the whole series including the OLED patch that's not on the
> list yet.
>
> Hardware: 2 x Intuos4 Wireless tested on usb and
Hi Guillaume
On 25/07/14 13:47, Guillaume Clement wrote:
Sparse reported that the data from tagSCmdRequest is given by
userspace, so it should be tagged as such.
extra is not in user space
All Wireless Extensions ioctl extra calls originate from
ioctl_standard_iw_point in wext-core.
Either
On Fri, Jul 25, 2014 at 1:36 AM, pramod gurav
wrote:
> Viresh,
> Be careful when you ACK Nick's patches. He has confessed he has no
> idea how to build test a kernel. His patches are NOT AT ALL build
> tested. And some of his patches are being reverted for causing
> problems in build and all. He l
Hey guys after compiling and running the kernel in the subject line I
get no sound
and a message of no sound codec could be found. I am new so this may be
a missed needed config for sound or it's a bug. I am attaching my config
to help you guys out :).
Nick
config
Description: Binary data
This patch fixes the wrongly used unlikely condition.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/checkpoint.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/f2fs/checkpoint.c b/fs/f2fs/checkpoint.c
index 42a16c1..36b0d47 100644
--- a/fs/f2fs/checkpoint.c
+++ b/fs/f2fs/checkpo
This patch eliminates the propagation of recovery errors to the next mount.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/checkpoint.c | 3 ++-
fs/f2fs/f2fs.h | 2 +-
fs/f2fs/recovery.c | 20 +++-
fs/f2fs/segment.c| 5 +
4 files changed, 23 insertions(+), 7 deletions(
This patch enforces in-place-updates only when fdatasync is requested.
If we adopt this in-place-updates for the fdatasync, we can skip to write the
recovery information.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/f2fs.h| 1 +
fs/f2fs/file.c| 7 +++
fs/f2fs/segment.h | 4
3 files ch
No need to do checkpoint, whenever any errors were detected.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/recovery.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/fs/f2fs/recovery.c b/fs/f2fs/recovery.c
index a112368..90d7e80 100644
--- a/fs/f2fs/recovery.c
+++ b/fs/f2fs/reco
If the bit is already set, we don't need to reset it, and vice versa.
Because we don't need to make the caches dirty for that.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/f2fs.h | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h
index 8f8685e..47
This patch intends to improve the fsync performance by skipping remaining the
recovery information, only when there is no data that we should recover.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/file.c | 16
1 file changed, 16 insertions(+)
diff --git a/fs/f2fs/file.c b/fs/f2fs/file
For better ino management, this patch replaces the data structure from list
to radix tree.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/checkpoint.c | 48 ++--
fs/f2fs/f2fs.h | 1 +
2 files changed, 27 insertions(+), 22 deletions(-)
diff --git a/fs/f
This patch introduces a inode number list in which represents inodes having
appended data writes or updated data writes after last checkpoint.
This will be used at fsync to determine whether the recovery information
should be written or not.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/checkpoint.c |
On Saturday, July 26, 2014 12:25:29 AM Rafael J. Wysocki wrote:
> On Friday, July 25, 2014 11:00:12 PM Thomas Gleixner wrote:
> > On Fri, 25 Jul 2014, Rafael J. Wysocki wrote:
> > > On Friday, July 25, 2014 03:25:41 PM Peter Zijlstra wrote:
> > > > OK, so Rafael said there's devices that keep on ra
This patch changes the naming of orphan-related data structures to use as
inode numbers managed globally.
Later, we can use this facility for managing any inode number lists.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/checkpoint.c | 72 +++-
fs/f2fs/de
On Fri, Jul 25, 2014 at 04:19:43PM -0400, Pranith Kumar wrote:
> On Fri, Jul 25, 2014 at 10:44 AM, Paul E. McKenney
> wrote:
> > On Fri, Jul 25, 2014 at 01:06:58AM -0400, Pranith Kumar wrote:
> >> The rcu_gp_kthread_wake() function checks for three conditions before
> >> waking up
> >> grace peri
This patch punches out the core functions to manage the inode numbers.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/checkpoint.c | 81
1 file changed, 44 insertions(+), 37 deletions(-)
diff --git a/fs/f2fs/checkpoint.c b/fs/f2fs/checkpoint.c
index
This patch adds a mount option, nobarrier, in f2fs.
The assumption in here is that file system keeps the IO ordering, but
doesn't care about cache flushes inside the storages.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/data.c| 5 -
fs/f2fs/f2fs.h| 1 +
fs/f2fs/segment.c | 3 +++
fs/f2fs/
There is a lack of usb_put_dev(udev) on failure path in gigaset_probe().
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
drivers/isdn/gigaset/bas-gigaset.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/isdn/gigaset/bas-gigaset.c
Quoting Javier Martinez Canillas (2014-07-14 04:35:56)
> This series are based on drivers added by Simon Glass to the Chrome OS
> kernel and adds support for the Maxim 77802 Power Management IC, their
> regulators, clocks, RTC and i2c interface.
>
> This is a v8 of the patch-set that addresses iss
On Fri, Jul 25, 2014 at 11:02 AM, Paul E. McKenney
wrote:
> On Fri, Jul 25, 2014 at 02:24:34AM -0400, Pranith Kumar wrote:
>> On Fri, Jul 25, 2014 at 1:06 AM, Pranith Kumar wrote:
>>
>> >
>> > In rcu_report_qs_rsp(), I added a pr_info() call testing if any of the
>> > above
>> > conditions is tr
On Fri, Jul 25, 2014 at 02:50:32PM -0400, Willem de Bruijn wrote:
> On Fri, Jul 25, 2014 at 2:43 PM, Alexei Starovoitov wrote:
> > On Fri, Jul 25, 2014 at 11:32 AM, Willem de Bruijn
> > wrote:
> This follows a convention in include/uapi/linux/netfilter/*.h that
> likely predates the in
rng_get_data() returns the number of bytes read from the hardware.
The entropy argument to add_hwgenerator_randomness() is passed
directly to credit_entropy_bits() so we should be passing the
number of bits, not bytes here.
Fixes: be4000bc464 "hwrng: create filler thread"
Cc: Torsten Duwe
Signed-
On Fri, Jul 25, 2014 at 10:24:29AM -0700, Alexei Starovoitov wrote:
> On Fri, Jul 25, 2014 at 6:00 AM, Daniel Borkmann wrote:
> > On 07/25/2014 01:54 PM, Pablo Neira Ayuso wrote:
> >>
> >> On Fri, Jul 25, 2014 at 01:25:35PM +0200, Daniel Borkmann wrote:
> >>>
> >>> [ also Cc'ing Willem, Pablo ]
>
On Fr, 2014-07-25 at 19:23 +0400, Andrey Ryabinin wrote:
> On 07/14/14 01:50, Sasha Levin wrote:
>
> >
> > I've tried debugging it, but I don't see a code path that could lead to
> > that.
> >
>
> I finally found some time to take look at this and I've found where the
> problem is.
>
> Sasha
On Fr, 2014-07-25 at 16:52 -0400, Sasha Levin wrote:
> On 07/25/2014 11:23 AM, Andrey Ryabinin wrote:
> > After this report there was no usual "Unable to handle kernel NULL pointer
> > dereference"
> > and this gave me a clue that address 0 is mapped and contains valid socket
> > address structur
Dnia 2014-07-24, czw o godzinie 14:13 -0400, Benjamin Tissoires pisze:
[..]
Hi Benjamin,
I'm testing the whole series including the OLED patch that's not on the
list yet.
Hardware: 2 x Intuos4 Wireless tested on usb and bluetooth until noted
otherwise.
What works:
1. Tablet in general, pressure,
On Friday, July 25, 2014 11:00:12 PM Thomas Gleixner wrote:
> On Fri, 25 Jul 2014, Rafael J. Wysocki wrote:
> > On Friday, July 25, 2014 03:25:41 PM Peter Zijlstra wrote:
> > > OK, so Rafael said there's devices that keep on raising their interrupt
> > > until they get attention. Ideally this won't
I'm seeing the following build error on arm64:
In file included from util/event.c:3:0:
util/event.h:95:17: error: 'PERF_REGS_MAX' undeclared here (not in a function)
u64 cache_regs[PERF_REGS_MAX];
^
This patch adds a PERF_REGS_MAX definition for arm64.
Signed-off-by: Mar
On Fri, Jul 25, 2014 at 02:42:13PM -0700, Jesse Barnes wrote:
> On Fri, 25 Jul 2014 23:38:06 +0200
> Joerg Roedel wrote:
> > I though about removing the need for invalidate_range_end too when
> > writing the patches, and possible solutions are
> >
> > 1) Add mmu_notifier_invalidate_range() to
Em Fri, 25 Jul 2014 07:25:05 +0200
David Härdeman escreveu:
> Mauro,
>
> On July 25, 2014 4:23:17 AM CEST, Stephen Rothwell
> wrote:
> >Hi Mauro,
> >
> >After merging the v4l-dvb tree, today's linux-next build (x86_64
> >allmodconfig)
> >failed like this:
> >
> >drivers/hid/hid-picolcd_cir.c:
1 - 100 of 720 matches
Mail list logo
