From: Rolf Fokkens <rolf-6w2rdlBuEQTpMFipWq+H6g@public.gmane.org>
To: Kent Overstreet <kmo-PEzghdH756F8UrSeD/g0lQ@public.gmane.org>
Cc: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: bcache-tools: minor change for bcache-register
Date: Tue, 27 Aug 2013 08:58:51 +0200 [thread overview]
Message-ID: <521C4E2B.8090008@rolffokkens.nl> (raw)
In-Reply-To: <20130826214155.GA2798@kmo-pixel>
Would you consider another change as well:
--- bcache-tools-20130827.orig/bcache-register 2013-08-26
23:46:19.000000000 +0200
+++ bcache-tools-20130827/bcache-register 2013-08-27
08:55:48.060477014 +0200
@@ -1,4 +1,4 @@
#!/bin/sh
-modprobe -qba bcache
+/sbin/modprobe -qba bcache
test -f /sys/fs/bcache/register_quiet && echo "$1" >
/sys/fs/bcache/register_quiet
/sbin is not in the $PATH for utilities started from udev. For Fedora it
isn't anyway, but it won't harm other distro's neither.
On 08/26/2013 11:41 PM, Kent Overstreet wrote:
> On Mon, Aug 26, 2013 at 11:14:06AM +0200, Rolf Fokkens wrote:
>> Hi!
>>
>> bcache-register is called from the provided udev rules in
>> bcache-tools. During boot it seams like some devices are registered
>> multiple times, which results in messages during boot. To suppress
>> these messages I redirect them to /dev/null in the following patch:
>>
>> --- bcache-tools-20130820/bcache-register.register 2013-08-20
>> 22:03:46.000000000 +0200
>> +++ bcache-tools-20130820/bcache-register 2013-08-25
>> 21:31:11.707823194 +0200
>> @@ -1,4 +1,9 @@
>> #!/bin/sh
>> -modprobe -qba bcache
>> -test -f /sys/fs/bcache/register && echo "$1" > /sys/fs/bcache/register
>> +#
>> +# Utility script to be called from udev, so it's not monkey proof
>> at all. It's
>> +# sole purpose is to load the bcache kernel module whenever a
>> bcache device is
>> +# detected.
>> +#
>> +/usr/sbin/modprobe -qba bcache
>> +test -f /sys/fs/bcache/register && echo "$1" >
>> /sys/fs/bcache/register 2>/dev/null
>>
>> I can imagine there's a more elegant solution, suggestions are welcome.
> Just use /sys/fs/bcache/register_quiet instead of register.
>
> I'll change it to do that.
next prev parent reply other threads:[~2013-08-27 6:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 9:14 bcache-tools: minor change for bcache-register Rolf Fokkens
[not found] ` <521B1C5E.2090007-6w2rdlBuEQTpMFipWq+H6g@public.gmane.org>
2013-08-26 16:17 ` Darrick J. Wong
2013-08-26 16:31 ` Gabriel de Perthuis
2013-08-26 16:54 ` [PATCH] bcache: Downgrade "device already registered" to pr_debug Gabriel de Perthuis
2013-08-26 21:48 ` bcache-tools: minor change for bcache-register Kent Overstreet
2013-08-26 22:16 ` Gabriel de Perthuis
[not found] ` <521BD3C0.9070209-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-08-26 22:31 ` [PATCH] bcache: register_quiet should still report errors Gabriel de Perthuis
[not found] ` <1377556306-29938-1-git-send-email-g2p.code-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-08-26 22:37 ` Gabriel de Perthuis
2013-08-26 21:41 ` bcache-tools: minor change for bcache-register Kent Overstreet
2013-08-27 6:58 ` Rolf Fokkens [this message]
[not found] ` <521C4E2B.8090008-6w2rdlBuEQTpMFipWq+H6g@public.gmane.org>
2013-08-27 10:00 ` Alex Pyrgiotis
2013-08-27 11:45 ` Gabriel de Perthuis
2013-08-27 12:02 ` Rolf Fokkens
[not found] ` <521C9560.2020603-6w2rdlBuEQTpMFipWq+H6g@public.gmane.org>
2013-08-27 12:11 ` Gabriel de Perthuis
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=521C4E2B.8090008@rolffokkens.nl \
--to=rolf-6w2rdlbueqtpmfipwq+h6g@public.gmane.org \
--cc=kmo-PEzghdH756F8UrSeD/g0lQ@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.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