From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
To: Jan Kara <jack@suse.cz>
Cc: "Karpov Denis.2 (EXT-Teleca/Helsinki)"
<ext-denis.2.karpov@nokia.com>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"hirofumi@mail.parknet.co.jp" <hirofumi@mail.parknet.co.jp>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Hunter Adrian (Nokia-D/Helsinki)" <adrian.hunter@nokia.com>
Subject: Re: [PATCH 0/4] FS: userspace notification of errors
Date: Thu, 04 Jun 2009 09:10:59 +0300 [thread overview]
Message-ID: <4A276573.5000900@nokia.com> (raw)
In-Reply-To: <20090603223005.GA9050@atrey.karlin.mff.cuni.cz>
ext Jan Kara wrote:
> Hi,
>
>> 2. Make FAT and EXT2 file systems use the above mechanism to optionally
>> notify user space about errors. Implemented as 'notify' mount option
>> (PATCH 3,4).
>> FAT error reporting facilities had to be re-factored (PATCH 2) in
>> order to simplify sending error notifications.
> One question: Why would not a filesystem / admin want the notification
> to be sent? Or in other words what's the point of the mount option?
I agree on this. I guess we should instead implement a VFS helper
like 'send_error_notification(sb, error_type)'. Then we can teach
certain FSes to utilize it. We are particularly interested in FAT,
actually.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-06-04 6:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 15:05 [PATCH 0/4] FS: userspace notification of errors Denis Karpov
2009-06-03 15:05 ` [PATCH 1/4] FS: filesystem corruption notification Denis Karpov
2009-06-03 15:05 ` [PATCH 2/4] FAT: generalize errors and warning printing Denis Karpov
2009-06-03 15:05 ` [PATCH 3/4] FAT: add 'notify' mount option Denis Karpov
2009-06-03 15:05 ` [PATCH 4/4] EXT2: " Denis Karpov
2009-06-03 19:00 ` Andrew Morton
2009-06-10 21:03 ` Pavel Machek
2009-06-03 18:59 ` [PATCH 3/4] FAT: " Andrew Morton
2009-06-03 18:58 ` [PATCH 1/4] FS: filesystem corruption notification Andrew Morton
2009-06-03 15:36 ` [PATCH 0/4] FS: userspace notification of errors Eric Sandeen
2009-06-03 18:56 ` Andrew Morton
2009-06-04 1:59 ` Jamie Lokier
2009-06-04 5:57 ` Artem Bityutskiy
2009-06-04 14:27 ` Denis Karpov
2009-06-10 21:05 ` Pavel Machek
2009-06-04 12:53 ` Kay Sievers
2009-06-04 14:29 ` Russell Cattelan
2009-06-05 7:25 ` Jon Masters
2009-06-05 11:07 ` Artem Bityutskiy
2009-06-05 11:51 ` Denis Karpov
2009-06-05 13:06 ` Kay Sievers
[not found] ` <ac3eb2510906050606u7527654dv789364549b36f3e7@mail.gmail.com>
2009-06-09 13:49 ` Jan Kara
2009-06-03 22:30 ` Jan Kara
2009-06-04 6:10 ` Artem Bityutskiy [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=4A276573.5000900@nokia.com \
--to=artem.bityutskiy@nokia.com \
--cc=adrian.hunter@nokia.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=ext-denis.2.karpov@nokia.com \
--cc=hirofumi@mail.parknet.co.jp \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).