All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Cambrant <tim@cambrant.com>
To: Jesper Juhl <juhl-lkml@dif.dk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Suspected bug in fs/ufs/inode.c - test for < 0 on unsigned sector_t - [2.6.1-rc1-mm1]
Date: Sun, 4 Jan 2004 13:57:14 +0100	[thread overview]
Message-ID: <20040104125714.GA24157@cambrant.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0401032326050.4664@jju_lnx.backbone.dif.dk>

[-- Attachment #1: Type: text/plain, Size: 627 bytes --]

On Sat, Jan 03, 2004 at 11:45:56PM +0100, Jesper Juhl wrote:
> 
> Is this analysis correct?  If it is, can the code simply be removed?

It does seem odd, but indeed, a confirmation from someone with authority
would be nice before digging in to a cleanup-process like this. Try e-mailing
the maintainer of the code directly, since it doesn't seem like anyone
feels like wasting any time on this :)

Nice job on the discovery though, if this is true, these things really should
be removed.

-- 
Tim Cambrant <tim@cambrant.com> 
GPG KeyID 0x59518702
Fingerprint: 14FE 03AE C2D1 072A 87D0  BC4D FA9E 02D8 5951 8702

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2004-01-04 12:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-03 22:45 Suspected bug in fs/ufs/inode.c - test for < 0 on unsigned sector_t - [2.6.1-rc1-mm1] Jesper Juhl
2004-01-04  3:04 ` Suspected bug in fs/ufs/inode.c and other filesystems " Jesper Juhl
2004-01-04 12:57 ` Tim Cambrant [this message]
2004-01-04 22:14   ` Suspected bug in fs/ufs/inode.c - test for < 0 on unsigned se ctor_t " Jesper Juhl

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=20040104125714.GA24157@cambrant.com \
    --to=tim@cambrant.com \
    --cc=juhl-lkml@dif.dk \
    --cc=linux-kernel@vger.kernel.org \
    /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.