kernel August 2008

kernel@lists.fedoraproject.org

28 participants
21 discussions

[PATCH] nfs: BUG_ON in nfs_follow_mountpoint
by Steve Dickson 29 Aug '08

29 Aug '08

Here is a patch that was posted a while back on lkml that does indeed stop a OOPS.... I notice that is not in the latest rawhide kernel... We might want to think about taking this one early due to the obvious... steved. From: "Denis V. Lunev" <den(a)openvz.org> Unfortunately, BUG_ON(IS_ROOT(dentry)) can happen inside nfs_follow_mountpoint with NFS running Fedora 8 using a specific setup. See https://bugzilla.redhat.com/show_bug.cgi?id=458622 So the situation should be handled on NFS client gracefully. Signed-off-by: Denis V. Lunev <den(a)openvz.org> Cc: Trond Myklebust <Trond.Myklebust(a)netapp.com> Cc: J. Bruce Fields <bfields(a)fieldses.org> Signed-off-by: Andrew Morton <akpm(a)linux-foundation.org> --- fs/nfs/namespace.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff -puN fs/nfs/namespace.c~nfs-bug_on-in-nfs_follow_mountpoint fs/nfs/namespace.c --- a/fs/nfs/namespace.c~nfs-bug_on-in-nfs_follow_mountpoint +++ a/fs/nfs/namespace.c @@ -105,7 +105,10 @@ static void * nfs_follow_mountpoint(stru dprintk("--> nfs_follow_mountpoint()\n"); - BUG_ON(IS_ROOT(dentry)); + err = -EIO; + if (IS_ROOT(dentry)) + goto out_err; + dprintk("%s: enter\n", __func__); dput(nd->path.dentry); nd->path.dentry = dget(dentry); _

2 2

Potenzprobleme? Mit uns nicht mehr
by Mike Wiggett-Bassett 28 Aug '08

28 Aug '08

Online bestellen - original Qualitaet - 100% wirksam Unsere Kunden: - Sex ist befriedigender denn je. Stress und Leistungsdruck verschwinden. Sie ist nie wieder frustriert, ich habe keine Angst mehr zu versagen. Es ist ein wundervolles koerperliches Erlebnis, dem ein genauso tiefes Gefuehl folgt. - Das Beste an Vi. ist die Sicherheit, dass man "mit Autopilot fliegt", dass man entspannt und ohne Sorgen zur Sache kommen kann, dass der Staender auch haelt, auch wenn man unterbrochen wird (die Kinder klopfen an die Schlafzimmertuer, der Hund bellt, das Kondom sitzt schlecht). Wenn man Vi. bewusst anwendet, kann es auch der Partnerin gegenueber ein grosses Geschenk sein. Nur ein Rat: Sagen Sie ihr nicht, dass Sie es verwenden, das weibliche Selbstwertgefuehl ist genauso verletzlich wie das unsere. Angebote des Monats: NEU - Vi. Super Active 100 mg 30 Tab. 81,08 Euro Vi. 10 Tab. 100 mg + Ci. 10 Tab. x 20 mg 48,95 Euro Vi. 10 Tab. 22,60 Euro Vi. 30 Tab. 55,00 Euro - Sie sparen: 17,00 Euro Vi. 60 Tab. 82,70 Euro - Sie sparen: 53,00 Euro Vi. 90 Tab. 118,00 Euro - Sie sparen: 85,00 Euro Ci. 10 - 27,00 Euro Ci. 20 - 54,00 Euro - Sie sparen: 2,00 Euro Ci. 30 - 72,00 Euro - Sie sparen: 11,00 Euro - bequem und diskret online bestellen. - Visa verifizierter Onlineshop - keine versteckte Kosten - diskrete Verpackung - diskrete Zahlung - kein peinlicher Arztbesuch erforderlich - kostenlose, arztliche Telefon-Beratung - kein langes Warten - Auslieferung innerhalb von 2-3 Tagen Bestellen Sie noch heute und vergessen Sie Ihre Enttaeuschungen, anhaltende Versagensaengste und wiederholte peinliche Situationen http://img60.imageshack.us/img60/4697/jgzpewbigyg4.swf

1 0

boot failures on very-large systems with CONFIG_SYSFS_DEPRECATED not set
by Doug Chapman 26 Aug '08

26 Aug '08

Sometime leading up to the F9 kernel my very large ia64 system (64 cpu 1TB ram, bunch of PCI busses and I/O) fails to boot. It appears to be something in how nash/mkinitrd gets information from sysfs. Since this is an early boot-time issue and nash isn't very easy to debug I am having trouble getting to the root of the issue (but I am still investigating). I have however found what change triggered this. The default config file used to have CONFIG_SYSFS_DEPRECATED=y set. Upstream kernel commit d47846c5866b7d98a1173c86a39d810a06647329 renamed this to CONFIG_SYSFS_DEPRECATED_V2. It appears the default is still "y" however somehow with the transition the Fedora kernel now has this off. If possible I would like to see this get set to "y" for now. I will continue to debug this as it certainly _should_ boot just fine without this set. Even if we just turn it on for ia64 that works for me (but I imagine some new big x86_64 systems may run into it once they grow this large). thanks, - Doug

2 1

UNIX Process range 32769-65535 impossible?
by todd.e.rinaldo＠jpmorgan.com 25 Aug '08

25 Aug '08

Hi, We have a need to increase the kernel pid_max. Right now it's at the default 32768. The maximum allowable we can increase to is 99,999 due to 3rd party vendor limitations. When we increased it to that value this weekend, we noticed that even though next pid increased sequentially, the range 32769-65535 was explicitly skipped. I note that the range 32769-65535 would be the negative numbers in a signed 2 byte int. This indicates to me that maybe there is some sort of design/legacy issue forcing this behaviour. Because we can only increase to 99,9999, not having access to the above range has limited our available pids by 1/3. Could anyone point me to some sort of documentation explaining this logic? Thanks for your help, Todd Rinaldo Generally, this communication is for informational purposes only and it is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. In the event you are receiving the offering materials attached below related to your interest in hedge funds or private equity, this communication may be intended as an offer or solicitation for the purchase or sale of such fund(s). All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to UK legal entities.

1 0

You are nominated for a Ph.d
by Merle Rosario 24 Aug '08

24 Aug '08

WHAT A GREAT IDEA! We provide a concept that will allow anyone with sufficient work experience to obtain a fully verifiable University Degree. Bachelors, Masters or even a Doctorate. For US: 1.781.634.7970 Outside US: +1.781.634.7970 "Just leave your NAME & PHONE NO. (with CountryCode)" in the voicemail. Our staff will get back to you in next few days!

1 0

Découvre mon profil Facebook
by Arafat Bouchafra 22 Aug '08

22 Aug '08

J'ai créé mon profil Facebook sur lequel je peux publier mes photos, mes vidéos et des événements. Je souhaite t'ajouter à mes amis pour que tu puisses y accéder. Pour cela, tu dois d'abord t'inscrire à Facebook ! Tu pourras ensuite créer ton propre profil. Merci, Arafat Clique sur ce lien : http://www.facebook.com/p.php?i=1439241295&k=65GUQ4RZQ43M5FGEWE55ST&r&v=2 ___________________ Ce courrier électronique peut contenir des messages publicitaires. Si vous ne souhaitez plus recevoir de messages publicitaires de la part de Facebook, cliquez sur le lien ci-dessous. Les bureaux de Facebook sont situés au 156 University Ave., Palo Alto, CA 94301. http://www.facebook.com/o.php?u=1435671220&k=484b8e

1 0

Arafat Bouchafra added you as a friend on Facebook...
by Facebook 22 Aug '08

22 Aug '08

Arafat added you as a friend on Facebook. We need to confirm that you know Arafat in order for you to be friends on Facebook. To confirm this friend request, follow the link below: http://www.facebook.com/n/?reqs.php ___________________ This e-mail may contain promotional materials. If you do not wish to receive future commercial mailings from Facebook, please click on the link below. Facebook's offices are located at 156 University Ave., Palo Alto, CA 94301. http://www.facebook.com/o.php?u=1435671220&k=484b8e Want to control which emails you receive from Facebook? Go to: http://www.facebook.com/editaccount.php?notifications&md=ZnJpZW5kO2Zyb209MT…

1 0

RFC: split changelog out of spec
by Jarod Wilson 18 Aug '08

18 Aug '08

Hey all, Been toying with the idea of splitting the changelog out of the kernel spec itself, to reduce the size of the spec file. Basically, instead of %changelog followed by all the entries, it'd be %include %{SOURCE1}, which is a file 'fedora-kernel-changelog', which carries all the usual changelog entries. Its reasonably trivial to implement, though my current hack-around for 'make clog' complains about me redefining the clog target. Is shaving 800+ lines out of the spec file (only to put them in another file) worth the hassle though? -- Jarod Wilson jarod(a)redhat.com

5 8

KGDB kernel panic no init found in linux 2.6.26 after booting KGDB enabled
by amruth 14 Aug '08

14 Aug '08

Hi > All > I am configuring linux 2.6.26 kernel in laptop and > transferring image to desktop. > My desktop is IDE drive. I am getting kernel panic try > init= option error after booting the kernel. > I am trying to setup KGDB on linux 2.6.26 kernel between > dev machine and test machine. I have issues and it is not > working. > I can get the kgdb to communicate but I cannot start init > images to start. I am using Redhat grub configuration. > Do we need apply any patch for 2.6.26 kernel. I am using > 2.4.15.5-kgdb patch. I can get communication to work after > applying patches. > The system gets into kernel panic after the connection is > made because of corrupted initram image. > Can anybody please give me sample grub entry so that I can > try. > Should we use init-2.6-kgdb.img or not. If yes how to > create it, what about modules in /lib/modules/2.6.../ > Can you please let me know how to fix this issue. > After KGDB is enabled the kernel gets into panic mode > otherwise it works fine.Can anybody please let me know why > KGDB crashes the system. > > Thanks > Amruth p.v > > > > > > > > -- > To unsubscribe from this list: send the line > "unsubscribe linux-usb" in > the body of a message to majordomo(a)vger.kernel.org > More majordomo info at > http://vger.kernel.org/majordomo-info.html

1 0

kernel-doc
by Roland McGrath 13 Aug '08

13 Aug '08

I reenabled kernel-doc and tweaked it up. * Make htmldocs too. Some pithy bits are only in the .tmpl stuff and it is nice to be able to point people at "install kernel-doc and point your browser at file:///...", etc. * make in %build, only install in %install. Pure rpm anality. * Use %{?_smp_mflags}. mandocs is slow enough already. * New macro switch %{doc_build_fail} to suppress barfing on 'make mandocs' failure. We should get real kernel-doc and can eyeball the logs for errors, but won't be breaking our builds on every rebase where upstream tweaked comments so they broke kerneldoc. The switch defaults from %{released_kernel}, so we should break again if kernel-doc would come out bogus in a non-rawhide build. No extra human intervention required. * Install in kernel-doc-%{rpmversion} (.27) subdir, not -%{kversion} (.26). It was obviously insane to have kernel-doc-2.6.27-0.xyz.fc10 that installs /usr/share/doc/kernel-doc-2.6.26/ files. Gabba gabba, Roland

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

kernel August 2008