mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Kenneth R. Crudup" <kenny@panix.com>
To: Kirill Smelkov <kirr@nexedi.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Commit 0be0ee71 ("fs: properly and reliably lock f_pos in fdget_pos()") breaking userspace
Date: Tue, 26 Nov 2019 04:46:39 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1911260445170.6292@hp-x360n> (raw)
In-Reply-To: <20191126100010.GA15941@deco.navytux.spb.ru>


On Tue, 26 Nov 2019, Kirill Smelkov wrote:

> P.S. even though I was put into cc there, somehow I did not received any
> notification email for commits d8e464ecc17b (vfs: mark pipes and sockets as
> stream-like file descriptors) and 0be0ee71816b (vfs: properly and
> reliably lock f_pos in fdget_pos()).

That's my fault; the CC: list for those commits was pretty long and I was
worried about it appearing like SPAMming anyone who'd signed off on it, so
I'd punted and sent it to Linus and the LKML only.

	-Kenny

-- 
Kenneth R. Crudup  Sr. SW Engineer, Scott County Consulting, Silicon Valley

  reply	other threads:[~2019-11-26 12:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-25 21:30 Kenneth R. Crudup
2019-11-25 22:55 ` Linus Torvalds
2019-11-26  1:58   ` Linus Torvalds
2019-11-26  2:03     ` Kenneth R. Crudup
2019-11-26  3:21     ` Linus Torvalds
2019-11-26  3:34       ` Linus Torvalds
2019-11-26  3:39       ` Linus Torvalds
2019-11-26 10:00         ` Kirill Smelkov
2019-11-26 12:46           ` Kenneth R. Crudup [this message]
2019-11-27  8:12             ` Kirill Smelkov
2019-11-26 20:03         ` Linus Torvalds

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=alpine.DEB.2.21.1911260445170.6292@hp-x360n \
    --to=kenny@panix.com \
    --cc=kirr@nexedi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®