On Fri, Feb 08 2008, Nick Piggin wrote:
> On Fri, Feb 08, 2008 at 08:47:47AM +0100, Jens Axboe wrote:
> > On Fri, Feb 08 2008, Nick Piggin wrote:
> > > On Thu, Feb 07, 2008 at 07:25:45PM +0100, Jens Axboe wrote:
> > > > Hi,
> > > >
> > > > Here's a variant using kernel threads only, the nasty arch
Paul Menage wrote:
> On Feb 7, 2008 7:37 AM, Pavel Emelyanov <[EMAIL PROTECTED]> wrote:
>> The Documentation/cgroups.txt file contains the info on how
>> to write some controller for cgroups subsystem, but even with
>> this, one need to write quite a lot of code before developing
>> the core (or co
On Friday 08 February 2008 18:29, Eric Dumazet wrote:
> Nick Piggin a écrit :
> > On Friday 08 February 2008 13:13, Christoph Lameter wrote:
> >> are available in the git repository at:
> >>
> >> git://git.kernel.org/pub/scm/linux/kernel/git/christoph/vm.git
> >> slub-linus
> >>
> >> (includes th
* Pekka Enberg <[EMAIL PROTECTED]> wrote:
> On Feb 8, 2008 1:32 AM, Christoph Lameter <[EMAIL PROTECTED]> wrote:
> > But the slab layer allocates pages < PAGE_SIZE. You need to take a
> > fault right? So each object would need its own page?
>
> No. We allocate a shadow page for each data page w
On Fri, 8 Feb 2008, Eric Dumazet wrote:
> And SLAB/SLUB allocators, even if only used from process context, want to
> disable/re-enable interrupts...
Not any more. The new fastpath does allow avoiding interrupt
enable/disable and we will be hopefully able to increase the scope of that
over
On Fri, Feb 08, 2008 at 08:59:55AM +0100, Jens Axboe wrote:
> On Fri, Feb 08 2008, Nick Piggin wrote:
> > And if you don't?
>
> Well if you don't ask for anything, you wont get anything :-)
> As I mentioned, the patch is a playing ground for trying various setups.
> Everything defaults to 'do as u
>I cannot see any other way out of this than to loose all the newly added
>consts. We have to different behavior across platforms to find a suitable
>solution that is reliable.
>
>[Kept rest of mail as I added Jan - hope he have some ideas to throw in].
I'd first of all need a better understanding
On Fri, Feb 08 2008, Nick Piggin wrote:
> On Fri, Feb 08, 2008 at 08:59:55AM +0100, Jens Axboe wrote:
> > On Fri, Feb 08 2008, Nick Piggin wrote:
> > > And if you don't?
> >
> > Well if you don't ask for anything, you wont get anything :-)
> > As I mentioned, the patch is a playing ground for tryi
Greg KH wrote:
Can you please add this information to Documentation/ABI/ so that people
know what is going on here?
Sent you the patch (Subject: [PATCH] Documentation: add UBI sysfs ABI docs).
I assume you'll put it into your tree and take the further care of it, right?
--
Best Regards,
Artem
>From 1297e1e60ec1a3ac9c64370fd089aa6c4807b65a Mon Sep 17 00:00:00 2001
From: Artem Bityutskiy <[EMAIL PROTECTED]>
Date: Fri, 8 Feb 2008 12:13:08 +0200
Subject: [PATCH] Documentation: add UBI sysfs ABI docs
Signed-off-by: Artem Bityutskiy <[EMAIL PROTECTED]>
---
Documentation/ABI/stable/sysfs-cla
On Fri, 2008-02-08 at 01:44 +0100, Bartlomiej Zolnierkiewicz wrote:
> - couple of fixes and preparatory patches
>
> - rework of PowerMac media-bay support ([un]register IDE devices instead of
> [un]registering IDE interface) [ it is the main reason for spamming PPC ML ]
Interesting... I was th
On Thu, 7 Feb 2008, Tomasz Chmielewski wrote:
> According to kernel/kexec.c:
>
> * kexec does not sync, or unmount filesystems so if you need
> * that to happen you need to do that yourself.
>
>
> I saw this was true with 2.6.18 kernel (i.e., it didn't sync), but kexec syncs
> with recent kern
On Fri, Feb 08 2008, S, Chandrakala (STSD) wrote:
> Hi,
>
> Thanks for the information!
> We would like to know when does the 2.6.25 kernel will be available at
> kernel.org.
So would I, if I locate my crystal ball I'll be sure to let you know :-)
Seriously, given past experience, it's probably
David Newall ha scritto:
Precisely: One purpose of the driver is to enforce local compliance.
It can't *enforce* it anyway, at least if the users are all around the
world.
Yes it can. You're confusing the software with different or modified
software. Different things. And by the way, if you
On Fri, Feb 08, 2008 at 09:24:22AM +0100, Jens Axboe wrote:
> On Fri, Feb 08 2008, Nick Piggin wrote:
> > On Fri, Feb 08, 2008 at 08:59:55AM +0100, Jens Axboe wrote:
> > > On Fri, Feb 08 2008, Nick Piggin wrote:
> > > > And if you don't?
> > >
> > > Well if you don't ask for anything, you wont get
On Thu, 7 Feb 2008, James Bottomley wrote:
> On Thu, 2008-02-07 at 17:04 -0800, Harvey Harrison wrote:
> > On Thu, 2008-02-07 at 18:56 -0600, James Bottomley wrote:
> > > Quite a bit of this is fixing things broken previously (the advansys fix
> > > is still pending resolution, but I'll send it as
On 02/08/2008 03:17 AM, Stephen Neuendorffer wrote:
This includes code for new fifo-based xps_hwicap in addition to the
older opb_hwicap, which has a significantly different interface. The
common code between the two drivers is largely shared.
Significant differences exists between this driver
On Fri, Feb 08, 2008 at 08:14:11AM +, Jan Beulich wrote:
> >I cannot see any other way out of this than to loose all the newly added
> >consts. We have to different behavior across platforms to find a suitable
> >solution that is reliable.
> >
> >[Kept rest of mail as I added Jan - hope he have
Lee Mathers ha scritto:
Now we have hardware ASIC that depend on the most part a (dll in
windows) or .ko .o file under linux to provide the entire instruction
set. Think Winmodems, Winprinters etc
Well, winmodem case is the only I could *almost* understand
closed-source drivers: the al
On Thu, 2008-02-07 at 23:40 -0800, Andrew Morton wrote:
> On Wed, 24 Oct 2007 16:32:59 +0200 Thomas Renninger <[EMAIL PROTECTED]> wrote:
>
> > Provide acpi_check_{mem_}region.
> >
> > Drivers can additionally check against possible ACPI interference by also
> > invoking this shortly before they c
Hi David,
> > I think you're missing my point: as long as the license stays the way
> > it is now, you can never distribute proprietary code unless you've
> > consulted a lawyer and even then you run the risk of being sued for
> > infringement if the copyright holder thinks what yo
>Al posted the following:
>
>; cat >a.c <<'EOF'
>const char foo[] __attribute__ ((__section__(".blah"))) = "";
>const char * const bar __attribute__((__section__(".blah"))) = "";
>EOF
>; gcc -m32 -S a.c
>; gcc -m64 -S a.c
>a.c:2: e
From: Christoph Hellwig <[EMAIL PROTECTED]>
From: Christoph Hellwig <[EMAIL PROTECTED]>
Signed-off-by: Christoph Hellwig <[EMAIL PROTECTED]>
Acked-by: Jiri Slaby <[EMAIL PROTECTED]>
---
drivers/char/mxser.c | 229 ++
drivers/char/mxser.h | 137 --
On Thu, 2008-02-07 at 19:26 -0600, Jay Cliburn wrote:
> On Thu, 07 Feb 2008 21:24:47 +0100
> Peter Zijlstra <[EMAIL PROTECTED]> wrote:
> The trace isn't from me; it's from Zan. He's running -mm, I'm not, if
> that makes a difference.
>
> >
> > Call Trace:
> > [schedule
On Thu, 2008-02-07 at 21:23 +0100, Sam Ravnborg wrote:
> Both situations are trivially fixable by introducing
> HAVE_IDE and HAVE_MTD.
> See attached patch.
HAVE_MTD is wrong. The actual problem we're trying to solve is that when
the architecture lacks alignment fixups, certain patterns of write
On Fre, 2008-02-08 at 10:51 +0530, rohit h wrote:
> Hi,
> I am a kernel newbie.
> I tried to insmod a C++ module containing classes, inheritance.
> I am getting 'unresolved symbol' error when I use the 'new' keyword.
> What could the problem be?
That you used C++ is the problem. Use plain C an
On Fri, 2008-02-08 at 09:04 +, David Woodhouse wrote:
> We could add get_unaligned() in certain places in the code, but that
> isn't ideal for the majority of architectures.
Actually, we already did that, despite the fact that it isn't optimal.
So there's no need to omit anything MTD-related f
Hi,
Ted wrote:
And I do agree that we probably should just implement this in
filesystem independent way, in which case all of the filesystems that
support this already have super_operations functions
write_super_lockfs() and unlockfs().
So if this is done using a new system call, there should b
On Fri, 2008-02-08 at 10:23 +, Russell King - ARM Linux wrote:
> That would be misleading though - !CPU_CP15_MMU does not mean we
> support unaligned accesses. It means that we may have no way to
> support fixing up unaligned accesses.
Doesn't that mean you should disallow MTD (or at least 1
Andrew Morton <[EMAIL PROTECTED]> writes:
> On Thu, 7 Feb 2008 14:38:58 +0100 Holger Schurig <[EMAIL PROTECTED]>
> wrote:
>
>> Disable sysctl_check.c for embedded targets. This saves about about 11 kB
>> in .text and another 11 kB in .data on a PXA255 embedded platform.
>>
>
> Nice improvement.
[EMAIL PROTECTED] wrote:
On Thu, 7 Feb 2008, Vladislav Bolkhovitin wrote:
Bart Van Assche wrote:
- It has been discussed which iSCSI target implementation should be in
the mainstream Linux kernel. There is no agreement on this subject
yet. The short-term options are as follows:
1) Do not inte
On Fri, Feb 08, 2008 at 10:18:31AM +, David Woodhouse wrote:
> But still, it's HAVE_UNALIGNED_ACCESS which we want to depend on, not a
> newly-invented HAVE_MTD. And there are other places we really ought to
> be depending on HAVE_UNALIGNED_ACCESS too.
That would be misleading though - !CPU_CP
Hi,
The 2.6.24-git18 kernel build fails on the power machine with following message
drivers/input/mouse/psmouse-base.c:44: error: __param_proto causes a section
type conflict
drivers/input/mouse/psmouse-base.c:44: error: __param_proto causes a section
type conflict
make[3]: *** [drivers/input/m
On Fri, 08 Feb 2008, Németh Márton wrote:
> Richard Purdie wrote:
> >>> leds: Add support for hardware accelerated LED flashing
> >> This one has a loose end: when you call brightness_set on a led with
> >> hardware flash acceleration, you will leave the trigger armed, BUT the led
> >> won't
On Thu, 2008-02-07 at 12:37 -0800, Luben Tuikov wrote:
> Is there an open iSCSI Target implementation which does NOT
> issue commands to sub-target devices via the SCSI mid-layer, but
> bypasses it completely?
>
>Luben
>
Hi Luben,
I am guessing you mean futher down the stack, which I don't
I have trouble locating some of the git urls (the mm repository, for
example). I have browsed around
http://www.kernel.org/pub/scm/linux/kernel/git/,
consulted the kernel FAQ, and read the obvious links on www.kernel.org.
git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.x.y.git is easy
to
> Well, winmodem case is the only I could *almost* understand
> closed-source drivers: the algorithms used *are* the modem. It's not a
> simple firmware upload.
Winmodem is all about patents, the modem standards come from ISO so are
created by all out corporate warfare with the winner getting th
On Feb 8, 2008 2:15 PM, Andi Kleen <[EMAIL PROTECTED]> wrote:
> > need to worry about it just yet. In case it's from kmalloc() you can
> > pass __GFP_NOTRACK to annotate those call sites where the memory is
>
> Ok you should add that then to skbuff.c.
Indeed. If you look at the second patch, I thi
On Thu, Feb 07 2008, Linus Torvalds wrote:
>
>
> On Thu, 7 Feb 2008, Ingo Molnar wrote:
> > INIT_HLIST_NODE(&rq->hash);
> > RB_CLEAR_NODE(&rq->rb_node);
> > - rq->ioprio = 0;
> > - rq->buffer = NULL;
> > - rq->ref_count = 1;
> > - rq->q = q;
> > - rq->special = NULL;
> > - rq-
Hi Andi,
On Feb 8, 2008 1:55 PM, Andi Kleen <[EMAIL PROTECTED]> wrote:
> Also i'm not sure how you handle initializedness of DMAed data
> (like network buffers). Wouldn't you need hooks into pci_dma_*
> for this?
If the DMA'd memory is allocated from the page allocator, we don't
need to worry abo
On Fri, 08 Feb 2008 13:25:33 +1030
David Newall <[EMAIL PROTECTED]> wrote:
> Alan Cox wrote:
> >> It would not be improper to say that "such and such a lawyer said this
> >> and that." I'm not proposing that you breach their copyright in their
> >>
> >
> > It would be highly improper given t
On Fri, Feb 08, 2008 at 01:31:44PM +0200, Pekka Enberg wrote:
> Hi Andi,
>
> On Feb 8, 2008 1:55 PM, Andi Kleen <[EMAIL PROTECTED]> wrote:
> > Impressive patch! On the other hand a lot of the interesting
> > data isn't it kmalloc anymore, but in slab. Does it really track
> > all that much?
>
> I
Hi Andi,
On Feb 8, 2008 1:55 PM, Andi Kleen <[EMAIL PROTECTED]> wrote:
> Impressive patch! On the other hand a lot of the interesting
> data isn't it kmalloc anymore, but in slab. Does it really track
> all that much?
It tracks all slab caches. What we're not tracking is pages from the
page alloc
Linus,
Please pull a second batch of dlm updates for 2.6.25 from:
git://git.kernel.org/pub/scm/linux/kernel/git/teigland/dlm.git for-linus
Al Viro (13):
dlm: use proper C for dlm/requestqueue stuff (and fix alignment bug)
dlm: dlm_process_incoming_buffer() fixes
dlm: do not b
Signed-off-by: Liam Girdwood <[EMAIL PROTECTED]>
Signed-off-by: Graeme Gregory <[EMAIL PROTECTED]>
Signed-off-by: Mike Arthur <[EMAIL PROTECTED]>
Signed-off-by: Mark Brown <[EMAIL PROTECTED]>
Cc: Dmitry Baryshkov <[EMAIL PROTECTED]>
Cc: Stanley Cai <[EMAIL PROTECTED]>
Cc: Rodolfo Giometti <[EMAIL P
This patch series adds support for the touchscreen controllers provided
by Wolfson Microelectronics WM97xx series chips in both polled and
streaming modes.
These drivers have been maintained out of tree since 2003. During that
time the driver the primary maintainer was Liam Girdwood and a number
Signed-off-by: Liam Girdwood <[EMAIL PROTECTED]>
Signed-off-by: Graeme Gregory <[EMAIL PROTECTED]>
Signed-off-by: Mike Arthur <[EMAIL PROTECTED]>
Signed-off-by: Mark Brown <[EMAIL PROTECTED]>
Cc: Dmitry Baryshkov <[EMAIL PROTECTED]>
Cc: Stanley Cai <[EMAIL PROTECTED]>
Cc: Rodolfo Giometti <[EMAIL P
Signed-off-by: Liam Girdwood <[EMAIL PROTECTED]>
Signed-off-by: Graeme Gregory <[EMAIL PROTECTED]>
Signed-off-by: Mike Arthur <[EMAIL PROTECTED]>
Signed-off-by: Mark Brown <[EMAIL PROTECTED]>
Cc: Dmitry Baryshkov <[EMAIL PROTECTED]>
Cc: Stanley Cai <[EMAIL PROTECTED]>
Cc: Rodolfo Giometti <[EMAIL P
Updates the 8139too driver to work with recently added
(a724605cb7a66d423a494a395f9a8ba871b8a1eb) declared coherent memory
patch for the Dreamcast.
Jeff - I am assuming you are still the maintainer and I guess Paul
should also ack this as it is SH related.
Signed-off-by: Adrian McMenamin <[EMAIL
On Thu, Feb 07, 2008 at 10:36:20PM +0100, Vegard Nossum wrote:
> With a lot of help from Ingo Molnar and Pekka Enberg over the last couple of
> weeks, we've been able to produce a new version of kmemcheck!
Impressive patch! On the other hand a lot of the interesting
data isn't it kmalloc anymore,
As long as one or more GPIOs on a gpio chip are used its driver should not
be unloaded.
Signed-off-by: Guennadi Liakhovetski <[EMAIL PROTECTED]>
---
Note, that existing drivers do not have to be modified, for example those,
that are always statically linked in the kernel, as long as the respec
On Fri, Feb 08, 2008 at 10:43:42AM +, David Woodhouse wrote:
> On Fri, 2008-02-08 at 10:23 +, Russell King - ARM Linux wrote:
> > That would be misleading though - !CPU_CP15_MMU does not mean we
> > support unaligned accesses. It means that we may have no way to
> > support fixing up unali
> because it's not just an open-coded __tlb_flush_all(), it _disables PGE
> and keeps it so while the MTRR's are changed on all CPUs_.
Yes and?
>
> Your patch adds __flush_tlb_all() which re-enables the PGE bit in cr4,
> see asm-x86/tlbflush.h:
>
> /* clear PGE */
> write_cr4
On Fri, Feb 08, 2008 at 04:02:59PM +0530, Kamalesh Babulal wrote:
> Hi,
>
> The 2.6.24-git18 kernel build fails on the power machine with following
> message
>
> drivers/input/mouse/psmouse-base.c:44: error: __param_proto causes a section
> type conflict
> drivers/input/mouse/psmouse-base.c:44:
Sam Ravnborg wrote:
> I have lost the actual patch.
> But what you see is what happens when you mix const and non-const data
> in the same section.
>
> Look for use of __initdata for const data and replace it with __initconst.
>
> And modpost cannot warn about it as gcc errors out before we look
On Thu, Feb 07, 2008 at 10:21:18PM +0100, Prakash Punnoor wrote:
> On the day of Thursday 07 February 2008 Andi Kleen hast written:
>
> > Replace the old "for all of nvidia" quirk with a quirk containing pci
> > device ID. I goobled this list together from pci.ids and googling and it
> > may be in
Luben Tuikov wrote:
Is there an open iSCSI Target implementation which does NOT
issue commands to sub-target devices via the SCSI mid-layer, but
bypasses it completely?
What do you mean? To call directly low level backstorage SCSI drivers
queuecommand() routine? What are advantages of it?
> - set_cpus_allowed(current, tmp);
> + smp_mb();
> + /* kick all the CPUs so that they exit out of pm_idle */
> + smp_call_function(do_nothing, NULL, 0, 0);
I think the last argument (wait) needs to be 1 to make sure it is
synchronous (for 32/64) Otherwise the patch looks great.
On Fri, 2008-02-08 at 09:45 +, Russell King - ARM Linux wrote:
> If we are serious about allowing ARM to use drivers/Kconfig, then let's
> not get distracted by perfection - by trying to do too many changes in
> one go.
>
> If, today, we conditionalise MTD or IDE on a certain set of symbols,
Serge E. Hallyn wrote:
>
> But note that in either case we need to deal with a bunch of locking.
> So getting back to Pierre's patchset, IIRC 1-8 are cleanups worth
> doing no matter 1. 9-11 sound like they are contentuous until
> we decide whether we want to go with a create_with_id() type app
Hi,
2.6.24-mm1 won't build if CONFIG_X86_PAE is defined:
/home/lkernel/src/linux-2.6.24-mm1/arch/x86/mm/pgtable_32.c: In function
‘pgd_mop_up_pmds’:
/home/lkernel/src/linux-2.6.24-mm1/arch/x86/mm/pgtable_32.c:302:
warning: passing argument 1 of ‘pmd_free’ from incompatible pointer type
/home/
On Fri, Feb 01 2008, Jerome Marchand wrote:
> This patch contain the core infrastructure of enhanced partition
> statistics. It adds to struct hd_struct the same stats data as struct
> gendisk and define basics function to manipulate them.
>
> Signed-off-by: Jerome Marchand <[EMAIL PROTECTED]>
> -
On Fri, Feb 08, 2008 at 09:04:13AM +, David Woodhouse wrote:
> On Thu, 2008-02-07 at 21:23 +0100, Sam Ravnborg wrote:
> > Both situations are trivially fixable by introducing
> > HAVE_IDE and HAVE_MTD.
> > See attached patch.
>
> HAVE_MTD is wrong.
If we are serious about allowing ARM to use
Hi Christoph,
Christoph Hellwig wrote:
> But kgdb traditionally was more than just a simple gdb stub and
> contained hooks all over the place for additional functionality.
> I don't think all this is a good idea and I'd be against it.
>
> I'd be really happy to see a common gdb stub with small ar
This patch enables to export code/name pair of capabilities supported
on the running kernel, under the /sys/kernel/capability .
We can apply it onto the latest Linus's git tree.
Changes from the previous version:
- I added "names/" ans "codes/" directories, and we can use them
to lookup capabili
Serge E. Hallyn wrote:
> Quoting Pavel Emelyanov ([EMAIL PROTECTED]):
>> The Documentation/cgroups.txt file contains the info on how
>> to write some controller for cgroups subsystem, but even with
>> this, one need to write quite a lot of code before developing
>> the core (or copy-n-paste it from
On Friday 08 February 2008 06:53:13 Pavel Machek wrote:
> I believe selct is the way to go here. What do acer-wmi handle?
> Additional buttons? Leds? Temperatures? Fan states?
Enabling wireless, bluetooth and 3G; and exposing the mail LED and backlight.
tc1100-wmi handles wireless and the jog dia
Linus,
Please do
git pull \
git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git for-2.6.25
to get some bug-fixes for powerpc (1 for powermac and 8 for Cell),
plus 3 commits from Badari Pulavarty that implement memory hot-remove
for 64-bit powerpc. These 3 commits have been signed-o
This patch extends the sm501 mfd with 8250 uart support. We're currently
doing this in the board specific r2d-1 code already, but it would be nice to
do move things into the mfd since it's more chip specific than board specific.
Signed-off-by: Magnus Damm <[EMAIL PROTECTED]>
---
drivers/mfd/sm50
This uses the newly introduced owner field in struct gpio_chip to protect
pca953x from being unloaded as long as its GPIOs are in use.
Signed-off-by: Guennadi Liakhovetski <[EMAIL PROTECTED]>
---
diff --git a/drivers/gpio/pca953x.c b/drivers/gpio/pca953x.c
index 0bd594d..89cee66 100644
--- a/dr
On Fri, Feb 08, 2008 at 01:37:11PM +0200, Pekka Enberg wrote:
> Hi Andi,
>
> On Feb 8, 2008 1:55 PM, Andi Kleen <[EMAIL PROTECTED]> wrote:
> > Also i'm not sure how you handle initializedness of DMAed data
> > (like network buffers). Wouldn't you need hooks into pci_dma_*
> > for this?
>
> If the
The source code for this driver is currently located in drivers/char, and
given that this is not an x86 processor feature, it shouldn't live in the
x86 Kconfig.
So lets move it to the Kconfig for drivers/char instead, and just add
a dependency on x86.
Signed-off-by: Carlos Corbacho <[EMAIL PROTEC
As reported at:
https://bugs.gentoo.org/show_bug.cgi?id=203196
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/152689
This unbranded bluetooth USB dongle causes the following message to
repeatedly appear in the kernel logs:
hci_scodata_packet: hci0 SCO packet for unknown con
On Fri, Feb 08, 2008 at 01:18:37PM +0100, Vegard Nossum wrote:
> On 2/8/08, Andi Kleen <[EMAIL PROTECTED]> wrote:
> > Your assumption that only the string instructions can take
> > multiple page faults seems a little dangerous too.
>
> Yes, this is true. I cannot guarantee that there are no other
When trying to put some stress on qemu by running the xfs testsuite
I get the following:
debian:~/xfs-cmds/xfstests# sh check
[ 438.166822] SGI XFS with ACLs, security attributes, realtime, large block
numbers, no debug enabled
[ 438.185557] SGI XFS Quota Management subsystem
[ 438.193150] hd
On Feb 9 2008 00:14, Joonwoo Park wrote:
>2008/2/8, rohit h <[EMAIL PROTECTED]>:
>> Hi,
>> I am a kernel newbie.
>> I tried to insmod a C++ module containing classes, inheritance.
>> I am getting 'unresolved symbol' error when I use the 'new' keyword.
>> What could the problem be?
>>
>> What
On Thu, Feb 07, 2008 at 02:42:14PM -0800, Joe Perches wrote:
> On Thu, 2008-02-07 at 16:03 -0500, Jason Baron wrote:
> > make the pr_debug() function dependent upon the new immediate infrastruture.
>
> What's wrong with klogd -c 8 or equivalent?
>
>
Setting the loglevel higher, will not make pr
- Push the BKL down into the line disciplines
- Switch the tty layer to unlocked_ioctl
- Introduce a new ctrl_lock spin lock for the control bits
- Eliminate much of the lock_kernel use in n_tty
- Prepare to (but don't yet) call the drivers with the lock dropped
on the paths that historically hel
On Thu, Feb 07, 2008 at 01:26:04PM -0800, Randy Dunlap wrote:
> > --- a/Documentation/kernel-parameters.txt
> > +++ b/Documentation/kernel-parameters.txt
> > @@ -1494,6 +1494,11 @@ and is between 256 and 4096 characters. It is
> > defined in the file
> > autoconfiguration.
> >
The word "illegal" has a precise dictionary meaning of "prohibited by
law". The error messages are therefore incorrect as so far nobody has
made SCSI violations a criminal offence.
This corrects scsi to match various other subsystems I've slowly been
ridding of this.
Pedantically-signed-off-by:
On Fri, Feb 08, 2008 at 04:13:35PM +0100, Prakash Punnoor wrote:
> On the day of Friday 08 February 2008 Andi Kleen hast written:
> > On Thu, Feb 07, 2008 at 10:21:18PM +0100, Prakash Punnoor wrote:
> > > On the day of Thursday 07 February 2008 Andi Kleen hast written:
> > > > Replace the old "for
On the day of Friday 08 February 2008 Andi Kleen hast written:
> On Thu, Feb 07, 2008 at 10:21:18PM +0100, Prakash Punnoor wrote:
> > On the day of Thursday 07 February 2008 Andi Kleen hast written:
> > > Replace the old "for all of nvidia" quirk with a quirk containing pci
> > > device ID. I goobl
On Fri, 2008-02-08 at 22:59 +0800, Eugene Teo wrote:
> RLIMIT_RTTIME was introduced to allow the user to set a runtime timeout on
> real-time tasks: http://lkml.org/lkml/2007/12/18/218. This patch updates
> /proc//limits with the new rlimit.
Ah, didn't know about that file, thanks!
> Signed-off-
On Fri, 8 Feb 2008, Andi Kleen wrote:
> > Can someone who knows take a minute or two to put a note of the main
> > urls on www.kernel.org or the FAQ, or have I just missed something?
> -mm is not maintained in git, but in quilt format. The latest version is
> on the ftp server in akpm's people
Nicholas A. Bellinger wrote:
- It has been discussed which iSCSI target implementation should be in
the mainstream Linux kernel. There is no agreement on this subject
yet. The short-term options are as follows:
1) Do not integrate any new iSCSI target implementation in the
mainstream Linux kernel
On Feb 8, 2008 1:18 PM, <[EMAIL PROTECTED]> wrote:
> Long ago when the CLONE_THREAD support first went it someone thought it
> would be wise to point /proc/self at /proc/ instead of /proc/.
The last message about this conversation is:
http://lkml.org/lkml/2007/12/1/172
So I thought we would end
On Feb 08, 2008 19:48 +0900, Takashi Sato wrote:
> OK I would like to implement the freeze feature on VFS
> as the filesystem independent ioctl so that it can be
> available on filesystems that have already had write_super_lockfs()
> and unlockfs().
> The usage for the freeze ioctl is the followin
> For now, yes, we should mirror what is going to be in the 2.6.25
kernel
> release. I see the split happening for 2.6.26. So I say leave this
for
> now, it adds support for users of these devices.
It's not that big a of a deal and I'm not sure how much of a pain it
would be to change it, but if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
KaiGai,
Thanks for trying to accommodate me :-)
Kohei KaiGai wrote:
| In addition, Andrew suggested me to export these translation by symlinks
| to reduce the number of invocation of system call.
Yes, I wanted to make use of readlink() instead of o
found some code in misc.c that could be ifdef'ed for KMOD
Signed-off-by: Jiri Olsa <[EMAIL PROTECTED]>
---
drivers/char/misc.c |7 ++-
1 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/drivers/char/misc.c b/drivers/char/misc.c
index a39101f..3455b09 100644
--- a/drivers/char/
Add a function to install a monitor on the page lock waitqueue for a particular
page, thus allowing the page being unlocked to be detected.
This is used by CacheFiles to detect read completion on a page in the backing
filesystem so that it can then copy the data to the waiting netfs page.
Signed-
Recruit a couple of page flags to aid in cache management. The following extra
flags are defined:
(1) PG_fscache (PG_private_2)
The marked page is backed by a local cache and is pinning resources in the
cache driver.
(2) PG_fscache_write (PG_owner_priv_2)
The marked page is be
These patches add local caching for network filesystems such as NFS.
The patches can roughly be broken down into a number of sets:
(*) 01-keys-inc-payload.diff
(*) 02-keys-search-keyring.diff
(*) 03-keys-callout-blob.diff
Three patches to the keyring code made to help the CIFS peop
Check the starting keyring as part of the search to (a) see if that is what
we're searching for, and (b) to check it is still valid for searching.
The scenario: User in process A does things that cause things to be
created in its process session keyring. The user then does an su to
another user
Somebody recently asked me about this patch, so I dug it up for one last
try. I do believe there is value in describing patch tags, and,
certainly, nobody has objected to the idea. Comments from several
reviewers were addressed before the previous posting.
jon
--
Add a document describing the
From: Jens Axboe <[EMAIL PROTECTED]>
vmsplice_to_user() must always check the user pointer and length
with access_ok() before copying. Likewise, for the slow path of
copy_from_user_mmap_sem() we need to check that we may read from
the user region.
Signed-off-by: Jens Axboe <[EMAIL PROTECTED]>
Cc:
Andrew Morton <[EMAIL PROTECTED]> writes:
>> */
>> -static int do_change_type(struct nameidata *nd, int flag)
>> +static noinline int do_change_type(struct nameidata *nd, int flag)
>
> What we could do here is defined a new noinline_because_of_stack_suckiness
> and use that. Reasons:
>
> - self-
There is a big difference between NX and RO. NX absolutely has to be cleared
or the kernel will fail while RO just can be set, but does not need to.
And for a large page area not setting NX if there is a area below
it that needs it is essential, while making it ro is optional again.
This is need
There are multiple call sites and they are not time critical
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
arch/x86/mm/pageattr.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Index: linux/arch/x86/mm/pageattr.c
===
There were some conflicts applying the previous patchkit
to the latest mainline tree; only difference is that I resolved
them.
-Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.
1 - 100 of 586 matches
Mail list logo
