lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAP9B-Qm7fD90C6FQxBzbfht_pM-GpNcaXfrtY=sQV3XdvqNchQ@mail.gmail.com>
Date:	Mon, 14 Jan 2013 19:33:00 +0800
From:	shilong wang <wangshilong1991@...il.com>
To:	"Theodore Ts'o" <tytso@....edu>
Cc:	linux-ext4@...r.kernel.org, Greg KH <gregkh@...uxfoundation.org>
Subject: Re: [PATCH 2/2] Ext3: return ENOMEM rather than EIO if sb_getblk fails

Hi,

2013/1/14 Theodore Ts'o <tytso@....edu>:
> On Mon, Jan 14, 2013 at 12:10:51PM +0800, Wang wrote:
>> I am sorry, i am a newbie....
>> I make it confused what it  means if
>> i bcc stable@...r.kernel.org......
>
> Yeah, don't do that.  (1) Bcc's are bad since they're not visible, so
> others can't comment on whether it's appropriate for a patch to be
> marked as going into stable, and (2) what's important is that the
> commit is tagged as going into the stable in the commit description,
> so when the commit hits Linus's git tree, the scripts run by the
> stable kernel maintainers will automatically take those commits and
> start processing them for backporting into the stable git trees.
>
> You can tag a patch with Cc: stable@...r.kernel.org, i.e:
>
>     Signed-off-by: Eryu Guan <guaneryu@...il.com>
>     Signed-off-by: "Theodore Ts'o" <tytso@....edu>
>     Cc: stable@...r.kernel.org
>
> Generally the maintainer (i.e., me for ext4, Jan Kara for ext3) will
> take care of adding the stable@...r.kernel.org if we think it's
> appropriate.  Feel free to add such an annotation as a suggestion to
> us, but we may end up adding or removing such a tag, just as I often
> will end up clarifying the commit description (either for English
> grammar/readability, or to make it clearer for people deciding whether
> they should backport the patch into distro kernels, etc.)
>
 I get it ,thanks very much for your help!

> Cheers.
>
>                                                 - Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ