On Wed, 9 Jan 2008 13:16:42 +0900
KAMEZAWA Hiroyuki <[EMAIL PROTECTED]> wrote:
> > +
> > + free = zone_page_state(zone, NR_FREE_PAGES);
> > +
> > + /*
> > +* If we have no swap space, do not bother scanning anon pages
> > +*/
> > + if (nr_swap_pages <= 0)
> > + percent[0] =
(no-one with a g965 mobo who uses the serial port?)
Hi,
I'm trying to figure out a problem that I have with 2 different
motherboards. Both have the Intel G965 chipset, an Intel DG965WH and a
Gigabyte 965G-DS3. What happens is, that datacommunication, either
through normal receiving bytes and via
Andre Noll wrote:
On 17:40, Andi Kleen wrote:
Here's a proposal for some useful code transformations the kernel janitors
could do as opposed to running checkpatch.pl.
Here's my take on drivers/scsi/sg.c. It's only compile-tested on x86-64.
... and x86 with all(yes|mod)config. :)
On Wed, Jan 09, 2008 at 01:45:09PM +0100, Jan Engelhardt wrote:
>
> On Jan 8 2008 20:08, Miklos Szeredi wrote:
> >> On Tue, 2008-01-08 at 12:35 +0100, Miklos Szeredi wrote:
> >> > +static int reserve_user_mount(void)
> >> > +{
> >> > + int err = 0;
> >> > +
> >> > + spin_lock(&vfsmount
On Wed, 9 Jan 2008, Matthew Wilcox wrote:
> > default:
> > printk("%s: Unimplemented ioctl 0x%x\n", tape->name, cmd);
> > + unlock_kernel();
> > return -EINVAL;
> Surely a bug ... shouldn't this return -ENOTTY?
What POSIX states [1]:
[EINVAL]
The request
On Tue, 8 Jan 2008, David Miller wrote:
> You can set a kprobe on the x86 fault handler to do things like
> mmiotrace.
Currently, on x86, you can not, because:
fastcall void __kprobes do_page_fault( ... );
--
Jiri Kosina
--
To unsubscribe from this list: send the line "unsubscribe linu
Am Mittwoch, 9. Januar 2008 schrieb Fengguang Wu:
> On Wed, Jan 09, 2008 at 01:22:33PM +0100, Joerg Platte wrote:
> > Am Mittwoch, 9. Januar 2008 schrieb Fengguang Wu:
> >
> > Thank your for the hint with the filesystems!
> >
> > > Thank you for the clue. However I cannot reproduce the bug on
> > >
> ...this will break with FUSE enabled, right? (Minor security hole by
> allowing users to stop c-a-delete, where none existed before?)
Yup (or I don't know, I'm sure there was or is some problem with
ptrace, that could be used to create unkillable processes).
Fuse could actually be fixed to exit
* Vaidyanathan Srinivasan <[EMAIL PROTECTED]> wrote:
> I will watch this during the experiments. I have been using klog
> application to dump relayfs data. I did run powertop and top as well,
> I will bind them to certain CPUs and isolate their impact.
>
> I believe the margin of error would
> case EMFILE:
> error ("mount table full"); break;
OK, we could go with EMFILE, but the message should be changed to
something like "maximum unprivileged mount count exceeded".
Miklos
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
From: Jiri Kosina <[EMAIL PROTECTED]>
Date: Wed, 9 Jan 2008 14:19:58 +0100 (CET)
> On Tue, 8 Jan 2008, David Miller wrote:
>
> > You can set a kprobe on the x86 fault handler to do things like
> > mmiotrace.
>
> Currently, on x86, you can not, because:
>
> fastcall void __kprobes do_page_
> I'm not saying fuse is worthless. It is a nice toy for single-user
> systems. But I do not think we should be merging "allow ordinary users
> to mount their own fuse's" before issues above are fixed.
I think multi user systems are not all that interesting. And I
suspect very few of them want re
On 14:17, Richard Knutsson wrote:
> Would had preferred:
>
> if (x) {
>result = -E;
>goto out;
> }
>
> then:
>
> result = -E;
> if (x)
>goto out;
>
AFAIK, the second form is preferred in Linux because it is better
readable and it generates slightly better code.
Thanks for
@ Wed, Jan 09, 2008 at 10:22:08AM +0800, WANG Cong wrote:
>
> >"I will use ...
> >http://images.google.cz/images?svnum=100&um=1&hl=cs&client=firefox-a&rls=org.mozilla%3Acs%3Aofficial&q=I+will+use+Google+before&btnG=Hledat+obr%C3%A1zky
> >... for making translations..."
> >http://www.google.com/tra
Hi!
> > ...this will break with FUSE enabled, right? (Minor security hole by
> > allowing users to stop c-a-delete, where none existed before?)
>
> Yup (or I don't know, I'm sure there was or is some problem with
> ptrace, that could be used to create unkillable processes).
>
> Fuse could actual
Vous m'avez dit récemment :
> On 2008-01-08, John Stoffel <[EMAIL PROTECTED]> wrote:
>> Look at your filesystems, using 'tune2fs' and see if the ext3 journal
>> is actually turned on and used. If it's not, then I can see why
>> you're having problems on reboots.
>
> Journalling is on, but it's
On Jan 9, 2008 1:25 PM, Theodore Tso <[EMAIL PROTECTED]> wrote:
> On Wed, Jan 09, 2008 at 10:54:11AM +0100, Martin Schwidefsky wrote:
> > Actually you can force Windows to accept a hardware clock in UTC:
> > HKEY_LOCAL_MACHINE/SYSTEMCurrentControlSetControl/TimeZoneInformation/RealTimeIsUniversal
>
Hello,
I'd like to ask your help with strange behavior of kernel 2.6.21-7.
Sometimes it becomes to inoperable state and the system time stops. Also
I couldn't ping the system that moment. But if I try to use keyboard the
system will wake up and begin working. In other words all programs are
c
On Wed 2008-01-09 14:48:53, Miklos Szeredi wrote:
> > I'm not saying fuse is worthless. It is a nice toy for single-user
> > systems. But I do not think we should be merging "allow ordinary users
> > to mount their own fuse's" before issues above are fixed.
>
> I think multi user systems are not a
> Yes, very good point. Does checkpatch.pl enforce diff -p already?
> If not, should it?
I don't think it should. That would reject a lot of perfectly good
patches.
-Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
On Fri, 28 Dec 2007, Adolfo R. Brandes wrote:
> It is a 2.4 Ghz RF remote, and its receiver connects via USB to the
> computer, registering two devices, a keyboard and a mouse. From
> /proc/bus/input/devices:
> I: Bus=0003 Vendor=0c16 Product=0002 Version=0110
> N: Name="Gyration Gyration RF Te
> Rank 1: __ieee80211_rx
> Warning at net/mac80211/rx.c:1672
> Reported 6 times (11 total reports)
> Same issue that was ranked 2nd last week
> Johannes has diagnosed this as a driver bug in the iwlwifi drivers
> More info: http://www.kerneloops.org/search.php?search=
> > > I'm not saying fuse is worthless. It is a nice toy for single-user
> > > systems. But I do not think we should be merging "allow ordinary users
> > > to mount their own fuse's" before issues above are fixed.
> >
> > I think multi user systems are not all that interesting. And I
> > suspect
> nope, it's a 64-bit setup/dependency bug/problem: the vsyscall mappings
> are installed via an __initcall, and that's too late for early use. The
> combo patch below fixed the crash for me, does it work on your box too?
That gives
/home/lsrc/quilt/linux/arch/x86/kernel/setup_64.c: In function
On 2008-01-09, Mathieu SEGAUD <[EMAIL PROTECTED]> wrote:
> fix your hardware clock then
It displays just the right time. On boot anyway. (Linux has had some
serious problems keeping the time after the switch from 2.6.7 to 2.6.14,
advanding even 15 minutes a day -- that ntpd doesn't seem to be able
On Wednesday 09 January 2008 11:47:11 Ingo Molnar wrote:
> * Andi Kleen <[EMAIL PROTECTED]> wrote:
> > There's one Jan pointed out: iounmap does not subtract the guard page
> > size so it ends up resetting one page too much. That is probably what
> > causes your problem. But again you should be pas
> You can set a kprobe on the x86 fault handler to do things like
> mmiotrace.
That would mean that if the kprobe faults it goes into an endless loop.
Most of do_page_fault() is not really safe for kprobes.
-Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
On 09/01/2008, Anton Salikhmetov <[EMAIL PROTECTED]> wrote:
> Since no reaction in LKML was recieved for this message it seemed
> logical to suggest closing the bug #2645 as "WONTFIX":
>
> http://bugzilla.kernel.org/show_bug.cgi?id=2645#c15
>
> However, the reporter of the bug, Jacob Oestergaard, i
On 09-01-08 10:34, Frans Pop wrote:
Bjorn:
Len Brown wrote:
Well, yes, the warning is actually new as well. Previously your kernel
just silently ignored 8 more mem resources than it does now it seems.
Given that people are hitting these limits, it might make sense to just
do away with the w
Hello,
On Wed, January 9, 2008 05:39, Tetsuo Handa wrote:
> Hello.
>
> Indan Zupancic wrote:
>> I think you focus too much on your way of enforcing filename/attributes
>> pairs.
> So?
So that you miss alternatives and don't see the bigger picture.
>
>> The same can be achieved by creating the de
On Wed, 9 Jan 2008 14:52:14 +0300
Al Boldi <[EMAIL PROTECTED]> wrote:
> Ok, but let's look at this a bit more opportunistic / optimistic.
You can't play fast and loose with data integrity.
Besides, if we looked at things optimistically, we would conclude
that no fsck will be needed, ever :)
>
On Wed, Jan 09, 2008 at 07:18:46AM -0800, Arjan van de Ven wrote:
> On Wed, 9 Jan 2008 03:17:37 + (GMT)
> Dave Airlie <[EMAIL PROTECTED]> wrote:
>
> > So all distros with 2.6.24 kernels are useless to mmiotrace I don't
> > see why leaving things as is until a suitable replacement mechanism
> >
* Andi Kleen <[EMAIL PROTECTED]> wrote:
> > nope, it's a 64-bit setup/dependency bug/problem: the vsyscall mappings
> > are installed via an __initcall, and that's too late for early use. The
> > combo patch below fixed the crash for me, does it work on your box too?
>
> That gives
>
> /home/
Rusty Russell wrote:
On Wednesday 09 January 2008 11:21:59 Andrew Morton wrote:
[...]
And the fact that incoming arg `namebuf' MUST point at a
KSYM_NAME_LEN-sized buffer could be better communicated by using a
dedicated struct for this, or by giving the arg a type of `char
namebuf[KSYM_NAME_LEN]
* Andi Kleen <[EMAIL PROTECTED]> wrote:
> On Wed, Jan 09, 2008 at 07:18:46AM -0800, Arjan van de Ven wrote:
> > On Wed, 9 Jan 2008 03:17:37 + (GMT)
> > Dave Airlie <[EMAIL PROTECTED]> wrote:
> >
> > > So all distros with 2.6.24 kernels are useless to mmiotrace I don't
> > > see why leaving t
VUB Stefan Seidel <[EMAIL PROTECTED]> writes:
> I have the following system here: two dual-core Xeon 5130 on an Intel
> S5000V-SA motherboard. The kernel detects 4 CPUs, from what I learn
> through /proc/cpuinfo, these are the 4 cores (two per
> package). However, I think it should be 8 logical pr
Christer Weinigel wrote:
Did I miss anyting?
Nothing that seems *crucial* going forward for Linux. The fate of
"legacy machines" is really important to get right.
I have a small suggestion in mind that might be helpful in the future:
the "motherboard resources" discovered as PNP0C02 devi
On Wed, 9 Jan 2008 03:17:37 + (GMT)
Dave Airlie <[EMAIL PROTECTED]> wrote:
> So all distros with 2.6.24 kernels are useless to mmiotrace I don't
> see why leaving things as is until a suitable replacement mechanism
> can be used..
you work for a distro.. surely you can convince your own dist
Hi,
In windows one can configure at what point the uart will trigger an
interrupt. E.g. 1, 4, 8 or 14 bytes received. Setserial doesn't let you
and I saw in the sources of the serial driver no hint that it is
supported in linux at all. Also in MAINTAINERS I saw that sreial is
orphaned. Can someone
Jens Axboe <[EMAIL PROTECTED]> writes:
>
> So how does it work? Instead of punting IO to a thread and passing it
> through the page cache, we instead attempt to send the IO directly to the
Great -- something like this was needed for a long time.
> - The file block mappings must not change while l
Folkert van Heusden <[EMAIL PROTECTED]> writes:
> (no-one with a g965 mobo who uses the serial port?)
I do.
The typical problem is to use the wrong connector -- there
are three different ones floating around, but all fit on the
same pins on the motherboard.
Has nothing to do with Linux of cours
Johannes Berg wrote:
Rank 1: __ieee80211_rx
Warning at net/mac80211/rx.c:1672
Reported 6 times (11 total reports)
Same issue that was ranked 2nd last week
Johannes has diagnosed this as a driver bug in the iwlwifi drivers
More info: http://www.kerneloops.or
Hi,
This very small patch:
ipc-convert-handmade-min-to-min.patch
introduces a new warning when compiling the -mm kernel:
.../linux-2.6.24-rc6-mm1/ipc/msg.c: In function `do_msgrcv':
.../linux-2.6.24-rc6-mm1/ipc/msg.c:939: warning: comparison of distinct pointer
types lacks a cast
I don't kno
On Wed, Jan 09, 2008 at 04:22:08PM +0100, Ingo Molnar wrote:
>
> * Andi Kleen <[EMAIL PROTECTED]> wrote:
>
> > > nope, it's a 64-bit setup/dependency bug/problem: the vsyscall mappings
> > > are installed via an __initcall, and that's too late for early use. The
> > > combo patch below fixed th
> In windows one can configure at what point the uart will trigger an
> interrupt. E.g. 1, 4, 8 or 14 bytes received. Setserial doesn't let you
> and I saw in the sources of the serial driver no hint that it is
> supported in linux at all. Also in MAINTAINERS I saw that sreial is
> orphaned. Can so
On 09-01-08 06:30, Christer Weinigel wrote:
On Tue, 08 Jan 2008 18:52:42 -0800
Zachary Amsden <[EMAIL PROTECTED]> wrote:
What is the outcome of this thread? Are we going to use timing based
port delays, or can we finally drop these things entirely on 64-bit
architectures?
I a have a doubly
2008/1/9, Jesper Juhl <[EMAIL PROTECTED]>:
> I've only looked briefly at your patch but it seems resonable. I'll
> try to do some testing with it later.
Jesper, thank you very much for your answer!
In fact, I tested my change quite extensively using test cases for the
mmap() and msync() system ca
On Wed, 09 Jan 2008 18:16:02 +0900,
Tejun Heo <[EMAIL PROTECTED]> wrote:
> This isn't supported. sysfs doesn't allow parents to die first and the
> dangling children to be salvaged using sysfs_move().
But (with the sysfs bugs fixed) it will return an error, won't it? It
seems the bluetooth code
Hi,
On Tue, 2008-01-08 at 18:16 -0500, Chuck Ebbert wrote:
> On 01/07/2008 02:06 PM, Brice Figureau wrote:
>
> > Thanks for the answer.
> > I'm using whatever is the default mount option (which I think is
> > data=ordered). The only other mount option I use is nodiratime,noatime.
> >
> > Note
Am Montag, 7. Januar 2008 schrieb Mauro Carvalho Chehab:
>
> Hans Verkuil (1):
> V4L/DVB (6916): ivtv: udelay has to be changed *after* the eeprom
> was read, not before
boils down to this patch:
89dab3573aa1d95fd222ee4551f964bfa4c16823
drivers/media/video/ivtv/ivtv-driver.c |4
d
Nick Piggin <[EMAIL PROTECTED]> wrote:
> It is to make everybody happy. Especially in code that everyone works
> on like mm/ and fs/, you can't just have everybody following their own
> slightly different conventions.
Conventions are what people agree they are.
Anyway, I've attached a revised pa
* Harvey Harrison <[EMAIL PROTECTED]> wrote:
> Use the fixup_exception() helper instead of the open-coded
> search_extable() users.
thanks, applied.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majord
* Harvey Harrison <[EMAIL PROTECTED]> wrote:
> Small step towards unifying traps_32|64.c. No functional changes.
> Pull out a small helper from an if() statement in die().
>
> Marked as __kprobes as eventually we will want to call this from
> do_page_fault similar to how X86_64 does it.
tha
* Harvey Harrison <[EMAIL PROTECTED]> wrote:
> Should be the last of the error_code tests that could use the PF_
> defines. Makes X86_32|64 a little closer.
thanks, applied.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EM
* Paolo Ciarrocchi <[EMAIL PROTECTED]> wrote:
> Simple coding style fixes.
thanks, applied. If this interfers with ongoing drivers/pci work then
we'll rearrange it (drop/reapply) to around those changes.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
On Wed, 09 Jan 2008 09:29:41 +0100, Geert Uytterhoeven said:
> We have plenty of DB9-to-RJ45 at work. Very useful when abusing the
> Ethernet cabling in the wall for serial connections (also used for
> phone).
>
> Maybe surprisingly to you, I haven't seen the RJ11 variant ;-)
I have to admit, th
On Wed, 9 Jan 2008, Roland McGrath wrote:
>
> The show_task function invoked by sysrq-t et al displays the
> pid and parent's pid of each task. It seems more useful to
> show the actual process hierarchy here than who is using
> ptrace on each process.
Hmm. It could go both ways. If the proble
Hi Dmitry,
* Micah Parrish <[EMAIL PROTECTED]>:
> Devices like the HP Integrated Remote Console Virtual Mouse, which are
> standard equipment on all Proliant and Integrity servers, produce
> absolute coordinates instead of relative coordinates. This is done to
> synchronize the position of the mo
* Andi Kleen <[EMAIL PROTECTED]> wrote:
> On Wed, Jan 09, 2008 at 04:22:08PM +0100, Ingo Molnar wrote:
> >
> > * Andi Kleen <[EMAIL PROTECTED]> wrote:
> >
> > > > nope, it's a 64-bit setup/dependency bug/problem: the vsyscall mappings
> > > > are installed via an __initcall, and that's too lat
Hello,
> >>> Got this when doing usual looping over /proc entries on fresh test
> >>> kernel:
> >> What is the usual looping, please?
> >
> > #!/bin/bash
> >
> > for i in `find /proc -type f`; do
> > echo -n "cat $i > /dev/null ... ";
> > ( cat $i > /dev/null & );
> >
Add device_init_wakeup to init wakeup.
Signed-off-by: Dmitry Baryshkov <[EMAIL PROTECTED]>
diff --git a/drivers/power/pda_power.c b/drivers/power/pda_power.c
index d98622f..28360e8 100644
--- a/drivers/power/pda_power.c
+++ b/drivers/power/pda_power.c
@@ -207,6 +207,8 @@ static int pda_power_prob
On Jan 9, 2008 3:23 PM, Pierre Ossman <[EMAIL PROTECTED]> wrote:
> On Wed, 9 Jan 2008 11:21:40 +0800
> "Cai, Cliff" <[EMAIL PROTECTED]> wrote:
>
> >
> > Hi,all
> >
> > I'd like to say something about this issue.
> > Currently,the blackfin on chip SD host ONLY support 1-bit MMC while
> > support 1-
On Jan 9, 2008 7:54 PM, Sam Ravnborg <[EMAIL PROTECTED]> wrote:
> > >
> > > What is generally seen as a showstopper is the amount of work needed
> > > to do the translation - and keeping it up-to-date.
> >
> > Sure. The key is to have more participants to involve. The work can't
> > be done witho
Okay. I can:
(1) Have cachefilesd (the daemon) pass a security context string to the
cachefiles kernel module, which can then convert it to a secID. It'll
require a security_secctx_to_secid() function, but I'm fairly certain I
have a patch to add such kicking around somewhere.
* Mathieu Desnoyers <[EMAIL PROTECTED]> wrote:
> static inline int vmalloc_fault(unsigned long address)
> {
> unsigned long pgd_paddr;
> pmd_t *pmd_k;
> pte_t *pte_k;
> /*
> * Synchronize this task's top level page-table
> * with the 'reference' p
* Ingo Molnar ([EMAIL PROTECTED]) wrote:
>
> (kprobes folks Cc:-ed)
>
> * David Miller <[EMAIL PROTECTED]> wrote:
>
> > From: Christoph Hellwig <[EMAIL PROTECTED]>
> > Date: Wed, 9 Jan 2008 08:19:45 +0100
> >
> > > On Wed, Jan 09, 2008 at 03:55:20AM +, Dave Airlie wrote:
> > > > now because
> serial8250_set_mctrl(&up->port, up->port.mctrl);
> spin_unlock_irqrestore(&up->port.lock, flags);
> }
>
> But I don't know how to interface this to an ioctl or so.
tty ioctl calls both ldisc and driver ioctls (in your case the
serial_core ioctl). The triggers get recomputed in t
David Howells <[EMAIL PROTECTED]> wrote:
> Now, I recall the addition of another security class being mentioned, which
> presumably would give something like:
>
> avc_has_perm(daemon_tsec->sid, nominated_sid,
>SECCLASS_CACHE, CACHE__USE_AS_OVERRIDE, NULL);
H... I c
On Tue, 1 Jan 2008, H. Peter Anvin wrote:
> It's specifically a side effect *we don't care about*, except in the
> by-now-somewhat-exotic case of 386+387 (where we indeed can't use it once user
> code has touched the FPU -- but we can fall back to 0x80 on those, a very
> small number of systems.)
On Wed, 9 Jan 2008 14:26:26 +0100 (CET)
Jiri Kosina <[EMAIL PROTECTED]> wrote:
> On Wed, 9 Jan 2008, Matthew Wilcox wrote:
>
> > > default:
> > > printk("%s: Unimplemented ioctl 0x%x\n", tape->name, cmd);
> > > + unlock_kernel();
> > > return -EINVAL;
> > Surely a bu
We (the -stable team) are announcing the release of the 2.6.23.13 kernel.
It contains one serious fix for the w83627ehf.c hardware monitoring
driver. If you use this driver, PLEASE, upgrade to this kernel version.
To quote the developer, Jean Delvare:
I have had a private report that this
diff --git a/Makefile b/Makefile
index 96c3f02..55edf2f 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 23
-EXTRAVERSION = .12
+EXTRAVERSION = .13
NAME = Arr Matey! A Hairy Bilge Rat!
# *DOCUMENTATION*
diff --git a/drivers/hwmon/w83627ehf.c b/driver
On Tue, Jan 08, 2008 at 02:33:17PM -0500, Jeff Layton wrote:
> - struct svc_serv * serv;
> - int error = 0;
> + struct svc_serv *serv;
> + struct svc_rqst *rqstp;
> + int error = 0;
>
> mutex_lock(&nlmsvc_mutex);
> /*
>
On Wed, Jan 09, 2008 at 05:30:18PM +0100, Ingo Molnar wrote:
>
> * Andi Kleen <[EMAIL PROTECTED]> wrote:
>
> > On Wed, Jan 09, 2008 at 04:22:08PM +0100, Ingo Molnar wrote:
> > >
> > > * Andi Kleen <[EMAIL PROTECTED]> wrote:
> > >
> > > > > nope, it's a 64-bit setup/dependency bug/problem: the v
HNY. :-)
Bartlomiej Zolnierkiewicz wrote:
* Move wait_hwif_ready() documentation before this function.
* Fix trailing whitespaces.
* s/wait-for-busy/wait-for-non-busy/
* Remove no longer valid comment about the current code behavior.
* Docbook-ize it.
* Rename wait_hwif_ready() t
On Tue, Jan 08, 2008 at 02:33:18PM -0500, Jeff Layton wrote:
> ...and only have lockd exit when the last reference is dropped.
>
> The problem is this:
>
> When a lock that a client is blocking on comes free, lockd does this in
> nlmsvc_grant_blocked():
>
> nlm_async_call(block->b_call, NLMP
On Tue, 8 Jan 2008, Yinghai Lu wrote:
> [PATCH] x86_64: cleanup setup_node_zones called by paging_init
The whitespace cleanups make it difficult to review the patch. Could you
send those separately?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a mess
Hi, I wrote:
* Move wait_hwif_ready() documentation before this function.
* Fix trailing whitespaces.
* s/wait-for-busy/wait-for-non-busy/
* Remove no longer valid comment about the current code behavior.
* Docbook-ize it.
* Rename wait_hwif_ready() to ide_port_wait_ready().
Si
On Wednesday 09 January 2008 03:41:16 Tejun Heo wrote:
> Ondrej Zary wrote:
> > Hello,
> > I switched to libata drivers for my onboard PATA controller (PIIX4)
> > recently. Everything works fine except that kernel tries to start not
> > only my hard drive (sda) but also LS-120 floppy drive (sdb) wh
Jiri Kosina wrote:
thanks a lot for the detailed and accurate report. Yes, this device would
require a mapping quirk for the non-working keys. The endlessly repeating
key might need something more sophisticated. I will look into your report
and send you a patch to test in a few days. Currently,
On Tue, Jan 08, 2008 at 02:33:15PM -0500, Jeff Layton wrote:
> lockd_start_done is a global var that can be reused if lockd is
> restarted, but it's never reinitialized. On all but the first use,
> wait_for_completion isn't actually waiting on it since it has
> already completed once.
I don't thin
On Wed, 9 Jan 2008, Tetsuo Handa wrote:
> Did you try MSG_WAITALL flag? See "man 2 recv".
> A TCP socket handles data in bytes.
> You cannot complain if the amount received by recv() is smaller than expected
> unless you use MSG_WAITALL flag.
Yes. It made no difference, as noted in the comments i
Pavel Machek wrote:
Of course, if we'd been using kinit, "soft panic" would
have been done exclusively in userspace...
What's the status of kinit, btw?
Pavel
It's bitrotted a bit since it was first rejected. It wouldn't take too
much
On Wed, 9 Jan 2008 17:35:42 +
Christoph Hellwig <[EMAIL PROTECTED]> wrote:
> I don't think we'll need lockd_start_done anymore after the kthread
> conversion. When kthread_run returns the thread it created is
> guaranteed to have run until it scheduled away.
>
Makes sense. My only concern i
On Wed, 9 Jan 2008 17:45:06 +
Christoph Hellwig <[EMAIL PROTECTED]> wrote:
> On Tue, Jan 08, 2008 at 02:33:17PM -0500, Jeff Layton wrote:
> > - struct svc_serv * serv;
> > - int error = 0;
> > + struct svc_serv *serv;
> > + struct svc_rqst *rqstp;
> > + int
On Wed, 2008-01-09 at 16:27 +0100, Rene Herman wrote:
> On 09-01-08 06:30, Christer Weinigel wrote:
> I'd not expect very time crtical. The current outb_p use gives a delay
> somewhere between .5 and 2 microseconds as per earlier survey meaning a
> udelay(1) or 2 would be enough -- again, at the
On Wed, 2008-01-09 at 16:51 +, David Howells wrote:
> Okay. I can:
>
> (1) Have cachefilesd (the daemon) pass a security context string to the
> cachefiles kernel module, which can then convert it to a secID. It'll
> require a security_secctx_to_secid() function, but I'm fairly c
On Wed, Jan 09, 2008 at 01:05:54PM -0500, Jeff Layton wrote:
> Makes sense. My only concern is that we make sure this is behavior we
> can count on in the future and not just an artifact of the current
> kthread implementation. If that's the case, then I'll plan to remove it
> on the next respin.
>> Or do you mean the syscall return value ending up in the userspace
>> completion event ring? That's mostly about being able to wait for
>> pending syslets to complete.
>
> The latter. A ring is optimal for processing a huge number of requests, but
> if you're really going to be firing off s
On Wed, 2008-01-09 at 11:26 +1100, Benjamin Herrenschmidt wrote:
> > Christoph,
> >
> > it is generic code, it works by patching the module you load and is in
> > no way nvidia specific, I think we should revert your chance
> > as the notifiers have a valid user and one it has been planned to ups
Maciej W. Rozycki wrote:
On Tue, 1 Jan 2008, H. Peter Anvin wrote:
It's specifically a side effect *we don't care about*, except in the
by-now-somewhat-exotic case of 386+387 (where we indeed can't use it once user
code has touched the FPU -- but we can fall back to 0x80 on those, a very
small
Zachary Amsden wrote:
I'm speaking specifically in terms of 64-bit platforms here. Shouldn't
we unconditionally drop outb_p doing extra port I/O on 64-bit
architectures? Especially considering they don't even have an ISA bus
where the decode timing could even matter?
Why should the bitsize
On Wed, Jan 09, 2008 at 01:18:44PM -0500, Pavel Roskin wrote:
> notification without patching the kernel. But if no such solution is
> found, I would also support reverting the patch that removed fault
> notifiers on i386.
With your fixation on not patching the kernel you sound like a windows
dev
On Wed, Jan 09, 2008 at 10:17:24AM -0800, Zachary Amsden wrote:
> On Wed, 2008-01-09 at 16:27 +0100, Rene Herman wrote:
> > On 09-01-08 06:30, Christer Weinigel wrote:
> > I'd not expect very time crtical. The current outb_p use gives a delay
> > somewhere between .5 and 2 microseconds as per earl
[PATCH] x86_64: cleanup setup_node_zones called by paging_init v2
setup_node_zones calcuates some variable but only use them when
FLAT_NODE_MEM_MAP is set
so change the MACRO postion to avoid calculating.
also change it to static
Signed-off-by: Yinghai Lu <[EMAIL PROTECTED]>
Index: linux-2.6/
Adrian Bunk wrote:
I don't think the latter statement was true - AFAIR there are Alphas
with ISA slots.
See subject line.
-hpa
--
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://vge
On Wed, 9 Jan 2008 16:43:51 +0100
Hans-Peter Jansen <[EMAIL PROTECTED]> wrote:
> + /* The mspx4xx chips need a longer delay for some reason */
> + if (!(itv->hw_flags & IVTV_HW_MSP34XX))
> + itv->i2c_algo.udelay = 5;
> +
>
> where the logic in hunk #1 was switched, resulting i
Ingo Molnar wrote:
* Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
Edit / Prefs / Email Preferences / Users to watch
add [EMAIL PROTECTED] to that list and you'll
be notified about new bugs and changes to existing bugs.
Still, I'd like the list to be notified, not only me (eg. I might be
of
On Wed, 9 Jan 2008 17:47:07 +
Christoph Hellwig <[EMAIL PROTECTED]> wrote:
> On Tue, Jan 08, 2008 at 02:33:18PM -0500, Jeff Layton wrote:
> > ...and only have lockd exit when the last reference is dropped.
> >
> > The problem is this:
> >
> > When a lock that a client is blocking on comes fr
On Wed, Jan 09, 2008 at 01:36:21PM -0500, Jeff Layton wrote:
> I don't see a good alternative though. We need to be able to drop the
> and check the refcount in nlmsvc_unlink_block. That function is called
> from lockd, and we can't have lockd call kthread_stop on itself.
>
> If you see a better w
101 - 200 of 442 matches
Mail list logo
