From: Mike Fedyk <mfedyk@matchmail.com>
To: Oleg Drokin <green@linuxhacker.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Suspected bug infilesystems (UFS,ADFS,BEFS,BFS,ReiserFS) related to sector_t being unsigned, advice requested
Date: Tue, 6 Jan 2004 14:25:25 -0800 [thread overview]
Message-ID: <20040106222525.GF1882@matchmail.com> (raw)
In-Reply-To: <200401062135.i06LZAOY005429@car.linuxhacker.ru>
On Tue, Jan 06, 2004 at 11:35:10PM +0200, Oleg Drokin wrote:
> Hello!
>
> Mike Fedyk <mfedyk@matchmail.com> wrote:
> MF> Did you check the locking after this is removed?
>
> Locking should be fine.
> As I remember, we take this lock near reiserfs_get_block() entrance,
> and then drop it on exit.
>
Ok, I just wondered if the sector_t merge overlooked this part, maybe it
also changed the locking in this area because of that.
> MF> Maybe after the sector_t merges, this code covered a case that is left open
> MF> now...
>
> This code was never executing anyway.
Right.
Thanks,
Mike
next prev parent reply other threads:[~2004-01-06 22:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 23:20 Suspected bug infilesystems (UFS,ADFS,BEFS,BFS,ReiserFS) related to sector_t being unsigned, advice requested Jesper Juhl
2004-01-06 8:51 ` Hans Reiser
2004-01-06 11:28 ` Jesper Juhl
2004-01-06 17:46 ` Mike Fedyk
2004-01-06 21:35 ` Oleg Drokin
2004-01-06 22:25 ` Mike Fedyk [this message]
2004-01-06 23:37 ` Hans Reiser
2004-01-06 23:53 ` Oleg Drokin
2004-01-07 9:26 ` Hans Reiser
2004-01-07 10:01 ` Oleg Drokin
2004-01-07 11:00 ` Hans Reiser
2004-01-07 12:08 ` Oleg Drokin
2004-01-07 12:17 ` Jesper Juhl
2004-01-07 12:27 ` Oleg Drokin
2004-01-07 17:45 ` Mike Fedyk
2004-01-13 16:26 ` Adrian Bunk
2004-01-06 22:43 ` Jesper Juhl
2004-01-06 22:58 ` Mike Fedyk
2004-01-06 23:26 ` Hans Reiser
2004-01-07 0:46 ` 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=20040106222525.GF1882@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=green@linuxhacker.ru \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox