From: Steven Rostedt
The names used to display the field and type in the event format
files are copied, as well as the system name that is displayed.
All these names are created by constant values passed in.
If one of theses values were to be removed by a module, the module
would also be
From: Steven Rostedt
The event structures used by the trace events are mostly persistent,
but they are also allocated by kmalloc, which is not the best at
allocating space for what is used. By converting these kmallocs
into kmem_cache_allocs, we can save over 50K of space that is
permanently
From: Steven Rostedt
If the ring buffer is empty, a read to trace_pipe_raw wont block.
The tracing code has the infrastructure to wake up waiting readers,
but the trace_pipe_raw doesn't take advantage of that.
When a read is done to trace_pipe_raw without the O_NONBLOCK flag
set, have the read
From: "Steven Rostedt (Red Hat)"
Move the logic to wake up on ring buffer data into the ring buffer
code itself. This simplifies the tracing code a lot and also has the
added benefit that waiters on one of the instance buffers can be woken
only when data is added to that instance instead of data
From: Steven Rostedt
The trace_pipe_raw never implemented polling and this was casing
issues for several utilities. This is now implemented.
Blocked reads still are on the TODO list.
Reported-by: Mauro Carvalho Chehab
Signed-off-by: Steven Rostedt
---
kernel/trace/trace.c | 78
From: Steven Rostedt
With the new descriptors used to allow multiple buffers in the
tracing directory added, the kernel command line parameter
trace_events=... no longer works. This is because the top level
(global) trace array now has a list of descriptors associated
with the events and the
From: "Steven Rostedt (Red Hat)"
Currently only the splice NONBLOCK flag is checked to determine if
the splice read should block or not. But the file descriptor NONBLOCK
flag also needs to be checked.
Signed-off-by: Steven Rostedt
---
kernel/trace/trace.c |2 +-
1 file changed, 1
On 03/01/13 15:51, a...@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2013-03-01-15-50 has been uploaded to
>
>http://www.ozlabs.org/~akpm/mmotm/
>
on i386:
ERROR: "copy_from_user_overflow" [fs/binfmt_misc.ko] undefined!
which I don't understand.
lib/usercopy.o is built and
On Sat, 2 Mar 2013, Ric Mason wrote:
> On 03/02/2013 04:03 AM, Hugh Dickins wrote:
> > On Fri, 1 Mar 2013, Ric Mason wrote:
> > > I think the ksm implementation for num awareness is buggy.
> > Sorry, I just don't understand your comments below,
> > but will try to answer or question them as best
On Sat, 2013-03-02 at 04:49 +0800, Stephen Warren wrote:
> On 03/01/2013 02:41 AM, Bill Huang wrote:
> > On Thu, 2013-02-28 at 12:49 +0800, Mike Turquette wrote:
> >> There are three prerequisites to using this feature:
> >>
> >> 1) the affected clocks must be using the common clk framework
> >>
On Sat, 2013-03-02 at 04:48 +0800, Mike Turquette wrote:
> Quoting Mike Turquette (2013-03-01 10:22:34)
> > Quoting Bill Huang (2013-03-01 01:41:31)
> > > On Thu, 2013-02-28 at 12:49 +0800, Mike Turquette wrote:
> > > > Dynamic voltage and frequency scaling (dvfs) is a common power saving
> > > >
On 03/02/2013 09:42 AM, Hugh Dickins wrote:
On Sat, 2 Mar 2013, Simon Jeons wrote:
In function __add_to_swap_cache if add to radix tree successfully will result
in increase NR_FILE_PAGES, why? This is anonymous page instead of file backed
page.
Right, that's hard to understand without
On Fri, 2013-03-01 at 13:47 +1100, Stephen Rothwell wrote:
> Hi Steven,
>
> After merging the ftrace tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> kernel/trace/trace_kdb.c: In function 'ftrace_dump_buf':
> kernel/trace/trace_kdb.c:29:33: error: invalid type
On 03/02/2013 02:20 AM, Yinghai Lu wrote:
> On Fri, Mar 1, 2013 at 9:17 AM, Neil Horman wrote:
>> A few years back intel published a spec update:
>> http://www.intel.com/content/dam/doc/specification-update/5520-and-5500-chipset-ioh-specification-update.pdf
>>
>> For the 5520 and 5500 chipsets
Hi,
Some issues with the device PM QoS core code have been uncovered recently
and the following two patches are supposed to fix them.
[1/2] Fix concurrency problems and memory leaks in device PM QoS core.
[2/2] Fix removal of device PM QoS attributes during device remove.
On top of the current
From: Rafael J. Wysocki
The current device PM QoS code assumes that certain functions will
never be called in parallel with each other (for example, it is
assumed that dev_pm_qos_expose_flags() won't be called in parallel
with dev_pm_qos_hide_flags() for the same device and analogously
for the
From: Rafael J. Wysocki
Device PM QoS sysfs attributes, if present during device removal,
are removed from within device_pm_remove(), which is too late,
since dpm_sysfs_remove() has already removed the whole attribute
group they belonged to. However, moving the removal of those
attributes to
On Fri, Feb 15, 2013 at 11:03 AM, Cousson, Benoit wrote:
> Hi Matthias,
>
>
> On 2/15/2013 10:35 AM, Matthias Brugger wrote:
>>
>> 2013/1/26 Javier Martinez Canillas :
>>>
>>> On Sat, Jan 26, 2013 at 4:16 PM, Matthias Brugger
>>>
>>> wrote:
Hi Benoit,
2012/12/12 Benoit
On Sat, 2 Mar 2013, Simon Jeons wrote:
>
> In function __add_to_swap_cache if add to radix tree successfully will result
> in increase NR_FILE_PAGES, why? This is anonymous page instead of file backed
> page.
Right, that's hard to understand without historical background.
I think the quick
On Fri, Mar 1, 2013 at 5:32 PM, Linus Torvalds
wrote:
> On Fri, Mar 1, 2013 at 4:16 PM, Davidlohr Bueso
> wrote:
>>
>> With Rik's semop-multi.c microbenchmark we can see the following
>> results:
>
> Ok, that certainly looks very good.
Side note: it's fairly late in the merge window, and I
On Fri, Mar 1, 2013 at 4:16 PM, Davidlohr Bueso wrote:
>
> With Rik's semop-multi.c microbenchmark we can see the following
> results:
Ok, that certainly looks very good.
> + 59.40%a.out [kernel.kallsyms] [k] _raw_spin_lock
> + 17.47%a.out [kernel.kallsyms] [k]
The rearranging done for user ns has resulted in allowing arbitrary
kernel module loading[1] (i.e. re-introducing a form of CVE-2011-1019)
by what is assumed to be an unprivileged process.
At present, it does look to require at least CAP_SETUID along the way
to set up the uidmap (but things like
From: Daniel Kurtz
This same driver can be used by atmel based touchscreens and touchpads
(buttonpads) by instantiating the i2c device as a "atmel_mxt_tp".
This will cause the driver to perform some touchpad specific
initializations, such as:
* register input device name "Atmel maXTouch
Add basic platform data to get the current upstream driver working
with the 224s touchpad and 1664s touchscreen.
We will be using NULL config so we will use the settings from the
devices' NVRAMs.
Signed-off-by: Benson Leung
Change-Id: I712bf4726fb4b194fbde44ad200c54d13dc3bdb9
---
Add support for an "atmel_mxt_tp" variant in the atmel_mxt_ts.c driver.
Then, add platform data for the 224s trackpad and the 1664s touchscreen
in chromeos_laptop so that the existing version of the driver will
probe these devices correctly.
[PATCH 1/2] Input: atmel_mxt_ts - add device id for
On Fri, Mar 1, 2013 at 4:16 PM, Davidlohr Bueso wrote:
> +static inline struct sem_array *sem_obtain_object(struct ipc_namespace *ns,
> int id)
> +{
> + struct kern_ipc_perm *ipcp = ipc_obtain_object(_ids(ns), id);
> +
> + if (IS_ERR(ipcp))
> + return (struct sem_array
Hey Linus,
Please git pull the following tag:
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
stable/for-linus-3.9-rc1-tag
which has
Bug-fixes:
- Update the Xen ACPI memory and CPU hotplug locking mechanism.
- Fix PAT issues wherein various applications would not start
- Fix
On Fri, Mar 1, 2013 at 4:16 PM, Davidlohr Bueso wrote:
>
> +struct kern_ipc_perm *ipc_obtain_object(struct ipc_ids *ids, int id)
This looks good..
> +struct kern_ipc_perm *ipc_obtain_object_check(struct ipc_ids *ids, int id)
The comment on ipc_checkid() says that it should only be called with
Hi Hugh,
On 03/02/2013 04:03 AM, Hugh Dickins wrote:
On Fri, 1 Mar 2013, Ric Mason wrote:
I think the ksm implementation for num awareness is buggy.
Sorry, I just don't understand your comments below,
but will try to answer or question them as best I can.
For page migratyion stuff, new
Hi,
since a kernel upgrade to 2.6.33 on debian and now 3.4.11 i cannot longer
use (read, write) dvds medias as the /dev/sr0 symlink appears ignoring the dvd
drive (incorrectly dentified as /dev/hda).
I read intensively on this issue over google and found many users looking
for clues how to
I recently fixed a long standing bug in the splice code for ftrace. This
was something that I wanted fixed so that trace-cmd would work better.
The fix is to finally have the splice system call block until data is
available, instead of having trace-cmd poll reading the trace_pipe_raw
data file.
On 03/02/2013 06:41 AM, Andrew Shewmaker wrote:
On Fri, Mar 01, 2013 at 10:40:43AM +0800, Ric Mason wrote:
On 02/28/2013 11:48 AM, Andrew Shewmaker wrote:
On Thu, Feb 28, 2013 at 02:12:00PM -0800, Andrew Morton wrote:
On Wed, 27 Feb 2013 15:56:30 -0500
Andrew Shewmaker wrote:
The following
On Thu, Feb 28, 2013 at 04:54:25PM +0800, Hu Tao wrote:
> > > diff --git a/arch/x86/include/uapi/asm/kvm_para.h
> > > b/arch/x86/include/uapi/asm/kvm_para.h
> > > index 06fdbd9..c15ef33 100644
> > > --- a/arch/x86/include/uapi/asm/kvm_para.h
> > > +++ b/arch/x86/include/uapi/asm/kvm_para.h
> > >
On Wed, Feb 20, 2013 at 04:13:49PM +0800, Hu Tao wrote:
> On Thu, Feb 07, 2013 at 11:50:28PM -0200, Marcelo Tosatti wrote:
> > On Wed, Jan 23, 2013 at 03:19:23PM +0800, Hu Tao wrote:
> > > From: Wen Congyang
> > >
> > > The guest should run after resetting it, but it does not run if its
> > >
Through ipc_lock() and, therefore, ipc_lock_check() we currently
return the locked ipc object. This is not necessary for all situations,
thus introduce, analogous, ipc_obtain_object and ipc_obtain_object_check
functions that only mark the RCU read critical region without acquiring
the lock and
Instead of holding the ipc lock for permissions and security
checks, among others, only acquire it when necessary.
Signed-off-by: Davidlohr Bueso
---
ipc/sem.c | 94 ---
1 file changed, 66 insertions(+), 28 deletions(-)
diff --git
The following set of not-thoroughly-tested patches are based on the
discussion of holding the ipc lock unnecessarily, such as for permissions
and security checks:
https://lkml.org/lkml/2013/2/28/540
Patch 0/1: Introduces new functions, analogous to ipc_lock and ipc_lock_check
in the ipc utility
On Wednesday, January 16, 2013 3:16:38 PM UTC+1, Evgeniy Polyakov wrote:
> Can you confirm that bug still persists and that it doesn't exist in
>
> 3.1? Do you have a possibility to bisect w1 bits down to broken
> commit?
Hi
I can confirm that this bug persists in recent kernel. Onewire netlink
On 03/02/2013 06:33 AM, Hugh Dickins wrote:
On Fri, 1 Mar 2013, Simon Jeons wrote:
On 03/01/2013 05:22 PM, Simon Jeons wrote:
On 02/23/2013 01:56 AM, Johannes Weiner wrote:
Mapped file pages have to get scanned twice before they are reclaimed
because we don't have enough usage information
On Thu, Feb 28, 2013 at 4:30 PM, Dave Jones wrote:
> [ 39.878535] =
> [ 39.879670] [ BUG: rpc.nfsd/666 still has locks held! ]
> [ 39.880871] 3.8.0+ #3 Not tainted
> [ 39.881858] -
> [ 39.882850] 2 locks on stack by
On Fri, Mar 01, 2013 at 12:09:12PM +0200, Ивайло Димитров wrote:
> Unfortunately it is necessary, on RX-51 PPA/NOLO leaves IBE bit unset.
You sure? I think you need to explain this more - the commit message in
the original patch is empty/missing...
A.
--
To unsubscribe from this list: send the
The mm-of-the-moment snapshot 2013-03-01-15-50 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You
On 01/03/13 21:52, Michail Kurachkin wrote:
> From: Michail Kurochkin
>
> Signed-off-by: Michail Kurochkin
> ---
> drivers/staging/tdm/kirkwood_tdm.c | 932
>
> drivers/staging/tdm/kirkwood_tdm.h | 110 +
> 2 files changed, 1042 insertions(+), 0
The following changes since commit 09884964335e85e897876d17783c2ad33cf8a2e0:
mm: do not grow the stack vma just because of an overrun on preceding vma
(2013-02-27 08:36:04 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git/
The following changes since commit 74e1a2a39355b2d3ae8c60c78d8add162c6d7183:
Merge tag 'usb-3.9-rc1' of
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb (2013-02-21 12:20:00
-0800)
are available in the git repository at:
on today mainline tree.
[ 529.379490] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
[ 529.399350] swapper/0 D 883025294000 0 1 0 0x
[ 529.399726] 8810274f5ab8 0046 810b3111
8810274f5fd8
[ 529.424058]
Add an admin_reserve_pages knob to allow admins of large memory
systems running with overcommit disabled to change the hardcoded
memory reserve to something other than 3%.
admin_reserve_pages is initialized to min(3%, k) as Alan suggested.
k=2000 pages should allow the admin to spawn new
On 26/02/13 13:53, Laxman Dewangan wrote:
On Saturday 23 February 2013 10:05 PM, Ian Lartey wrote:
From: Graeme Gregory
Read the chip varient and the OTP information from the chip and display
this on probe to aid in debugging of issues.
Older palmas chips do not have the USB_ID programmed
於 五，2013-03-01 於 16:31 +，Matt Fleming 提到：
> On Fri, 2013-03-01 at 15:17 +, Matt Fleming wrote:
> > On Fri, 2013-03-01 at 11:20 +0800, Lee, Chun-Yi wrote:
> > > From: Michael Schroeder
> > >
> > > On HP z220 system (firmware version 1.54), some EFI variables are
> > > incorrectly
> > >
Limit the growth of the memory reserved for other processes
to the smaller of 3% or 2000 pages.
This affects OVERCOMMIT_NEVER mode.
Signed-off-by: Andrew Shewmaker
---
I had simply removed the reserve previously, but that caused forks
to fail easily. This allows a user to recover similar to
On Mon, Feb 18, 2013 at 6:52 AM, Varun Sethi wrote:
[cut]
> +static phys_addr_t get_phys_addr(struct fsl_dma_domain *dma_domain, unsigned
> long iova)
> +{
> + u32 win_cnt = dma_domain->win_cnt;
> + struct dma_window *win_ptr =
> + _domain->win_arr[0];
>
8SE91xx-SATA-controllers..
patch
patching file drivers/iommu/intel-iommu.c
patching file drivers/pci/quirks.c
Hunk #1 succeeded at 3230 (offset 3 lines).
patching file include/linux/pci.h
# pwd
/usr/src/linux-3.7.10
Full dmesg with the patch applied: (but with IOMMU off)
http://home.comcast.net/~jpis
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/agk/linux-dm tags/dm-3.9-changes
to get the following device-mapper updates for 3.9.
Thanks,
Alasdair
The main addition here is a long-desired target framework to
> This is exactly the kind of approach that makes sense rather than
> trying to put entire TCP stacks in the network card firmware.
>
And should also obviate the need to put a full TCP stack in user space!
> Thanks again for doing this work and I look forward to applying
> this stuff once all the
Tim found:
[0.181441] WARNING: at
/home/rtg/ukb/raring/amd64/unstable-3.9/ubuntu-raring/arch/x86/kernel/smpboot.c:324
topology_sane.isra.2+0x6f/0x80()
[0.181443] Hardware name: S2600CP
[0.181445] sched: CPU #1's llc-sibling CPU #0 is not on the same
node! [node: 1 != 0]. Ignoring
On 01/03/13 21:50, Michail Kurachkin wrote:
> From: Michail Kurochkin
>
> Signed-off-by: Michail Kurochkin
Hi Michail,
Quick review below. I'll try to find some time to look through
the other patches later.
~Ryan
> ---
> drivers/staging/Kconfig|4 +
>
On Fri, Mar 1, 2013 at 12:21 AM, Erik Gilling wrote:
> On Thu, Feb 28, 2013 at 7:59 PM, John Stultz wrote:
>> Given its the sync driver, its most obvious choice, but I agree its likely
>> to collide with filesystem related or other sync_ named functions that don't
>> have a subsystem prefix.
>>
On Fri, Mar 01, 2013 at 10:40:43AM +0800, Ric Mason wrote:
> On 02/28/2013 11:48 AM, Andrew Shewmaker wrote:
> >On Thu, Feb 28, 2013 at 02:12:00PM -0800, Andrew Morton wrote:
> >>On Wed, 27 Feb 2013 15:56:30 -0500
> >>Andrew Shewmaker wrote:
> >>
> >>>The following patches are against the mmtom
On Fri, 1 Mar 2013, Simon Jeons wrote:
> On 03/01/2013 05:22 PM, Simon Jeons wrote:
> > On 02/23/2013 01:56 AM, Johannes Weiner wrote:
> > > Mapped file pages have to get scanned twice before they are reclaimed
> > > because we don't have enough usage information after the first scan.
> >
> > It
Thanks for testing!
Patching 3.7.10 looks somewhat different here. I'm using the
linux-3.7.y branch from
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
at commit 356d8c6fb2a7cf49e836742738a8b9a47e77cfea. The output I get
is:
$ patch -p1 <
~/devel/lk_patches_dma_sourc
The latest maintenance release Git v1.8.1.5 is now available at
the usual places.
The release tarballs are found at:
http://code.google.com/p/git-core/downloads/list
and their SHA-1 checksums are:
3349a15de7c5501715bda9b68301d0406272f8e0 git-1.8.1.5.tar.gz
On Fri, 2013-03-01 at 13:56 -0800, Tejun Heo wrote:
> On Fri, Mar 1, 2013 at 1:54 PM, Peter Hurley wrote:
> >> The WARN_ON() is just for cases where someone might be doing something
> >> crazy with the previous behavior of ignoring high bit. Maybe I was
> >> being overly paranoid and we should
From: Greg KH
Date: Fri, 1 Mar 2013 13:56:09 -0800
> On Fri, Mar 01, 2013 at 04:47:11PM -0500, David Miller wrote:
>>
>> I'm getting these non-stop right when the hypervisor console registers
>> on sparc64, and the machine won't boot up properly. This is with
>> Linus's current tree.
>>
>>
From: David Miller
Date: Fri, 01 Mar 2013 16:47:11 -0500 (EST)
>
> I'm getting these non-stop right when the hypervisor console registers
> on sparc64, and the machine won't boot up properly. This is with
> Linus's current tree.
As a quick addendum I'm looking at all of these
On Fri, Mar 1, 2013 at 1:54 PM, Peter Hurley wrote:
>> The WARN_ON() is just for cases where someone might be doing something
>> crazy with the previous behavior of ignoring high bit. Maybe I was
>> being overly paranoid and we should just drop it from idr_find().
>
> Can we revert the
On Fri, Mar 01, 2013 at 04:47:11PM -0500, David Miller wrote:
>
> I'm getting these non-stop right when the hypervisor console registers
> on sparc64, and the machine won't boot up properly. This is with
> Linus's current tree.
>
> [511865.556835] console [ttyHV0] enabled
> [511865.564555]
On Fri, 2013-03-01 at 13:35 -0800, Tejun Heo wrote:
> Hello, Andrew.
>
> On Fri, Mar 01, 2013 at 01:31:59PM -0800, Andrew Morton wrote:
> > okluar passed a negative `wd' into inotify_rm_watch()?
> >
> > I wonder why it did that. I doubt if inotify_add_watch() ever returns
> > negative
On Fri, Mar 01, 2013 at 01:43:21PM -0800, Andrew Morton wrote:
> On Fri, 1 Mar 2013 11:30:27 +0100
> Jan Kara wrote:
>
> > > If a CPU remains in your loop where you invoke rcu_cpu_stall_reset(),
> > > there is no indication of the stall. Now, I do understand why having
> > > RCU add a CPU stall
I'm getting these non-stop right when the hypervisor console registers
on sparc64, and the machine won't boot up properly. This is with
Linus's current tree.
[511865.556835] console [ttyHV0] enabled
[511865.564555] [ cut here ]
[511865.612410] WARNING: at
idr_find(), idr_remove() and idr_replace() used to silently ignore the
sign bit and perform lookup with the rest of the bits. The weird
behavior has been changed such that negative IDs are treated as
invalid. As the behavior change was subtle, WARN_ON_ONCE() was added
in the hope of determining
On Fri, 1 Mar 2013 11:30:27 +0100
Jan Kara wrote:
> > If a CPU remains in your loop where you invoke rcu_cpu_stall_reset(),
> > there is no indication of the stall. Now, I do understand why having
> > RCU add a CPU stall warning into the mix would be very bad, but it
> > would be good to have
Yes that was the crash I was referring to which stopped me from testing
my other patch on mainline. I think the crashes started since some
workqueue patches introduced by commit
57b30ae77bf00d2318df711ef9a4d2a9be0a3a2a Earlier kernels should be fine.
Patch
If single_open() fails in drbd_proc_open(), module refcount is left incremented.
The patch adds module_put() on the error path.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
drivers/block/drbd/drbd_proc.c | 10 --
1 file changed,
Hello, Andrew.
On Fri, Mar 01, 2013 at 01:31:59PM -0800, Andrew Morton wrote:
> okluar passed a negative `wd' into inotify_rm_watch()?
>
> I wonder why it did that. I doubt if inotify_add_watch() ever returns
> negative descriptors, in which case I expect that okular's call to
>
On Fri, Mar 01, 2013 at 02:39:13PM -0500, Mimi Zohar wrote:
[..]
> I was suggesting that a builtin appraise rule chain and everything else
> on the other chain. Userspace could replace the other chain with
> whatever they wanted, including additional appraisal rules.
>
> > > Given the fact that
On Friday 01 March 2013, Dan Carpenter wrote:
> We're iterating through abps[] printing information, but here we
> use the wrong array index. IndexCard comes from the user and in
> this case it was specifically not range checked because we didn't
> expect to use it.
>
> Signed-off-by: Dan
On Thu, 28 Feb 2013 10:08:46 +0100
mar...@trippelsdorf.de wrote:
> Just hit the following warning on current git tree:
>
> [ cut here ]
> WARNING: at lib/idr.c:678 idr_find_slowpath+0x97/0xc0()
> Hardware name: System Product Name
> Pid: 12366, comm: okular Not tainted
From: Eliezer Tamir
Date: Wed, 27 Feb 2013 09:55:49 -0800
> This patchset adds the ability for the socket layer code to poll directly
> on an Ethernet device's RX queue. This eliminates the cost of the interrupt
> and context switch and with proper tuning allows us to get very close
> to the HW
From: Freddy Xin
Date: Wed, 27 Feb 2013 20:01:58 +0800
> + eeprom_buff = kmalloc(sizeof(u16) * (last_word - first_word + 1),
> + GFP_KERNEL);
> + if (!eeprom_buff)
> + return -ENOMEM;
> +
> + /* ax88179/178A returns 2 bytes from eeprom on read */
On Fri, 2013-03-01 at 11:44 -0800, Greg Kroah-Hartman wrote:
> 3.8-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Konrad Rzeszutek Wilk
>
> commit 01c681d4c70d64cb72142a2823f27c4146a02e63 upstream.
>
> The 'handle' is the device that
From: "John W. Linville"
Date: Fri, 1 Mar 2013 14:23:33 -0500
> This is another flurry of fixes intended for the 3.9 stream...
>
> A mac80211 pull from Johannes:
>
> "Seth fixes a stupid bug I introduced into one of his earlier patches,
> Chun-Yeow fixes mesh forwarding and Felix fixes monitor
In commit e36815e2e4a2fb675207d8968bb68e22bc938328:
ARM: Fix broken commit 0cc41e4a21d43 corrupting kernel messages
...a "#define DEBUG" line was accidentally left in. This has the side
effect of spewing massive numbers of debug messages into the log at
boot. Remove the DEBUG define.
On Fri, 2013-03-01 at 17:07 +0100, Borislav Petkov wrote:
> From: Borislav Petkov
>
> So basically this function copies EFI memmap stuff from boot_params into
> the EFI memmap descriptor and reserves memory for it. Make it much more
> readable.
>
> Signed-off-by: Borislav Petkov
> ---
>
On 03/01/2013 02:41 AM, Bill Huang wrote:
> On Thu, 2013-02-28 at 12:49 +0800, Mike Turquette wrote:
>> Dynamic voltage and frequency scaling (dvfs) is a common power saving
>> technique in many of today's modern processors. This patch introduces a
>> common clk rate-change notifier handler which
Hello, Al.
On Fri, Mar 1, 2013 at 12:39 PM, Al Viro wrote:
>> > Flexible array members can be statically initialized. If you wanna be
>> > really anal about it, you can do it manually with a wrapping struct
>> > but I don't think that would be necessary.
>> >
>>
>> I didn't know this difference
Ping. Any objections to that patch?
On Thu, Jan 24, 2013 at 7:34 PM, Marek Belisko
wrote:
> Signed-off-by: Marek Belisko
> ---
> arch/arm/boot/dts/omap3-gta04.dts | 94
> +
> 1 file changed, 94 insertions(+)
> create mode 100644
On Fri, Mar 01, 2013 at 02:36:29PM +0800, Li Zefan wrote:
> On 2013/2/28 22:49, Tejun Heo wrote:
> > On Wed, Feb 27, 2013 at 10:53 PM, Li Zefan wrote:
> >>> static const struct cgroup_name root_cgroup_name = { .name = "/" };
> >>
> >> Can't... That's char name[0] not char *name.
> >
> > Flexible
On Fri, 2013-03-01 at 21:20 +0100, Paul Bolle wrote:
> On Fri, 2013-03-01 at 12:02 -0800, Joe Perches wrote:
> > commit 85fd6d6 ("ARM: S3C2410: move mach-s3c2410/* into mach-s3c24xx/")
> > moved the files, update the F: patterns.
>
> The BAST MAINTAINER entry has come up a few times already. I
Clean-up: Fix incorrect path to header file
Commit af170c5 (originally introduced in v3.8-rc1) moved some header
files around and forgot to adjust the path to one of those. Thus the
header cannot be found, the macros are not defined and the kernel will
not compile.
Signed-off-by: Jonathan
We're iterating through abps[] printing information, but here we
use the wrong array index. IndexCard comes from the user and in
this case it was specifically not range checked because we didn't
expect to use it.
Signed-off-by: Dan Carpenter
diff --git a/drivers/char/applicom.c
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Mihail Zenkov
commit d28215996b0c3a900411769039aa3c54cf7008ab upstream.
This patch fix regression in emu1010 firmware loading after
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Florian Zeitz
commit b56ddbe55a363eee4ff7410a97050dad08215f7c upstream.
This expands the regression fix from
d28215996b0c3a900411769039aa3c54cf7008ab.
The firmware also needs to be loaded when
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Bart Van Assche
commit e1b2f13aba9ff714d23ecd4a950e744ee7ad72e1 upstream.
Remove an assignment that incorrectly overwrites the connection state
update by srp_connect_target().
Signed-off-by:
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Bart Van Assche
commit c7c4e7ff8047e43c45628b85ac200582e9404c39 upstream.
If a SCSI command times out it is passed to the SCSI error
handler. The SCSI error handler will try to abort the
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Bart Van Assche
commit 2ce19e72f4d570c87e025ee6fca4eae699a8b712 upstream.
If an SRP target is no longer reachable and srp_reset_host() fails to
reconnect then ib_srp will invoke
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Theodore Ts'o
commit c3ad83d9efdfe6a86efd44945a781f00c879b7b4 upstream.
Otherwise, ext4 file systems with the quota featured enable will get a
very confusing "No such process" error message if
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Pratyush Anand
commit 2b758350af19db9a5c98241cf222c2e211d7a912 upstream.
Synopsys says:
The HIRD Threshold field must be set to ‘0’ when the device core is
operating in super speed mode.
This
On 03/01/13 09:51, Mark Tinguely wrote:
On 02/26/13 01:28, Tony Lu wrote:
I get a reliable way to reproduce this bug. The logprint and metadump
are attached.
Kernel version: 2.6.38.8
Mkfs.xfs version: xfsprogs-3.1.1
mkfs.xfs -s size=4096 /dev/sda1
Run the following mount-cp-umount script to
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Pratyush Anand
commit 7efea86c2868b8fd9df65e589e33aebe498ce21d upstream.
There are two reasons to generate missed isoc.
1. when the host does not poll for all the data.
2. because of
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Pratyush Anand
commit cdc359dd87ab6c39a67dab724fd0b61c16e6f08b upstream.
There were still some corner cases where isoc transfer was not able to
restart, specially when missed isoc does not
101 - 200 of 1302 matches
Mail list logo
