9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Eric Van Hensbergen <ericvh@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Cc: V9FS Developers <v9fs-developer@lists.sourceforge.net>
Subject: Re: [9fans] mount acme on plan9port
Date: Wed, 27 Jan 2010 11:27:15 -0600	[thread overview]
Message-ID: <a4e6962a1001270927o621650e7j204a1980e1b761eb@mail.gmail.com> (raw)
In-Reply-To: <80c99e791001240955m726daae0w16d5f1ab4454d7ee@mail.gmail.com>

Thanks for generating the debug trace, that's a wacky place for a
problem, fidcreate should just be allocating resources.  I'll try and
reproduce and add it to the bug list.  There were some latent boofhead
bugs in the option parsing code -- its possible that there's one in
the trans_fd option parsing that is overflowing a buffer and
corrupting memory.

Thanks Again,

      -eric


On Sun, Jan 24, 2010 at 11:55 AM, Lorenzo Bolla <lbolla@gmail.com> wrote:
>
>
> On Sun, Jan 24, 2010 at 4:54 PM, Eric Van Hensbergen <ericvh@gmail.com>
> wrote:
>>
>> On Sun, Jan 24, 2010 at 7:02 AM, Lorenzo Bolla <lbolla@gmail.com> wrote:
>> > I'm trying to use "9 mount" to mount acme's socket (in `namespace`/acme)
>> > to
>> > some directory in /mnt (let's say /mnt/acme). I'm using ArchLInux:
>> > $> uname -a
>> > Linux eee 2.6.32-ARCH #1 SMP PREEMPT Sat Dec 26 08:26:17 UTC 2009 i686
>> > Intel(R) Atom(TM) CPU N280 @ 1.66GHz GenuineIntel GNU/Linux
>> > The simple command:
>> > mount -t 9p -o unix,trans=unix,name=lollo,uname=lollo,noextend,nodev
>> > /tmp/ns.lollo.:0/acme /home/lollo/acme
>> > and I've traced down the offending option to be "trans=unix".
>> > Any suggestions?
>>
>> you shouldn't need -o unix,trans=unix -- just trans=unix.
>> Double check the 9pnet module is installed as well as the 9p module
>> (it should be automagically in the kernel version you are running).
>> Also, a good tip when trying to figure out whats going south when v9fs
>> is involved is to add debug=0xffff into your mount options and post
>> the respective sections of your /var/log/messages.
>>
>> Just tried it on 2.6.33-rc4 and it mounted fine
>> mount -t 9p /tmp/ns.root.localhost:10/acme /mnt -o trans=unix,uname=root
>>
>>       -eric
>>
>
> Thanks for the answer Eric.
> 9pnet is loaded, as well as 9p.
> I've tried to mount both as a user (with sudo) and as root, with no luck.
> Here is the messages I get, with debug=0xffff enabled.
>
> Jan 24 17:51:19 eee kernel: *pde = 00000000
> Jan 24 17:51:19 eee kernel: Modules linked in: 9p 9pnet fscache usbhid hid
> ipv6 ntfs arc4 ecb ath9k snd_seq_dummy mac80211 i915 snd_seq_oss ath
> uvcvideo snd_seq_midi_event drm_kms_helper videodev joydev
> snd_hda_codec_realtek snd_seq cfg80211 v4l1_compat eeepc_laptop drm
> snd_seq_device snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss iTCO_wdt
> rfkill fan psmouse iTCO_vendor_support i2c_algo_bit snd_mixer_oss snd_pcm
> intel_agp uhci_hcd snd_timer ehci_hcd led_class pci_hotplug ac serio_raw
> pcspkr i2c_core sg atl1e thermal agpgart processor battery snd usbcore video
> output soundcore button snd_page_alloc evdev rtc_cmos rtc_core rtc_lib ext3
> jbd mbcache sd_mod ata_piix ata_generic pata_acpi libata scsi_mod
> Jan 24 17:51:19 eee kernel:
> Jan 24 17:51:19 eee kernel: Pid: 22660, comm: mount Tainted: G      D
>  (2.6.32-ARCH #1) 1000HE
> Jan 24 17:51:19 eee kernel: EIP: 0060:[<f81144ff>] EFLAGS: 00010246 CPU: 1
> Jan 24 17:51:19 eee kernel: EIP is at p9_fid_create+0x6f/0x140 [9pnet]
> Jan 24 17:51:19 eee kernel: EAX: 00000001 EBX: f5a247c0 ECX: 00000000 EDX:
> 00000202
> Jan 24 17:51:19 eee kernel: ESI: f627d800 EDI: f5a247dc EBP: f6673000 ESP:
> e123fe24
> Jan 24 17:51:19 eee kernel: DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
> Jan 24 17:51:19 eee kernel: f64c0fb8 00000000 00002000 f5a24540 00000000
> f627d800 f6673000 f81155fe
> Jan 24 17:51:19 eee kernel: <0> f8115b82 00000023 00000286 e8083f00 00000000
> f5a244c6 f5a244ca f64c0fbe
> Jan 24 17:51:19 eee kernel: <0> f64c0fb8 c1174cf8 e123feb8 00000000 00000000
> f5a24540 f59a9000 00000000
> Jan 24 17:51:19 eee kernel: [<f81155fe>] ? p9_client_attach+0x1e/0x110
> [9pnet]
> Jan 24 17:51:19 eee kernel: [<f8115b82>] ? p9_client_create+0xe2/0x2a0
> [9pnet]
> Jan 24 17:51:19 eee kernel: [<c1174cf8>] ? match_number+0x88/0xa0
> Jan 24 17:51:19 eee kernel: [<f819b044>] ? v9fs_session_init+0x124/0x3d0
> [9p]
> Jan 24 17:51:19 eee kernel: [<f819909f>] ? v9fs_get_sb+0x4f/0x250 [9p]
> Jan 24 17:51:19 eee kernel: [<c10e12d9>] ? vfs_kern_mount+0x69/0x170
> Jan 24 17:51:19 eee kernel: [<c10f4f72>] ? get_fs_type+0x32/0xb0
> Jan 24 17:51:19 eee kernel: [<c10e143f>] ? do_kern_mount+0x3f/0xe0
> Jan 24 17:51:19 eee kernel: [<c10f7ae0>] ? do_mount+0x1f0/0x730
> Jan 24 17:51:19 eee kernel: [<c10f5f40>] ? copy_mount_options+0xd0/0x140
> Jan 24 17:51:19 eee kernel: [<c10f808e>] ? sys_mount+0x6e/0xa0
> Jan 24 17:51:19 eee kernel: [<c10039f3>] ? sysenter_do_call+0x12/0x28
> Jan 24 17:51:19 eee kernel: ---[ end trace 3fd7199bdae8deac ]---
>
> Thanks again for you help!
> Lorenzo.
>
>
>



      parent reply	other threads:[~2010-01-27 17:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-24 13:02 Lorenzo Bolla
2010-01-24 16:54 ` Eric Van Hensbergen
2010-01-24 17:55   ` Lorenzo Bolla
2010-01-24 19:27     ` Russ Cox
2010-01-24 20:09       ` David Leimbach
2010-01-24 21:51         ` Russ Cox
2010-01-27 11:44           ` Ethan Grammatikidis
2010-01-27 13:23             ` Lorenzo Bolla
2010-01-27 13:40               ` roger peppe
2010-01-27 14:12                 ` erik quanstrom
2010-01-27 14:35                   ` roger peppe
2010-01-27 21:20                     ` erik quanstrom
2010-01-27 21:35                       ` Eric Van Hensbergen
2010-01-27 21:49                         ` ron minnich
2010-01-27 22:47                           ` Charles Forsyth
2010-01-28  6:24                       ` Russ Cox
2010-01-28 10:43                         ` roger peppe
2010-01-27 17:27     ` Eric Van Hensbergen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a4e6962a1001270927o621650e7j204a1980e1b761eb@mail.gmail.com \
    --to=ericvh@gmail.com \
    --cc=9fans@9fans.net \
    --cc=v9fs-developer@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).