All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Schmidt <berni@birkenwald.de>
To: Jeff Layton <jlayton@redhat.com>
Cc: linux-cifs-client@lists.samba.org, linux-kernel@vger.kernel.org,
	stefan.bader@canonical.com, Suresh Jayaraman <sjayaraman@suse.de>,
	Shirish Pargaonkar <shirishpargaonkar@gmail.com>,
	Steve French <smfrench@gmail.com>
Subject: Re: [linux-cifs-client] BUG: Possible cifs+IPv6-Regression 2.6.27.4 -> 2.6.27.9
Date: Thu, 22 Jan 2009 18:02:57 +0100	[thread overview]
Message-ID: <4978A6C1.5000003@birkenwald.de> (raw)
In-Reply-To: <20090122094517.42e724e4@barsoom.rdu.redhat.com>

Hello Jeff,

> I think I may see the bug...
> 
> I think the "addr" struct in cifs_mount is too small for ipv6 addresses.
> Here's a proposed patch for 2.6.27.y. Could you apply it and let me
> know if it fixes the bug?

Sorry, I was out of town, I'll build a kernel asap.

Stefan confirmed the bug (on i386 platform, apparently x86_64 did not 
expose the broken behaviour) and the bug fixed at Ubuntu with your 
patch. See https://bugs.launchpad.net/bugs/318565 . So I assume he 
tested it and it fixed the problem, but I'll test as well myself.

Thanks!
Bernhard

  reply	other threads:[~2009-01-22 17:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-18 22:13 BUG: Possible cifs+IPv6-Regression 2.6.27.4 -> 2.6.27.9 Bernhard Schmidt
2009-01-19  2:03 ` [linux-cifs-client] " Jeff Layton
2009-01-19 10:32   ` Bernhard Schmidt
2009-01-19 21:07     ` Jeff Layton
2009-01-19 21:38       ` Bernhard Schmidt
2009-01-20 12:25         ` Jeff Layton
2009-01-20 18:50           ` Jeff Layton
2009-01-22 13:41         ` Jeff Layton
2009-01-22 14:45         ` Jeff Layton
2009-01-22 17:02           ` Bernhard Schmidt [this message]
2009-01-23  0:00           ` Steve French
2009-01-23  1:49           ` Bernhard Schmidt

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=4978A6C1.5000003@birkenwald.de \
    --to=berni@birkenwald.de \
    --cc=jlayton@redhat.com \
    --cc=linux-cifs-client@lists.samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shirishpargaonkar@gmail.com \
    --cc=sjayaraman@suse.de \
    --cc=smfrench@gmail.com \
    --cc=stefan.bader@canonical.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.