Fix spelling typo in DocBook/drm.tmpl
Signed-off-by: Masanari Iida
---
Documentation/DocBook/drm.tmpl | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/Documentation/DocBook/drm.tmpl b/Documentation/DocBook/drm.tmpl
index 702c4474..bdb932f 100644
--- a/Documentatio
#cat gdb.base/interrupt.c
#include
#include
#include
#include
#ifdef SIGNALS
#include
static void
sigint_handler (int signo)
{
}
#endif
int
main ()
{
char x;
int nbytes;
#ifdef SIGNALS
signal (SIGINT, sigint_handler);
#endif
printf ("talk to me baby\n");
while (1)
{
nbyt
On Mon, Apr 21, 2014 at 09:48:16AM -0400, Christopher Covington wrote:
> In that thread, Olof wrote, "The code [going into drivers/soc] isn't the pure
> drivers. Those we find homes for."
Right. I see this as glue for the most part. You could argue it's a small
pinctrl, but this doesn't route
This is a prototype of a real fix for a longstanding issue. See patch 2
for the full descripton.
Andy Lutomirski (2):
fs,proc: Pass nameidata to proc_get_link implementations
fs,proc: Respect FMODE_WRITE when opening /proc/pid/fd/N
fs/namei.c| 3 +++
fs/proc/base.c| 13
This patch does this:
# (echo asdf >/proc/self/fd/3) 3flags is correct. I'm also not
confident that this hooks in to path lookup in the right place.
It is not complete. It doesn't handle FMODE_READ. It also doesn't
handle FMODE_EXEC or FMODE_PATH, but the desired semantics there are
less c
proc_fd_link should respect fs modes, and it needs to know the open
mode to do so.
Signed-off-by: Andy Lutomirski
---
fs/proc/base.c | 13 -
fs/proc/fd.c | 3 ++-
fs/proc/internal.h | 3 ++-
3 files changed, 12 insertions(+), 7 deletions(-)
diff --git a/fs/proc/base.c b/
On 04/21/2014 09:17 AM, Masanari Iida wrote:
> Fix spelling typo in DocBook/drm.tmpl
>
> Signed-off-by: Masanari Iida
Applied. Thanks.
> ---
> Documentation/DocBook/drm.tmpl | 12 ++--
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/Documentation/DocBook/drm.tmpl b
This feature allows multiple channels to be used by each virtual NIC.
It is available on Hyper-V host 2012 R2.
Signed-off-by: Haiyang Zhang
Reviewed-by: K. Y. Srinivasan
---
drivers/net/hyperv/hyperv_net.h | 110 +-
drivers/net/hyperv/netvsc.c | 136 +++
On Mon, Apr 21, 2014 at 09:22:47AM -0700, Andy Lutomirski wrote:
> proc_fd_link should respect fs modes, and it needs to know the open
> mode to do so.
So pass it by value. NAK in that form.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to maj
On Sun, 20 Apr 2014, Vladimir Davydov wrote:
> * Way #1 - prevent dead kmem caches from caching slabs on free *
>
> We can modify sl[au]b implementation so that it won't cache any objects
> on free if the kmem cache belongs to a dead memcg. Then it'd be enough
> to drain per-cpu pools of all dead
On Mon, Apr 21, 2014 at 09:22:48AM -0700, Andy Lutomirski wrote:
> +static int proc_may_follow(struct nameidata *nd, struct file *f)
> +{
> + if (!nd)
> + return 0; /* This is readlink, */
> +
> + if ((nd->flags & LOOKUP_WRITE) && !(f->f_mode & FMODE_WRITE))
> + re
On 04/21/2014 09:19 AM, Hui Zhu wrote:
> }
> Now ax is in 32 bits now, need sign-extend to 64 bits. But
> current_thread_info()->status TS_COMPAT is cleared when GDB call "call
> func1()".
> Linux kernel don't know this is a 32 bits task and will not extend it.
> Then -ERESTARTSYS is not be handl
On Wed, Apr 16, 2014 at 02:04:22PM -0400, Dave Jones wrote:
> On Tue, Apr 15, 2014 at 04:57:49PM +0200, Miklos Szeredi wrote:
>
> > Some callers (aio_run_iocb, vmsplice_to_user) forget to free the iov on
> > error. This seems to be a recurring problem, with most callers being
> buggy
>
From: Colin Ian King
static code analysis from cppcheck reports:
[drivers/net/wireless/rtlwifi/rtl8188ee/trx.c:322]:
(error) Uninitialized variable: packet_beacon
packet_beacon is not initialized and hence packet_beacon
contains garbage from the stack, so set it to false.
Signed-off-by: Coli
On Mon, 21 Apr 2014, Felipe Balbi wrote:
> Hi,
>
> On Fri, Apr 18, 2014 at 07:34:08PM +0530, sundeep subbaraya wrote:
>
>
>
> > >> in ep_queue driver starts dma transfer from/to IP buffer to/from
> > >> req->buf.
> > >> If transfer is completed then request is not added to ep request queue
>
The two functions to write out to the console (one used in normal
console mode and one in polling console mode) were slightly different.
One used a barrier() in its loop and the other a cpu_relax(). The
barrier() really doesn't do anything since we're using rd_regl() to
read the port anyway. Swit
The s3c24xx_serial_console_putchar() is _only_ ever used by
s3c24xx_serial_console_write() and is called in a loop (indirectly
through uart_console_write()). There's no reason to call
s3c24xx_port_configured() for every iteration through the loop. Move
it outside the loop.
Signed-off-by: Doug An
The two functions in the samsung serial driver used for writing
characters out to the port were inconsistent about whether they used
the passed in "port" or the global "cons_uart". There was no reason
to use the global and the use of the global in
s3c24xx_serial_put_poll_char() caused a crash in t
On 04/20/2014 05:03 PM, Randy Dunlap wrote:
> From: Randy Dunlap
>
> Fix new kernel-doc warnings in fs/bio.c:
>
> Warning(fs/bio.c:316): No description found for parameter 'bio'
> Warning(fs/bio.c:316): No description found for parameter 'parent'
Thanks Randy, applied.
--
Jens Axboe
--
To un
On Fri, Mar 28, 2014 at 7:31 PM, Sebastian Reichel wrote:
> Create device tree binding documentation for
> OMAP Synchronous Serial Interface (SSI) device.
>
> Signed-off-by: Sebastian Reichel
> ---
> Documentation/devicetree/bindings/hsi/omap-ssi.txt | 85
> ++
> 1 file chan
On Mon, 21 Apr 2014 12:10:04 -0400
Rich Felker wrote:
> On Mon, Apr 21, 2014 at 04:23:54PM +0200, Michael Kerrisk (man-pages) wrote:
> > On 04/21/2014 04:02 PM, Rich Felker wrote:
> > > On Mon, Apr 21, 2014 at 09:45:35AM -0400, Jeff Layton wrote:
> > >> File-private locks have been merged into Li
On Mon, 21 Apr 2014 09:09:27 -0700
Christoph Hellwig wrote:
> On Mon, Apr 21, 2014 at 04:23:54PM +0200, Michael Kerrisk (man-pages) wrote:
> >
> > There's at least two problems to solve here:
> >
> > 1) "File private locks" is _meaningless_ as a term. Elsewhere
> >
> > (http://thread.gmane.
On Mon, Apr 21, 2014 at 10:25:18AM +0530, Viresh Kumar wrote:
> > --- a/scripts/mod/modpost.c
> > +++ b/scripts/mod/modpost.c
> > @@ -1707,7 +1707,7 @@ static char *remove_dot(char *s)
> > int n = strcspn(s, ".");
> >
> > if (n > 0 && s[n] != 0) {
> > - strtoul(s + n +
Booting kernel 3.15-rc2 on an AOpen i915GMm-hfs, I see the framebuffer broken.
Only about the upper left quarter of the monitor is used for displaying the
boot messages,
these (and the cursor) are replicated at the right of that area.
Approximately the lower half of the monitor stays black. The o
On Fri, Mar 28, 2014 at 7:31 PM, Sebastian Reichel wrote:
> Implement and document generic DT bindings for HSI clients.
>
> Signed-off-by: Sebastian Reichel
Seems pretty reasonable although I know little about HSI.
> ---
> .../devicetree/bindings/hsi/client-devices.txt | 44 +
> drive
Hi x86/vdso people,
I've been working on adding a vDSO to 32-bit ARM, and Kees suggested I
look at x86_64's algorithm for placing the vDSO at a randomized offset
above the stack VMA. I found that when the stack top occupies the
last slot in the PTE (is that the right term?), the vdso_addr routine
Hi Myron,
On 04/20/2014 09:44 PM, Myron Stowe wrote:
On Sun, Apr 20, 2014 at 4:54 AM, Borislav Petkov wrote:
On Fri, Apr 18, 2014 at 08:53:46PM -0600, Myron Stowe wrote:
With the amd_bus.c updates to support additional AMD processors (11h, 12h,
14h 15h and 16h) 'quirk_amd_nb_node' seems to b
Hi Vinod, Dan,
On 04/14/2014 06:41 AM, Peter Ujfalusi wrote:
> Hi,
>
> Changes since v2:
> - Dropped patch 10 from v2 (simplify direction configuration...)
> - Dropped the channel priority related patches since we are going to go via
> different route for configuring the priority.
> - Added ACK
On Apr 21, 2014, at 12:30 AM, Andy Gross wrote:
> Add device tree binding support for the QCOM GSBI driver.
>
> Signed-off-by: Andy Gross
> ---
> .../devicetree/bindings/soc/qcom/qcom,gsbi.txt | 78
> 1 file changed, 78 insertions(+)
> create mode 100644 Documentation
On Mon, Apr 21, 2014 at 9:14 AM, Felipe Balbi wrote:
> Hi,
>
> On Fri, Apr 04, 2014 at 03:18:11PM -0700, Tim Bird wrote:
>> Select the secondary PHY using the TCSR register, if phy-num=1
>> in the DTS (or phy_number is set in the platform data). The
>> SOC has 2 PHYs which can be used with the OT
> On Mon, Apr 21, 2014 at 04:23:54PM +0200, Michael Kerrisk (man-pages)
> wrote:
> >
> > There's at least two problems to solve here:
> >
> > 1) "File private locks" is _meaningless_ as a term. Elsewhere
> >
> >
> (http://thread.gmane.org/gmane.network.samba.internals/76414/focus=16
> 8
> > 5376),
On Mon, Apr 21, 2014 at 10:00 AM, Andy Lutomirski wrote:
> On Mon, Apr 21, 2014 at 9:30 AM, Al Viro wrote:
>> On Mon, Apr 21, 2014 at 09:22:48AM -0700, Andy Lutomirski wrote:
>>
>>> +static int proc_may_follow(struct nameidata *nd, struct file *f)
>>> +{
>>> + if (!nd)
>>> + retur
On Mon, Apr 21, 2014 at 9:30 AM, Al Viro wrote:
> On Mon, Apr 21, 2014 at 09:22:48AM -0700, Andy Lutomirski wrote:
>
>> +static int proc_may_follow(struct nameidata *nd, struct file *f)
>> +{
>> + if (!nd)
>> + return 0; /* This is readlink, */
>> +
>> + if ((nd->flags & LOOKU
On Mon, Apr 21, 2014 at 12:30:42AM -0500, Andy Gross wrote:
> The GSBI (General Serial Bus Interface) driver controls the overarching
> configuration of the shared serial bus infrastructure on APQ8064, IPQ8064, and
> earlier QCOM processors. The GSBI supports UART, I2C, SPI, and UIM
> functionalit
In (efe2f29 kgdboc,kdb: Allow kdb to work on a non open console port)
support was added to directly use the "write_char" functions when
doing kdb over a non-open console port. This is great, but it ends up
bypassing the normal code in uart_console_write() that adds a carriage
return before any new
On Mon, Apr 21, 2014 at 10:03:28AM -0700, Tim Bird wrote:
> On Mon, Apr 21, 2014 at 9:14 AM, Felipe Balbi wrote:
> > Hi,
> >
> > On Fri, Apr 04, 2014 at 03:18:11PM -0700, Tim Bird wrote:
> >> Select the secondary PHY using the TCSR register, if phy-num=1
> >> in the DTS (or phy_number is set in th
On Mon, Apr 21, 2014 at 11:54:00AM -0500, Josh Cartwright wrote:
> > +
> > +struct gsbi_dev {
> > + struct device *dev;
> > + void __iomem*base;
>
> You don't really need these.
Old habits die hard. I'll remove.
> > + if (of_property_read_u32(node, "qcom,mode", &mode)) {
> > +
On 04/21/2014 11:38 AM, Colin King wrote:
From: Colin Ian King
static code analysis from cppcheck reports:
[drivers/net/wireless/rtlwifi/rtl8188ee/trx.c:322]:
(error) Uninitialized variable: packet_beacon
packet_beacon is not initialized and hence packet_beacon
contains garbage from the st
On Sun, Apr 20, 2014 at 4:12 AM, Geert Uytterhoeven
wrote:
>> +*/
>> + vma = find_vma(current->mm, addr);
>> + if (vma == NULL || addr < vma->vm_start || addr + len > vma->vm_end)
>> + return -EFAULT;
>> +
>> + /* Ignore the scope and cache arguments. */
>
>
On Mon, 2014-04-21 at 16:26 +0200, Manfred Spraul wrote:
> Hi all,
>
> the increase of SHMMAX/SHMALL is now a 4 patch series.
> I don't have ideas how to improve it further.
Manfred, is there any difference between this set and the one you sent a
couple of days ago?
>
> The change itself is tri
On Mon, Apr 21, 2014 at 12:11:18PM -0500, Andy Gross wrote:
> On Mon, Apr 21, 2014 at 11:54:00AM -0500, Josh Cartwright wrote:
> > > + if (of_property_read_u32(node, "qcom,mode", &mode)) {
> > > + dev_err(gsbi->dev, "missing mode configuration\n");
> > > + return -EINVAL;
> > > + }
On Sun, Apr 20, 2014 at 12:09 AM, Pavel Machek wrote:
>> +/* Additional Nios II specific syscalls. */
>> +#define __NR_cacheflush (__NR_arch_specific_syscall)
>> +__SYSCALL(__NR_cacheflush, sys_cacheflush)
>
> I guess you should Cc: Michael Kerrisk on this one.
CC him this email.
>
> Also... expl
From: Haiyang Zhang
Date: Mon, 21 Apr 2014 10:20:28 -0700
> This feature allows multiple channels to be used by each virtual NIC.
> It is available on Hyper-V host 2012 R2.
>
> Signed-off-by: Haiyang Zhang
> Reviewed-by: K. Y. Srinivasan
Applied, th anks.
--
To unsubscribe from this list: sen
Hi,
On Wed, Mar 26, 2014 at 07:04:45PM -0500, Felipe Balbi wrote:
> this series lets us access the newer registers introduced
> back in OMAP4 which give us some valid information about
> the OMAP HSMMC IP like max block size, support for ADMA,
> support for Retention.
>
> Right now, only setting
Fix "Should be static" sparse warning:
* Add Check_D_MediaFmt() declaration to smil.h;
* Move Check_D_MediaFmt() implementation up in smilmain.c to keep
all the non-static functions at the top of the file;
* Include "init.h" into "smil.h", remove externs from "smil.h"
which are no longer needed
On Mon, Apr 21, 2014 at 10:04 AM, Andy Lutomirski wrote:
> On Mon, Apr 21, 2014 at 10:00 AM, Andy Lutomirski wrote:
>> On Mon, Apr 21, 2014 at 9:30 AM, Al Viro wrote:
>>> On Mon, Apr 21, 2014 at 09:22:48AM -0700, Andy Lutomirski wrote:
>>>
+static int proc_may_follow(struct nameidata *nd, s
On Mon, Apr 21, 2014 at 7:32 PM, Ley Foon Tan wrote:
> On Sun, Apr 20, 2014 at 12:09 AM, Pavel Machek wrote:
>>> +/* Additional Nios II specific syscalls. */
>>> +#define __NR_cacheflush (__NR_arch_specific_syscall)
>>> +__SYSCALL(__NR_cacheflush, sys_cacheflush)
>>
>> I guess you should Cc: Mich
On 04/17/2014 12:36 PM, Doug Anderson wrote:
> On ARM Chromebooks we have a few devices that are accessed by both the
> AP (the main "Application Processor") and the EC (the Embedded
> Controller). These are:
> * The battery (sbs-battery).
> * The power management unit tps65090.
...
> On the Samsu
On Mon, Apr 21, 2014 at 3:52 AM, WANG Chao wrote:
> Hi, Kees
>
> When I'm testing kaslr with kdump, I find that when 2nd kernel is loaded
> high, it doesn't boot.
>
> I reserved 128M memory at high with kernel cmdline
> "crashkernel=128M,high crashkernel=0,low", and for which I got:
>
> [0.000
21.04.2014 20:29, Christoph Lameter:
> On Sun, 20 Apr 2014, Vladimir Davydov wrote:
>
>> * Way #1 - prevent dead kmem caches from caching slabs on free *
>>
>> We can modify sl[au]b implementation so that it won't cache any objects
>> on free if the kmem cache belongs to a dead memcg. Then it'd be
[adding Rusty]
On 03/24/2014 02:19 PM, Ryan Nicholl wrote:
> I would like to know if it would be possible to use a 64 bit futex
> call? If not, I would like to request it be added. (It is acknowledged
> in the manpages that it must be added eventually anyway.)
>
> I am programming a C++11+ librar
On 04/21/2014 10:56 AM, Yinghai Lu wrote:
>>
>> 32-bit relocation outside of kernel!
>
> Interesting, when kernel get at "early console in decompress_kernel"
> kernel already in 64 bit...
>
> what does it mean "32-bit relocation outside of kernel" ?
>
> why 32-bit is involved ?
>
Most addresse
[adding more patch committers]
On 04/13/2014 12:05 PM, Stefani Seibold wrote:
> Since some kernel version it is impossible to select the Enhanced Real
> Time Clock Support (legacy PC RTC driver) because RTC_LIB is set by
> default in arch/x86/Kconfig, but the rule for selecting CONFIG_RTC is
> RTC
On Mon, Apr 21, 2014 at 10:56 AM, Yinghai Lu wrote:
> On Mon, Apr 21, 2014 at 3:52 AM, WANG Chao wrote:
>> Hi, Kees
>>
>> When I'm testing kaslr with kdump, I find that when 2nd kernel is loaded
>> high, it doesn't boot.
>>
>> I reserved 128M memory at high with kernel cmdline
>> "crashkernel=128
On 04/21/2014 09:45 AM, Jeff Layton wrote:
> On Mon, 21 Apr 2014 12:10:04 -0400
> Rich Felker wrote:
>> I'm well aware of that. The problem is that the proposed API is using
>> the two-letter abbreviation FD, which ALWAYS means file descriptor and
>> NEVER means file description (in existing usage
On Mon, Apr 21, 2014 at 2:02 AM, Alexandre Courbot wrote:
> Pad the microcode to a multiple of 0x40 bytes, otherwise firmware will
bytes or u32's? From the code, I'm guessing the latter. (Similar
concern about comment in the code.)
> fail to run from non-prepadded firmware files.
>
> Signed-off-
From: Dave Hansen
Nobody outputs memory addresses in decimal. PFNs are essentially
addresses, and they're gibberish in decimal. Output them in hex.
Also, add the nid and zone name to give a little more context to
the message.
Signed-off-by: Dave Hansen
---
b/mm/page_alloc.c |5 +++--
On Mon, Apr 21, 2014 at 2:02 AM, Alexandre Courbot wrote:
> Skip the creation of a software channel for GK20A as software methods
> are not yet supported.
How is GK20A different from a nvc0+ card that lacks PDISPLAY (like all
the 3D Controller ones, and I guess even some that come up as VGA
contr
On Mon, Apr 21, 2014 at 11:50 AM, Paul E. McKenney
wrote:
>
> Good observation, but this approach prevents someone from building an
> rcutorture module after the fact for a kernel that was built with
> CONFIG_RCU_TORTURE_TEST=n. So I have to say "no" on this one.
>
OK, I did not consider that ca
Hi
I've raised https://bugzilla.kernel.org/show_bug.cgi?id=74391 as I've
been having issues compiling the kernel since
26f5ef2e3c3c18f1dc31461ddf1db00b014edcd4
I'm not sure if linking with ld.gold is officially supported but it
did used to work before this commit and continues to work if I revert
On 04/17/2014 11:59 AM, Doug Anderson wrote:
> This adds the EC i2c tunnel (and devices under it) to the
> tegra124-venice2 device tree.
The series,
Tested-by: Stephen Warren
I can apply this one patch once the other patches in the series are
acked or applied (in order to make sure the DT bindin
Dear Santosh Shilimkar,
On Mon, 21 Apr 2014 09:35:25 -0400, Santosh Shilimkar wrote:
> > In mach-mvebu, what we do is that we register a bus notifier on the
> > platform bus, so that we can set our custom DMA operations for all
> > platform devices in the system. Should this be done in a differen
Jeff,
On 04/21/2014 06:45 PM, Jeff Layton wrote:
> On Mon, 21 Apr 2014 12:10:04 -0400
> Rich Felker wrote:
>
>> On Mon, Apr 21, 2014 at 04:23:54PM +0200, Michael Kerrisk (man-pages) wrote:
>>> On 04/21/2014 04:02 PM, Rich Felker wrote:
On Mon, Apr 21, 2014 at 09:45:35AM -0400, Jeff Layton wr
From: Terence Eden
Signed-off-by: Terence Eden
---
drivers/target/iscsi/iscsi_target_parameters.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/target/iscsi/iscsi_target_parameters.c
b/drivers/target/iscsi/iscsi_target_parameters.c
index 4d2e23f..ce8
Christoph,
On 04/21/2014 06:09 PM, Christoph Hellwig wrote:
> On Mon, Apr 21, 2014 at 04:23:54PM +0200, Michael Kerrisk (man-pages) wrote:
>>
>> There's at least two problems to solve here:
>>
>> 1) "File private locks" is _meaningless_ as a term. Elsewhere
>>
>> (http://thread.gmane.org/gmane
From: Dave Hansen
This has been run through Intel's LKP tests across a wide range
of modern sytems and workloads and it wasn't shown to make a
measurable performance difference positive or negative.
Now that we have some shiny new tracepoints, we can actually
figure out what the heck is going o
From: Dave Hansen
I think the flush_tlb_mm_range() code that tries to tune the
flush sizes based on the CPU needs to get ripped out for
several reasons:
1. It is obviously buggy. It uses mm->total_vm to judge the
task's footprint in the TLB. It should certainly be using
some measure of
From: Dave Hansen
Most of the logic here is in the documentation file. Please take
a look at it.
I know we've come full-circle here back to a tunable, but this
new one is *WAY* simpler. I challenge anyone to describe in one
sentence how the old one worked. Here's the way the new one
works:
From: Dave Hansen
We don't have any good way to figure out what kinds of flushes
are being attempted. Right now, we can try to use the vm
counters, but those only tell us what we actually did with the
hardware (one-by-one vs full) and don't tell us what was actually
_requested_.
This allows us
From: Dave Hansen
If we take the
if (end == TLB_FLUSH_ALL || vmflag & VM_HUGETLB) {
local_flush_tlb();
goto out;
}
path out of flush_tlb_mm_range(), we will have flushed the tlb,
but not incremented NR_TLB_LOCAL_FLUSH_ALL. This unifies the
way o
Changes from v2:
* Added a brief comment above the ceiling tunable
* Updated the documentation to mention large pages and say
"individual flush" instead of invlpg in most cases.
Reposting with an instrumentation patch, and a few minor tweaks.
I'd love some more eyeballs on this, but I think
From: Dave Hansen
The
if (cpumask_any_but(mm_cpumask(mm), smp_processor_id()) < nr_cpu_ids)
line of code is not exactly the easiest to audit, especially when
it ends up at two different indentation levels. This eliminates
one of the the copy-n-paste versions. It also gives us a unifi
Sebastian, Russell,
On Tue, 15 Apr 2014 20:15:58 +0200, Sebastian Hesselbarth wrote:
> This is a patch set fixing regressions in v3.15-rc1 ultimately caused
> by adding DT-enabled Marvell Dove to MULTI_V7. There was a fix
> introduced late in the merge window to fix a related regression for
> non-
The union contains only one member now, so we use the variables in it directly.
Signed-off-by: Haiyang Zhang
Reviewed-by: K. Y. Srinivasan
---
drivers/net/hyperv/hyperv_net.h | 10 +++---
drivers/net/hyperv/netvsc.c |7 +++
drivers/net/hyperv/netvsc_drv.c |8
Removed recv_pkt_list and lock, and updated related code, so that
the locking overhead is reduced especially when multiple channels
are in use.
The recv_pkt_list isn't actually necessary because the packets are
processed sequentially in each channel. It has been replaced by a
local variable, and t
On 04/21/2014 06:10 PM, Rich Felker wrote:
> On Mon, Apr 21, 2014 at 04:23:54PM +0200, Michael Kerrisk (man-pages) wrote:
>> On 04/21/2014 04:02 PM, Rich Felker wrote:
>>> On Mon, Apr 21, 2014 at 09:45:35AM -0400, Jeff Layton wrote:
File-private locks have been merged into Linux for v3.15, and
On Mon, 21 Apr 2014 20:18:50 +0200
"Michael Kerrisk (man-pages)" wrote:
> Jeff,
> On 04/21/2014 06:45 PM, Jeff Layton wrote:
> > On Mon, 21 Apr 2014 12:10:04 -0400
> > Rich Felker wrote:
> >
> >> On Mon, Apr 21, 2014 at 04:23:54PM +0200, Michael Kerrisk (man-pages)
> >> wrote:
> >>> On 04/21/2
On Mon, Apr 21, 2014 at 08:32:44PM +0200, Michael Kerrisk (man-pages) wrote:
> So, can you *please* answer this question: what do you call (i.e.,
> what everyday technical language term do use for) the thing
> that sits between a file descriptor and an i-node?
An open file.
--
To unsubscribe f
On 04/21/2014 08:34 PM, Christoph Hellwig wrote:
> On Mon, Apr 21, 2014 at 08:32:44PM +0200, Michael Kerrisk (man-pages) wrote:
>> So, can you *please* answer this question: what do you call (i.e.,
>> what everyday technical language term do use for) the thing
>> that sits between a file descript
On 04/21/2014 08:01 PM, Andy Lutomirski wrote:
> On 04/21/2014 09:45 AM, Jeff Layton wrote:
>> On Mon, 21 Apr 2014 12:10:04 -0400
>> Rich Felker wrote:
>>> I'm well aware of that. The problem is that the proposed API is using
>>> the two-letter abbreviation FD, which ALWAYS means file descriptor a
On Mon, Apr 21, 2014 at 08:32:44PM +0200, Michael Kerrisk (man-pages) wrote:
> On 04/21/2014 06:10 PM, Rich Felker wrote:
> > I'm well aware of that. The problem is that the proposed API is using
> > the two-letter abbreviation FD, which ALWAYS means file descriptor and
> > NEVER means file descrip
On Mon, Apr 21, 2014 at 02:32:38PM -0400, Jeff Layton wrote:
> > > Fair enough. Assuming we kept "file-description locks" as a name, what
> > > would you propose as new macro names?
> >
> > I assume you meant, "assume we kept the term 'file-private locks'..."
> > In that case, at least make the co
On Mon, Apr 21, 2014 at 08:32:44PM +0200, Michael Kerrisk (man-pages) wrote:
> So, can you *please* answer this question: what do you call (i.e.,
> what everyday technical language term do use for) the thing
> that sits between a file descriptor and an i-node?
>
> (Please don't say 'struct file
Fix a potential memory leak in the error handling of test_aead_speed(). In case
the size check on the associate data length parameter fails, the function goes
through the wrong exit label. Reported by Coverity - CID 1163870.
Signed-off-by: Christian Engelmayer
---
crypto/tcrypt.c | 14 ++
Conrad Meyer writes:
> Add structure for parsed BPB information, struct fat_bios_param_block,
> and move all of the deserialization and validation logic from
> fat_fill_super() into fat_read_bpb().
>
> Add a 'dos1xfloppy' mount option to infer DOS 2.x BIOS Parameter Block
> defaults from block de
Fix a potential memory leak in the error handling of test_aead_speed(). In case
crypto_alloc_aead() fails, the function returns without going through the
centralized cleanup path. Reported by Coverity - CID 1163870.
Signed-off-by: Christian Engelmayer
---
crypto/tcrypt.c | 3 ++-
1 file changed,
Fix leakage of memory for struct aead_request that is allocated via
aead_request_alloc() but not released via aead_request_free().
Reported by Coverity - CID 1163869.
Signed-off-by: Christian Engelmayer
---
crypto/tcrypt.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/cr
This is a cleanup of Coverity ressource leak findings for the quick & dirty
crypto testing module crypto/tcrypt.c.
All 3 changesets address function test_aead_speed() that was introduced in
53f52d7a (crypto: tcrypt - Added speed tests for AEAD crypto alogrithms in
tcrypt test suite)
The series ap
From: Haiyang Zhang
Date: Mon, 21 Apr 2014 12:26:15 -0700
> @@ -401,8 +401,6 @@ static void rndis_filter_receive_data(struct rndis_device
> *dev,
> pkt->total_data_buflen = rndis_pkt->data_len;
> pkt->data = (void *)((unsigned long)pkt->data + data_offset);
>
> - pkt->is_data_p
On Mon, Apr 21, 2014 at 02:48:41PM -0400, Theodore Ts'o wrote:
> On Mon, Apr 21, 2014 at 08:32:44PM +0200, Michael Kerrisk (man-pages) wrote:
> > So, can you *please* answer this question: what do you call (i.e.,
> > what everyday technical language term do use for) the thing
> > that sits betwee
The call from the IPv6 part can be simplified as the beginning of the
calling function ensures that we end up here when having a proper IPv6
source address only.
Introduced by 6565b9eeef194afbb3beec80d6dd2447f4091f8c
("bridge: multicast: add sanity check for query source addresses")
Reported-by:
On Mon, Apr 21, 2014 at 10:54 AM, Tony Lindgren wrote:
> * Rob Herring [140421 06:47]:
>> On Fri, Apr 18, 2014 at 6:24 PM, Tony Lindgren wrote:
>> > * Russell King - ARM Linux [140418 16:04]:
>> >> On Fri, Apr 18, 2014 at 02:58:48PM -0700, Tony Lindgren wrote:
>> >> > Oh come on, let's stop pre
Hi Linus,
This is a single build fix for building with gold as opposed to GNU
ld. It got queued up separately and was expected to be pushed during
the merge window, but it got left behind.
The following changes since commit 37c975545ec63320789962bf307f000f08fabd48:
x86, vdso: Fix the symbol v
On Mon, Apr 21, 2014 at 06:25:50AM -0700, Guenter Roeck wrote:
> On 04/20/2014 07:13 PM, Greg Kroah-Hartman wrote:
> >
> >
> > Note, this is the LAST 3.13.y kernel I will be releasing. It will be
> > end-of-life after this release, please move to 3.14.y at this time.
> >
> > -
On Mon, Apr 21, 2014 at 02:51:44PM -0400, Rich Felker wrote:
> I don't think "struct file" has any meaning to any userspace
> developers, and as such doesn't belong in documentation for userspace
> programming. It's an implementation detail of the kernel that
> userspace developers have no need to
On Mon, Apr 21, 2014 at 03:04:10PM -0400, Theodore Ts'o wrote:
> I think what you mean is that there is no need that we expose the name
> "struct file". My point is that "struct file" is actually a much
> _better_ name than "file description". Heck, "open file object" would
> be better name than
On Monday 21 April 2014 10:25:25 Ed Tomlinson wrote:
> On Saturday 19 April 2014 21:03:05 Markus Trippelsdorf wrote:
> > On 2014.04.19 at 08:19 +0100, Dave Airlie wrote:
> > >
> > > Unfortunately this contains no easter eggs, its a bit larger than I'd
> > > like, but I included a patch that just
On Mon, 21 Apr 2014 14:48:29 -0400
Rich Felker wrote:
> On Mon, Apr 21, 2014 at 02:32:38PM -0400, Jeff Layton wrote:
> > > > Fair enough. Assuming we kept "file-description locks" as a name, what
> > > > would you propose as new macro names?
> > >
> > > I assume you meant, "assume we kept the te
On Monday 21 April 2014 02:19 PM, Thomas Petazzoni wrote:
> Dear Santosh Shilimkar,
>
> On Mon, 21 Apr 2014 09:35:25 -0400, Santosh Shilimkar wrote:
>
>>> In mach-mvebu, what we do is that we register a bus notifier on the
>>> platform bus, so that we can set our custom DMA operations for all
>>>
We track shadow vmcs fields through two static lists,
one for read only and another for r/w fields. However, with
addition of new vmcs fields, not all fields may be supported on
all hosts. If so, copy_vmcs12_to_shadow() trying to vmwrite on
unsupported hosts will result in a vmwrite error. For exa
201 - 300 of 561 matches
Mail list logo
