From: "Alexandre Lymberopoulos" <lymber@gmail.com>
To: "Theodore Tso" <tytso@mit.edu>,
"Rogério Brito" <rbrito@ime.usp.br>,
"Alexandre Lymberopoulos" <lymber@gmail.com>,
502583@bugs.debian.org, 502583-submitter@bugs.debian.org,
linux-kernel@vger.kernel.org
Subject: Re: Bug#502583: scary messages in dmesg
Date: Tue, 21 Oct 2008 18:21:58 -0300 [thread overview]
Message-ID: <2bfaaf400810211421i100d10fexbea8f74d86d813de@mail.gmail.com> (raw)
In-Reply-To: <20081021123348.GB15685@mit.edu>
On Tue, Oct 21, 2008 at 9:33 AM, Theodore Tso <tytso@mit.edu> wrote:
> A patch to suppress the WARN information will be in 2.6.28 when the
> user does something stupid (i.e., yank out a USB stick without
> unmounting the filesystem first). This was done mainly to suppress
> the "scary message" in dmesg, which on distributions that support
> uploading such messages to http://www.kerneloops.org for analysis, was
> cluttering the reports.
I don't think removing these messages is a good idea. It's good even
for non-developer users to have information about what is happening on
their systems. At least to know that they (me in that case) did
something stupid.
> However, the patch does not make it any *safer* to uncerimoniously
> yank out a USB stick without unmounting it first. This can still lead
> to data loss, unless you're *sure* that no process is writing to the
> stick and you issued the sync command, and you know enough time has
> passed so all of the data has been written to the USB stick.
Another reason to keep these messages. To hide information without
provinding a solution (I can see none here, i´'s impossible to prevent
anyone from doing stupid things) is not a good idea, sounds like the
philosophy of other operating systems...
> If you see "lost page write due to I/O error", then you will have lost
> data due to premature removal of the USB stick, and fundamentally
> *that* bug exists between the keyboard and the chair.
;-)
> Regards,
>
> - Ted
Sincerley, Alexandre
--
===============================================================================
Alexandre Lymberopoulos - lymber@gmail.com
===============================================================================
next prev parent reply other threads:[~2008-10-21 21:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2bfaaf400810172145g4aba4827l87a19e67b9742815@mail.gmail.com>
2008-10-18 6:04 ` Rogério Brito
2008-10-20 23:54 ` Alexandre Lymberopoulos
2008-10-21 10:15 ` Rogério Brito
2008-10-21 12:33 ` Theodore Tso
2008-10-21 14:35 ` Rogério Brito
2008-10-21 15:31 ` Theodore Tso
2008-10-21 15:43 ` Jon Smirl
2008-10-21 21:21 ` Alexandre Lymberopoulos [this message]
2008-10-21 20:55 ` Alexandre Lymberopoulos
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=2bfaaf400810211421i100d10fexbea8f74d86d813de@mail.gmail.com \
--to=lymber@gmail.com \
--cc=502583-submitter@bugs.debian.org \
--cc=502583@bugs.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rbrito@ime.usp.br \
--cc=tytso@mit.edu \
/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
all inboxes | Powered by JetHome®